-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Use rasterio's transform instead of homemade coordinates #1712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
c038897
Fix y-coordinates for non-georeferenced data
fmaussion 10195d1
Add regression test, fix imports
fmaussion 67a88ae
version conundrum
fmaussion 9595a7f
What's new
fmaussion 4a6b03b
Merge branch 'master' into rio-coords
fmaussion 70e85b1
Merge branch 'master' into rio-coords
fmaussion b6eddc0
Add recti block
fmaussion 040ce40
Merge branch 'rio-coords' of github.com:fmaussion/xarray into rio-coords
fmaussion 2f6c286
Add 2d coords
fmaussion 49730e8
Merge branch 'master' into rio-coords
fmaussion 10814d3
Merge branch 'master' into rio-coords
fmaussion 7ab95c8
whatsnew mixup
fmaussion 95016ce
center pixels
fmaussion 2b4fc41
More sensible defaults
fmaussion d49e766
Merge branch 'master' into rio-coords
fmaussion a366304
Some doc
fmaussion 4172e6e
More docs
fmaussion 7e28402
Remove redundant tests
fmaussion 69566f9
Review
fmaussion 21957aa
Merge branch 'master' into rio-coords
fmaussion File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use attribute lookup fallback instead, e.g.,
That's usually slightly more robust than explicitly checking versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
transform
attribute exists on the older version as well, but there it is a tuple specifying the transform in GDAL format. Maybe it'd be better to check whethertransform
is an instance ofAffine
instead?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know... Reading the transform attribute with rio < 1.0 raises a warning, reading the affine attribute with rio >= 1.0 raises a warning, so we'll have to catch the warnings in order to test this. Would that be more elegant?