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
Hello,
I'm developing a plugin for QGIS and I've noticed that my code can no longer handle a particular OGC service in the latest stable version of QGIS. Here are the URLs of the services involved:
Perhaps the problem lies in the fact that these are services whose Content-Type is ‘application/octet-stream’ and not ‘application/xml’.
I don't know if this is a bug or if I just couldn't find the information on how to handle this with owslib 0.32.0. In any case, is there a workaround for this problem?
The text was updated successfully, but these errors were encountered:
SimonSAMPERE
changed the title
owslib.wms.WebMapService and owslib.wfs.WebFeatureService creation fails with application/xml content-type servicesowslib.wms.WebMapService and owslib.wfs.WebFeatureService creation fails with application/octet-stream content-type services
Mar 18, 2025
I've implemented a workaround in the code of my plugin to parse the XML directly.
I hope that this PR will be approved, that it will lead to the publication of a new version of owslib and that this new version will be quickly integrated into a future version of QGIS. 🤞🏼
Anyway, congratulations and thank you @geographika for your responsiveness.
Hello,
I'm developing a plugin for QGIS and I've noticed that my code can no longer handle a particular OGC service in the latest stable version of QGIS. Here are the URLs of the services involved:
I've tried to investigate and to sum up, the following python code works well with
owslib
version 0.29.2 but not with version 0.32.0:With
owslib
0.32.0 aValuError
is raised by thegetXMLTree
method ofutil.py
.Here are some files with the entire error using owslib 0.32.0:
Perhaps the problem lies in the fact that these are services whose Content-Type is ‘application/octet-stream’ and not ‘application/xml’.
I don't know if this is a bug or if I just couldn't find the information on how to handle this with owslib 0.32.0. In any case, is there a workaround for this problem?
The text was updated successfully, but these errors were encountered: