[owslib-devel] update on WPS development

[Cinquini, Luca (3880)]

Thanks Tom and Dom, I'll do that today or tomorrow...
thanks, Luca

On Nov 2, 2011, at 6:20 AM, Tom Kralidis wrote:


Dom: thanks for the vote of confidence.

Luca: I have given you svn commit access.  Please go ahead and make a branch (i.e. branches/wps), and we can go from there.

Thanks!

..Tom


> Date: Wed, 2 Nov 2011 12:15:44 +0000
> From: dominic.lowe at stfc.ac.uk<mailto:dominic.lowe at stfc.ac.uk>
> To: tomkralidis at hotmail.com<mailto:tomkralidis at hotmail.com>
> CC: luca.cinquini at jpl.nasa.gov<mailto:luca.cinquini at jpl.nasa.gov>; pywps-devel at wald.intevation.org<mailto:pywps-devel at wald.intevation.org>; owslib-devel at lists.sourceforge.net<mailto:owslib-devel at lists.sourceforge.net>
> Subject: Re: [owslib-devel] update on WPS development
>
> No objections from me - I think this would be a great addition to OWSLib.
>
> Dom
>
> On 02/11/11 00:24, tomkralidis at hotmail.com<mailto:tomkralidis at hotmail.com> wrote:
> > Hi Luca: thanks for the info. Looks good!! I think would be a good fit for OWSLib. Without seeing the client code, I would say that keeping wps.py as agnostic as possible would be valuable. That and one or two doctests as per those owslib/tests/.
> >
> > Dom: any opposition to giving Luca svn commit access? I think the WPS work would be a valuable addition to the codebase.
> >
> > Pending this, we could get you a branch setup or in trunk, depending.
> >
> > ..Tom
> >
> >
> >
> > ________________________________
> > From: Luca.Cinquini at jpl.nasa.gov<mailto:Luca.Cinquini at jpl.nasa.gov>
> > To: pywps-devel at wald.intevation.org<mailto:pywps-devel at wald.intevation.org>; owslib-devel at lists.sourceforge.net<mailto:owslib-devel at lists.sourceforge.net>
> > Date: Tue, 1 Nov 2011 10:19:13 -0700
> > Subject: Re: [owslib-devel] update on WPS development
> >
> > Hi all,
> > (sorry for the double-posting since I forgot to cc the pywps list):
> >
> > Sorry I did not report back when I said I would, indeed I have been diverted onto other things...
> >
> > Anyway, the current status of the WPS development is that I have some code that is able to query a WPS GetCapabilities URL, a WPS DescribeProcess URL, and submit a POST Execute request, waiting for the process to complete. I have tested this against the USGS WPS service, although for only a limited number of process inputs and outputs.
> >
> > I am including a python script that shows how to use the API - although off course it won't run unless the code is installed. Comments and feedback is welcome, for example if this is the right client API, what could be improved and so on.
> >
> > If there is interest, I can contribute this code back into the repo, perhaps on branch.
> >
> > thanks, Luca
> >
> >
> >
> >
> >
>
> --
> Scanned by iCritical.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/owslib-devel/attachments/20111102/b0e007b9/attachment.html>