This object is in archive! 

Cannot obtain zoom levels

Mark Brough shared this problem 8 years ago
Not a Problem

I archive my (Bing raster) maps on a PC and import them back to Android (Nexus 10) as needed.


For the first time, when opening Locus Pro after depositing files (.sqlitedb-journal and .sqlitedb) into Maps folder, Locus reports "error: Cannot obtain zoom levels".


I then tried using the Locus menu option "Import data" and received error "Problem with <filename>.sqlitedb"


This has happened with two different (Bing) maps, that is, two pairs of files (.sqlitedb-journal and .sqlitedb).


Previously, this method of archiving-and-reloading maps has worked fine. That is, these two maps have been imported in this way previously without problem.


My Android, Locus Pro and PC W8.1 are running up to date versions. Locas was closed when copying the maps across.


Regards, Mark.

Replies (8)

photo
1

Good Mark,


hard to say where is a problem to be true. Should be an issue in copy of your files. Also should be a problem in your device ( in case you use OnePlus2 device http://help.locusmap.eu/topic/sqlite-offline-maps-not-working-on-oneplus-2 ).


Really suggest to copy maps into device one more (or with different method). If this won't be a problem, we should try to create a debug log to check what exactly is a problem with these maps. Alternatively you may try to share one of your map, so I may test it map itself is fine.

photo
1

Thanks for suggestions Menion.


I am attempting to upload the pair of files for one of the maps using the "Attach a file" button here. However this web page gives me the error "<file> has incorrect file type".


Cotswolds.sqlitedb-journal size 97KB

Cotswolds.sqlitedb


I tried adding the extension ".nul" after these filenames - that did not help. Please tell me how to share the map to you.


My device is Nexus 10, not OnePlus.


I have tried copying the files across from PC to Android several times. I do not believe this is the problem - never any problems copying files successfully from Windows to Android.

photo
1

I have now reproduced the problem on my Nexus 4 phone. So that means that the problem is independent of hardware.

photo
1

I note from this Locus Knowledge Base article that what I have been doing to archive maps off-device is a supported feature:


http://docs.locusmap.eu/doku.php?id=manual:user_guide:maps_external

photo
1

Good day Mark,


unfortunately your map file seems to be corrupted. When I try to open this file with any desktop SQLite viewer, I get error code 14. My colleague suggest to read any of these methods http://docs.locusmap.eu/doku.php?id=manual:advanced:map_tools:corrupted_sqlite , which may helps.


So I suggest to check your SQLite file on PC, if is valid then transfer to device and check it also on device (by any MD5 hash or at least by filesize). There is nothing more I may do for you, sorry. (btw. I remember that some guys some time ago also wrote similar problems and solution was to use different method how they uploaded map from PC to device). Good luck.

photo
1

Thanks for your investigation Menion. I cannot believe that the corruption is caused by moving from device to PC or back - this is a process which works day in, day out for other files with never any corruption. Since it has happened with two different files and two different devices then I suspect the Locus software somehow.


I shall raise this as an "idea" feature request. We are all aware of the madness whereby today's devices (mostly) do not have SD card slots, and so Locus needs to have a robust mechanism for archiving maps off-device, and then bringing them back "on board" when needed, without any hassle.


Regards, Mark.

photo
1

Mark, believe or not, database I downloaded from your Google Drive is already corrupted. Even without moving it to my own device. So there probably had to be some issue during your backup. Idea on backup of data is already existing, but it is not so simply to implement ...

Replies have been locked on this page!