-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
QGIS Server - GetMap URI inconsistency #14651
Comments
Author Name: Paolo Cavallini (@pcav)
|
Author Name: René-Luc ReLuc (@rldhont) Hi Marco, I think this bug has been fixed. Can you closed it ? Regards,
|
Author Name: René-Luc ReLuc (@rldhont) I think this issues can be closed, isn't it ? |
Author Name: René-Luc ReLuc (@rldhont) Marco, can we close this issue ? |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Andy Harfoot (Andy Harfoot)
Original Redmine Issue: 4799
Affected QGIS version: master
Redmine category:qgis_server
Assignee: Marco Hugentobler
Using the OSGeo4W package installer on Windows7 64bit I installed QGIS Server 1.7.3-1, Apache 2.2.14-4 and associated dependencies including fcgi. I created a demo project in QGIS Desktop 1.7.3-1 and successfully returned a GetCapabilities document in my web browser.
The next step was to try to access the QGIS server WMS in various GIS packages (QGIS, MapInfo and ArcGIS). In all cases the software was able to parse the GetCapabilities document, however I could not view the data. Generating a GetMap request in my web browser did return a map image though. Eventually I got a WMS layer to display in QGIS Desktop by enabling the 'Ignore GetMap URI reported in capabilities' option in the WMS connection setup dialog.
The same problem is reported here:
http://osgeo-org.1803224.n2.nabble.com/I-can-not-visualize-the-WMS-Service-from-the-QGIS-Server-at-a-desktop-GIS-td6783271.html
and here:
http://lists.osgeo.org/pipermail/qgis-user/2011-November/014252.html
As reported in the second thread above, the problem appears to stem from the fact that the GetCapabilities document reports the GetMap link omitting the http: prefix. An excerpt from my test GetCapabilities document is shown below:
I believe this is a bug, and is restricting the functionality of what would otherwise be a very quick way to set up a WMS service.
The text was updated successfully, but these errors were encountered: