Author Topic: GEMF: converted to sqlitedb  (Read 1239 times)

Offline stebu

  • Expert
  • Padavan of Locus
  • ***
  • Posts: 252
  • Thanked: 1 times
    • View Profile
  • Device: Xcover 2
GEMF: converted to sqlitedb
« on: September 12, 2013, 17:25:24 »
I started a new thread, because this is not a speed issue.
wait converted?? nono, nothing like this is possible with Locus :)

Well all my personal files (.SQL and former .GEMF) seem to have a mapname.sqlitedb-journal file associated, date = 9/8/2013.
This is the date I upgraded my phone from ZTE Blade to Xcover 2. I just moved the SD card and re-installed Locus PRO.

One of my original GEMF maps causes an error and will not load, 2 others work well.

The (assumed) conversion probably thought, that the maps used ellipsoidal model, but they had spherical. I do not remember if we ever solved how this data is placed into GEMF file. The provider number wasn't a global solution.

Currently I have only "academic" interest in GEMF maps, other maps provided by Locus are just fine!
 

Online Menion

  • Locus team
  • Professor of Locus
  • *****
  • Posts: 12535
  • Thanked: 797 times
    • View Profile
    • http://www.asamm.com
  • Device: Pixel 5, A12
Re: GEMF: converted to sqlitedb
« Reply #1 on: September 18, 2013, 08:10:17 »
Hello stebu,
  hmm so used some external tool to convert Locus SQLite database right?

  problem you have is same as should appear in SQLite maps. There is also not any general information if map use sphere, ellipsoid or some other projection, it just store tiles by x, y and z parameter.

  So even a native SQLite maps use "provider ID" as main parameter to set correct map projection on source tiles. Same it's with GEMF format
- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 final download