Open-EO / Open-EO/openeo-python-client
Deprecate (or drop) GeometryCollection support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
triggered from #682: we allow GeometryCollection as GeoJSON type, but that's actually an anti-pattern (e.g. see https://github.com/Open-EO/openeo-processes/issues/389)
We should get rid of that. I'm not sure if we should first deprecate it with warnings, or just drop support without deprecation phase
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 GeometryCollection handling in openeo/rest/datacube.py at the referenced lines 630-632, 1197-1199, 1474-1477, and 2058. Resolve whether support should be deprecated with warnings or removed directly, then update all listed entry points consistently. Done means GeometryCollection is no longer accepted according to the chosen policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100