-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
WMS not working on master a625eeb (2.15.0-80) #22923
Comments
Author Name: Pedro Venâncio (Pedro Venâncio) Loading the WMS with a geographic CRS (WGS84), which is also supported by the server, already shows the content on canvas. But it is very slow, as it is showing tile by tile, which was not the standard behaviour on 2.14.3 nor the yesterday's master behaviour. |
Author Name: Nyall Dawson (@nyalldawson) Should be fixed (d77a33) in tomorrow's build -
|
Author Name: Pedro Venâncio (Pedro Venâncio) Thanks Nyall! |
Author Name: Pedro Venâncio (Pedro Venâncio) Hi Nyall, I'm reopening this bug report, but I don't know if this is related with the same question fixed in d77a33. The WMS continues to not show up on the canvas in QGIS master, and comes up with the wrong layer extent. But I realized the source of the problem. I'm using mapserver as WMS server. So, if I declare the CRS in the mapfile, pointing to a NTv2 grid file, like this:
in GetCapabilities I get:
the CRS is empty, but the extent is correct. With this configuration, QGIS 2.14.3 works great and load the WMS layer in all CRS that are provided by the server. QGIS master loads the layer without any error message, but it does not show anything in canvas. It only works if I choose EPSG:4326 in QGIS WMS provider. Instead, if I declare the CRS by the EPSG code in mapfile
the GetCapabilities shows
and QGIS master already shows the WMS layer in canvas.
|
Author Name: Christoph Candido (Christoph Candido) The problem even exists in qgis-dev 2.15.0-85 f1ec121 (OSGeo4W x86). The QGIS WMS Client only accepts CRS 4326 and 3857. With EPSG:3857 and EPSG:4326 everything is fine. |
Author Name: Even Rouault (@rouault) @Christophe Could you paste or give a link to the GetCapabilities ? |
Author Name: Nyall Dawson (@nyalldawson)
|
Author Name: Christoph Candido (Christoph Candido) Even, you point me in the right direction! The problem lies in the "GetCapabilities" response.
|
Author Name: Christoph Candido (Christoph Candido) Sorry, I was wrong. |
Author Name: Christoph Candido (Christoph Candido) Nope, i revise my last statement. Can I disable the WMS area-of-use restriction with a local user setting? |
Author Name: Pedro Venâncio (Pedro Venâncio) Hi Christoh, From my investigation, I think the problem is in the explicit declaration of the BBox CRS, with the corresponding EPSG code. If you see here
the BBox extent is the same in both cases in GetCapabilities, but QGIS master only interprets the BBox correctly in the second case, except for WGS84, that works in every case. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Martin Dobias (@wonder-sk) Pedro, is it possible to access the WMS server somewhere so we can test it?
|
Author Name: Martin Dobias (@wonder-sk) Fixed in changeset "0409f5e30cfaab7a0baf2f127c4c30c68a65d29f".
|
Author Name: Martin Dobias (@wonder-sk) (Thanks to Pedro who provided me with WMS server to replicate the problem) |
Author Name: Pedro Venâncio (Pedro Venâncio)
Original Redmine Issue: 14974
Affected QGIS version: master
Redmine category:web_services_clients/wms
WMS are not working on the master (qgis-dev 2.15.0-80 a625eeb OSGeo4W 64bits). With yesterday's master version, they were working very well.
The problem I see in the metadata properties is in the layer extent.
The WMS I'm using, uses a projected CRS, and it works ok in QGIS 2.14.3, with the following layer extent:
Strangely, with today's QGIS master, it takes a geographic extent, although the CRS is projected, and it shows nothing in canvas:
As I said, with yesterday's master version it was working well. So it must have been caused by any recent change.
The text was updated successfully, but these errors were encountered: