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

CRS management efforts #453

Open
rbavery opened this issue Sep 29, 2021 · 2 comments
Open

CRS management efforts #453

rbavery opened this issue Sep 29, 2021 · 2 comments
Labels
feature request New feature or request Needs Triage Need team to review and classify

Comments

@rbavery
Copy link

rbavery commented Sep 29, 2021

@thomcom
Hello, I'm very new to this library but wanted to offer a suggestion after watching the FOSS 4GPU presentation.

There's some ongoing discussion of the best way to performantly manage CRSs to allow for performant reads of cloud optimized data formats here: gjoseph92/stackstac#50
and here: https://gist.github.com/sharkinsspatial/f1c3a8f871b58416fa30c377178b5f9c

I'm not familiar with all the technical internals, but I get the sense that there is interest (within my company at Development Seed) and among others in those threads to develop a separate library for CRS management that abstracts out the relevant parts of the rioxarray library into a new geoxarray library. It might be something to pay attention to (even contribute to?) so that cuSpatial doesn't reinvent the wheel for CRS management.

@rbavery rbavery added Needs Triage Need team to review and classify feature request New feature or request labels Sep 29, 2021
@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@github-actions
Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request Needs Triage Need team to review and classify
Projects
Status: Todo
Development

No branches or pull requests

2 participants