Open-EO / Open-EO/openeo-python-client
[localprocessing] implement spatial and temporal filter in load_collection
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
The current local load_collection implementation is not doing apply any of the spatial or temporal ranges provided to filter the data. It can be done chaining filter_bbox and filter_temporal later, but we can also use their implementation internally to perform it.
Current implementation here: https://github.com/Open-EO/openeo-python-client/blob/c59fe34d442f919aef18313d1752ea404ead27da/openeo/local/processing.py#L50
@elmaic @pierocampa
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/local/processing.py around load_collection at the linked line. Read the existing filter_bbox and filter_temporal implementations and determine how their spatial and temporal ranges should be applied during local loading. Done means load_collection filters data using the provided ranges.
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
- 42/100