Open-EO / Open-EO/openeo-python-driver
properly evaluate property filters
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
openeo_driver.filter_properties.extract_literal_match does not actually evaluate the callback/predicate process graphs in the properties argument to load_collection/load_stac; rather, it handles the JSON in a more mechanical way so it only works for the simplest of cases.
Evaluating these predicates against properties of features (client-side filtering) seems doable and intuitive but instead we typically translate them to HTTP params (server-side filtering).
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 in openeo_driver/filter_properties.py at extract_literal_match, then trace how properties are handled by load_collection and load_stac. Compare the current mechanical JSON handling with the callback or predicate process graphs described in the issue; done means these predicates are properly evaluated rather than only supporting the simplest cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100