RE: [Geoserver-devel] Working WPS

GeoServer GeoServer Developer
1

Jonas,

FYI, there is a MapBuilder WPS demo that I did for the WPS IE last summer.
However be warned that it's based on the 0.2.4 version of the spec and many
of the services that I tested against are gone, so it definitely needs an
update, but with a little bit of work, it could be a client interface to
test with.

Try clicking on the "GDAS XML Stream Based Geoprocessing Service (AAFC)"
link in the sidebar at http://geoservices.cgdi.ca/mapbuilder/demo/wpsIE/
(and imagine a map showing up :wink: It will step through getCapabilities,
describeProcess, setting parameters and execute process. The intention with
this interface is that the map can be used as a source of inputs and for
displaying outputs. Combine that with some of the feature selection and
rendering stuff going on in MapBuilder and there is a good start to a WPS
client.

Mike

-----Original Message-----
From: geoserver-devel-admin@lists.sourceforge.net
[mailto:geoserver-devel-admin@lists.sourceforge.net] On
Behalf Of Jonas Johansson
Sent: March 16, 2006 1:34 PM
To: Geoserver-devel
Subject: [Geoserver-devel] Working WPS

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

2

Thanks for the info Mike. I can imagine how that demo worked before.
However, uDig was the first client I got to try out and I kind of fell
for it. I like how it lets you develop plugins and stuff. So I would
like to get this working with the uDig client.

Jonas

On Thu, 2006-03-16 at 13:59 -0500, Adair, Mike wrote:

Jonas,

FYI, there is a MapBuilder WPS demo that I did for the WPS IE last summer.
However be warned that it's based on the 0.2.4 version of the spec and many
of the services that I tested against are gone, so it definitely needs an
update, but with a little bit of work, it could be a client interface to
test with.

Try clicking on the "GDAS XML Stream Based Geoprocessing Service (AAFC)"
link in the sidebar at http://geoservices.cgdi.ca/mapbuilder/demo/wpsIE/
(and imagine a map showing up :wink: It will step through getCapabilities,
describeProcess, setting parameters and execute process. The intention with
this interface is that the map can be used as a source of inputs and for
displaying outputs. Combine that with some of the feature selection and
rendering stuff going on in MapBuilder and there is a good start to a WPS
client.

Mike

> -----Original Message-----
> From: geoserver-devel-admin@lists.sourceforge.net
> [mailto:geoserver-devel-admin@lists.sourceforge.net] On
> Behalf Of Jonas Johansson
> Sent: March 16, 2006 1:34 PM
> To: Geoserver-devel
> Subject: [Geoserver-devel] Working WPS
>
> 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
>

3

Jonas Johansson wrote:

Thanks for the info Mike. I can imagine how that demo worked before.
However, uDig was the first client I got to try out and I kind of fell
for it. I like how it lets you develop plugins and stuff. So I would
like to get this working with the uDig client.
  

I would be happy to help you get set up Jonas, simply ask on the devel list for subversion control access
and we can set you up in the community directory. We package the interesting ones up on an
"update siste", although when you are finished your plug-in works we could include it in the formal
release (after some docs and QA).

Jody

Jonas

On Thu, 2006-03-16 at 13:59 -0500, Adair, Mike wrote:
  

Jonas,

FYI, there is a MapBuilder WPS demo that I did for the WPS IE last summer.
However be warned that it's based on the 0.2.4 version of the spec and many
of the services that I tested against are gone, so it definitely needs an
update, but with a little bit of work, it could be a client interface to
test with.

Try clicking on the "GDAS XML Stream Based Geoprocessing Service (AAFC)"
link in the sidebar at http://geoservices.cgdi.ca/mapbuilder/demo/wpsIE/
(and imagine a map showing up :wink: It will step through getCapabilities,
describeProcess, setting parameters and execute process. The intention with
this interface is that the map can be used as a source of inputs and for
displaying outputs. Combine that with some of the feature selection and
rendering stuff going on in MapBuilder and there is a good start to a WPS
client.

Mike

-----Original Message-----
From: geoserver-devel-admin@lists.sourceforge.net [mailto:geoserver-devel-admin@lists.sourceforge.net] On Behalf Of Jonas Johansson
Sent: March 16, 2006 1:34 PM
To: Geoserver-devel
Subject: [Geoserver-devel] Working WPS

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

-------------------------------------------------------
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