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

Should GeoArrays use Extents.Extent instead of Named tuples? #156

Closed
alex-s-gardner opened this issue Feb 22, 2024 · 1 comment · Fixed by #162
Closed

Should GeoArrays use Extents.Extent instead of Named tuples? #156

alex-s-gardner opened this issue Feb 22, 2024 · 1 comment · Fixed by #162

Comments

@alex-s-gardner
Copy link
Contributor

GeoArrays.crop accepts Named tuple for extents. I've converged on using Extents.Extent in all of my workflows and I'm wondering if GeoArrays should as well.
@evetion
Copy link
Owner

evetion commented Jun 8, 2024

Agreed, a breaking relase is coming up!

@evetion evetion mentioned this issue Jun 9, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow for GeoArray to be a Matrix evetion/GeoArrays.jl
2 participants
@evetion @alex-s-gardner