Open-EO / Open-EO/openeo-python-driver
global_extent: not aligned when mixing cubes with different crs's
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
Example job j-25022615155945a2a14cfbc36d4e5467
Loading mask in UTM and target cube in epsg:3035 causes target cube to have a layoutDefinition that is not nicely aligned with the target extent provided by filter_bbox.
The global extent does not necessarily need to be global across all cubes, it mostly makes sense for cubes that can have a shared layoutdefinition, so share a CRS.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with example job j-25022615155945a2a14cfbc36d4e5467 and trace how global_extent, filter_bbox, layoutDefinition, and CRS are handled when cubes use UTM and EPSG:3035. Compare the resulting alignment for cubes sharing a CRS versus cubes with different CRSs. Done means the target cube remains correctly aligned when these mixed-CRS inputs are processed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100