Open-EO / Open-EO/openeo-python-driver
Need for point buffering ?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
While working on #141/ Open-EO/openeo-geopyspark-driver#239 a lot of struggle was related to point handling and (ad-hoc) buffering of these to get a non-empty bbox with enough pixels to work with.
First problem is currently the hardcoded 10m buffering (which assumes Sentinel2 resolution I guess). Can this be made more generic and made dependent on the collection metadata?
But maybe even better is to eliminate the point buffering hacks we now have in various places (in openeo-python-driver, openeo-geopyspark-driver, ...) and move that to the logic that actually loads the pixels (where it is easier to buffer in terms of pixels)?
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 reviewing the point-handling and buffering logic in openeo-python-driver and the related work in openeo-geopyspark-driver#239, with context from issue #141. Trace where the hardcoded 10m buffer is applied and where pixels are loaded. Done requires an agreed approach for collection-dependent or pixel-level buffering, but the issue does not specify which alternative to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100