[owslib-devel] [owslib-users] WPS support

Cinquini, Luca (3880) Luca.Cinquini at jpl.nasa.gov
Thu Oct 13 14:36:05 PDT 2011


Thanks Tom, will do... and I am indeed using as much of ows.py as possible.
Will report back next week,
thanks, Luca

On Oct 13, 2011, at 3:29 PM, Tom Kralidis wrote:


Luca: thanks -- good news!

Be sure to use svn trunk at https://owslib.svn.sourceforge.net/svnroot/owslib/trunk/ (svn repo recently changed hosts).  And be sure to check out / leverage owslib/ows.py for processing WPS capabilities.

We would welcome a patch if possible, or if you'd like a sandbox area.  Let us know how things go!

Thanks

..Tom




________________________________
From: Luca.Cinquini at jpl.nasa.gov<mailto:Luca.Cinquini at jpl.nasa.gov>
To: owslib-devel at lists.sourceforge.net<mailto:owslib-devel at lists.sourceforge.net>
Date: Thu, 13 Oct 2011 13:56:16 -0700
CC: jachym.cepicky at gmail.com<mailto:jachym.cepicky at gmail.com>; pywps-devel at wald.intevation.org<mailto:pywps-devel at wald.intevation.org>
Subject: Re: [owslib-devel] [owslib-users] WPS support

Hi all,
I transferred this conversation to owslib-devel...

I think having multiple implementation of client-side WPS functionality is certainly a good thing.
I was indeed aware of a JS implementation under development in the context or pywps, and I think it would be a very valuable tool for some apps.
In my personal case, I'd rather execute python invocation from within my django views and models, so building on top of OWSLib makes more sense.
Maybe the two approaches can even be combined...

In any case, I started looking at using the existing OWSlib classes to make WPS requests and parse WPS response, and it seems like it wouldn't be too difficult of a job.
Off course, I'll be happy to either collaborate at doing so, or simply using existing code. My timeline is somewhat short though, as I'd like to show some working prototype
within a couple of weeks. I can probably report more on how it's going sometimes next week.

thanks to all,
Luca


On Oct 13, 2011, at 2:13 PM, Tom Kralidis wrote:


Jachym: thanks for the info.  OK, let's continue discussion on owslib-devel [1].

..Tom

[1] https://lists.sourceforge.net/mailman/listinfo/owslib-devel

> Date: Thu, 13 Oct 2011 21:36:57 +0200
> From: jachym.cepicky at gmail.com<mailto:jachym.cepicky at gmail.com>
> 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>
> Subject: Re: [owslib-users] WPS support
>
> PyWPS is the server implementation, it does not make much sense to me,
> to make any client distributed with it, when there are OpenLayers (for
> JavaScript) and naturaly, owslib is to me *the* Python OWS client
> software, so making one in PyWPS is not good idea (and there is none
> currently).
>
> So, when I write, that I would like to help, I'm speaking about OWSLib
>
>
> J
>
> On 13.10.2011 21:14, Tom Kralidis wrote:
> >
> >
> > Jachym: thanks for the info. I guess the question is where a good
> > home for a WPS client in python would be. WPS client is in owslib's
> > scope, and there are full OWS Common/Filter/etc. parsers in owslib,
> > which a client implementation (like WPS) could leverage.
> >
> > Are there plans to put a python client in pywps? I think it would be
> > valuable in owslib for sure.
> >
> > ..Tom
> >
> >
> >
> > ----------------------------------------
> >> Date: Thu, 13 Oct 2011 21:06:52 +0200 From:
> >> jachym.cepicky at gmail.com<mailto:jachym.cepicky at gmail.com> To: tomkralidis at hotmail.com<mailto:tomkralidis at hotmail.com> CC:
> >> luca.cinquini at jpl.nasa.gov<mailto:luca.cinquini at jpl.nasa.gov>; owslib-users at lists.sourceforge.net<mailto:owslib-users at lists.sourceforge.net>;
> >> Pywps-devel at wald.intevation.org<mailto:Pywps-devel at wald.intevation.org> Subject: Re: [owslib-users] WPS
> >> support
> >>
> >> Hi,
> >>
> >> I'm currently working on JavaScript implementation of WPS client.
> >>
> >> PyWPS is server-side.
> >>
> >> I can help with the python-based client, maybe there would be more
> >> people having interest in Python-client implementation.
> >>
> >> Luca, you can mail me directly, when ever you need some help. I
> >> personally do not have any clue about how things are done in
> >> owslib, but I have some experiences with it as user, and I have
> >> already written several javascript implementations (currently
> >> working with the native-openlayers), so I have some picture.
> >>
> >> Jachym
> >>
> >> On 13.10.2011 20:12, Tom Kralidis wrote:
> >>>
> >>>
> >>>
> >>> ----------------------------------------
> >>>> From: Luca.Cinquini at jpl.nasa.gov<mailto:Luca.Cinquini at jpl.nasa.gov> To:
> >>>> owslib-users at lists.sourceforge.net<mailto:owslib-users at lists.sourceforge.net> Date: Thu, 13 Oct 2011
> >>>> 10:39:23 -0700 Subject: [owslib-users] WPS support
> >>>>
> >>>> Hi, at NOAA/ESRL we have a need to execute HTTP requests to the
> >>>> WPS services offered by the USGS. I was referred to the OWSlib
> >>>> code as a library for executing OGC invocations... It is indeed
> >>>> a great start, but it looks like it does not contain any WPS
> >>>> support yet. So the question is - is anybody working on
> >>>> enabling WPS client-side functionality ? If not, what is the
> >>>> process for contributing such a code to the project ? It looks
> >>>> like it shouldn't be that difficult, building on what exists
> >>>> already.
> >>>>
> >>>> thanks a lot, Luca
> >>>
> >>> Luca: there is an open ticket for WPS client currently:
> >>> http://sourceforge.net/apps/trac/owslib/ticket/1, but no work
> >>> done on it so far (AFAIK).
> >>>
> >>> I've also cc'd Jachym Cepicky of pywps (WPS server), who has
> >>> expressed interest in building a WPS client in owslib.
> >>>
> >>> In terms of contributions, I would suggest signing up to the
> >>> owslib-devel list and we can take the discussion from there. At a
> >>> high level, a patch or committer status (on consensus) to add the
> >>> support would be the way to go. And reusing as much of what's in
> >>> the codebase (OWS Common, Filter, common methods, etc.).
> >>>
> >>> ..Tom
> >>>
> >>>
> >


------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________ owslib-devel mailing list owslib-devel at lists.sourceforge.net<mailto:owslib-devel at lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/owslib-devel

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


More information about the OWSLib-devel mailing list