Daniel Nüst
Daniel Nüst
The WPS currently creates documents using `xlin` as the namespace for XLink, which is totally fine and works, e.g. ``. But for readability by humans, it would be nice to...
WPS4R currently lists all resources and script files as seperate downloads in an `ows:Metadata` - Element. That should be replaced with a single download of an archive containing all the...
Even Java processes could run in their own virtual machine to run the actual process outside of the servlet container (e.g. Tomcat). This might be better suited for large data...
If I have a deployed WPS with potentially long running processes, which I might want to update, then I would like to let the WPS finish already running processes, but...
Some unit tests do not work without an internet connection. Imho these tests should be integration tests. Afaics this is related to parsers and encoders that use schemas from geoprocessing.demo.52north.org...
## Feature The WPS standard allows input values to occure multiple times with the same name (see also [here](http://geoserver.geo-solutions.it/edu/en/wps/wps.html)), e.g. ``` xml [...] levels 1200 levels 1400 levels 1600 [...]...
The WPS 2.0 standards supports nesting of inputs and outputs. Once this is implemented in the WPS internal API, this can be mapped to groups of inputs and outputs in...
Implement an annotation that can be used to provide allowed values for literal inputs, see class `RAttribute`. Possible features: - a collection of strings, e.g. `# wps.in: names, string, allowedValues...
The resource annotation mechanism can be extended to configure a resource to be used "as reference", meaning that it is not copied to the workspace but that it's full path...