<div dir="ltr">Hi,<div><br></div><div>if possible, you can paste just the header of the process, without execute function - just to see, how PyWPS is dealing with the request and process configuration</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">čt 21. 4. 2016 v 14:15 odesílatel Jonas Eberle <<a href="mailto:jonas.eberle@gmx.de">jonas.eberle@gmx.de</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><div>Thanks. So there is a difference in your environment in having the slash after "wps" or not. </div><div><br></div><div>Works: </div><div><a href="http://localhost/wps/?service=WPS&request=GetCapabilities" target="_blank">http://localhost/wps/?service=WPS&request=GetCapabilities</a></div><div><br></div><div>Works not: </div><div><a href="http://localhost/wps?service=WPS&request=GetCapabilities" target="_blank">http://localhost/wps?service=WPS&request=GetCapabilities</a></div><div><br></div><div>The second one is stated as serviceInstance attribute in the ExecuteResponse tag. This is based on the server url variable from the configfile. There you should have <span style="color:#000000;font-family:arial,helvetica,sans-serif;font-size:13.3333px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;display:inline!important;float:none;background-color:#ffffff"><a href="http://localhost/wps/" target="_blank">http://localhost/wps/</a> with the trailing slash (default is without trailing slash I guess).</span></div><div><br></div><div>Cheers,</div><div>Jonas</div><div><br></div><span>----- Am 21. Apr 2016 um 14:02 schrieb Robin Skahjem-Eriksen <<a href="mailto:skahjem-eriksen@stcorp.no" target="_blank">skahjem-eriksen@stcorp.no</a>>:<br></span><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><div>Request:</div><div><a href="http://localhost/wps/?service=WPS&request=GetCapabilities" target="_blank">http://localhost/wps/?service=WPS&request=GetCapabilities</a><br></div><br><div>Response:</div><br><!-- PyWPS 4.0.0-alpha2 --><br><br><wps:Capabilities service="WPS" version="1.0.0" xml:lang="en-US" xsi:schemaLocation="<a href="http://www.opengis.net/wps/1.0.0" target="_blank">http://www.opengis.net/wps/1.0.0</a> <a href="http://schemas.opengis.net/wps/1.0.0/wpsGetCapabilities_response.xsd" target="_blank">http://schemas.opengis.net/wps/1.0.0/wpsGetCapabilities_response.xsd</a>" updateSequence="1"><br> <ows:ServiceIdentification><br> <ows:Title>PyWPS Processing Service<br> </ows:Title><br> <ows:Abstract>PyWPS is an implementation of the Web Processing Service standard from the Open Geospatial Consortium. PyWPS is written in Python.<br> </ows:Abstract><br> <ows:Keywords><br> <ows:Keyword>PyWPS<br> </ows:Keyword><br> <ows:Keyword>WPS<br> </ows:Keyword><br> <ows:Keyword>OGC<br> </ows:Keyword><br> <ows:Keyword>processing<br> </ows:Keyword><br> <ows:Type codeSpace="ISOTC211/19115">theme<br> </ows:Type><br> </ows:Keywords><br> <ows:ServiceType>WPS<br> </ows:ServiceType><br> <ows:ServiceTypeVersion>1.0.0<br> </ows:ServiceTypeVersion><br> <ows:Fees>NONE<br> </ows:Fees><br> <ows:AccessConstraints>NONE<br> </ows:AccessConstraints><br> </ows:ServiceIdentification><br> <ows:ServiceProvider><br> <ows:ProviderName>Organization Name<br> </ows:ProviderName><br> <ows:ProviderSite xlink:href="<a href="http://pywps.org/" target="_blank">http://pywps.org/</a>"/><br> <ows:ServiceContact><br> <ows:IndividualName>Lastname, Firstname<br> </ows:IndividualName><br> <ows:PositionName>Position Title<br> </ows:PositionName><br> <ows:ContactInfo><br> <ows:Phone><br> <ows:Voice>+xx-xxx-xxx-xxxx<br> </ows:Voice><br> </ows:Phone><br> <ows:Address><br> <ows:AdministrativeArea>Administrative Area<br> </ows:AdministrativeArea><br> <ows:PostalCode>Zip or Postal Code<br> </ows:PostalCode><br> <ows:Country>Country<br> </ows:Country><br> <ows:ElectronicMailAddress>Email Address<br> </ows:ElectronicMailAddress><br> </ows:Address><br> <ows:OnlineResource xlink:href="Contact URL"/><br> <ows:HoursOfService>Hours of Service<br> </ows:HoursOfService><br> <ows:ContactInstructions>During hours of service. Off on weekends.<br> </ows:ContactInstructions><br> </ows:ContactInfo><br> <ows:Role>pointOfContact<br> </ows:Role><br> </ows:ServiceContact><br> </ows:ServiceProvider><br> <ows:OperationsMetadata><br> <ows:Operation name="GetCapabilities"><br> <ows:DCP><br> <ows:HTTP><br> <ows:Get xlink:href="<a href="http://localhost/wps" target="_blank">http://localhost/wps</a>"/><br> <ows:Post xlink:href="<a href="http://localhost/wps" target="_blank">http://localhost/wps</a>"/><br> </ows:HTTP><br> </ows:DCP><br> </ows:Operation><br> <ows:Operation name="DescribeProcess"><br> <ows:DCP><br> <ows:HTTP><br> <ows:Get xlink:href="<a href="http://localhost/wps" target="_blank">http://localhost/wps</a>"/><br> <ows:Post xlink:href="<a href="http://localhost/wps" target="_blank">http://localhost/wps</a>"/><br> </ows:HTTP><br> </ows:DCP><br> </ows:Operation><br> <ows:Operation name="Execute"><br> <ows:DCP><br> <ows:HTTP><br> <ows:Get xlink:href="<a href="http://localhost/wps" target="_blank">http://localhost/wps</a>"/><br> <ows:Post xlink:href="<a href="http://localhost/wps" target="_blank">http://localhost/wps</a>"/><br> </ows:HTTP><br> </ows:DCP><br> </ows:Operation><br> </ows:OperationsMetadata><br> <wps:ProcessOfferings></blockquote></div></div></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><br> <wps:Process wps:processVersion="0.1"><br></blockquote></div></div></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"> <ows:Identifier>hello_world<br> </ows:Identifier><br> <ows:Title>My very first process!<br> </ows:Title><br> <ows:Abstract>This process takes the name of a person and displays Hello World with it.</blockquote></div></div></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><br> </ows:Abstract><br> </wps:Process><br> <wps:Process wps:processVersion="0.1"><br> <ows:Identifier>ipf<br> </ows:Identifier><br> <ows:Title>Generic IPF processor<br> </ows:Title><br> <ows:Abstract>Processors for handling IPF products<br> </ows:Abstract><br> </wps:Process><br></blockquote></div></div></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"> </wps:ProcessOfferings><br> <wps:Languages><br> <wps:Default><br> <ows:Language>en-US<br> </ows:Language><br> </wps:Default><br> <wps:Supported><br> <ows:Language>en-US<br> </ows:Language><br> </wps:Supported><br> </wps:Languages><br></wps:Capabilities></blockquote></div></div></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Apr 20 2016, at 5:00 pm, Jonas Eberle <<a href="mailto:jonas.eberle@gmx.de" target="_blank">jonas.eberle@gmx.de</a>> wrote:
<br>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><div>Can you try the following URL: </div><div><span style="color:#000000;font-family:'Times New Roman';font-size:14.16px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;display:inline!important;float:none;background-color:#fdfdfd">localhost/wps/?service=WPS&request=GetCapabilities</span></div><br><div>Cheers,</div><div>Jonas</div><br><span>----- Am 20. Apr 2016 um 12:38 schrieb Robin Skahjem-Eriksen <<a href="mailto:skahjem-eriksen@stcorp.no" target="_blank">skahjem-eriksen@stcorp.no</a>>:<br></span><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">I am wondering if I have stumbled upon a bug, if not, I find the response quite cryptic:<div><br><div>request:</div><br><div>localhost/wps/?service=WPS&request=Execute&Identifier=ipf&version=1.0.0&DataInputs=processor_name=ST_IPF_TESTER;processor_version=01.13;input_selector=time-range;muninn_query=validity_stop > 1980-07-03 and validity_start < 1980-07-05&status=true&storeExecuteResponse=true<br></div><br><div>reponse:</div><br><div><!-- PyWPS 4.0.0-alpha2 --><br><wps:ExecuteResponse xsi:schemaLocation="<a href="http://www.opengis.net/wps/1.0.0" target="_blank">http://www.opengis.net/wps/1.0.0</a> <a href="http://schemas.opengis.net/wps/1.0.0/wpsExecute_response.xsd" target="_blank">http://schemas.opengis.net/wps/1.0.0/wpsExecute_response.xsd</a>" service="WPS" version="1.0.0" xml:lang="en-US" serviceInstance="<a href="http://localhost/wps?service=WPS&request=GetCapabilities" target="_blank">http://localhost/wps?service=WPS&request=GetCapabilities</a>" statusLocation="<a href="http://localhost/wps/3c7e38b6-06e0-11e6-8f17-0242ac190008.xml" target="_blank">http://localhost/wps/3c7e38b6-06e0-11e6-8f17-0242ac190008.xml</a>"></div><div><span style="white-space:pre-wrap"> </span><wps:Process wps:processVersion="0.1"></div><div><span style="white-space:pre-wrap"> </span><ows:Identifier>ipf</ows:Identifier></div><div><span style="white-space:pre-wrap"> </span><ows:Title>Generic IPF processor</ows:Title></div><div><span style="white-space:pre-wrap"> </span><ows:Abstract>Processors for handling IPF products</ows:Abstract></div><div><span style="white-space:pre-wrap"> </span></wps:Process></div><div><span style="white-space:pre-wrap"> </span><wps:Status creationTime="2016-04-20T10:11:23Z"></div><div><span style="white-space:pre-wrap"> </span><wps:ProcessAccepted>PyWPS Process ipf accepted</wps:ProcessAccepted></div><div></wps:Status></div><div></wps:ExecuteResponse><br></div><br><div>The document (<a href="http://localhost/wps?service=WPS&request=GetCapabilities" target="_blank">http://localhost/wps?service=WPS&request=GetCapabilities</a>):</div><br><div><!-- PyWPS 4.0.0-alpha2 --><br><ows:ExceptionReport xsi:schemaLocation="<a href="http://www.opengis.net/ows/1.1" target="_blank">http://www.opengis.net/ows/1.1</a> <a href="http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd" target="_blank">http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd</a>" version="1.0.0"></div><div><span style="white-space:pre-wrap"> </span><ows:Exception exceptionCode="MissingParameterValue" locator="service"></div><div><span style="line-height:1.4"><span style="white-space:pre-wrap"> </span><ows:ExceptionText>service</ows:ExceptionText></span></div><div><span style="line-height:1.4"><span style="white-space:pre-wrap"> </span></ows:Exception></span></div><div><span style="line-height:1.4"></ows:ExceptionReport></span><br></div><br><div>I am wondering why the exception is raised, when my Execute request contains the service attribute.</div><div>Is this a bug, or am I missing something?</div><br><br><div>Med vennlig hilsen / With kind regards,<br><br>Robin Skahjem-Eriksen<br><br>Software developer<br><br>Science [&] Technology AS<br><br>Reg. nr.: 996 229 009 MVA<br><br>[E]: <a href="mailto:skahjem-eriksen@stcorp.no" target="_blank">skahjem-eriksen@stcorp.no</a><br><br>[Address]:<br><br>Forskningsparken<br><br>Gaustadalléen 21<br><br>0349 Oslo<br><br>Norway<br><br>[W]: <a href="http://www.stcorp.no" target="_blank">http://www.stcorp.no</a><br><br>[P]:+47 45 911 694<br><br>[E]: <a href="mailto:info@stcorp.no" target="_blank">info@stcorp.no</a></div></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Apr 20 2016, at 12:01 pm, Robin Skahjem-Eriksen <<a href="mailto:skahjem-eriksen@stcorp.no" target="_blank">skahjem-eriksen@stcorp.no</a>> wrote:
<br>
Thank you so much for catching that and sharing it with me.<div><br><br><div>Med vennlig hilsen / With kind regards,<br><br>Robin Skahjem-Eriksen<br><br>Software developer<br><br>Science [&] Technology AS<br><br>Reg. nr.: 996 229 009 MVA<br><br>[E]: <a href="mailto:skahjem-eriksen@stcorp.no" target="_blank">skahjem-eriksen@stcorp.no</a><br><br>[Address]:<br><br>Forskningsparken<br><br>Gaustadalléen 21<br><br>0349 Oslo<br><br>Norway<br><br>[W]: <a href="http://www.stcorp.no" target="_blank">http://www.stcorp.no</a><br><br>[P]:+47 45 911 694<br><br>[E]: <a href="mailto:info@stcorp.no" target="_blank">info@stcorp.no</a></div></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Apr 20 2016, at 11:57 am, Jonas Eberle <<a href="mailto:jonas.eberle@gmx.de" target="_blank">jonas.eberle@gmx.de</a>> wrote:
<br>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><div>You have an error in the request, storeExecuteResponse=true and status=true are individual attributes of the request, in your example these are data inputs! Please use <strong>&</strong>storeExecuteResponse=true<strong>&</strong>status=true at the end instead using the semicolon. Using the "old" PyWPS I also embraced the data inputs with brackets, this leads to less errors in my opinion: DataInputs=<strong>[</strong>processor_name=ST_IPF_;processor_version=01.13<strong>]</strong></div><br><div>Cheers,</div><div>Jonas</div><br><br><div><span>----- Am 20. Apr 2016 um 10:05 schrieb Robin Skahjem-Eriksen <<a href="mailto:skahjem-eriksen@stcorp.no" target="_blank">skahjem-eriksen@stcorp.no</a>>:<br></span></div><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">Jonas, thank you for your clarification on the request attributes and the changes to the WPS spec.<div><br><div>I have added `status=true`to the execution request in addition to the aforementioned attributes, and I still don't get a reponse with any URL to the ResponseDocument.</div><br><div>My request looks like this:</div><br><div><a href="http://localhost/wps/?service=WPS&request=Execute&Identifier=ipf&version=1.0.0&DataInputs=processor_name=ST_IPF_TESTER;processor_version=01.13;input_selector=time-range;muninn_query=validity_stop" target="_blank">http://localhost/wps/?service=WPS&request=Execute&Identifier=ipf&version=1.0.0&DataInputs=processor_name=ST_IPF_TESTER;processor_version=01.13;input_selector=time-range;muninn_query=validity_stop</a> > 1980-07-03 and validity_start < 1980-07-05;storeExecuteResponse=true;status=true<br></div><br><div>And the process is defines as such:</div><br><div>class IPF(Process):<br> def __init__(self):<br> inputs = [<br> LiteralInput(<br> 'processor_name',<br> 'IPF processor name',<br> data_type='string'<br> ),<br> LiteralInput(<br> 'processor_version',<br> 'IPF processor version',<br> data_type='string'<br> ),<br> LiteralInput(<br> 'input_selector',<br> 'SOL input selection',<br> data_type='string'<br> ),<br> LiteralInput(<br> 'muninn_query',<br> 'Muninn product catalog query string',<br> data_type='string'<br> ),<br> ]<br> outputs = [<br> LiteralOutput(<br> 'ipf_result',<br> 'SUCCESS/FAILURE',<br> data_type='string'<br> )<br> ]<br><br> super(IPF, self).__init__(<br> self._handler,<br> identifier='ipf',<br> version='0.1',<br> title='Generic IPF processor',<br> abstract='Processors for handling IPF products',<br> inputs=inputs,<br> outputs=outputs,<br> store_supported=True,<br> status_supported=True<br> )<br></div><br>(.. handler omitted ..)</div><div><br><div>Am I missing something?</div><br><br><div>Med vennlig hilsen / With kind regards,<br><br>Robin Skahjem-Eriksen<br><br>Software developer<br><br>Science [&] Technology AS<br><br>Reg. nr.: 996 229 009 MVA<br><br>[E]: <a href="mailto:skahjem-eriksen@stcorp.no" target="_blank">skahjem-eriksen@stcorp.no</a><br><br>[Address]:<br><br>Forskningsparken<br><br>Gaustadalléen 21<br><br>0349 Oslo<br><br>Norway<br><br>[W]: <a href="http://www.stcorp.no" target="_blank">http://www.stcorp.no</a><br><br>[P]:+47 45 911 694<br><br>[E]: <a href="mailto:info@stcorp.no" target="_blank">info@stcorp.no</a></div></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Apr 19 2016, at 9:26 pm, Jonas Eberle <<a href="mailto:jonas.eberle@gmx.de" target="_blank">jonas.eberle@gmx.de</a>> wrote:
<br>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">Hi Robin, </div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">I guess you're looking for the "statusLocation" attribute of the ExecuteResponse tag. The value of this attribute is the URL to the response document, especially needed when you use asynchronous execution (both, status=true and storeExecuteResponse=true, needed in the execute request). There is no executeResponseLocation element, please see the "Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0 (0.0.8)" [1]. </div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">Best regards,</div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">Jonas</div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:#000000">[1] = <a href="http://portal.opengeospatial.org/files/?artifact_id=32766" target="_blank">http://portal.opengeospatial.org/files/?artifact_id=32766</a><br><br><span>----- Am 19. Apr 2016 um 11:09 schrieb Robin Skahjem-Eriksen <<a href="mailto:skahjem-eriksen@stcorp.no" target="_blank">skahjem-eriksen@stcorp.no</a>>:<br></span><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">I am trying to get pywps working so that a ResponseDocument is used to show the process status, by having the Execute response provide a URL to the ResponseDocument, as specified in the WPS 1.0 standard.<div><br><div>I am not sure if pywps actually supports this and if so, the feature is not well documented. I see that pywps supports serving output files and serving these, and I was hoping that this could be used to provide the response document.</div><br><div>I initialize a Process object with `store_supported` and `status_supported` set to `True` and provide `storeExecuteResponse=true` in the GET request. However, I haven't manged to receive a response containing the `executeResponseLocation` element, and I cannot find any code in the master branch code base that handles an `ExecuteResponseLocation`.</div><br><div>Am I missing anything, or is this feature simply not supported by pywps?</div><br><div>Med vennlig hilsen / With kind regards,<br><br>Robin Skahjem-Eriksen<br><br>Software developer<br><br>Science [&] Technology AS<br><br>Reg. nr.: 996 229 009 MVA<br><br>[E]: <a href="mailto:skahjem-eriksen@stcorp.no" target="_blank">skahjem-eriksen@stcorp.no</a><br><br>[Address]:<br><br>Forskningsparken<br><br>Gaustadalléen 21<br><br>0349 Oslo<br><br>Norway<br><br>[W]: <a href="http://www.stcorp.no" target="_blank">http://www.stcorp.no</a><br><br>[P]:+47 45 911 694<br><br>[E]: <a href="mailto:info@stcorp.no" target="_blank">info@stcorp.no</a></div></div><br>_______________________________________________<br>pywps-dev mailing list<br><a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/pywps-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/pywps-dev</a></blockquote></div></div><br></div>
</blockquote><br></blockquote></div></div>
</blockquote>
</blockquote><br></blockquote></div></div>
</blockquote><br></blockquote></div></div></div>_______________________________________________<br>
pywps-dev mailing list<br>
<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pywps-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/pywps-dev</a></blockquote></div>