I am absolutely sure that those numbers (coded coordinates) in the SQL (.db) file tables are different from original GPS coordinates used in other files like gpx, etc.
This is where I stand:
Right now I am working on putting together excerpts from the SQL (.db) file tables for Topo Austria v3 and Topo France v3 SudEst.
For these excerpts I am trying to find some of the shortest 'Named Trails' in the respective SQL (.db) files.
Since the 'nodes' are only identified by node IDs (just integers, no names or other hints given) in the SQL tables, we do not know where the node is located on a given trail (but we do know where the trail is, because BaseCamp shows it).
Therefore, in my thinking, shorter trails should have the advantage of smaller location uncertainty (by picking one or a few nodes on a short trail your margin of location error is smaller than on a long trail).
The results (data from the SQL tables and original GPS coordinates) will be provided in the form of comma-delimited CSV files, and they will be uploaded and posted ASAP after I have finished working on it.
This process is somewhat time-consuming, so please be patient...
Bookmarks