-
-
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
QGIS 1.3.0 does not respect WMS scales #12080
Comments
Author Name: Jürgen Fischer (@jef-n) Replying to "jrh":/issues/show/2020:
I doubt that this is true. Are you sure you're using the same server with 1.0.2 and 1.3.0? QGIS doesn't know about those settings. It justs requests a bitmap with:
mapserver needs to decide what's visible in the bounding box and on the layers. |
Author Name: jrh - (jrh -) I'm certainly no expert on Mapserver, so it is more than likely that the server is misconfigured and happens to work in QGIS 1.0.2, [[OpenJump]], UDig, but not in 1.3.0, so I'll have a further look at that. I also note that 1.3.0 passes the layers to the mapserver in the opposite order than 1.0.2 does, which in this case (layers are also ordered in the map file), may explain what's going on, if that's significant. "GET /maps?map=/var/www/maps/osm-gshhs.map&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap "GET /maps?map=/var/www/maps/osm-gshhs.map&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&BBOX=-1.677925,50.833438,-1.382075,51.026562&SRS=EPSG:4326&WIDTH=1081&HEIGHT=705&LAYERS=villes%2Coneways%2Cbridges%2Csports%2Cbuilding%2Ctram%2Caeroways%2Cpedestrian_hack%2Chighways-close%2Chighways-far%2Crailways%2Clanduse_layer6%2Clanduse_layer5%2Clanduse_layer4%2Clanduse_layer3%2Clanduse_layer2%2Clanduse_layer1%2Cgshhs_pond%2Cgshhs_isle%2Cgshhs_lake%2Cgshhs_land%2Ccountries&STYLES=%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C&FORMAT=image/png&DPI=96&TRANSPARENT=TRUE HTTP/1.1" 200 76055 "-" "Quantum GIS - 1.3.0-Mimas" Thanks |
Author Name: Jürgen Fischer (@jef-n) Replying to [comment:2 jrh]:
You can reorder the layers in the second tab (I think that was introduced in 1.3). Looks like the layers are in reverse selection order by default. |
Author Name: jrh - (jrh -) Replying to [comment:3 jef]:
Even easier is to click on the 'Id' tab in the Add Layer window. However, it would be easier if the dialogue worked like 1.0.2 and retained the MS provider order rather than inverting it. But I now know how to make it work like 1.0.2. Thanks for the pointers. Priority amended accordingly, please drop if you see fit. -jh |
Author Name: jrh - (jrh -)
Original Redmine Issue: 2020
Redmine category:web_services_clients/wms
Assignee: Marco Hugentobler
Using a WMS with many layers (served by Mapserver 5.4.2), with a number of layers with scales defined with {MIN,MAX}SCALEDENOM values to control layer visibilityI observe the following:
Using QGIS 1.0.2, the data is displayed as expected, e.g. layers are drawn respecting the current scale in QGIS, in accordance with the map {min,max}scaledenom definitions;
When using QGIS 1.3.0, the data is not drawn as expected, the zoomed out layers are drawn over the more detailed layers, regardless of the actual scale, making 1.3.0 un-suitable as a WMS viewer.
Unfortunately, 1.0.2 does not build in Ubuntu 9.10, so Karmic users lose the best Linux WMS client.
-jh
The text was updated successfully, but these errors were encountered: