Update quickstart example raster creation with correct pixel height (not upside down)#3337
Merged
sgillies merged 1 commit intorasterio:mainfrom May 9, 2025
tveness:tv/update-docs-with-conventional-ordering
Merged
Update quickstart example raster creation with correct pixel height (not upside down)#3337sgillies merged 1 commit intorasterio:mainfrom tveness:tv/update-docs-with-conventional-ordering
sgillies merged 1 commit intorasterio:mainfrom
tveness:tv/update-docs-with-conventional-ordering
Conversation
sgillies
approved these changes
May 9, 2025
snowman2
pushed a commit
that referenced
this pull request
Nov 6, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I noticed that the example of creating a raster file in the quickstart documents end up with the creation of a raster with "negative pixel height" ("upside down"). Following the steps in the quickstart docs, and then loading the file shows this in two separate ways: we can examine the bounds directly, and also induce an error by attempting to merge just the single file created:
The changes here modify this to produce the following behaviour: