Open-EO / Open-EO/openeo-python-client
no-panic mode for client-side metadata handling/validation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
The openeo python client does (client-side) validation of some things (e.g. when filtering bands, are the specified bands valid?), in the spirit of catching errors as soon as possible (e.g. before submitting a job) to have a quick feedback loop.
However, in practice we have situations where the client sometimes fails too panicky about things that will be handled by the backend anyway. For example: client side detection of bands in STAC resources is not as complete (or different) from back-end side handling.
There should be some escape hatch to disable this kind of validation when necessary
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 the client's metadata validation, particularly band filtering and STAC resource band detection. Determine how validation is currently triggered and define an escape hatch that allows backend handling when needed while preserving the default checks; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100