The goal is to specify a consistent api request/repsonse cycle while keeping enough room for project specific implementation.
- Every property is always returned in the response, even when
null
.
The context is a long running server side calculation. Because of this long running necessity, we can not use the default request/response, but need to handle it asynchronously.
We have 3 api endpoints available to implement this asynchronous result calculation.
{ | |
"$defs": { | |
"FnameSettings": { | |
"properties": { | |
"landuse_CORINE": { | |
"description": "Path to the CORINE land use file", | |
"title": "Landuse Corine", | |
"type": "string" | |
}, | |
"landuse_LCZ": { |