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
An experiment by gpx I want to share.

Navigation instructions attached into the routepoints.

Gpx (rte)route_navrtept + wpt    (Locus)
Contains Via points, Nav points, rtept's, and free (isolated) wpt's (poi).

Import into Locus. (attachment = 22_G_stwg_navrtept_NL_POI.gpx)
- Routepoints(rtept) without <sym> are indicated by the "Red Arrow" Icon.
   A cosmetical improvement by discrete small dot Icon is prefered. See picture ViewRanger.

- Rtept and Poi containing Garmin_Locus Icons by <sym> are correctly displayed.

Start Navigate.
- Locus navigate announces the NavPoints and ViaPoints.
- Poi alerter (if set) the Poi's.

- Navigation alerts are (too) late because (no_sym)rtept's behave as (TTS silent)Via Points.

Only rtept's with <sym>(text) should be promoted into Nav_Point OR (target) Via_Point.
No <sym> rtept's should behave as simple trackpoints(trkpt) in tracks(trk).

Note: A variant
Navigation instructions attached into the trackpoints.
- Gpx (trk)track_navtrkpt + wpt
- Difference with similar method by (trk)track_navtrkpt is very minimal.
- Change rte into trk and add trkseg. (See picture compare)
- Optimalisation: trkpt's with <sym>(text) should be promoted into Nav_Point OR (target) Via_Point.

Title: Re: Locus Navigation experimental
Post by: 0709 on December 13, 2017, 19:52:48
Navigation by gpx (rte)route_navrtept.  Comparing test with android app Viewranger.

ViewRanger "Info" navigate display by gpx element <cmt> AND (optional)<desc>
In the VR link example see the waypoint 2. "Info" text by <cmt> and <desc>

ViewRanger <sym> versus Locus <sym> are not compatible. No "Standard" :(

Navigation by gpx (rte)route_navrtept is "natural" strict as the nav info is attached into the rtept's.
No "hocus pocus" to match "isolated" waypoints containing navigation data, with correct individual trackpoints as in the track_navwpt  method.

Locus officially does not support route(rte) navigation, but a testresult was very promising !.
Observed:  Some generated Locus nav announcements are "too late". (See previous # 0)

Route (rte) navigation ViewRanger info !
13.1. Navigation (Follow a Route)  See: TARGET WAYPOINTS
Title: Re: Locus Navigation experimental
Post by: 0709 on December 22, 2017, 17:22:41
Edit <sym>text by (pc) * GPX Editor or Android DroidEdit, Quoda etc.
The exact <sym>text must be known.
In attachment : 3 gpx files to exactly find out.
Locus Navigation List Details. (Need a VR login to see all waypoints with the details)

1. The Garmin list.  (Wpt) <name> is identical to <sym>text.
2. The Locus Icon list. (Wpt). <name> is identical to <sym>text.
3. The Locus Navigation Icon list. (Route by rte_navrtept)
Import route into Locus. Tap the imported "Route from waypoints".
Choose trackdetails -> Waypoints. <name> is identical to <sym>text.

* GPX Editor:
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 23, 2017, 10:03:09

I already tested navigation by direct attached info into trkpt's (or rtept's) some time ago.
But this experimenal info was "hidden" into the tcx tread, so I moved it here.

The next topic was another "extra new experiment" trigger:
Is it possible add support for standalone application for navigation? Watch has gps and barometer.
For inspiration see ViewRanger watch app :)

How VR do design and transfer routes ? Imported a file into Locus and surpise, is +/- recognised !

Gpx (rte)route_navrtept + wpt.     (Locus)

- Easy import: Navigate succes without "must" set: "Merge points with imported track".
- No need for timestamped rtept's, but can be added optional to represent a certain 'speed'
- 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 (isolated) wpt's as POI into the gpx file. (Locus can't, function is not offered)
- Retune individual route rtept's into Via or Navigation Points. (Locus "track" editor alternative)
- A point "marker" by element <type>Shape "could" offer full functional Locus to Locus exchanges
....more to discover ?

* trk_navwpt" method:
Title: Re: Locus Navigation experimental
Post by: 0709 on December 30, 2017, 18:00:57
@Marius.  This is open for discussion only. No idea launch in help desk !

- No need for timestamped rtpe's, but can be added optional to represent a certain 'speed'

By Direct Route(rte) navigation. - Timestamps can be added optional in total freedom.
Flexible timestamped rtept's without worry to damage the navigation strictness

At Planning !
Router adds timestamps according to +/- realistic speed expectations.
Set your personal avg speed, visualised in the Locus % Slope trackcolor legend.
Speed is variable within the % Slope zones by using the gpx <ele> data.
Dark Blue_36kmh - Green_16kmh - Red/brown_3.2 kmh (off bike).
Use case: In "statistic" route detail find the expected travel time between selected rtept's.

Update: The principle does work...had a quick test by website generator:
- Consider Elevation in Calculating Speed !  See the attached gpx route(rte) file.
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: 0709 on December 31, 2017, 09:14:59
Tap individual rtept's for details in description and comment.
Question by Marius is to be able at planning by selecting individual rtept's "point details" or in the route graphics screen, find distance and +/- realistic travel time, BEFORE operational start.
That #6 web example only offers you a 'standard' setting. The Locus track(route) coloriser already has a free to set personal operational %Slope range. According to the activity both %Slope range and according speed set (NEW) to be integrated into a single tool. By comparing real trackrecords (yours) the speed settings are to be 'trimmed' to a best time estimate performance pro activity.
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 January 11, 2018, 17:25:21
By PM I noticed there is still some misunderstanding by the Locus direct route(rte) file system.

rte represents route - an ordered list of WAYPOINTS representing a series of turn points LEADING to a destination. A gpx route(rte) file is able to describe a detailed pathshape as exactly as a track .

1. Standard (compact) route(rte) only contains the Via routepoints (and the Shape routepoints).

- When the precise path being taken to the destination(s) Via Points is not important.
The activated "mobile" router planner creates an onroad path to pass all Points in correct order.
2. Locus (direct) route(rte) also includes normal (no sym) routepoints and the Navigation rtept's.

- When it's PREFERED to travel on a very specific path to reach the desired destination(s).
By a mobile router recalculate may navigate by an alternative onroad path to a next Via Point.
- When it's NECESSARY to travel on a very specific (offroad) path to reach the desired destination(s).
By unactivated mobile (re)router strictly navigates to precisely follow the original pathdesign.

*** Locus route navigates at OFFROAD paths and thereby maintains the (re)routing function when driving "off path". ***
Title: Re: Locus Navigation experimental
Post by: 0709 on January 17, 2018, 12:41:05
Elements gpx in the Locus navigation (rte)route example files.

Required Information:
<lat> Latitude of the routepoint.
<lon> Longitude of the routepoint.
Optional Position Information:
<ele> Elevation of the routepoint.
<time> Date_time of the routepoint.
Optional Description Information:
<name> GPS waypoint name of the routepoint. (Local language)
<cmt> GPS comment of the routepoint. (Local language ex: street name)
<desc> Description of the routepoint. (Local language ex: track grade, path, surface)
<sym> Routepoint symbol. (English text "Required Locus element". Contains Via or Navigation information)
<type> Type (category) of routepoint. (Shape)
Title: Re: Locus Navigation experimental
Post by: 0709 on February 09, 2018, 11:44:15
ViewRanger compatible gpx (rte)route can contain info in <cmt> and (optional)<desc>
Locus nav should display <cmt> and (optional)<desc> text otherwise info could be lost.

By removing indication [II]<=>[III] the navigation button can be shifted slightly upwards.

Alternative status indication [II]<=>[III] by top bar background color change.

Navpoint_viapoint info text in gpx <name> <cmt> <desc>
Displayed in max 2 single line top bars ! (<name> lowest priority)
If text in top bar does not fit into a single line lenght.       <=<=<= Move text  <=<=<=
(Total characters in a single line depends by portrait // landscape // screen dpi // top bar lettertype etc.)

Suggest: By config.cfg select prefered top bar lettertype.
By the move action text 'auto fits' into a single line top bar.
Large letterype <=> Small lettertype
+:  Important for the older guys.
- :  Less map view.

Example view by webdisplay ! (Open this topic in browser !)
By the gpx rtept elements <name> <cmt> <desc>
<name> Free (any language) content. (lowest priority, not displayed in example)
<cmt> Free (any language) content. In example = Street name
<desc> Free (any language) content.  In example = Long descriptive point information  ;)

Lorem Ipsum is simply dummy text of the printing and typesetting industry.