-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of GeometryCollection #389
Comments
Getting rid of GeometryCollection as an allowed geometry type simplifies things for backend implementors, so that's good. Related: Open-EO/openeo-python-driver#71 (in VITO backend we handle a GeometryCollection as a feature collection, and we want to get rid of that inconsistency) |
PR #395 proposes to remove GeometryCollection. It has been deprecated in 1.1.0 and as such is a good candidate for removal in 2.0.0. |
We are working towards v2 of the processes for vector cubes. I think this is a good chance to disallow and remove the already "not recommended" GeometryCollection from the processes.
Thoughts?
The text was updated successfully, but these errors were encountered: