[PyWPS-dev] Why is PyWPS using different XML tags/namespaces for BoundingBoxData as Input and Output?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[PyWPS-dev] Why is PyWPS using different XML tags/namespaces for BoundingBoxData as Input and Output?

gunnar.stroeer
Hi Community,

during my processes coding I've found out a discrepance in the supported Input and Output XML code in the case of using bounding box data. Am I right assuming that the built-in support for Input XML is based on the tag <wps:BoundingBoxData><ows:LowerCorner>(...) and for Output/Response XML is based on the tag <ows:BoundingBox><ows:LowerCorner>(...) only? Or can I modify this XML tag within PyWPS and without XML parse/replace?


As INPUT:

<wps:BoundingBoxData crs="EPSG:25832">
    <ows:LowerCorner>413236.919203 5316621.52211</ows:LowerCorner>
    <ows:UpperCorner>413719.644442 5317104.24735</ows:UpperCorner>
</wps:BoundingBoxData>

As OUTPUT:

<ows:BoundingBox crs="EPSG:25832" dimensions="2">
    <ows:LowerCorner>413236.919203 5316621.52211</ows:LowerCorner>
    <ows:UpperCorner>413719.644442 5317104.24735</ows:UpperCorner>
</ows:BoundingBox>


Cheers, Gunnar


_______________________________________________
pywps-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/pywps-dev
Reply | Threaded
Open this post in threaded view
|

Re: Why is PyWPS using different XML tags/namespaces for BoundingBoxData as Input and Output?

Carsten Ehbrecht-3
Hi Gunnar,

I find the bbox also quite confusing. But I think your bbox description looks right.

See also owslib:

But it looks like we still have an issue in PyWPS:

Cheers,
Carsten

On 18 Jan 2019, at 1:40 pm, Gunnar Ströer <[hidden email]> wrote:

Hi Community,

during my processes coding I've found out a discrepance in the supported Input and Output XML code in the case of using bounding box data. Am I right assuming that the built-in support for Input XML is based on the tag <wps:BoundingBoxData><ows:LowerCorner>(...) and for Output/Response XML is based on the tag <ows:BoundingBox><ows:LowerCorner>(...) only? Or can I modify this XML tag within PyWPS and without XML parse/replace?


As INPUT:

<wps:BoundingBoxData crs="EPSG:25832">
    <ows:LowerCorner>413236.919203 5316621.52211</ows:LowerCorner>
    <ows:UpperCorner>413719.644442 5317104.24735</ows:UpperCorner>
</wps:BoundingBoxData>

As OUTPUT:

<ows:BoundingBox crs="EPSG:25832" dimensions="2">
    <ows:LowerCorner>413236.919203 5316621.52211</ows:LowerCorner>
    <ows:UpperCorner>413719.644442 5317104.24735</ows:UpperCorner>
</ows:BoundingBox>


Cheers, Gunnar

_______________________________________________
pywps-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/pywps-dev


_______________________________________________
pywps-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/pywps-dev

smime.p7s (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Why is PyWPS using different XML tags/namespaces for BoundingBoxData as Input and Output?

gunnar.stroeer
Thanks Carsten for validation. I found a workaround and use ComplexData as BoundingBoxData, I just have to parse again. It seems the mechanism has changed a bit in the current master.

Cheers, Gunnar
Am Montag, 21. Januar 2019, 17:40:46 MEZ hat Carsten Ehbrecht <[hidden email]> Folgendes geschrieben:


Hi Gunnar,

I find the bbox also quite confusing. But I think your bbox description looks right.

See also owslib:

But it looks like we still have an issue in PyWPS:

Cheers,
Carsten

On 18 Jan 2019, at 1:40 pm, Gunnar Ströer <[hidden email]> wrote:

Hi Community,

during my processes coding I've found out a discrepance in the supported Input and Output XML code in the case of using bounding box data. Am I right assuming that the built-in support for Input XML is based on the tag <wps:BoundingBoxData><ows:LowerCorner>(...) and for Output/Response XML is based on the tag <ows:BoundingBox><ows:LowerCorner>(...) only? Or can I modify this XML tag within PyWPS and without XML parse/replace?


As INPUT:

<wps:BoundingBoxData crs="EPSG:25832">
    <ows:LowerCorner>413236.919203 5316621.52211</ows:LowerCorner>
    <ows:UpperCorner>413719.644442 5317104.24735</ows:UpperCorner>
</wps:BoundingBoxData>

As OUTPUT:

<ows:BoundingBox crs="EPSG:25832" dimensions="2">
    <ows:LowerCorner>413236.919203 5316621.52211</ows:LowerCorner>
    <ows:UpperCorner>413719.644442 5317104.24735</ows:UpperCorner>
</ows:BoundingBox>


Cheers, Gunnar

_______________________________________________
pywps-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/pywps-dev


_______________________________________________
pywps-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/pywps-dev