Open-EO / Open-EO/openeo-python-driver
Deprecate GeometryCollection in favor of FeatureCollection (e.g. DelayedVector)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
see Open-EO/openeo-processes#253:
In VITO backend code we use GeometryCollection as a collection of separate geometries, for which separate aggregations should be calculated for example. In Open-EO/openeo-processes#253 there is discussion to deprecate GeometryCollection usage as much as possible and promote FeatureCollections instead.
In DelayedVector (and other places) we do things the other way around at the moment: when we get a FeatureCollection, we convert it to a GeometryCollection.
Changing this will probably cause some nuisance, e.g. in the interaction between geopyspark driver and in UDFs that depend on this behavior.
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 reading the DelayedVector handling and the interactions with the geopyspark driver and UDFs mentioned in the issue. Review the discussion in Open-EO/openeo-processes#253 to understand the intended FeatureCollection behavior. Done means identifying and updating the affected conversions without breaking separate geometry aggregations or dependent UDF behavior.
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