You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@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.
In the way it is handled in your PR for example, I cannot use the same filters because the element namespace/names have in changed.
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?
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: