Author Topic: Locus Navigation experimental  (Read 1110 times)

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 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. (file 1 in zip)  (Locus_Garmin)
Contains the user placed Via and *Shape Points.   

- Locus_Brouter route result inclusive turninstructions.
https://youtu.be/P0POD0d6uOY
- Garmin Basecamp route result in attachment.
Routing Garmin Basecamp.gif

A gpx route (rte) = After (a) Router action. (file 2 in zip)  (Locus)

A gpx route (rte + wpt) = After (a) Router action. (file 22 in zip)  (Locus)
Contains Via and *Shape points, the (router generated) Nav points, the router generated standard rtept's, and free (isolated) wpt's (poi).

Import into Locus.
- Standard rtept's without <sym> are 'actualy' indicated by the "Red Arrow" Icon.
  A cosmetical improvement by discrete small dot Icon would be prefered. See example picture by ViewRanger.
- Rtept and Poi containing Garmin_Locus Icons by <sym> are displayed.

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

Issues:
- Navigation orders announced, the displayed description text is "at random" so mostly incorrect.
- Navigation announcements too late because standard (no_sym) rtept's behave as (TTS silent)Via Points.

Optimalisation suggestion.
Only rtept's with <sym>(text) should be promoted into Nav_Point OR Via_Point.
http://help.locusmap.eu/topic/locus-routerte-file-import-to-navigate%C2%A0

* Full functional Locus to Locus exchange: Point function marker by element <type>: Shape. (optional Via_Nav)
« Last Edit: February 06, 2018, 19:38:13 by 0709 »
Locus Pro 3.29.1
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #1 on: December 13, 2017, 19:52:48 »
Route (rte) Navigation.

Compatibility and comparing test with android app Viewranger.

ViewRanger onscreen display "Info" at navigate is by both gpx elements <cmt> AND <desc>

http://my.viewranger.com/route/details/MTY1OTAwOA==

In attachment: 22_G_stwg_navrtept_NL_POI_type.gpx
Element <cmt> contains: Streetname.
Element <desc> contains: Description, track_type_grade, surface etc

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

Route(rte) navigation should be "natural" strict as the navigation data is directly put into the rtept's. No "hocus pocus" to match "isolated" waypoints containing the navigation data, with the correct individual routepoints.

Locus officially does not support route(rte) navigation, but the result was very acceptable.
- Locus has some "very late" alerts (see previous # 0)
- Locus displays "at random" text in the map info top bar
Results in nonsense info.

Route (rte) navigation ViewRanger info !
http://support.viewranger.com/index.php?pg=kb.page&id=169
13.1. Navigation (Follow a Route)  See: TARGET WAYPOINTS
« Last Edit: February 12, 2018, 18:20:46 by 0709 »
Locus Pro 3.29.1
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #2 on: December 21, 2017, 10:52:17 »
Another experiment by an imported gpx rte route. 
Create an Informative Via Point by the Locus (routepoint) editor.
Export into a compatible route(rte) file is currently not supported by Locus.
See attached .gif and and a example gpx file result created by "gpx editor"(pc) edit in attachment.

   <rtept lat="51.0506558" lon="4.0031862">
      <name>Eekhoorn</name>
      <desc>Hier zie je soms eekhoorntjes</desc>
      <sym>Small Game</sym>
   </rtept>
« Last Edit: January 07, 2018, 22:14:09 by 0709 »
Locus Pro 3.29.1
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #3 on: December 22, 2017, 17:22:41 »
Edit <sym>text by (pc) "gpx editor" or Android DroidEdit, Quoda etc.
The exact <sym>text to be used 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 internal Icon list. (Wpt). <name> is identical to <sym>text.
3. The Locus Navigation Icon list. (Route by rte/rtept)
Import route into Locus. Tap the imported "Route from waypoints".
Choose trackdetails -> Waypoints. <name> is identical to <sym>text.
Tap individual rtept's for details in description and comment.
4. Compatibility test Locus Navigation order list by Icon <sym> as shown into ViewRanger web. (App)
Need VR login (free)
http://my.viewranger.com/route/details/MTYyMDkwMQ==
« Last Edit: January 26, 2018, 08:44:18 by 0709 »
Locus Pro 3.29.1
 

Offline uatschitchun

  • More than Newbie
  • *
  • Posts: 30
    • View Profile
Re: Locus Navigation experimental
« Reply #4 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 :-)🤔
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #5 on: December 23, 2017, 10:03:09 »
**Sure**
I already tested rte (route) gpx some time ago.
Info was "hidden" in the tcx tread, so moved it here

The next topic was another "extra experiment" trigger:
http://forum.locusmap.eu/index.php?topic=5973.msg49693#msg49693
Is it possible add support for standalone application for navigation? Watch has gps and barometer.
For inspiration see ViewRanger watch app :) https://play.google.com/store/apps/details?id=com.augmentra.viewranger.android

I was wondering how VR do design and transfer the routes ?
I noticed a very easy simple editable gpx route (rte) file system..

Always curious I imported a file into Locus and surpise, is +/- recognised !

Gpx route (rte) IMO is superior because of the simplicity.

- Clearly separates Routes_rte (planned/future) and Tracks_trk (records/history)
- Easy import: Navigate without Set: "Merge points with imported track".
- No need for timestamped rtept's, but can be added optional to represent a certain 'speed'
- 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 ?
« Last Edit: February 08, 2018, 17:34:05 by 0709 »
Locus Pro 3.29.1
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #6 on: December 30, 2017, 18:00:57 »
@Marius.  This is open for discussion only. No idea launch in help desk !
http://help.locusmap.eu/topic/distance-to-specific-point-in-navigation-mode#comment-48474

- 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.
http://gotoes.org/strava/Add_Timestamps_To_GPX.php

http://www.klimtijd.nl/beklimming/muur-van-geraardsbergen
« Last Edit: January 30, 2018, 19:20:49 by 0709 »
Locus Pro 3.29.1
 

Offline emariu

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Locus Navigation experimental
« Reply #7 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 ?
« Last Edit: December 31, 2017, 00:25:17 by emariu »
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #8 on: December 31, 2017, 09:14:59 »
Tap individual rtept's for details in description and comment.
Question by Marius in helpdesk 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, so BEFORE operational start.
That #6 web example only offer 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.
« Last Edit: January 07, 2018, 22:15:38 by 0709 »
Locus Pro 3.29.1
 

Offline emariu

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Locus Navigation experimental
« Reply #9 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
 

Offline emariu

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Locus Navigation experimental
« Reply #10 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
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #11 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. Also a gpx route(rte) file is able to describe a detailed pathshape as exactly as tracks do.

1. Standard (compact) route(rte) only contains the Via routepoints and the Shape routepoints.
Marked in the attached picture example by element <type>Via_Shape.

- 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". ***
« Last Edit: February 06, 2018, 19:32:31 by 0709 »
Locus Pro 3.29.1
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #12 on: January 17, 2018, 12:41:05 »
Compare Locus (direct) route(rte) with standard (compact) route(rte) & the track(trk)_wpt system in the attached pdf. In this pdf see the simple Locus (direct) route(rte) navigation system.
Page 1. By reading the text in the list , browse the individual points one by one see the instructions. Simple. No need to puzzle and find the correct belonging instructions as used by the track(trk) + wpt system as shown in page 3.

Elements gpx as used in the Locus experimental navigation example files.
http://www.topografix.com/gpx_manual.asp

<RTEPT> ROUTEPOINT
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> Descriptive description of the routepoint. (Local language ex: track grade, path, surface)
<sym> Routepoint symbol. (Always English text "required element in Locus". Contains Via or Navigation information)
<type> Type (category) of routepoint. (Via_Shape_Nav)
« Last Edit: February 07, 2018, 11:07:58 by 0709 »
Locus Pro 3.29.1
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 175
  • Thanked: 19 times
    • View Profile
  • Device: GT-I8160 CM11 SM-T235 4.4.2 THL4000 4.4.2
Re: Locus Navigation experimental
« Reply #13 on: February 09, 2018, 11:44:15 »
@Menion:  Long text <desc> example:
Navigation Display text in Locus map top bar: 
By: <cmt> and <desc>:  2x single line Top Bars
<cmt> content = street name
<desc> content = Very descriptive information by Menion


====
Gratiebossen
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum====
Map
map
map
......
« Last Edit: February 09, 2018, 18:43:15 by 0709 »
Locus Pro 3.29.1