Thread: Data in SQL (.db) files

Originally Posted by acleite

IMHO, org_pnt is Origin Point and dst_pnt is Destination Point of the trail.
And Lat/Lon data in csv file are in Decimal degrees. (separate the first two digits before the comma and the rest after the comma, and test)
Then -250320992 should be the same as -25.0320992
And so on for all coordinates.
Checking on Google Maps, this sample point (-25.0320992,66.0638272) is in sea at a point described in the coverage area of the map you used. (TOPO France v3 DOM-TOM Pro)

See the coverage area map: .....

Well, it's only my humble opinion ...

When you look at TOPO France v3 DOM-TOM Pro, you see that the trail GR G1 on Guadeloupe extends roughly North-South between a point named 'N2 and Alley1' (latitude 16.353294, longitude -61.751871) and a point named 'Light House1' (latitude 15.948334, longitude -61.707566).
The integer values for latitude and longitude given in the table 'trail_segs' do not fall into this range (when adjusted according to your suggestion).
In fact, your mentioned sample point (latitude -25.0320992, longitude 66.0638272) lies in the Indian Ocean (approximately 1900 km E of southern Madagascar). That is not where Guadeloupe is located.
Also, the integer values for the (presumed) latitudes and longitudes given in the table 'trail_segs' can be positive as well as negative (indicating N or S latitudes and E or W longitudes).
The solution to the (coordinate) puzzle is probably not as simple as making some decimal adjustments.