-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add WMS problem: 'NoneType' object has no attribute 'find' #23
Comments
Thanks @SaraRT. Looking deeper, MetaSearch uses OWSLib to test whether the WMS/WMTS/WFS/WCS is what it says it is, and this is where the problem happens. It appears that in this WMS's case the Capabilities XML INSPIRE definitions are giving problems to the XML parser. I also verified this using XMLSpy |
@tomkralidis the capabilities are valid xml isn't it? And QGIS is able to load the layers from it if I load it via the normal AddWMS route. |
Hi, |
@rduivenvoorde: it's being thrown out by OWSLib. As well, the XML is not valid. Here is exactly what is happening in OWSLib:
Testing in XML Spy yields similar errors. The WMS XML is just problematic. Having said this, MetaSearch does an OWSLib check to smoke test that the URL is what the metadata says it is by doing a GetCapabilities request and parsing it. It looks like the Add WMS dialogue in QGIS proper is not doing the same amount of checking. We could lift this checking, but then all responsibility goes to the OWS provider dialogues. Thoughts? |
Adding a WMS from a metadata using CSW it's came out this error message( see below):
An example of metadata with this problem is:
http://www.geoportale.piemonte.it/geocatalogorp/geonetworkrp/srv/it/metadata.show?id=1358
Any clue? Thanks.
The text was updated successfully, but these errors were encountered: