Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Store transform #139

Closed
davidbrochart opened this issue Jun 20, 2020 · 1 comment · Fixed by #141
Closed

Store transform #139

davidbrochart opened this issue Jun 20, 2020 · 1 comment · Fixed by #141
Labels
proposal Idea for a new feature.

Comments

@davidbrochart
Copy link
Contributor

As described here, information can be lost when doing xarray operations. Similar to the write_crs method, should we have a write_transform method that would ensure the transform gets propagated across operations? It also makes sense because some rioxarray operations, like clip_box, could update the transform.
@davidbrochart davidbrochart added the proposal Idea for a new feature. label Jun 20, 2020
@snowman2
Copy link
Member

It would be good to have it write according to #129

@snowman2 snowman2 mentioned this issue Jun 23, 2020
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
proposal Idea for a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ENH: Add write_transform to store cache in GDAL location corteva/rioxarray
2 participants
@davidbrochart @snowman2