2gb map limit

Myron Reimer shared this problem 3 years ago
Solved

I've made a fairly large map in the MBtiles sqlite format. I can't load it with locus, it says an Android limitation of 2Gb. The same map file works fine with Orux. Is there a fix for this?? I paid for Locus Pro, and prefer it over Orux!!

Comments (16)

photo
1

Good day Myron,


may I ask you, what device you use? This limit was on older devices with 2.X Android on board. Is this your case? Because otherwise this limit is 8, maybe even 16 GB?


I'm also surprised that map works in different app. 2 GB limit was limitation of internal SQLite database engine of Android. Interesting.

photo
1

I'm using a note 3 running cyanogenmod 11 (android 4.4).

photo
1

Hmm seems to be wrong "Hardcoded" text that warns about 2GB.


How big is your map?? It should be bigger then 16 GB. Is it possible?


And it works really correctly without any issues? Seems that in new Android devices is limit on SQLite database completely removed. Unfortunately it should be just some improvement in CM ROM. Is anyone using such huge map on own device with Stock rom?

photo
photo
1

I haven't tried the map on a stock rom yet. I will try to do that today. Thanks for your help so far.

photo
1

You have this possibility? Perfect. Then please try it. If there won't be any problem, I'll completely remove this limitation on 4.4 devices to next Locus version. Thanks for help!

photo
photo
1

Stock android does not read NTFS SD cards, which is needed to put my map file on to it, because it's too large a file for fat32.

Cyanogenmod includes NTFS built in. I think someone made something which allows stock Roms to use NTFS, so I'll have to try that yet.

photo
1

Hmm good point with NTFS.


Anyway stop - I don't want to waste you time with this. Limitation on more then 16 GB do not have any serious reason as I think about it. Such huge file is limited by FAT32 and also by time spend to download it :).


I'll remove this limitation to next Locus version as I now do not see good reason to keep it. Thanks for your time!

photo
photo
1

Any idea when the next version will come out? Thanks

photo
1

it will take some time now. I'll be really glad for last week in January. Anyway expect it rather at start of February.

photo
photo
1

I also just confirmed this issue. I have a map in mbtiles that is 1.8GB that loads fine and any map I create that is larger than 2GB will not load. I never receive an error, Locus just tries to load it and the loading progress bar never completes.

photo
1

What version are you using? The new version fixes any limitation on SQL files. Also, I've experienced the same problem as you, but if I close the app, and reopen it (make sure to fully close it), the map loads better when the app loads from scratch for some reason.

photo
1

I am using 3.6.2. I transferred the files to default Locus directory on the device and also tried it on an external microsd card formatted exFAT. The file does load fine in Oruxmaps on the same device. After force closing Locus and restarting, it goes right back to the initializing map screen and never loads (I have waited over 40 minutes).


My device: Samsung Galaxy Tab S 8.4 (Android 4.4.2)

photo
1

Hello Brandon,


hard to say where is a problem. May you try to place your device to power-charge and let it be for longer then 40 minutes? Usually even for a big maps it took around max 5-10 minutes, but just in case ...


Also there is a possibility to create a log where should (or should not) be any useful information what happen on background - http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log


Sorry for a troubles

photo
photo
1

Hi everyone!

Perhaps interesting fact: My biggest map is 24.7GB, sitting on an exFAT formatted microSD card. Has been working flawlessly since at least 3.3.0 on an Android 4.4 device. It's definitely sqlite, dunno about MBtiles.

photo
1

Thanks for all the help. I finally got the map to load after 1 hour & 30 minutes. Now that it is loaded, it works great! I also tried the map on another device and it took about 1 hour & 10 minutes to load (Galaxy S5). Debug log did not show anything useful. It is kinda weird that my maps under 2GB load in less than 5 minutes and I have 2 maps that are between 2gb and 3gb that take over an hour. The only difference I can think of is I am generating more tiles (non transparent) at zoom 21.

photo
1

Brandon, for me it is sometimes also mystery why simple request into database may took more then even 10 minutes. Anyway I'm glad it works for you now! Enjoy