ReprojectRasterExtent: support single pixel input#3561
Closed
jdries wants to merge 1 commit intolocationtech:masterfrom
Closed
ReprojectRasterExtent: support single pixel input#3561jdries wants to merge 1 commit intolocationtech:masterfrom
jdries wants to merge 1 commit intolocationtech:masterfrom
Conversation
Member
|
Hmmm I wonder if there's smth off with the PR |
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
2 participants
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.
#3559
Overview
When a single pixel RasterExtent was reprojected, it often resulted in a GeoAttrsError.
The main cause is warping of square pixels into rectangular.
In the case where we anyway compute a custom cellsize, it seems valid to return a single pixel extent in X or Y direction rather than trying to construct a 0 pixel gridextens, which fails.
Checklist
docsguides update, if necessaryCloses #3559