Closed lmenard closed 9 years ago
@lmenard thanks for the report. I am able to reproduce the error. MetaSearch uses OWSLib 0.8.8. There was an OWSLib bug that has since been fixed since OWSLib 0.8.10 (see https://github.com/geopython/OWSLib/commit/4e5e24840372028be2858c5c6897818bf6059282). So the OWSLib depedency in QGIS needs to be updated. I'll make this fix in QGIS by cutting a new MetaSearch release. So options are:
Hi Tom, thanks a lot for the extra fast reply. I think I will go for the simplest (at least for me) and wait for the next MetaSearch release. Will I be notify of the new release in this thread or elsewhere ?
Thanks again.
Lionel
@lmenard we usually tweet this. I'll also ping this thread.
@lmenard 0.3.2 is now at http://plugins.qgis.org/plugins/MetaSearch/. Can you try it out?
I updated the plugin successfully (see screencast) did a stop start but the bug is still there...
This might be due to Python path settings where perhaps QGIS is picking up the OWSLib in 2.6 (0.8.8), not 0.8.10. Can you try going into your QGIS and rename python/owslib
to something like python/owslib-old
? This worked for me, and forced MetaSearch to use the OWSLib version bundled with MetaSearch instead.
Done. Works fine (see screenshot). Any potential drawbacks due to this name changes ?
Thanks a lot and "Bravo".
Lionel
@lmenard thanks! The renaming is a temporary workaround. Once QGIS 2.6.1 / 2.8.0 is released this will be fully fixed. For now the issue seems to be bound to a small edge case.
Hi, I've installed MetaSearch on a QGIS 2.6.0 Brighton on Mac OS 10.9.5. I've been able to display some results (not for all) from default catalog collection. I've tried to include mine with the URL as follow: http://geocatalog.webservice-energy.org/geonetwork/srv/eng/csw
Though I can get successfully get the Information on the Service as well as the GetCapabilities response when I try to search for resources with or without keywords I get a pop-up window with the error as listed in the title of the email (see screenshot).
I did not see any reference to this error message in the GitHub.
Thanks for your help.
Cheers,
Lionel