-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QGISserver WFS returns invalid GML in case of cascading WFS #41292
Comments
Fixes qgis#41292 QGISserver WFS returns invalid GML in case of cascading WFS
waiting for the built release, this solution/workaround worked to me: [https://github.com//issues/25847] |
@elpaso just wondering: should you really replace the ':' with a '-'? Because you are rewriting the schema of the xml in that way. While I think if you cascade a WFS I would have hoped that I just receive the same gml as I would receive from the original WFS. Would it not be better to ONLY add a qgs-namespace if there is NO namespace? And IF there is a namespace, leave it as is? In that way applications which count on a xml schema would still work? |
Fixes qgis#41292 QGISserver WFS returns invalid GML in case of cascading WFS (cherry picked from commit 65b272d)
As reported in the user mailing list:
https://lists.osgeo.org/pipermail/qgis-user/2021-February/047880.html
it looks like QGIS WFS server does not return valid GML in case of a cascading WFS.
I think it tries to add a 'namespace' to the featuremember xml elements, while there IS already a 'namespace'.
See below: the
<qgs:test:provincies gml:id="test:provincies.3">
parts.Attached: test.gml.zip is the return data from QGISserver.
To reproduce:
By looking in the debug window of QGISserver, copy/pasting the url and saving the response as test.gml I was able to save the attached test.gml.zip
Also note the
```ogrinfo test.gml`` works and shows:
But
$ ogrinfo -al test.gml
ONLY returns the bbox info (and NOT the features):The text was updated successfully, but these errors were encountered: