Locus Map - forum

Development => Discussion/New features => Navigation & Guidance => Topic started by: 0709 on November 20, 2017, 18:21:50

Title: Locus Navigation experimental
Post by: 0709 on November 20, 2017, 18:21:50
Locus 3.50.1  Operational ! (Import)

Navigation by gpx track navigation instructions into trackpoints.

More Info:

Good to know !
(Auto)(re)calculation in Locus Navigate is toward the (router reference) target Via Points !
Instructions in trackpoints trkpt.

Trackpoints that do contain the Locus standard [EN]sym text are promoted to navigation points.
Only these points lead to navigation or via point alerts and give distance values @ navigate.


- Manage/separate the poi waypoints without any risk to damage the navigation.
- Easy import, navigate 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.
- Add individual freely positioned wpt's(poi) into the gpx file. (Locus can't, function is not offered)
- Timestamps are not obligatory for navigation,  but can be attached according to expected speed
- A single gpx file can contain multiple navigation tracks. The original and + the alternative tracks

Example in attachment. (Register and login into the forum !)
Title: Re: Locus Navigation experimental
Post by: 0709 on December 22, 2017, 17:22:41
Edit <sym>text by (pc) * GPX Editor or Android Notepad ++ etc.
GPX Editor:

The exact <sym>text must be known.

Elements gpx in the Locus navigation example files.

<TRKPT> (trackpoint).
Required Information:
<lat> Latitude.
<lon> Longitude.
Optional Position Information:
<ele> Elevation.
<time> Date_time.
Optional Description Information:
<name> Name. (Local language)
<cmt> Comment. (Local language) Displayed in Locus top panel @ navigate.
<desc> Description. (Local language)
<link> Link (to photos) related to objects on the map.
<sym> [EN] Symbol. Important Locus Icon element, contains the navigation turn instruction.
<type> Type. Locus actually does not use.

- Supported turns by [EN]<sym>text : Auto-translated in local language TTS turn commands and a direction turn icon is shown @ navigate
- Locus [EN]<sym> pass_place: The untranslated <name> element is used for TTS announcement and Via Point Icon is shown @ navigate

Locus gpx <cmt> is reserved for compact text info, but mainly used to attach the “street name”
The compact <cmt> text information is than displayed in the text top bar @ navigaton operation.
Locus gpx  <desc> is available to eventually attach some extra text info but is actually not used.

Examples in the attachments. (Register and login into the forum !)
Title: Re: Locus Navigation experimental
Post by: uatschitchun on December 22, 2017, 18:12:58
Could you give a little hint on what you are experimenting on? It's always hard to tell, what you want to tell :-)🤔
Title: Re: Locus Navigation experimental
Post by: 0709 on December 30, 2017, 18:00:57
@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


(Off bike 2kmh = non advised traject).

By the way...freely changing or adding timestamps is uncritical when using the direct route (rte) navigation mode as the method does not need any "associated waypoint" for secure navigation.
Title: Re: Locus Navigation experimental
Post by: emariu on December 31, 2017, 00:07:54
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 ?
Title: Re: Locus Navigation experimental
Post by: emariu on January 04, 2018, 10:43:19
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
Title: Re: Locus Navigation experimental
Post by: emariu on January 05, 2018, 17:07:46
@ poutnikl had proposed an algorithm for ETA in this old  thread:
Title: Re: Locus Navigation experimental
Post by: 0709 on February 09, 2018, 11:44:15

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.

Open in browser to see  <=<=<= Move text  <=<=<=

Lorem Ipsum is simply dummy text.