And what I forgot to mention: Do not use active overlaying maps. Say you have the map of entire Netherlands and a map of a subsection (province). If you have both maps active, so full Netherlands and the region you are currently in, *BOTH(!)* maps are rendered, giving you another reduction in rendering speed. Same of course when using the France Brittany full map and the France Brittany roads-only map, so having both active. Having one map active and the other inactive is fine.
Harrt 2018-04-28 11:19 GMT+02:00 Harry van der Wolf <[email protected]>: > > 2018-04-28 10:07 GMT+02:00 Eugene Muzychenko <[email protected]>: > >> On Saturday, April 28, 2018 at 2:32:02 PM UTC+7, Pere Pujal i Carabantes >> wrote: >>> >>> This would not be a problem if the world overview map contained enough >>> info as to route over the main roads it displays >>> >> >> If I understand correctly, OsmAnd does not handle overlapping maps a >> special way. If a local region map overlaps world/country map, both are >> rendered simultaneously. So there should be a setting to control rendering >> of overlapping maps. >> >> >> This is not correct. > > Below zoomlevel 11 the worldmap is used, meaining that the worldmap is > rendered. > Zoomlevel 11 is some ïntermediate level > > If you use inspector on a map you will see the following (note that > Bregenz is a map I made myself from a subpart of Austria. I only needed > that part and didn't want entire Austria): > Binary index Bregenz.obf version = 2 edition = Tue Jan 23 10:44:28 CET 2018 > 1 Map data Bregenz - 8086663 bytes > 1.1 Map level minZoom = 15, maxZoom = 22, size = 4950445 bytes > Bounds (left top - right bottom) : 9.5506, 47.5999 NE - 10.2402, 47.2221 NE > 1.2 Map level minZoom = 13, maxZoom = 14, size = 1819459 bytes > Bounds (left top - right bottom) : 9.5506, 47.5999 NE - 10.2402, 47.2221 NE > 1.3 Map level minZoom = 12, maxZoom = 12, size = 916619 bytes > Bounds (left top - right bottom) : 9.5506, 47.5999 NE - 10.2402, 47.2221 NE > 1.4 Map level minZoom = 11, maxZoom = 11, size = 377007 bytes > Bounds (left top - right bottom) : 9.5506, 47.5999 NE - 10.2401, 47.2222 NE > > So every zoom level uses its own of detail. > You can see on the sizes of the several 1.4 to 1.1 levels that the amount > of details increases. > Note also that I only showed the map levels here. The routing, POI and > Address sections do not come in levels. > > W.r.t. to rndering speed (or actually the opposite of it). I no longer use > OsmAnd for car navigation. I do use it for cycling and hiking as the level > of details in the OsmAnd maps is without compare to others and rendering > speeds can be low on cycling or hiking speeds. > I still follow OsmAnd very closely and occasionally I use it in the car. > In that case I always use the "roads-only" maps. They contain far less > details (are also much smaller) and render 2-4 times as fast. Then the > rendering speeds are acceptable (but still not good). > > > Harry > > > -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
