This object is in archive!
Locus route(rte) file import to navigate
Completed
At navigation only promote those rtept's with a <sym> into active Nav or Via_Point.
At navigation only promote those rtept's with a <sym> into active Nav or Via_Point.
I like this idea 
+1
thanks for your idea
+1
thanks for your idea
As I was asked ;-) The benefits ?
A Viewranger compatible route(rte) gpx file format.
Also Locus should recognise the import of this easy route gpx file system. Simple and robust as this gpx route (rte) file format does not need (easily broken) timestamped tracks nor (timestamped) or eliminating the (harder to debug/edit) extension waypoint use. Easy edits fine tunings by additional external pc tools using autosynced gpx files. (Autosync dropbox).
Information:
http://forum.locusmap.eu/index.php?topic=5953.0
As I was asked ;-) The benefits ?
A Viewranger compatible route(rte) gpx file format.
Also Locus should recognise the import of this easy route gpx file system. Simple and robust as this gpx route (rte) file format does not need (easily broken) timestamped tracks nor (timestamped) or eliminating the (harder to debug/edit) extension waypoint use. Easy edits fine tunings by additional external pc tools using autosynced gpx files. (Autosync dropbox).
Information:
http://forum.locusmap.eu/index.php?topic=5953.0
The very similar alternative by gpx (trk)_navtrkpt method also should be considered.
As tracks, by standard, do contain multiple trackpoints probably a more popular choice ?
http://forum.locusmap.eu/index.php?topic=5953.msg51395#msg51395
The very similar alternative by gpx (trk)_navtrkpt method also should be considered.
As tracks, by standard, do contain multiple trackpoints probably a more popular choice ?
http://forum.locusmap.eu/index.php?topic=5953.msg51395#msg51395
Completed by v 3.38.7.1 "route(rte)gpx"
Completed by v 3.38.7.1 "route(rte)gpx"
Correct. Thanks for pointing it out. I expect emails with complains about new behavior, but I'm sure it's number will be lower thank complains about "how to get rid of this huge number of waypoints on the track".
So summary: next version "promote" only <rte> points in GPX to big waypoints in case, it has defined something extra, not just it's location & altitude.
Correct. Thanks for pointing it out. I expect emails with complains about new behavior, but I'm sure it's number will be lower thank complains about "how to get rid of this huge number of waypoints on the track".
So summary: next version "promote" only <rte> points in GPX to big waypoints in case, it has defined something extra, not just it's location & altitude.
Replies have been locked on this page!