Just a few notes on that: 1) If the map is loaded correctly but drawing is suppressed because it would take too long, the map boundary is still visible as a black frame.
2) You can override that behavior at any time by defining a range of zoom levels. This is done with the bar and the two buttons in the map's properties. See https://bitbucket.org/maproom/qmapshack/wiki/DocControlMapDem#markdown-header-map-and-dem for details. 3) My experience is, that raster maps get quite useless when minimized by factor 6 and larger. Either you switch to a version of the map that matches the scale or you kick in TMS maps or vector maps when zooming out. You can control that for every map with the two buttons. That said QMapShack has a much better map handling than QLandkarte ever had. All my raster maps are switched off at a certain zoom level and a vector map is replacing them. For all areas I do not have a vector map a TSM map like Bing, Google or OSM kicks in. And if that does not fit I can move maps in the draw hierarchy or add another map from the archive. And if I messed up completely I can load my default map configuration from file. Am 03.05.2016 um 22:15 schrieb M.Z.O: > Hi Axel and all > > I have experienced something similar with some ECW files, they are > well and very fast shown in QlandkarteGt at every zoom level, but they > only appears at a very close zoom level in QMS. > > In the past I noticed about this here and Oliver posted this answer: > > Hi Mitxel, > > > > (...) > > > > If you have a layer of raster maps reading the files and scaling > the content to an upper zoomlevel is getting more and more > resource intensive the more you zoom out. To avoid endless map > loading, QMS will skip the map if the effort to display it is > getting too large. > > > > However if QMS detects overview levels attached to the map it will > use them. gdaladdo is the tool to do so. Things are getting a bit > more difficult for insane large map collections. gdaladdo will > create an overview file over all maps combined in the vrt. That > might get too large. In this case you have to create single > overview files and combine them in a vrt. > > > > HTH > > > > Oliver > > > this is a pity for me because I lost some zoom levels in QMS that were > very useful ( I was able to read all the texts in the map at that > levels ) and IMHO QLGT was more flexible and useful with this..... but > I will survive ;-) > > To Know if your problem is conceirning the same you can try this: > > 1- in Qlandkartegt: load the same VRT file( Archive-> load map) ¿can > you see it at every zoom level? > > 2-In QMS: once the VRT is active, first of all make sure that the view > is in the area covered by your VRT/greotif map. To do so you can load > a wp or track and zoom to it. Then try to make zoom IN , to get closer > and closer, and the map should appear at a certain zoom level. > > Hope it helps > > > > > > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > > > _______________________________________________ > Qlandkartegt-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
