Author Topic: Locus Navigation experimental  (Read 108 times)

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 165
  • Thanked: 16 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Locus Navigation experimental
« on: November 20, 2017, 18:21:50 »
Some experiments by gpx I want to share

A gpx route (rte) = Before Router action.
Contains the user placed Via and Shape Points.
Locus is able to contruct a navigation track inclusive turninstructions.
https://youtu.be/P0POD0d6uOY

A gpx route (rte + wpt) = After (a) Router action.
Contains the Via and Shape points, the router generated standard rtept's, the (router generated) rtept's with integrated turninstructions, and free (isolated) wpt's (poi).
Import into Locus.
Rtept and poi containing Garmin/Locus Icons by <sym> are displayed.
Start Navigate.
Locus navigate (TTS) announce NavPoints and ViaPoints. Poi alerter (if set) announce poi's.

Issues:
- Standard rtept's without <sym> indicated by "Red Arrow" Icon.
- Only rtept's with <sym> should be promoted to Via Point.
- Navigation announced orders are not perfect strict.

A gpx track. (trk + wpt) A conversion from route (rte)  (Not supported !)

 
(Used testfiles in attachment)
« Last Edit: Yesterday at 09:41:12 by 0709 »
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 165
  • Thanked: 16 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #1 on: Today at 19:52:48 »
Route (rte) Navigation.
Some comparing tests by concurent Android app "Viewranger".
Main test goal: Strictness and robustness tests of route (rte) Navigation function.
Not comparing features as there are TTS/MorseVoice name or description text display etc !
Route (rte) navigation should be most natural strict method because the nav info is directly put into the rtept's. No "hocus pocus" to match any "isolated" waypoint containing the nav info, with the correct individual route(track)points.

Result: (Only virtual tested...bad weather, snow and too muddy testcircuit).

Source by the attached gpx navrtept files. Small difference with previous examples !
By short T deviation !  R/R <=> Flag (Keerom) (return) has no medium rtept's.
A most critical (by short T) circuit but ViewRanger strict navigation is succesfull !
And navigation still is "flexible" as next "target" point is auto-skipable ! 
Test by not driving "Right" into the T path deviation, instead continu Straight.

Route (rte) navigation in the knowledge information that took my attention !
http://support.viewranger.com/index.php?pg=kb.page&id=169
13.1. Navigation (Follow a Route)  See: TARGET WAYPOINTS
13.2. Navigation Alarms.
13.3. Navigation settings