Open jdries opened 8 months ago
load_stac has to use proj:bbox or proj:geometry to determine the exact bounding box in the original CRS.
This then allows us to construct results without pixel shift.
This line takes care of aligning global_extent to the collection metadata, and won't work for load_stac, hence the issue: https://github.com/Open-EO/openeo-python-driver/blob/182ead3c19b8971e420929f71977d0ac9d1eaa26/openeo_driver/ProcessGraphDeserializer.py#L508
Proposed solution: store collection metadata from load_stac in the EvalEnv, making it available everywhere we might need it.
Another clear example: https://discuss.eodc.eu/t/spatial-shift-when-loading-data-from-the-stac-catalogue/738/3
load_stac has to use proj:bbox or proj:geometry to determine the exact bounding box in the original CRS.
This then allows us to construct results without pixel shift.
This line takes care of aligning global_extent to the collection metadata, and won't work for load_stac, hence the issue: https://github.com/Open-EO/openeo-python-driver/blob/182ead3c19b8971e420929f71977d0ac9d1eaa26/openeo_driver/ProcessGraphDeserializer.py#L508
Proposed solution: store collection metadata from load_stac in the EvalEnv, making it available everywhere we might need it.