Hi all,
Alright, the WPS is working. One process/calculation is supported right
now: caclulating a buffer on a MultiLineString or some other simple JTS
Geometry. It kind of fulfils the WPS 0.4.0 spec requirements in doing
that, but exceptions are not handled correctly yet, and there are
probably lots of bugs, and I have only tried it locally.
The WPS handles the operations
* GetCapabilities
* DescribeProcess
* Execute
The GetCapabilities operation gives you the usual info plus a brief
description of each process that the WPS serves (currently just one).
The DescribeProcess operation is called supplying one or many
identifiers for processes that was given in the GetCapabilities
response. The DescribeProcess response is a list of detailed
descriptions for each process specified, giving detailed information on
possibly required inputs and generated output:
<ProcessDescriptions>
<ProcessDescription>
<DataInputs>
..
<ProcessOutputs>
...
</ProcessDescription>
<ProcessDescription>
...
</ProcessDescription>
</ProcessDescriptions>
The Execute operation is supplied with the identifier of the process
that should be executed, and the possibly required input and possibly
also definitions of how outputs should be generated.
I have been following the GeoServer style of handling services, so there
has been lots of copy&pasting+editing. The GUI is not updated with WPS.
The implementation is an ugly one right now, adding the
ProcessDescription of the Process in static code. Future plans are to
use GTXML for reading in the ProcessDescription from an XML. The Process
interface is probably not the best one either. But hey, it works =)
But before fine-tuning the WPS I have to get a client working, that uses
the WPS in combination with WMS, to calculate a buffer around road
segments. The plan is to use uDig as a base for that.
Jonas
Congrats, Jonas!!! This is very exciting news.
-Justin
Jonas Johansson wrote:
Hi all,
Alright, the WPS is working. One process/calculation is supported right
now: caclulating a buffer on a MultiLineString or some other simple JTS
Geometry. It kind of fulfils the WPS 0.4.0 spec requirements in doing
that, but exceptions are not handled correctly yet, and there are
probably lots of bugs, and I have only tried it locally.
The WPS handles the operations
* GetCapabilities
* DescribeProcess
* Execute
The GetCapabilities operation gives you the usual info plus a brief
description of each process that the WPS serves (currently just one).
The DescribeProcess operation is called supplying one or many
identifiers for processes that was given in the GetCapabilities
response. The DescribeProcess response is a list of detailed
descriptions for each process specified, giving detailed information on
possibly required inputs and generated output:
<ProcessDescriptions>
<ProcessDescription>
<DataInputs>
..
<ProcessOutputs>
...
</ProcessDescription>
<ProcessDescription>
...
</ProcessDescription>
</ProcessDescriptions>
The Execute operation is supplied with the identifier of the process
that should be executed, and the possibly required input and possibly
also definitions of how outputs should be generated.
I have been following the GeoServer style of handling services, so there
has been lots of copy&pasting+editing. The GUI is not updated with WPS.
The implementation is an ugly one right now, adding the
ProcessDescription of the Process in static code. Future plans are to
use GTXML for reading in the ProcessDescription from an XML. The Process
interface is probably not the best one either. But hey, it works =)
But before fine-tuning the WPS I have to get a client working, that uses
the WPS in combination with WMS, to calculate a buffer around road
segments. The plan is to use uDig as a base for that.
Jonas
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel