Navigation not exactly along the track

Norbert Josten shared this problem 1 week ago
In Progress

Screenshot1:

You see the blue line from an imported gpx-File with few position-points.

I marked the position-points with red circles.

Screenshot2:

Switch on navigation. You see the wide purple line.

In screenshot2 I marked the same position-points with red circles.

But there are additional kink points, marked with "???", unusable.

Best regards

Norbert

Comments (16)

photo
1

What navigation do you use ? Is possible the area was recently modified in OSM and the OSM routing data differ from the OSM data the map is based on ?


Can you provide the location coordinate or the link to it, to reproduce the problem ?

photo
1

Hi,

do you have any automatic recalculation ON? If yes then Libor's remark can be true.

photo
1

Probably by navigation based on trackshape, no router service involved.

@ Josten What Locus version in use ? In picture: Speed 0.2 kmh.

Navigation by actual Locus Pro 3.25.1 (Speedindication: 18kmh.)

Tested by +/- similar track. A simple short gpx in zip file and see:

3 x tcx course generated by Locus Navigation (Low/Medium/High)

1 x tcx reference generated by JavawaRTWtool (turninstruction trackpoint angle trigger > 50°)

Locus: ->Setting->Navigation->Advanced settings->Number of commands: None,Low,Medium,High.

Josten advise 1 : Or use "None" or use "High" ( A lot of instructions, displays some small trackchange)

@Menion, suggestion: Remove Low/Medium. As by actual development system by router is most important/popular.

Josten advise 2. Use imported gpx as template and by few 'clicks' using routerservice (Brouter or online) generates you a new track with correct and minimal instructions.

photo
1

Hello Michal,

1) I use the navigation in Locus: Tracks > bike > klick on the imported gpx-Track > klick the button navigation at the bottom > than word "Navigation" > than zoom on the current GPS-Point, where I am

2) Same problem with all Tracks. Any location coordinates.

3) recalculation OFF

4) Locus 3.25.5

5) Speed 0.2means: I stopped and made the two hardcopies (png-Files), one with Navigation, one without it (switch it off)

6) Locus: ->Setting->Navigation->Advanced settings-> Strict=OFF, Max=50m, Snap=OFF, Number for voice=Low, Two commands=OFF, End=ON

7) Brouter installed

Best regards Norbert

photo
1

Does it happen even for GPX tracks generated by BRouter or any other OSM based router ? Or just for track prepared manually or imported from other, non OSM based sources ?


As for the latter the navigation may not follow the track, in contrary to guidance. In such a case, or if not using OSM map, or if OSM map or routing data are old, results may be strange.


Is BRouter also configured to be used in Locus ? What profile ?

photo
1

So, really need that example imported (gpx) file pse....pse... share.

If indeed is imported simple (external) (gpx) track: By Push navigation: Generation by "not optimal" system based on trackshape. (Brouter installed or not.)

By trackshape: Do not select Low/Medium, as results in serious trackdisplay position changes. Recommand 'High' but (-) expect A LOT of commands !

photo
2

I have not used imported external tracks and shape based hints for ages, using the luxury of BRouter. :-)

photo
photo
1

- GPX-Tracks generated on gpsies.com.

- BRouter was already installed. I tested some settings, no change.

- New Screenshots made at home. Location coordinates in water, the north sea.

First screenshot only with blue Line, caused of the imported file "Norbert-test.gpx".

Second, I switch on the "Navigation" in Locus. You see the wide purple line.

But with two additional kink points.

Best regards Norbert

photo
1

Hi Nobert. Nice example.

That excludes any (B)router (or family) clearly out of the game ;-)

Definitely by trackshape. By Locus used (older) imperfect system. (Compromises)

Locus generates (and displays) an artificial helper track in use for best turn order generation.

- System had to be functional for both low density AND high density imported tracks.

- System had to be able to determine Slight/Normal/Sharp turns,

Result:

The displayed artificial track is NOT a perfect copy of the original (adds extra/different positioned trackpoints)

SET 'High' creates a best similar (= not equal !) copy of original imported track.

@ Menion. Because fast evolution by intelligent (b)router remove/retire actual system ?

Who still use ? Replace by most simple basic system as used by (pc) Javawa RTwtool ?

Any single trackpoint that exceeds a user *free SET angle do generate a turn order.

* Free set: >50° is popular setting for cycling. = Compromise : As turns orders could be missed using high density tracks with a lot of "small angled individual trkpt's" around slow turns.

(-) Only generates basic Left/Right and final result succes do depend on import trackdensity.

(+) No trackchange !

In attachment: Resulting Navigation tcx track by the JavawaRTWtool.

photo
photo
1

Hi Norbert,

I can't simulate the issue with your test route:

aac8d515c1a981e64f9d76a35f7d33f0

Will you please share the problematic GPSies route here so I can test it? Thanks

photo
1

@ Michal. The example file is here:

http://help.locusmap.eu/topic/navigation-not-exactly-along-the-track#comment-44996

From my home position:

76a46d79d0e058fb36a872298eb41383

photo
1

Willy, I've tested the file - see the screenshot above. But Norbert reported a different file at the beginning - some imported from GPSies.com.

photo
1

This is what I download. = origin GPSies

Michal did you select: Number of commands "Low" ??

a75e8a5526d0ea69d2ed7437aa24e9f2

photo
1

ah, low number of commands set = issue simulated. Another task for Menion :) Thanks to all for reporting!

photo
1

Perfect ! I suggest: Simplification ! Remove set Low/Medium.

photo
photo
1

Good day guys,

cannot say this is directly an "issue". In case of track with navigation and selected other then "none" in number of navigation commands settings, Locus automatically generated new track with points after exactly same distance and then try to estimate navigation command suitable for certain area.

So simply, in case of selected "small number of commands", Locus Map generate new track based on source track with points exactly 30 metres between. And what you see is the result. What may happen in worst case, is around 15 m error, which I consider as really minor problem. Ok?