Open-EO / Open-EO/openeo-python-client
Support unordered band collection in BandDimension
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
In some situations (e.g. load_stac usage with certain STAC resources), the band names of the STAC resource can be extracted, but not their order (because of mappings instead of arrays in the STAC metadata).
Currently, an arbitrary order is enforced client side by blindly casting the bands in BandDimension to be a list, but we should not do that and allow it to be just a unordered set to avoid wrong assumptions
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 by locating BandDimension and the load_stac path in the Python client, then inspect how band names are converted to a list. The change is done when unordered band collections can be preserved without imposing an arbitrary order, including coverage for the STAC metadata case described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100