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

Route(rte) navigation by gpx file.
The routepoint(rtept) density is exactly the same as trackpoints in tracks.
 
Instructions in (target) routepoints (rtept).

Standard routepoints contain only basic elements: Longitude, Latitude, elevation (optional), time (optional).
These intermediate routepoints, treated as shaping points, do not lead to alerts nor give distance values.

Routepoints that do contain extra as name, cmt, desc, sym or type are promoted to navigation targets.
Only these routepoints lead to navigation or via point alerts and give distance values @ navigate.

Advantages instructions in rtept.

- Manage/separate the poi waypoints without any risk to damage the route navigation.
- Easy import: Navigate without "must" set: "Merge points with imported track".
- Navigate and information into routepoints by clear language instruction.
- Less fragile than the * trk_navwpt method with the more critical associated waypoints.
- Compact POI wpt_list not cluttered by many associated wpt's as by the * trk_navwpt method.
- Prevent theoretical discussions about "history" (trk)tracks and "future" (rte)routes.
- Synced gpx files to pc offers extra edit tools or an alternative for only Locus edit.
- Add individual (isolated) free wpt's(poi) into the gpx file. (Locus can't, function is not offered)
- Retune individual rtept's into Via or Navigation Points. (Locus "track" editor alternative)

(https://www.imgdumper.nl/uploads9/5e7b94a1e72f8/5e7b94a1e4a90-Locus_point_element_transfers.png)


Advantages instructions in routepoints by [EN]<sym>

- Supported navigation routepoints by the [EN]<sym> are announced by automatically translated local language TTS commands and a "Direction Icon" is shown @ navigate
- Unsupported navigation routepoints by <sym> are promoted into Via Points,  are announced by TTS <name> and the Via Point "Dot Icon" is shown @ navigate

(https://www.imgdumper.nl/uploads9/5dc06872071f2/5dc0687200418-Direction_commands.png)


Compare the most important navigation direction commands by tcx / fit /gpx

(https://www.imgdumper.nl/uploads9/5dbc8121aca80/5dbc8121a5559-Garmin_tcx_fit_%26_Locus_gpx.png)



Import and Start Navigate.

Gpx (rte)route_navrtept + wpt(poi) (attachment = 33_G_stwg_navrtept_poi.gpx)
Contains NavPoints, ViaPoints, standard rtept's, and freely positioned (isolated) (poi) wpt's.

-  Locus navigate announces the Nav Points and Via Points.
-  POI alerter (if set) announces the Poi's.

Demo video: https://youtu.be/Q7AshXsAe_M


* Instructions in (wpt)waypoints.
  Gpx (trk)track_navwpt + wpt(poi)
   http://forum.locusmap.eu/index.php?topic=4178.msg50723#msg50723

Examples in the attachments. (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:  https://sourceforge.net/projects/gpxeditor/

The exact <sym>text must be known.
In attachment: 3 gpx files to exactly find out.

1. The Garmin Icon list by <sym>. (Wpt) <name> is identical to <sym>text.
2. The Locus Icon list by <sym> . (Wpt) <name> is identical to <sym>text.
3. The Locus Navigation Icon list by <sym>. (Route) by rte_navrtept.
Import route into Locus, choose trackdetails -> Waypoints. (Rtept) <name> is identical to <sym>text.

Elements gpx in the Locus navigation (rte)(route) example files.
http://www.topografix.com/gpx_manual.asp

<RTEPT> (routepoint).
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)
<sym> [EN] Symbol. Important Locus Icon element, contains the navigation instruction.
<type> Type. Locus does not use.


- Supported navigation points by <sym> are translated in local language TTS commands and direction icon shown @ navigate
- Unsupported points by <sym> are promoted into Via Points,  announced by TTS <name> and via point icon shown @ navigate

Find the supported Locus navigation <sym> in the attachments.


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 start of tread > Advantages.
@Marius.  Open for discussion only. No idea launch in help desk !
http://help.locusmap.eu/topic/distance-to-specific-point-in-navigation-mode#comment-48474

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_1kmh
(https://www.imgdumper.nl/uploads9/5d19c75654934/5d19c7564a543-Set_Your_Personal_range_by_activity.png)
Planning tourist trekking inclusive luggage ! (Off bike 1kmh = non advised traject).

Example by website generator.
- Consider Elevation in Calculating Speed !  See the attached gpx route(rte) file.
http://gotoes.org/strava/Add_Timestamps_To_GPX.php
http://www.klimtijd.nl/beklimming/muur-van-geraardsbergen

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:
http://forum.locusmap.eu/index.php?topic=5176.msg45502#msg45502

Title: Re: Locus Navigation experimental
Post by: 0709 on February 09, 2018, 11:44:15

If text in 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 of the printing and typesetting industry.