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
Author Name: Dave Sampson (@samperd)
Original Redmine Issue: 16261
Affected QGIS version: 2.18.4
Redmine category:metasearch_catalogue_client
Assignee: Tom Kralidis
As a metasearch user
I want to access entries in catalogues that include a full GetCapabilities URL
So that these types of URLS don't fail and I can view a WMS or other OGC service within QGIS
---------------------------
WMS Provider
---------------------------
The server you are trying to connect to does not seem to be a WMS server. Please check the URL.
---------------------------
OK Hide Details...
---------------------------
when you enter URL with double params (created by Metasearch) you also get the error
Likely issue is in metasearch sending OWSLib an invild URL because the catalogue maintains the full GetCap string. Not sure if best to fix in Metasearch or OWSLIB.
Due to various business rules the actual GetCap request is managed in the catalogue.
The text was updated successfully, but these errors were encountered:
Implemented in 2.14 branch, 2.18 branch and master. Will be available on the next plugin release of MetaSearch or 2.14.13/2.18.5 on 24 March 2017 (whatever comes first)
Author Name: Dave Sampson (@samperd)
Original Redmine Issue: 16261
Affected QGIS version: 2.18.4
Redmine category:metasearch_catalogue_client
Assignee: Tom Kralidis
As a metasearch user
I want to access entries in catalogues that include a full GetCapabilities URL
So that these types of URLS don't fail and I can view a WMS or other OGC service within QGIS
Details:
#Reults in the following error:
Likely issue is in metasearch sending OWSLib an invild URL because the catalogue maintains the full GetCap string. Not sure if best to fix in Metasearch or OWSLIB.
Due to various business rules the actual GetCap request is managed in the catalogue.
The text was updated successfully, but these errors were encountered: