You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
@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.
The text was updated successfully, but these errors were encountered: