Open jdries opened 4 years ago
As soon as you have a process definition I'd suggest to open a draft PR so that we can shape it together.
Some inspiration for naming:
Can we model this as reducer in openEO? If not, reduce would be a bit confusing, I think. polygonize only works if it's always working on polygons only. I think I'd prefer something easy to understand and aligned with other processes such as create_raster_cube
like vector_cube
, to_vector
or convert_cube
(if it also allows vector to raster at some point). I'm not set on anything yet. Question is also how we'd like to name vector to raster once it comes up?
Implemented a first prototype: https://openeo.vito.be/openeo/1.0/processes/backend/raster_to_vector
@jdries We should complete the description and PR it for discussion.
@jdries and @m-mohr, is this being worked on?
VITO has a custom implementation, but we still need to get a version into openeo-processes. @PondiB
Cool, I will pick it up then.
Cool, please consider a survey of existing implementations, e.g. at VITO (already openEO), GRASSGIS, Python ecosystem (shapely?), R, ... @PondiB
@m-mohr , Sure, I will do that.
For an internal use case, we'd like to apply raster to vector conversion:
This is not uncommon, so we'd like to see if we can provide this as higher level process. We will probably implement something internally first, to see how it can look like.