Offline Map
I have a large map in jpg tiles right now (Z/X/Y) directory structure. Its around 60GB :)
I have used MOBAC to create various forms of map files from that. MBTiles seems to be best so far.
Problem is that if you copy a large sqlite db file like that to an SD card, the data base corrupts instantly, every time.
I'd like to be able to use my map as an offline map source, but not sure how I can.
I know that I can rename the image extensions to .png.tile, and set that as an external map, but if that map is too large, the phone cannot handle so many files.
I thought it would be great if I could have my mbtiles map on a shared network drive, and access it right in Locus. I have been trying ways to natively mount a network drive into Androids file system to be able to use it in Locus, but that seems to be rather tricky, as most android kernels do not support cifs.
And so I ask you, what do you recommend I do? I would really love to be able to use my whole map, I have before using otg and an external SSD, but that too was problematic with the accidental disconnection of the cable etc.
Thanks
The same question
Hello Mynor,
60 GB seems to be quite big map on all common tasks. From my point of view, best should be to separate it into more (more then 20) smaller maps made in MBT or simple SQLite format. Hard to say if MOBAC supports this, I'm worried that it doesn't.
Such maps placed into one directory may work in Locus as a single map.
Hard to say what is causing your corruption of DB, anyway as I know from previous experience, SQLite implementation in Android has sometimes problems with huge SQLite databases, so rather keep it smaller.
Hello Mynor,
60 GB seems to be quite big map on all common tasks. From my point of view, best should be to separate it into more (more then 20) smaller maps made in MBT or simple SQLite format. Hard to say if MOBAC supports this, I'm worried that it doesn't.
Such maps placed into one directory may work in Locus as a single map.
Hard to say what is causing your corruption of DB, anyway as I know from previous experience, SQLite implementation in Android has sometimes problems with huge SQLite databases, so rather keep it smaller.
For about a year now, I've been trying to get my 60GB sqlite map file to work on locus, and I thought I would share what I've found.
I run Android cm12.1
I've tried the following things to hold the map file, with the following results:
Otg cable with portable hdd ntfs: success
Otg cable with portable ssd ntfs: success
Otg cable with thumb drive ntfs: fail
Otg cable with thumb drive exfat: fail
Micro SD card ntfs: fail
Micro SD card exfat: fail
Micro SD card ext4: success!!
Ideal was always going to be map file on an external SD card, but never got it to work because I only tried ntfs and exfat.
It seems like all types of flash media corrupts a large sqlite database upon copying if it has ntfs or exfat file system. For some reason, it seems to be working perfectly everytime when it's formatted ext4! Only took me a year of passing around with it.
For about a year now, I've been trying to get my 60GB sqlite map file to work on locus, and I thought I would share what I've found.
I run Android cm12.1
I've tried the following things to hold the map file, with the following results:
Otg cable with portable hdd ntfs: success
Otg cable with portable ssd ntfs: success
Otg cable with thumb drive ntfs: fail
Otg cable with thumb drive exfat: fail
Micro SD card ntfs: fail
Micro SD card exfat: fail
Micro SD card ext4: success!!
Ideal was always going to be map file on an external SD card, but never got it to work because I only tried ntfs and exfat.
It seems like all types of flash media corrupts a large sqlite database upon copying if it has ntfs or exfat file system. For some reason, it seems to be working perfectly everytime when it's formatted ext4! Only took me a year of passing around with it.
Ah so problems are based just on drive format and not directly on size of SQLite file. Interesting and thanks for sharing! Hope, more people find your discovery useful.
Ah so problems are based just on drive format and not directly on size of SQLite file. Interesting and thanks for sharing! Hope, more people find your discovery useful.
Replies have been locked on this page!