Navigation not exactly along the track

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 !

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

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.

@ Michal. The example file is here:

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

From my home position:

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

This is what I download. = origin GPSies

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

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

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

I was patiently waiting for a response too. No original example track available.

I created a +/- similar track design as shown in the screenshots.

See Locus 'low" result. (A nice opportunity to simplify Locus menu a little bit)

(Track tcx by Locus 'low' generation ->Displayed by external program)

See the used example testfiles. The gpx design inclusive a "high" and a "low" result.

Hello Willy,

difference between log & high seems to me quite big. What you suggest? To remove this settings completely and leave in app only "middle" option that will apply automatically?

Correct.

My prefered setting always was (is): "High" (+) Most precise (-) Many commands

Simplify Menu:

Navigation -> Advanced settings -> Generate commands ? (Unset/Set button)

(If track contains no commands Locus will generate for you)

Little complicated task to be true. "High number of commands" is usually very talkative, but are situations when it's useful to have really often instructions.

I'll keep this in mind, but for now I'll leave as is. Thanks for understanding.

Hello Michal,

I don't use voice-commands. Currently I only use the purple route-line on the screen.

Negative: This purple route-line has additional kink points.

New examples.

Best regards

Norbert

Hi Norbert,

this situation occurs when the route is drawn with just a few routepoints (not a case of automatic router assisted routes with thousands of rtpoints) and number of commands set "LOW".

If you don't use navigation commands , set them as "NONE" in Locus settings > Navigation > Advanced > Number of commands.

Hello Michal,

with "NONE" it works. But my friend would like to navigate with commands, therefore I could not recommend Locus to him.

Now I set commands back to "LOW". Than I create two new tracks, one with less points and the other with automatic generated additional way-points (see Hardcopy). With navigation and more waypoints you see still kink-points from Locus, not in the gpx-data.

The error is complicated, isn't it?

Best regards

Norbert

Hi Norbert,

as Menion wrote here 4 months ago, Locus navigation commands generator works like this - it creates a copy of the route and optimizes according to assigned navigation commands. The "kink" points you report is a side effect of this process. The more navigation commands you set, the more similar is the navigated route but the high number of commands can be annoying. If you know any method of developing a navigation command generator without this side effect, please let us know.

EDIT by @menion: so try HIGH, this should help here.

Hello Michal,

in other navigation systems, like HERE-WeGo, sometimes the voice-command for "turn left" or "turn right" is too early or too late. But on the map you see the correct way in the navigation. This navigation follows the streets.

It is different to Locus's internal navigation with gpx-data:

– This kind of navigation does not follow streets and ways. (You remember, the "kinks" are also in a gpx-track on the north sea.)

– The purple route-line AND the voice are generated by command generator from the gpx-track data.

Is it necessary in Locus, that the voice-commands and the purple route-line are coupled ?

What do you think about, only the voice generates by command generator. Than, the purple route-line shows the gpx-track-data directly. I think, Locus needs the generator only for thin or bold figure of the purple route-line.

Best regards

Norbert

Good day Norbert,

as a main app developer, I'll try to explain here what is necessary. Locus use own internal generator for GPX tracks as mentioned here. This generator not just generates navigation commands, it also generates trackpoints along original route in defined interval. For low number of commands, this interval is equal 30 m. So in case of this option, it is possible that these 30 metres cause visible "shortcut" on the map.

It is necessary to consider that error will be in worst case around 10 - 15 metres and precission of GPS is usually somewhere between 5 - 10 metres, so real error will be really slow. If this is a problem, as I mentioned in Michal's post, you may use HIGH parameter for generating navigation commands, which cause interval to be only 5 metres and error, even on map, will be hardly significant.

Separating generating of commands and drawing of line on map is not possible. Thanks for understanding.

Menion