Thread: Data in SQL (.db) files

Originally Posted by p!xeldealer

Thanks for your interesting explanations. I had already the same idea, but not the time yet to do something.

I can't imagine, that the coordinates are relative coords. I think they are in somehow format, that must be possible to translate to any usable format.
Could you post here an part of these data?

I also think, it must be possible, to make a gpx file with all trails from this SQL files. From such gpx it is easily possible to make a .gpi-file or a transparent layer in .img format.

The SQL file 010-D1215-00.db (for TOPO France v3 DOM-TOM Pro) has 3 tables named 'trails', 'trail_segs', and 'garmin_metadata'.

The uploaded archive (around 39 kB)

[Only registered and activated users can see links. ]

contains the 3 tables in comma-delimited CSV format:

010-D1215-00trails.csv
010-D1215-00trail_segs.csv
010-D1215-00garmin_metadata.csv

The CSV format can be imported into most spreadsheet programs.
As I said, by sorting the table 'trail_segs' (in a spreadsheet) in various ways 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).
The big puzzle is how to get the GPS coordinates from the (integer values) 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).

PS:
I also found this in the SQL file 010-D1215-00.db:
CREATE INDEX adj_index ON trail_segs (map_id ASC, link_id ASC, org_node_id ASC, dst_node_id ASC)
CREATE INDEX trail_id_bbox ON trail_segs (trail_id ASC, org_pnt_lat ASC, org_pnt_lon ASC)
CREATE INDEX trails_bbox on trails(min_lon ASC, max_lon ASC, min_lat ASC, max_lat ASC)
Some guesses:
adj_index may mean adjoint or adjunction index (see en.wikipedia.org/wiki/Adjoint)
trail_id_bbox may mean trail_id boundary box
trails_bbox may mean trails boundary box