[Geoserver-users] In WPS is it possible to chain processes across different geoserver/wps service instances?

For example, would it be possible to have an custom WPS web-service, and then have a geoserver instance with a wps process that delegates/proxyies to that service?

If so, then does WPS protocol have native support or provide guidance about how to specify the urls where the processes should run?

Thanks

Julian

University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.

To chain to external WPS references we would need to work on the geotools gt-wps client, which so far has very limited functionality - but it is an interesting topic.

You may wish to look at other OSGeo WPS implementations such as the zoo wps (which uses server side javascript for chaining).

···

On 1 March 2015 at 15:48, Julian Atkinson <j.f.c.atkinson@anonymised.com> wrote:

For example, would it be possible to have an custom WPS web-service, and then have a geoserver instance with a wps process that delegates/proxyies to that service?

If so, then does WPS protocol have native support or provide guidance about how to specify the urls where the processes should run?

Thanks

Julian

University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.


Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/


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


Jody Garnett

On Wed, Mar 4, 2015 at 1:59 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

To chain to external WPS references we would need to work on the geotools
gt-wps client, which so far has very limited functionality - but it is an
interesting topic.

You may wish to look at other OSGeo WPS implementations such as the zoo
wps (which uses server side javascript for chaining).

Hum... chaining is the ability to call one process and get its outputs as
inputs of another process in the same Execute call. We do support it,
actually,
no standard compliant WPS can avoid supporting it afaik.

Server side combination via scripting languages is more than chaining,
allows to put logic in the glue, add extra actions, write your own
composite process
based on simpler processes. We sort of do support this via the scripting
modules in community land, but we don't have a good story (a really easy
way)
to invoke local processes, it can be done of course, but the setup code is
cumbersome.

Cascading is a different beast, you point to the capabilities document of a
remote WPS server, and start serving its processes as part
of your local offerings, when a call is made to one such processes, the
code would have to use a WPS client to call the other server.
The WPS client is the missing bit here, we have a start of one, but it's
not complete enough to do the job (it's the gt-wps Jody is referring to).

As a reference of a further type of integration, we are also working on
wps-remote module that allows calling remote processes wrapped via a python
script using XMPP as the transport
protocol, which allows GeoServer to discover, advertise, invoke, track
progress and retrieve outputs from these remote processes.
It's not ready yet, its config, functionality and network protocol are
still in flux, the plan is to donate it to GeoServer once its config gets
stable
enough to allow publishing it to a wider audience.

Cheers
Andrea

--

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
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.

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