<html><head><base href="x-msg://3/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Tom,<div><span class="Apple-tab-span" style="white-space:pre"> </span>thanks... my preference would be to check in the code in a branch, so that other people might have a chance to check it out and test it, before committing it to trunk. Also, I imagine that the code will develop considerably in the next few months, as we experiment more with invoking the USGS WPS service, so working on a branch might keep trunk more stable.</div><div>thanks, Luca</div><div><br><div><div>On Nov 1, 2011, at 6:24 PM, Tom Kralidis wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div class="hmmessage" style="font-size: 10pt; font-family: Tahoma; "><div dir="ltr"><br>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/.<br><br>Dom: any opposition to giving Luca svn commit access? I think the WPS work would be a valuable addition to the codebase.<br><br>Pending this, we could get you a branch setup or in trunk, depending.<br><br>..Tom<br><br><br><br><div><hr id="stopSpelling">From:<span class="Apple-converted-space"> </span><a href="mailto:Luca.Cinquini@jpl.nasa.gov">Luca.Cinquini@jpl.nasa.gov</a><br>To:<span class="Apple-converted-space"> </span><a href="mailto:pywps-devel@wald.intevation.org">pywps-devel@wald.intevation.org</a>;<span class="Apple-converted-space"> </span><a href="mailto:owslib-devel@lists.sourceforge.net">owslib-devel@lists.sourceforge.net</a><br>Date: Tue, 1 Nov 2011 10:19:13 -0700<br>Subject: Re: [owslib-devel] update on WPS development<br><br><div><div><div>Hi all,</div></div><div><span class="ecxx_Apple-tab-span" style="white-space: pre; "></span>(sorry for the double-posting since I forgot to cc the pywps list):</div><div><br><blockquote></blockquote><span class="ecxx_Apple-tab-span" style="white-space: pre; "></span>Sorry I did not report back when I said I would, indeed I have been diverted onto other things...<br><blockquote></blockquote><font class="ecxx_Apple-style-span" color="#144FAE"><br></font><blockquote></blockquote>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.<br><blockquote></blockquote><font class="ecxx_Apple-style-span" color="#144FAE"><br></font><blockquote></blockquote>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. <br><blockquote></blockquote><font class="ecxx_Apple-style-span" color="#144FAE"><br></font><blockquote></blockquote>If there is interest, I can contribute this code back into the repo, perhaps on branch.<br><blockquote></blockquote><font class="ecxx_Apple-style-span" color="#144FAE"><br></font><blockquote></blockquote>thanks, Luca<br><blockquote></blockquote><font class="ecxx_Apple-style-span" color="#144FAE"><br></font><blockquote></blockquote><div><font class="ecxx_Apple-style-span" color="#144FAE"></font></div></div></div><div><div><div><font class="ecxx_Apple-style-span" color="#144FAE"></font></div></div><br></div><br><br></div></div></div></span></blockquote></div><br></div></body></html>