<div dir="ltr">Hi Gunner,<div><br></div><div>Thanks for getting back to me, yes you have understood my request, I too tried to use the above example xml template to chain a request but came to the conclusion that it was failing because the nested <span style="color:rgb(6,40,115);font-family:inherit;font-size:14.4px;font-style:inherit;font-weight:bold;background-color:rgba(240,240,240,0.8);white-space:pre-wrap"><wps:Body> </span>tag was Geoserver specific - perhaps I was incorrect, if you say that you have a working chain with RawData. My understanding is that the server should seamlessly use the output from one request as input to the next request without any further coding required because it understands that a nested request's output is its input parameter, and that is why I thought the xml request was incorrect. I too was trying to chain with a ComplexInput that was the result of a ComplexOutput from a WFS request. I will have to revisit it and see what my errors were, perhaps it was not an error in the xml. I will keep you posted on my progress, and thanks for the discussion.</div><div><br></div><div>Suzana</div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, 19 Dec 2018 at 10:32, Gunnar Ströer <<a href="mailto:gunnar.stroeer@yahoo.de" target="_blank">gunnar.stroeer@yahoo.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_-414554028967192785gmail-m_-1801260901250473113ydp85aaf0eayahoo-style-wrap" style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px"><div></div>
<div><span> <span>Hi Suzana,<br><br>I agree a process should not know whether it is part of a chain. If you ask for a working XML request my example request above works fine for a simple chaining. My question aims to the python code behind the request, how to handle a chain with PyWPS and without using RawData. Of course it is possible to be wrong with my XML. I understand a chained request as a nested process of single processes, from inside to outside. The most inner request is the first process of your chain (intersection in my case), and the most surrounding process ist your last process (buffer in my case). I've used following URL for understanding:<br><br><a href="https://docs.geoserver.org/latest/en/user/services/wps/processes/chaining.html" target="_blank">https://docs.geoserver.org/latest/en/user/services/wps/processes/chaining.html</a><br><br>I hope I understood you correctly.<br><br>Best,<br>Gunnar</span></span><br></div>
</div><div id="gmail-m_-414554028967192785gmail-m_-1801260901250473113yahoo_quoted_6120163050" class="gmail-m_-414554028967192785gmail-m_-1801260901250473113yahoo_quoted">
<div style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px;color:rgb(38,40,42)">
<div>
Am Mittwoch, 19. Dezember 2018, 10:43:54 MEZ hat Suzana Barreto <<a href="mailto:suzana.barreto@envsys.co.uk" target="_blank">suzana.barreto@envsys.co.uk</a>> Folgendes geschrieben:
</div>
<div><br></div>
<div><br></div>
<div><div id="gmail-m_-414554028967192785gmail-m_-1801260901250473113yiv9028231219"><div><div dir="ltr">Hi Gunner,<div><br clear="none"></div><div>I have been trying to get chaining to work but have not had any luck yet, my understanding is that a process should not know whether it is part of a chain. I would be interested in knowing how you have structured your chained request, if you wouldn't mind sharing that information with me. </div><div><br clear="none"></div><div>All the best,</div><div>Suzana</div></div><br clear="none"><div class="gmail-m_-414554028967192785gmail-m_-1801260901250473113yiv9028231219gmail_quote"><div class="gmail-m_-414554028967192785gmail-m_-1801260901250473113yiv9028231219yqt2240105545" id="gmail-m_-414554028967192785gmail-m_-1801260901250473113yiv9028231219yqt53442"><div dir="ltr">On Mon, 17 Dec 2018 at 13:07, Carsten Ehbrecht <<a rel="nofollow" shape="rect" href="mailto:ehbrecht@dkrz.de" target="_blank">ehbrecht@dkrz.de</a>> wrote:<br clear="none"></div><blockquote class="gmail-m_-414554028967192785gmail-m_-1801260901250473113yiv9028231219gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Hi Gunnar,<div><br clear="none"></div><div>I haven’t looked into process chaining, but this question was just raised recently:</div><div><br clear="none"></div><div><a rel="nofollow" shape="rect" href="https://lists.osgeo.org/pipermail/pywps-dev/2018-December/001363.html" target="_blank">https://lists.osgeo.org/pipermail/pywps-dev/2018-December/001363.html</a></div><div><br clear="none"></div><div>Here is in addition a description of how a process chain can be done:</div><div><a rel="nofollow" shape="rect" href="http://geoprocessing.info/wpsdoc/Concepts#chaining" target="_blank">http://geoprocessing.info/wpsdoc/Concepts#chaining</a></div><div><br clear="none"></div><div>I’m not sure how your code and your chain works (the gitlab link is not public). A comment from my side would be, that your “worker” process should not know that it is part of a process chain.</div><div><br clear="none"></div><div>Cheers,</div><div>Carsten<br clear="none"><div><br clear="none"><blockquote type="cite"><div>On 12 Dec 2018, at 6:34 pm, <a rel="nofollow" shape="rect" href="mailto:gunnar.stroeer@yahoo.de" target="_blank">gunnar.stroeer@yahoo.de</a> wrote:</div><br class="gmail-m_-414554028967192785gmail-m_-1801260901250473113yiv9028231219gmail-m_5571806578248561641Apple-interchange-newline" clear="none"><div><div>Hi Everybody,<br clear="none"><br clear="none">I currently develop some processes for a masterthesis using PyWPS v4 as implementation. Mostly it works fine for single processes, as well with QGIS as client. However I stucked when it comes to chaining.<br clear="none"><br clear="none">Normally in single processes I use "in_file = request.inputs['in_geom'][0].file" for read in some complex GML geometry. In cases I wanna use the same process in a chain the code above doesn't work anymore because the input is the same as the output of the prior process. Therefore "in_file = request.inputs['in_geom'][0].file" additionally gets all the XML code of the prior response - and the process crashed.<br clear="none"><br clear="none">To handle this I use "import lxml" to parse the response XML looking for the "xlink:href" attribute value with the referenced GML output file of the first process. It works for the process in a chain, only. Whether the process is used in a chain or not I could handle in the process code, like a case distinction. Therefor I have to parse XML all the time again and again... and it makes me feel that I use PyWPS in a wrong way.<br clear="none"><br clear="none">I also could use "RawDataOutput", but this is obviously a bad solution for large data inputs/outputs.<br clear="none"><br clear="none">Is there any method to handle the described problem without writing too much code just to get know whether the process is used in a chain or not? Or is there something completely wrong what I'm doing?<br clear="none"><br clear="none"><a rel="nofollow" shape="rect" href="https://gitlab.com/hadlaskard/integration-of-wps-in-local-sdi/blob/master/processes/proc_buffer.py" target="_blank">https://gitlab.com/hadlaskard/integration-of-wps-in-local-sdi/blob/master/processes/proc_buffer.py</a><br clear="none"><br clear="none">Thanks,<br clear="none">Gunnar<br clear="none">_______________________________________________<br clear="none">pywps-dev mailing list<br clear="none"><a rel="nofollow" shape="rect" href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br clear="none"><a rel="nofollow" shape="rect" href="https://lists.osgeo.org/mailman/listinfo/pywps-dev" target="_blank">https://lists.osgeo.org/mailman/listinfo/pywps-dev</a></div></div></blockquote></div><br clear="none"></div></div>_______________________________________________<br clear="none">
pywps-dev mailing list<br clear="none">
<a rel="nofollow" shape="rect" href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br clear="none">
<a rel="nofollow" shape="rect" href="https://lists.osgeo.org/mailman/listinfo/pywps-dev" target="_blank">https://lists.osgeo.org/mailman/listinfo/pywps-dev</a></blockquote></div></div><br clear="all"><div><br clear="none"></div>-- <br clear="none"><div class="gmail-m_-414554028967192785gmail-m_-1801260901250473113yiv9028231219gmail_signature" dir="ltr"><div dir="ltr"><div><div dir="ltr"><p style="font:7.5pt arial,sans-serif;color:gray;text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal;background-color:rgb(255,255,255)"><b>Dr Suzana Barreto<br clear="none">Software Analyst<br clear="none">Environment Systems</b><br clear="none">Tel: <a rel="nofollow" shape="rect" style="color:rgb(17,85,204)">+44 (0) 1970 626688</a><br clear="none"><a rel="nofollow" shape="rect" style="color:rgb(17,85,204)" href="http://www.envsys.co.uk/" target="_blank">www.envsys.co.uk</a></p><p style="font:7.5pt arial,sans-serif;color:gray;text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal;background-color:rgb(255,255,255)">The information contained in this e-mail is intended only for the use of the person(s) to whom it is addressed and may contain confidential or privileged information. If you have received this e-mail in error please contact the sender and delete the material without copying, distributing or disclosing the content. All reasonable precautions have been taken to ensure that this e-mail is free from any virus, however, the recipient should verify this to be the case. Please 'think before you print'</p></div></div></div></div></div></div></div>
</div>
</div></div></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-414554028967192785gmail_signature"><div dir="ltr"><div><div dir="ltr"><p style="font:7.5pt arial,sans-serif;color:gray;text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal;background-color:rgb(255,255,255)"><b>Dr Suzana Barreto<br>Software Analyst<br>Environment Systems</b><br>Tel: <a style="color:rgb(17,85,204)" href="tel:%2B44%20%280%29%201970%20626688" value="+441970626688" target="_blank">+44 (0) 1970 626688</a><br><a style="color:rgb(17,85,204)" href="http://www.envsys.co.uk/" target="_blank">www.envsys.co.uk</a></p><p style="font:7.5pt arial,sans-serif;color:gray;text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;white-space:normal;background-color:rgb(255,255,255)">The information contained in this e-mail is intended only for the use of the person(s) to whom it is addressed and may contain confidential or privileged information. If you have received this e-mail in error please contact the sender and delete the material without copying, distributing or disclosing the content. All reasonable precautions have been taken to ensure that this e-mail is free from any virus, however, the recipient should verify this to be the case. Please 'think before you print'</p></div></div></div></div>