Re: [Geoserver-devel] WPS plugin for geoserver

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Ok, I will try tomorrow to get the FeatureType running for getSchema().
I will just use the GMLComplexTypes and parse the schema of the Output
of the designated process. Then I will implement getFeatureReader().
That will be tricky, because I have to get the right things out of the
queryObj.
Do you think, I have also to implement getFeatureSource?

Theodor

-----Original Message-----
From: Chris Holmes [mailto:ch...@op...]=20
Sent: Thursday, August 31, 2006 9:01 PM
To: Theodor Foerster
Cc: Jonas Johansson; geo...@li...
Subject: Re: [Geoserver-devel] WPS plugin for geoserver

Theodor Foerster wrote:
> Yes, something like this I had in mind. But I am still struggeling=20
> with the idea of featureTypes and the relation with namespaces.
What do you mean by this?  What namespaces are you talking about?  Those
used in GeoServer?  Or is this part of your work?  Namespaces in
GeoServer are very simple, you just define one and you can attach one or
more datastores to them.

Hopefully I
> will come to a solution tomorrow. Our WPS is able to serve all kind of

> data, XML and binary data. Therefore we have designed a pluggable=20
> architecture for dataHandlers and processes. The actual coupling is=20
> done through outside code configuration. The WPS architecture will be=20
> also the topic of my talk at the Foss4G in Lausanne in two weeks.
>=20
> For our scenario, which is into generalization (particularly in=20
> simplification), I need only to have Bbox and width and height, to=20
> calculate the scale parameter (additionally perhaps style).
Ok, this makes sense.  Let me think a bit on the best way to pass that
back.

>=20
> I am just reading the WFSDataStore, seems to be a good source of such=20
> problem solutions...
Could work.  WFS DataStore is still in beta, we're not distributing yet.

  It's not up to par for cascading WFS, but I think it works decently
for just WMS.

Chris

>=20
> Theodor
>=20
>=20
> -----Original Message-----
> From: Chris Holmes [mailto:ch...@op...]
> Sent: Thursday, August 31, 2006 8:31 PM
> To: Jonas Johansson
> Cc: Theodor Foerster; geo...@li...
> Subject: Re: [Geoserver-devel] WPS plugin for geoserver
>=20
> I think the difference is that Theodor is actually more looking to=20
> just use the WMS to portray the results of a WPS call.  So this is=20
> really more in the service chaining realm of things.
>=20
> Theodor, what does your WPS currently output?  GML?
>=20
> Thinking on it a bit, I think your approach is the quickest.  A=20
> datastore for each WPS, and a featureType for each process.  The=20
> problem though is getting the correct parameters passed back.
>=20
> I think the more pure way to do this would be to make a Feature=20
> Portrayal Service that works against a WPS instead of a WFS - and then

> you could pass the parameters in to it.  From a GeoServer perspective=20
> you'd use the WMS module hooks, but create the requests on the fly.
>=20
>  From a hackier, quicker way, you might just clone the WMS module and=20
> let it take additional parameters, and then also pass the scale and=20
> other stuff that's a part of the WMS to your backend.  You'd probably=20
> construct the featureStore on the fly based on your params.  Like the=20
> ideal would probably be a datastore that can create featureTypes based

> on params passed in?
>=20
> Not sure if this is for sure the right way, just throwing some=20
> thoughts out.  And not sure how dynamic you need things.  Obviously=20
> the simpler way out is that one would define a featureType based on=20
> set parameters...
>=20
> Chris
>=20
> Jonas Johansson wrote:
>> Hi Theodor,
>> I recently added WPS 0.4.0 support to the Geoserver 1.3.0 codebase in

>> the same style as the geoserver WMS and WFS modules. Sounds a lot=20
>> different from your DataStore approach, but you are free to take a=20
>> look at my source code if you want. The WPS supports two simple
> processes:
>> one that calculates the perimeter of a geometry, and one that=20
>> performs
>=20
>> an asynchronic or synchronic buffer operation on a geometry.
>>
>> Regards,
>> Jonas
>>
>>
>> On 8/31/06, *Theodor Foerster* <foe...@it...=20
>> <mailto:foe...@it...>> wrote:
>>
>>     Hi,
>>     I just started to extend geoserver (v.1.3.0) for WPS support. The
> idea
>>     is to serve geoprocesses through geoserver, in particular through
> the
>>     WMS (WFS could be a future task). I am writing the WPS extension
> as a
>>     read-only DataStore in geoserver. By now, I can create WPS
> instances in
>>     geoserver as DataStores, but what do I have to do to create
actual
>>     FeatureStores? Or how do I get the processed results out to
> geoserver?
>>     What is the role of the namespaces? How can I pass dynamic
> parameters of
>>     the WMS request to the DataStore?
>>
>>     I will match each WPS-process with a FeatureType. However that s
> perhaps
>>     not the best way, but straight-forward. Additionally I have to
> deal
>>     with
>>     a little time constraint. The stuff has to work until end of next
> week
>>     :)
>>
>>     I am looking forward to any comments concerning some design
> issues, but
>>     also how to solve the above mentioned problems.
>>
>>     Cheers
>>     Theodor
>>
>>     ITC, Enschede
>>     Department of Geo Information Processing PO. Box 6 7500 AA
> Enschede the
>>     Netherlands
>>
>>
> ----------------------------------------------------------------------
> --
> -
>>     Using Tomcat but need to do more? Need to support web services,
>>     security?
>>     Get stuff done quickly with pre-integrated technology to make
your
>>     job easier
>>     Download IBM WebSphere Application Server v.1.0.1 based on Apache
>>     Geronimo
>>
> =
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
1216
> 42
> =
<http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121
> 64
> 2>
>>     _______________________________________________
>>     Geoserver-devel mailing list
>>     Geo...@li...
>>     <mailto:Geo...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> -
>> --
>>
>> ---------------------------------------------------------------------
>> -
>> --- Using Tomcat but need to do more? Need to support web services,=20
>> security?
>> Get stuff done quickly with pre-integrated technology to make your=20
>> job
>=20
>> easier Download IBM WebSphere Application Server v.1.0.1 based on=20
>> Apache Geronimo
>> =
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121
>> 6
>> 42
>>
>> !DSPAM:1003,44f7279a120061362196140!
>>
>>
>> ---------------------------------------------------------------------
>> -
>> --
>>
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>>
>> !DSPAM:1003,44f7279a120061362196140!
>=20
> --
> Chris Holmes
> The Open Planning Project
> http://topp.openplans.org
>=20
> ----------------------------------------------------------------------
> --- Using Tomcat but need to do more? Need to support web services,=20
> security?
> Get stuff done quickly with pre-integrated technology to make your job

> easier Download IBM WebSphere Application Server v.1.0.1 based on=20
> Apache Geronimo
> =
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
1216
> 42 _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>=20
> !DSPAM:1003,44f72d8c123871995013331!
>=20

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org