Thread: Data in SQL (.db) files

For new readers:
We are trying to figure out how coordinate data is coded and stored in the SQL (.db) files that accompany the newer Garmin topo maps (and allow searching for 'Named Trails' in BaseCamp, and in some of the newer GPS units).

The provided information enables us to compare the coded coordinate data from the SQL files with original .gpx coordinate information (and hopefully arrive at a way to decode the coded coordinate data).
If we are successful, we will have access to the route information stored in the SQL files.
This in turn will allow us to use this route information with products (mapping software and GPS units) that cannot access the SQL file information directly.
I have put together excerpts from the SQL (.db) file tables for Topo Austria v3 and the corresponding .gpx (track) files (archive size less than 15 kB):

[Only registered and activated users can see links. ]

For these excerpts I have tried to find some of the shortest 'Named Trails' in the SQL (.db) file 010-D1199-00.db for Topo Austria v3 (see previous posts).

The files in the archive are:

010-D1199-00SelectedTrailsC8231729.csv
Excerpt from table trails providing the selected trail IDs and names and boundary information.

2 files for each named trail (file name starts with trail ID, followed by trail name):
The .csv files are excerpts from the table trail_segs (trail segments); for the data provided please see previous posts.
The .gpx files provide track data from BaseCamp 3.3.3 (tracks matching the named trails as exactly as possible).

Please see previous posts for supplementary information.
Right now I need a break.
Then I may start working on doing the same with Topo France v3 SudEst (unless the 'big coordinate puzzle' is solved before).

I hope that we will find a solution.