apply_polygons has a polygons argument:
|
"name": "polygons", |
|
"description": "A vector data cube containing at least one polygon. The provided vector data can be one of the following:\n\n* A `Polygon` or `MultiPolygon` geometry,\n* a `Feature` with a `Polygon` or `MultiPolygon` geometry, or\n* a `FeatureCollection` containing at least one `Feature` with `Polygon` or `MultiPolygon` geometries.\n* Empty geometries are ignored.", |
This is not in line with comparable processes that use geometries for the same concept, like aggregate_spatial, filter_spatial, filter_vector, vector_buffer. Note that mask_polygon also doesn't use polygons.
It also appears to be confusing users about how MultiPolygons are supported
apply_polygonshas apolygonsargument:openeo-processes/proposals/apply_polygon.json
Lines 19 to 20 in 965bbae
This is not in line with comparable processes that use
geometriesfor the same concept, likeaggregate_spatial,filter_spatial,filter_vector,vector_buffer. Note thatmask_polygonalso doesn't usepolygons.It also appears to be confusing users about how MultiPolygons are supported