-
Notifications
You must be signed in to change notification settings - Fork 8
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
Difference between GML from file and GML from WFS - inheritance #16
Comments
I tried the link you provided: I am able to connect to WFS ("http://kortforsyningen.kms.dk/ra_tn_elf_gml321?") both from QGIS2.18 and from QGIS3.4. Geometries are correctly displayed and info is correct + it is same info displayed in the case of GML. In the case of QGIS 3.4, however, I have to specify the wfs version in the connection URL to make it work (see attached screenshot). |
I investigated again. The scenario I described is without the use of the GML application toolbox plugin, The geometry is defined on the supertype, tn-ra:RailwayLink, and not on elf:RailwayLink, and then QGIS doesn't recognize the geometries. I tried also with the GML application toolbox plugin, in QGIS 3.4.10, but I get a Python error, and nothing is shown. Probably the same as described in BRGM/gml_application_schema_toolbox#88
|
Thank you Heidi for your follow-up. . |
The tests should differentiate between GML loaded from a file and GML served by WFS. In QGIS, it is apparently a complete different part of the source code that handles that, so the results can be completely different.
One example is the handling of inheritance. E.g. when the geometry is defined on the supertype, geometries are not rendered at all.
See e.g. the service described at https://geodata-info.dk/srv/eng/catalog.search#/metadata/8e82f1df-1352-4375-83ce-503aa8425661 (the first link).
The text was updated successfully, but these errors were encountered: