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
Experimental robust navigation method by gpx files I want to share.
- The prefered trk_navtrkpt method can't be tested by actual Locus version !
- Only the simular rte_navrtept method is (partly) recognised for a test.

Instructions in (trkpt)trackpoints..
Gpx (trk)track_navtrkpt + wpt
Contains Via points, Nav points, Shape points, trkpt's, and free (isolated) wpt's (poi).

The trkpt's with <sym> should be promoted into Nav_Point OR (target) Via_Point.

Instructions in (rtept)routepoints.  (= Testalternative)
Gpx (rte)route_navrtept + wpt   
Contains Via points, Nav points, Shape points, rtept's, and free (isolated) wpt's (poi).

Test import into Locus. (attachment = 33_G_stwg_navrtept_direct_NL_POI.gpx)
-  Rtept and Poi containing Garmin_Locus Icons by <sym> are correctly displayed.
-  Routepoints(rtept) without <sym> are indicated by the "Red Arrow" Icon.

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

No <sym> rtept's should behave as simple trackpoints(trkpt) in tracks(trk).

- Difference between (rte)route_navrtept or (trk)track_navtrkpt method is minimal.
- Change rte into trk and add trkseg. (See picture compare)
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.

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 attaching instructions into the trkpt's some time ago. But this info was "hidden" into the tcx tread, so I moved it here.

Instructions in (trkpt)trackpoints.

Gpx (trk)track_navtrkpt.


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

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 trkpt's, but can be added optional to represent a certain 'speed'

Instructions in (trkpt)trackpoints..
- Optionally add trkpt's timestamps without worry to damage the navigation strictness.

Route Planner.

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 points.

Update: 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 "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 17, 2018, 12:41:05
Elements gpx in the Locus navigation (trk)track example files.

Required Information:
<lat> Latitude of the (trk)point.
<lon> Longitude of the (trk)point.
Optional Position Information:
<ele> Elevation of the (trk)point.
<time> Date_time of the (trk)point.
Optional Description Information:
<name> GPS waypoint name of the (trk)point. (Local language)
<cmt> GPS comment of the (trk)point. (Local language ex: street name)
<desc> Description of the (trk)point. (Local language ex: track grade, path, surface)
<sym> The (trk)point symbol. (English text *Important Locus element contains Via or Navigation information)
<type> Type (category) of (trk)point. (Nav, Via, Shape)

Actual Locus does not use the <type> information. (Shape)
By <type>Via you could "force" a navigation point to behave as a Via Point.
At active navigation a router reference point for the 'auto re_calculate" function.

* Supported <sym>(text) at navigation is autotranslated into local language TTS order, or corresponding Morse sign.
  If <sym>(text) is not supported TTS navigation order is by the <name> element or by lower frequency Morse sign "t".

* Find supported Locus navigation <sym>(text) (+ corresponding Morse sign) in the attachments.

Title: Re: Locus Navigation experimental
Post by: 0709 on February 09, 2018, 11:44:15
ViewRanger app compatible gpx (rte)route rtept contains info in <cmt> and (optional)<desc>
Display <cmt> and (optional)<desc> navigation text by max 2 single line top bars !
By removing indication [II]<=>[III] the navigation button can be shifted slightly upwards.

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

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.

Open topic in browser !
<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.
Title: Re: Locus Navigation experimental
Post by: 0709 on May 29, 2018, 16:22:29
Navigation trackinfo  is preferably attached discretely and keep a clean map view.

A. By the (trk)track_navwpt method. Not recommanded, non discrete.
Navinstructions attached into "isolated" gpx waypoints.

-  Results in a LARGE waypoint list.
-  Map view cluttered by multiple (default) navigation waypoint Icons.
-  The necessary association between trackpoints and navwaypoints is fragile

B. By the (trk)track_navtrkpt method. Recommanded discrete.
Navinstructions attached in the trackpoint elements <name><cmt><sym><type>
Example video !

+ Clean wpt_(poi) list.
+ Clean map view.
+ Robust and simple.

Picture examples. Display by Android "GPX Viewer" !
( (
The trk_navtrkpt file contains all valuable navigation info. The track display is identical compared with a standard simple track.