Hi all,
I’d like to propose a new community module implementing OGC API Processes.
It’s going to follow the usual script, leverage the existing WPS implementation to
support process handling, async execution, output encoding, process security,
internal data access and so on.
2 Likes
+1
+1 
+1
+1
+1
Cheers,
Torben
1 Like
Hi all,
the first round of implementation is complete, not sure if there is going to be any more work on in in the short term.
You can find docs about what can and cannot be done with it here:
https://docs.geoserver.org/latest/en/user/community/ogc-api/processes/index.html
The code also contains a number of TODO for those that might want to improve the codebase (for example, adding configurable conformance classes)
The thing I like the most is the ability to start simple processes via GET requests … this conformance class is called KVP encoded execute and it’s part of the current OGC API Processes 1.1 DRAFT specification… but it’s pretty nice to have. One quick example buffering a point, expressed as WKT, with a distance of 10, and returning the result as GeoJSON:
Cheers
Andrea
1 Like