ENH: Add write_transform to store cache in GDAL location #141
Conversation
This file contains 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
jgruca
reviewed
Jun 23, 2020
|
Appveyor failure seems to be unrelated. I am guessing to an update in scipy. |
jgruca
approved these changes
Jun 24, 2020
|
Windows has scipy 1.5 & linux/osx has 1.4 |
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.
Closes Store transform where GDAL will find it #129
Closes Store transform #139
Tests added
Fully documented, including
docs/history.rstfor all changes anddocs/rioxarray.rstfor new APINoticed that the
sel()operation returned an array that way sharing the coordinates of the parent for some reason ... so addedcopy()inslice_xy().Noticed some test were using fixture instead of parametrize & weren't being run