This object is in archive! 

Map naming and zoom levels

Przemysław Burzyński shared this question 8 years ago
Answered

I noticed that locus automaticly tries to detect different zoom levels in offline maps (but I don't understand how it works)

1) I have 4 maps in /sdcard/Maps/Slaskie named: "Slaskie'N_A 1.100 000.tar" "Slaskie'N_B 1.100 000.tar" "Slaskie'S_C 1.100 000.tar" "Slaskie'S_D 1.100 000.tar" - Locus thinks they are different zoom levels when in fact it is different coverage.

2) I have few maps in few folders in/sdcard/Maps/Atlas_JuraSETKA_2015/ There are next folders named: Jura100; 01_Rudno; 02_Zabierzow and they contain seperate maps Jura100.tar; Rudno.tar; Zabierzow.tar. It this case Jura100.tar is map covering large area and rest folders are zoomed in fragments of this map. Is there any way for locus to load Jura100 map first and use other maps as zoom levels when at correct lat/long?

I hope I asked my question in logical way... I attached map files in .zip just in case you need to see what I mean.

Nexus 5 | Android 5.1.1 | Locus PRO

Replies (1)

photo
1

Good day Przemysław,

unfortunately I have to say, that support for TAR maps in Locus is far away from being perfect. It was format that Locus used five years ago and since then, system is almost same.


So issue one is correct - every maps placed in any subdirectory in Locus/maps is considered as separate zoom levels. Second question is unfortunately also not possible.


First issue should be solved if you place all maps directly into Locus/maps directory. If you then in settings > maps - advanced, enable "auto-loading", it should work and Locus should correctly load required maps.


Second issue anyway do not have a solution for now.


As you may see, there is not a big interest in TAR format ( http://help.locusmap.eu/search/tar - just search for "tar" word ), which I use to excuse of bad implementation of this format.


Thanks for understanding.

Replies have been locked on this page!