Open-EO / Open-EO/openeo-python-client
UDP parameterization problems with load_collection and filter_bands
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
@tbanyai brought this up in a use case he is working on:
if you try to parameterize the collection_id in load_collection() and/or band names in filter_bands() or band() you get into trouble because the current logic of filter_bands and band assumes there is metadata to normalize old band name aliases.
When collection_id or band names are parameterized, these method should not try to be too helpful with complaining that there is no metadata or that the band name is wrong
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 inspecting load_collection(), filter_bands(), and band(), focusing on how they handle parameterized collection IDs and band names when metadata is unavailable. Confirm the current alias normalization and validation behavior, then ensure parameterized values are accepted without metadata-based complaints while normalizing known aliases when metadata exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100