Thread: Data in SQL (.db) files

The SQL (.db) files contain the information that is used to display the routes of the 'Named Trails' (in BaseCamp, and in some of the newer GPS units).
It would be nice to use the data in these files to create routes, tracks and/or waypoints for the older GPS units (and for MapSource).
Since the SQL (.db) files are not locked, it is relatively easy to extract the data in the two relevant tables 'trails' and 'trail_segs' (trail segments).
I started with the SQL file 010-D1215-00.db (for TOPO France v3 DOM-TOM Pro), because it is relatively small (and probably easier to figure out than the larger ones).
When I search for 'Named Trails' in TOPO France v3 DOM-TOM Pro, only one is found ('GR G1', going roughly North-South on Guadeloupe).
The table 'trails' lists several trails (with different IDs and names), but I guess these separate trails are part of the whole 'GR G1'.
The table 'trail_segs' (trail segments) has the column headings dbg_line_id (??), map_id (obviously map ID), link_id (a link is possibly several nodes linked together), trail_id (IDs from table 'trails'), org_node_id (probably origin node ID), dst_node_id (probably distant node ID), org_pnt_lat (probably origin point latitude), org_pnt_lon (probably origin point longitude), dst_pnt_lat (probably distant point latitude), and dst_pnt_lon (probably distant point longitude).
It should contain most of the interesting data (the GPS coordinates of the route - or track - nodes).
Unfortunately, the GPS coordinates given are not absolute GPS coordinates, and it is not obvious how the Garmin people arrived at the values given in the table.
My guess is the values given are somehow coded (or maybe relative) coordinates.
I sorted the table 'trail_segs' (in a spreadsheet) in various ways (by the data in the different columns).
From this it is possible to find out how some of the nodes go together to form a chain (or maybe link - a tiny part of the whole trail).
This is as far as I got.
Maybe someone with more experience (and/or brainpower) can take a look (and possibly figure it out)?