UPDATE ! Locus 3.50.1
Operational ! (Import)Navigation by gpx track navigation instructions into trackpoints.
Instructions in trackpoints trkpt.Trackpoints that contain a Locus standard
[EN]sym text are
promoted to navigation
Turn points.
Trackpoints that contain the [EN]type Via text are promoted to be announced Via points.(Not yet)
Trackpoints that contain the [EN]type Shaping text are promoted to Shaping points.(Not yet)Only the Turn and or Via points lead to navigation alerts and give distance values @ navigation.
Advantages.
- Navigates 100% faithfull after gpx track import even without (routable) maps present in the app.
- Manage/separate the free located (poi) waypoints without any risk to damage the navigation.
- Easy import, navigate 100% faithfull without "must" set: "Merge waypoints with imported track".
- Less fragile than the *
trk_navwpt method with the more vulnarable associated waypoints.
- Compact POI wpt_list not cluttered by many associated wpt's as by the *
trk_navwpt method.
- Synced gpx files to pc offers extra edit tools or an alternative for only Locus edit.
- You can simply add multiple additional selected freely positioned wpt's(poi) into the gpx file.
-
Timestamps are not obligatory for navigation, but can be attached according to expected speed- A single gpx file can also contain multiple
navigation tracks including turn-by-turn instructions.
Contains the original plus several free to select alternative navigation tracks to choose from.
The <sym>pass_place is to be used for compatibility with the current Locus versions.
Find the <sym>pass_place in the start, the via, the shaping, and finish trackpoint.
The trackpoints with <sym>pass_place optimally has a <name> indication. (Start - Via - End)
The Shaping or Via points are separately indicated by the trackpoint <type> tag.
Similar functionality as the <type> tag supported in the route (rtept) routepoints by the Cruiser app.
Indicate the Shaping or Via Points by the trackpoint <type> tag.
Keep the point type tag intact this as well in the original offroad imported routepoints and in the generated onroad resulting trackpoints.
Results in perfect snapped to street planner points. The Shaping or Via point function is kept intact[/b].
Unexpected U-turns are alert signals for track glitches caused by badly positioned planner points.
Indicate the triggering Planner point positions that do cause the U-turns by a blinking dot.
Correcting the planner point positions than removes so these unexpected U-turns.*
trk_navwpt method: https://t.ly/lXkV More info in attachment. (Register and login into the forum !)https://youtu.be/h8XByisAAbQExport by the Route You Planner.
https://t.ly/1t85Update.
@ gpx IMPORT.
Locus map app. (V3.50.1)

Turninstructions by trkpt <sym> (turn text) & Via Points by the trkpt <sym> pass_place

No Shaping nor Via Point imports by the trkpt <type>. (
not yet)
Cruiser app.

Shaping and Via Point transfer in a gpx (rte)route by point <type> in the (rtept) routepoints.

Has no gpx navtrack support.
@ gpx EXPORT.
RouteYou web Planner by Locus gpx.

Turn instructions inclusive U-turns.

Shaping & Via Point exports by <type>.

No trackpoint timestamps.

No roundabout support yet. (planned)
Cruiser app.

Shaping and Via Point transfer in a gpx (rte)route by point <type> in the (rtept) routepoints.

Has no gpx navtrack support.
Attachment picture.
A Kurviger forum idea proposal..
Indicate Planner Points that do trigger U-turns by a blinking red dot.
If necessary move a planner point until the "blinking" halts