This would improve the mapView redraw, because we don't request unnecessary data.įor drawing tracks/waypoints: Always apply the first DEM at the top of the view, regardless of the scale range. More specifically, for DEMs make the scale range controls cut off not only rendering but also loading or requesting the data. Once the track is created, we apply the DEM elevation filter, and we choose the 'dummy view' DEM.įor the map view: Make the scale range controls work identically for Maps and DEMs. Second, another view without DEM or with a lighter DEM where we draw the track. First, a 'dummy view' with a very dense DEM activated and without any map. This is good for drawing tracks and waypoints, but has the downside that moving and zooming out on the map slows everything down.Īnother problem is that the DEM data request is not visible, this leads some users to think that QMS is very slow loading maps, not realizing that the problem is that they have activated a too dense DEM for the zoom level they are using.Īlternatives to handle this in the current version:ĭeactivate/Reactivate the DEM according to the zoom level, which is a bit boring, and then we have already lost the advantage we had to get elevation data while drawing a track.Ī trick for drawing tracks: Use two views. Even if we are outside the scale range, QMS always loads/request elevation data, regardless of whether the scale range is enabled or not. This is really useful to hillshade garmin maps, but for now you are requesting all the data.įor elevation profiles and status line, QMS gives us the data of the first one it finds, so the logical thing is to place the densest one on top, then another one more coarse.īut to make this work smoothly it is essential to limit the data load with the scale range slider.įor now, the only effect of the scale range is on the display of hillsade, slopes and elevation limit. It makes more sense to work as with maps, loading two DEMS with different resolution, one on top of the other, and control which one will be used with the scale range controls. However, this makes no sense if you make a very outer zoom with a very dense DEM, because at a distant zoom level you don't have enough precision with the mouse to know what point you are pointing at. One might want to cut the hillshading but still see the elevation data. Make the scale range controls work identically for Maps and DEMs. Then, after scrolling the map and zooming in, re-activate it, which is tedious and illogical. This leads to slow down the loading of the map when zooming out, and to avoid it the only remedy is to disable the DEM. However, even if you limit a scale range, QMS still loads/requests the elevation data for all the canvas area. Consequently, QMS does not load or request the map out of that range.įor DEMS: you can control the visibility of hillshading, slopes, and elevation limit with the scale range control. Is your feature request related to a problem? Please describe.įor maps: You can control visibility with the scale range controls.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |