UPDATE ! Locus 3.50.1 Operational ! (Import)
Gpx track navigation.
Instructions in trackpoints trkpt.
Trackpoints that contain a Locus standard [EN]sym are promoted to navigation instruction points.
The promoted trackpoints that contain [EN]type Via are considered announced Via points.
The promoted trackpoints that contain [EN]type Shaping are considered not announced Shaping points.
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 but recommanded and 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.
(Announced by TTS) via trackpoints by the <sym>pass_place additionally can have a <name> indication.
Via or Shaping points are optionally and additionally indicated by the trackpoint <type> tag.
*trk_navwpt method: https://t.ly/lXkV (https://t.ly/lXkV)
More info in attachment. (Register and login into the forum !)
https://youtu.be/h8XByisAAbQ
Export by the Route You Planner.
https://t.ly/1t85
Update.
@ gpx IMPORT.
Locus map app. (V3.62.1)
:) Turninstructions by trkpt <sym>(turn) & Via Points by the trkpt <sym>pass_place
:) Both Via and Shaping point support: By trkpt <type>Shaping = A "pass_place_silent"
:) Roundabout support.
:( U-turn plus Shaping or Via Point at the exact same trackpoint position is NOT supported.
Cruiser. (V3.0.0) https://wiki.openstreetmap.org/wiki/Cruiser
:) Turn instructions by trkpt <sym>(turn) & Via Points by the trkpt <sym>pass_place and <type>shaping or via.
:) Shaping & Via Point transfers by point <type> in gpx (trk)track (trkpt) and (rte)route (rtept) or wpt.
:) Via and Shaping by type support: By trkpt <type>Shaping = A non announced planner point.
:) U-turn plus Shaping or announced Via Point by the <name> at the exact same track point position support.
:) NEW: Straight line route planner support by the segment target trkpt <src>beeline and BRouter BETA app.
https://groups.google.com/g/cruiser-users/c/zvjvDrntLj8/m/8KhFB8ZBCAAJ[/i]
:) Roundabout support.
@ gpx EXPORT.
Locus map app.
:( Export is not supported
RouteYou web Planner by Locus gpx.
:) Turn instructions in trackpoints support.
:) Shaping & Via Point exports by <type>.
:) U-turn and Via Point at the exact same position support.
:( No trackpoint timestamps.
:( No roundabout support.
Cruiser app. (V3.0.0) https://wiki.openstreetmap.org/wiki/Cruiser
:) Shaping & Via Point transfers by point <type> in gpx (trk)track (trkpt) and (rte)route (rtept) or wpt.
:) Turn instructions by trkpt <sym>(turn) & Via Points by the trkpt <sym>pass_place and <type>shaping or via.
:) Via and Shaping by type support: By trkpt <type>Shaping is a non announced planner point.
:) U-turn plus Shaping or announced Via Point by the name at the exact same position support.
:) NEW: Straight line route planner support by the segment target trkpt <src>beeline and BRouter BETA app.
https://groups.google.com/g/cruiser-users/c/zvjvDrntLj8/m/8KhFB8ZBCAAJ[/i]
:) Trackpoint timestamps according to the transportation mode selected.
:) Roundabout support.
Could you give a little hint on what you are experimenting on? It's always hard to tell, what you want to tell :-)🤔
@uatschitchun. See > Advantages.
Suggestion Idea Locus Route Planner. (Non existing function in actual Locus !)
Router adds timestamps according to +/- realistic (personal) speed expectations.
Set your personal avg speed, visualised in the Locus % Slope trackcolor legend.
Personal variable speed within the % Slope zones by using the gpx <ele> data.
Dark Blue_36kmh - Green_16kmh - Red_2kmh
(https://www.imgdumper.nl/uploads9/5eaffcb664eed/5eaffcb6630dd-Personal_range_by_activity.png)
(Off bike 2kmh = non advised traject).
By the way...change or add timestamps is not critical using the trk_navtrkpt mode as the method does not need any "associated waypoint" for secure robust navigation.
Yes, I had proposed before that at least average moving speed should be a "custom defined value" by every user(according to personal fit level,age,sex,terrain,activity etc.)
Locus already kind of have speeds based on different activities defined(in navigation/more/Travel time/ like mountain hiker --with flat moving speed=5 km/h, 700 Vertical meters/hour descending and 400 vertical meters/hour ascending speed etc)
We can define ourself the ascending and descending vertical speed and Locus should compute the time,according to these user defined values.
Do you also have a verified slope range set for mountain hiking?But here the gradation is larger -40 --- +40 % maybe ?
If Locus could analyze the actual track recording during navigating a track,it would be best option for adjusting time estimate (because everyone is different... this way Locus can make a personalized slope range set chart with speeds according to everyone's fitness level)
But even if this is too much to ask, maybe if Locus would let us custom define the speeds according to slope angle(I can guess the average speeds for every slope range from the past experience).. this would also be good enough for accurate estimate the time to navigate the track
@ poutnikl had proposed an algorithm for ETA in this old thread:
http://forum.locusmap.eu/index.php?topic=5176.msg45502#msg45502
Proposal.
If the gpx point <cmt>text in the top panel does not fit into single line: < move < text.
(Total characters in single line depends by portrait // landscape // screen dpi // top bar lettertype etc.)
Suggest: By config.cfg select prefered top panel lettertype.
By move action text 'auto fits' into a single line top bar.
Large letterype <=> Small lettertype
+: Important for the older guys.
- : Less map view.