[Geoserver-users] WPS Execute GET request KVP syntax

GeoServer GeoServer User
1

Hi,

I am having a bit of a hard time getting a WPS execution to run through a
GET request as the documentation about the geoserver specifics of this is a
bit sparse.

I want to use the gs:Clip function.

So, as a base I need the following parameters:
* service=wps
* version=1.0.0
* request=execute
* identifier=gs:Clip

Now I struggle with the Data inputs. The features to clip come directly from
a Geoserver layer whereas the clipping features are provided in WKT.

For the internal Geoserver feature I am using a standard WFS getFeature
request. Is there an internal pipeline for achieving the same:
*
features=@xlink:http://<my-geoserver-host>/geoserve/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=<myLayer>&maxFeatures=50&outputFormat=application%2Fjson

For the WKT polygon I am a bit clueless. I tried:
* clip=<my-WKT-polygon>@mimeType=application/wkt

What am I missing here?
And what other parameters are required?

Thanks in advance
Max

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/WPS-Execute-GET-request-KVP-syntax-tp5265620.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

You probably need to read the Spec (http://portal.opengeospatial.org/files/?artifact_id=24151) - start around page 38 which covers how to specify and encode your parameters. As for which parameters are needed look at the DescribeProcess response.

Ian

···

On 10 May 2016 at 16:12, xzam <mail@anonymised.com> wrote:

Hi,

I am having a bit of a hard time getting a WPS execution to run through a
GET request as the documentation about the geoserver specifics of this is a
bit sparse.

I want to use the gs:Clip function.

So, as a base I need the following parameters:

  • service=wps
  • version=1.0.0
  • request=execute
  • identifier=gs:Clip

Now I struggle with the Data inputs. The features to clip come directly from
a Geoserver layer whereas the clipping features are provided in WKT.

For the internal Geoserver feature I am using a standard WFS getFeature
request. Is there an internal pipeline for achieving the same:
*
features=@anonymised.com:http:///geoserve/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=&maxFeatures=50&outputFormat=application%2Fjson

For the WKT polygon I am a bit clueless. I tried:

  • clip=@mimeType=application/wkt

What am I missing here?
And what other parameters are required?

Thanks in advance
Max

–
View this message in context: http://osgeo-org.1560.x6.nabble.com/WPS-Execute-GET-request-KVP-syntax-tp5265620.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

Ian Turton

3

any experience?

···

El 10/05/2016 a las 11:31 a. m., Ian Turton escribió:

You probably need to read the Spec (http://portal.opengeospatial.org/files/?artifact_id=24151) - start around page 38 which covers how to specify and encode your parameters. As for which parameters are needed look at the DescribeProcess response.

Ian

On 10 May 2016 at 16:12, xzam <mail@anonymised.com> wrote:

Hi,

I am having a bit of a hard time getting a WPS execution to run through a
GET request as the documentation about the geoserver specifics of this is a
bit sparse.

I want to use the gs:Clip function.

So, as a base I need the following parameters:

  • service=wps
  • version=1.0.0
  • request=execute
  • identifier=gs:Clip

Now I struggle with the Data inputs. The features to clip come directly from
a Geoserver layer whereas the clipping features are provided in WKT.

For the internal Geoserver feature I am using a standard WFS getFeature
request. Is there an internal pipeline for achieving the same:
*
features=@xlink:http:///geoserve/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=&maxFeatures=50&outputFormat=application%2Fjson

For the WKT polygon I am a bit clueless. I tried:

  • clip=@mimeType=application/wkt

What am I missing here?
And what other parameters are required?

Thanks in advance
Max

–
View this message in context: http://osgeo-org.1560.x6.nabble.com/WPS-Execute-GET-request-KVP-syntax-tp5265620.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

Ian Turton

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
[https://ad.doubleclick.net/ddm/clk/304595813;131938128;j](https://ad.doubleclick.net/ddm/clk/304595813;131938128;j)

_______________________________________________
Geoserver-users mailing list
[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)
4

Hi Ian,

thanks for the hint. Had a look at the DescribeProcess response and the WPS spec already but couldn’t really get it working based on that.

The spec says:

Complex := InputId “=” Value *( “@” ComplexAttribute )
ComplexAttribute:= ComplexAttributeName “=” Value
ComplexAttributeName := “mimetype” | “encoding” | “schema"

Based on I assumed the syntax for the second parameter would be:
clip=@mimetype=application/wkt.

But that didn’t work unfortunately.

Cheers,

Max

···

Von: Ian Turton ijturton@anonymised.com
Gesendet: Dienstag, 10. Mai 2016 17:31:47
An: Max Stephan
Cc: geoserver-users
Betreff: Re: [Geoserver-users] WPS Execute GET request KVP syntax

You probably need to read the Spec (http://portal.opengeospatial.org/files/?artifact_id=24151) - start around page 38 which covers how to specify and encode your parameters. As for which parameters are needed look at the DescribeProcess response.

Ian

On 10 May 2016 at 16:12, xzam <mail@anonymised.com> wrote:

Hi,

I am having a bit of a hard time getting a WPS execution to run through a
GET request as the documentation about the geoserver specifics of this is a
bit sparse.

I want to use the gs:Clip function.

So, as a base I need the following parameters:

  • service=wps
  • version=1.0.0
  • request=execute
  • identifier=gs:Clip

Now I struggle with the Data inputs. The features to clip come directly from
a Geoserver layer whereas the clipping features are provided in WKT.

For the internal Geoserver feature I am using a standard WFS getFeature
request. Is there an internal pipeline for achieving the same:
*
features=@anonymised.com:http:///geoserve/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=&maxFeatures=50&outputFormat=application%2Fjson

For the WKT polygon I am a bit clueless. I tried:

  • clip=@mimeType=application/wkt

What am I missing here?
And what other parameters are required?

Thanks in advance
Max

–
View this message in context: http://osgeo-org.1560.x6.nabble.com/WPS-Execute-GET-request-KVP-syntax-tp5265620.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

Ian Turton

5

On Tue, May 10, 2016 at 6:41 PM, Max Stephan <mail@anonymised.com> wrote:

Hi Ian,

thanks for the hint. Had a look at the DescribeProcess response and the
WPS spec already but couldn't really get it working based on that.

I don't have a quick answer, but just as a reference, as far I know WPS 2.0
specification dropped GET request support
altoghether because it resulted too problematic to use for clients and
complicated to reliably implement for servers.

You might also want to check a few examples in the GeoServer own tests,
might point you in the right direction:
https://github.com/geoserver/geoserver/blob/master/src/extension/wps/wps-core/src/test/java/org/geoserver/wps/ExecuteTest.java#L330

Also quite important for this type of request, make sure you are url
encoding all parameters values in your request.

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------