Closed robbibt closed 3 months ago
Interested in your thoughts @SpacemanPaul @Ariana-B @omad. Would definitely make the product team's lives easier by letting us start using odc-geo
functionality before it's fully/officially integrated in version 1.9.
Given there's an existing .compat
method on the odc-geo
GeoBoxes, I imagine this could be as simple as just calling that method under the hood in dc.load
if a user passes in an odc-geo
GeoBox instead of a datacube-core
one.
Makes sense to me.
Expected behaviour
A user may try to use an
odc.geo
GeoBox to load data fromdatacube-core
. e.g.:Actual behaviour
However, the code above fails with an![image](https://github.com/opendatacube/datacube-core/assets/17680388/0c9e28c2-951b-4329-b2ce-2643684e5559)
AttributeError
:To make it work correctly, the user must add
.compat
to the end of theodc.geo
GeoBox to get out an older-styledatacube
GeoBox, e.g.gbox.compat
:Even though our timeline for
odc-geo
integration isn't expected until version 1.9, it would be very helpful to supportodc-geo
GeoBoxes indc.load
even in version 1.8 to allow users to start writing code that integrates withodc-geo
.This could be as simple as detecting
odc-geo
GeoBoxes and converting them via the.compat
method internally withindatacube-core
.Environment information
datacube --version
are you using?1.8.17