I am trying to make a RESTful WPS using ZOO Project. According to the following OGC Papers WPS 2.0 Interface Standard and Web Processing Service for WPS 2.0 and 1.0 respectively, it does seem possible to make a RESTful WPS. There is also WPS 2.0 REST API TAMIS which seems to be a RESTful implementation of WPS.

Is there a way to make a RESTful WPS using ZOO Project? (I did not find anything about this mentioned in their documentation)

  • 1
    Whilst the TAMIS API you reference calls itself RESTful. It seems to rely on application/json. REST requires hypermedia. application/json is not hypermedia, so that API cannot be RESTful. – nmtoken Jun 7 '18 at 5:18

There is no way to make a conforming OGC WPS answer REST requests. The standard only allows for GET with KVP requests and POST of XML documents.

However looking at the TAMIS document you link to you might be able to make use of their "Generic WPS REST Proxy" to convert RESTful interactions to standards based WPS requests. But it is likely to need a specific wrapper (as 52N use) to make it specific for the processes you want to access.

However for a general WPS provider like Zoo (or GeoServer) which can provide access to hundreds of processes and include subprocess calls in the request it is hard to see what REST gains you.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.