-
Notifications
You must be signed in to change notification settings - Fork 33
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
odc-geo repo? #58
Comments
In general I agree Alan. I think moving some of the lower level functionality into a separate library will benefit It will be a significant refactor and will take quite a bit of developer time, so this is not something I can commit to on my own. I will raise this proposal with members of ODC Steering Council. And while I do not expect resistance to this proposal, I do expect that it won't happen quickly, as there are currently some high-priority tasks that won't be finished soon. We can probably justify including this in ODC 2.0 work. On a technical level this will involve moving geometry and xarray related utilities out of pinging some ODC people for visibility: |
In case you are interested, |
Thanks Kirill. |
Work starting here: https://github.com/opendatacube/odc-geo |
Thanks @Kirill888 👍 |
Thoughts on moving geospatial tools to a separate package/repository (maybe odc-geo)?
Maybe combine:
opendatacube-core
geobox functionalityThis would be useful for the geospatial xarray community. For example, the geobox stuff is used in geocube and the dask supported reprojection stuff would be a nice engine to use in rioxarray.
The text was updated successfully, but these errors were encountered: