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.

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

Simplify get_transform(), get_bounds(), get_resolution(), and get_extent() #42

Closed
jnhansen opened this issue Sep 16, 2019 · 0 comments · Fixed by #44
Closed

Simplify get_transform(), get_bounds(), get_resolution(), and get_extent() #42

jnhansen opened this issue Sep 16, 2019 · 0 comments · Fixed by #44
Labels
enhancement New feature or request

Comments

@jnhansen
Copy link
Owner

Is your feature request related to a problem? Please describe.
The following methods are not currently very consistent in what information is used to extract the corresponding parameter:

  • nd.warp.get_transform()
  • nd.warp.get_bounds()
  • nd.warp.get_extent()
  • nd.warp.get_resolution()

Describe the solution you'd like
The most reliable information to determine the transform etc. is probably the coordinate arrays and should be used even if there is relevant metadata present.

The methods may optionally raise a warning if the coordinate arrays don't seem to match the values specified in the metadata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant