[PyWPS-dev] Process Chaining

[PyWPS-dev] Process Chaining

Hi All,

I was wondering if there is an xml template or xml example of a chained process POST request. I have been trying to use OWSLib to chain my PyWPS Process requests but am finding it difficult as there is no examples of how this is achieved using OWSLib. I have been able to 'simulate' a chained request by sending requests in order and then using the output from the first as the input to the next. I have also tried embedding a request in another but have found that the library escapes the xml special characters, resulting in malformed xml. I also attempted to manually create an XML POST request but not sure how the embedding is achieved ie. what is the element called that identifies a chained or embedded request. So I would therefore like to know if anyone can point me in the right direction in terms of what the XML for a chained PyWPS request would look like.

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'

I was wondering if there is an xml template or xml example of a chained process POST request. I have been trying to use OWSLib to chain my PyWPS Process requests but am finding it difficult as there is no examples of how this is achieved using OWSLib. I have been able to 'simulate' a chained request by sending requests in order and then using the output from the first as the input to the next. I have also tried embedding a request in another but have found that the library escapes the xml special characters, resulting in malformed xml. I also attempted to manually create an XML POST request but not sure how the embedding is achieved ie. what is the element called that identifies a chained or embedded request. So I would therefore like to know if anyone can point me in the right direction in terms of what the XML for a chained PyWPS request would look like.

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'

Re: Process Chaining

Hi Carsten,

Thanks for getting back to me with the info, the links on testing are definitely helpful, and I had come across the Ana Homolka contribution but I was not sure whether it had been implemented in the current version of PyWPS. I think it should be possible to chain processes using the XML approach given the correct tag to nest within the input section of a process, the next execute request. Unfortunately, the geoserver chained xml docs are not compatible.

I was wondering if there is an xml template or xml example of a chained process POST request. I have been trying to use OWSLib to chain my PyWPS Process requests but am finding it difficult as there is no examples of how this is achieved using OWSLib. I have been able to 'simulate' a chained request by sending requests in order and then using the output from the first as the input to the next. I have also tried embedding a request in another but have found that the library escapes the xml special characters, resulting in malformed xml. I also attempted to manually create an XML POST request but not sure how the embedding is achieved ie. what is the element called that identifies a chained or embedded request. So I would therefore like to know if anyone can point me in the right direction in terms of what the XML for a chained PyWPS request would look like.

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'

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'