Incorrect navigation commands in opposite direction

Hi Egon, could you please somehow document the error? Or describe the procedure leading to it? I'm not able to simulate it.

It is exactly the same process as described and documented by Thomas Stiegler 8 months ago.

There must be something different in your set up because with the default settings it 's not possible to simulate the issue and nobody else has reported it.

Hi Michal,

because you write "we have a different setup": No, it is the default. But I have an idea. Could it be because we are working with offline maps without internet access?

no, the map has nothing to do with navigation - only the route matters.

Hi Michael.

Today I drove a route in reverse mode again. The part of the route documented in screenshots, was automatically determined by Locus. As you can see on the screenshots, the direction is indicated incorrectly every second turn. Please see attached files.

Locus Version 4.1.1 , Samsung Galaxy A8

Hi Egon, could you please send a GPX of the route? Thanks

Hi Michael, attached you find the gpx-file.

ONLY FOR TERRAIN !

Did you see the message and take it into account?

Not on roads!

Because traffic rules are not respected in this way, and much more is guaranteed to go wrong.

Driving incorrectly on one-way streets, entering roundabouts incorrectly, incorrect street name announcements etc etc.

Reverse ROAD navigation ? Do not. Not !

Egon, thanks for the file. The navigation works correctly - the route contains micro turns that are hidden when the map is zoomed out, see pictures:

These micro turns are created during route planning when the routepoints are put on intersections. We recommend putting them always behind the turn so that the router knows the direction of the turn.

Hi Michal,

I checked the test route for micro-waypoints and found some with a distance of approx. 2 ... 3 meters. That explains the wrong signposts.

However, I had carried out the route with the route planner and it had also generated these micro-waypoints. The solution would be to skip such short sections or to discard them when the route planner is creating them.

In the track editor I noticed that you can only move this point at the beginning or end of a route. But adding is not possible.

I hope I could help. Many greetings Thomas

Hi 0709. Thanks for your hint. I know that and I have deliberately ignored it. By the way, one-way streets were also detected and avoided in reverse mode. But that is not the cause of my problem.

Hi Michael. Thank you for your helpful analysis, unfortunately I didn't see that. Sorry. This can be clearly seen after enlarging the turns. I'll take that into account in the future.

@ Egon.

The reversed ROAD Navigation issue.

Test Locus Reverse navigation with attached ROAD navigation track.

So the result imo is bad.

- You are invited to do stupid things.

- Driving in the not allowed direction of the one-way street.

- Entering the traffic circle in the wrong direction.

- Traffic circle designation (exit) inoperative.

- Arriving street name designations incorrect.

And possibly more...I won't test further.

Translated with http://www.DeepL.com/Translator (free version)

@ Egon (and other)

False turn instructions by (mini) trackglitches.

False turn instructions resulting from the sloppy placement of some Planner (shaping) waypoints. Not only beginners fall into this trap, but also inattentive experienced users. However, Locus could, in my opinion, distract from this annoying phenomenon by means of additional planner soft development. I fear, however, whether there is the will to realize or optimize this. Although it would be a nice added value if you indeed do offer a "GOLD" planner.

Willy, how do you imagine it would work? When the user places the shaping(way)point just by his finger tapping on an intersection, the point is placed on the routable way closest to the middle of the finger tap. The app has no chance to guess the user's intentions. The user has to put the routepoint always behind the intersection. No "Gold" can do this instead of the user.

@ Michal.

As usual good planning discipline is preferred. Total fool proof solutions do not exist.

A tool that presents you the planner mistakes positions causing these short track glitches.

Quickly detect and even correct received files is possible even if you are not the route producer.

Michal, your checked shown track is quite short. Checking long tracks in map view is hopeless.

You can than better correct on the basis of the track template and than more carefully redesign it.

Tool.

Only possible through the use of a capable router engine. (currently only GH).

At the end of track glitches you will find non-directional U-turns. (180° backfolding track)

Unless exceptionally, we do NOT want U-turns in the compact instruction list. So look out for U-turns !

Clicking a U-turn takes you quickly to the map position with the falsely placed triggering waypoint.

Eliminate unwanted U-turns by repositioning the relevant (shaping) waypoint.

U-turns gone? Result is no more false turn instructions.

Checking the instruction list is faster than checking long tracks in detail on a zoomed map.

Demo with Locus is not possible:

1. Locus does not generate U-turns even with online GH. Was requested but does not work (yet).

2. Locus removes the valuable Shaping points in both Navigation and "shared" gpx files. Sin.

Demo with Kurviger is possible.

Only since the most RECENT version does Kurviger support U-turns triggered by associated Shaping or Via waypoints.

Planned U-turns are best triggered by a Via with a name, so you do indicate indeed it is a planned U-turn.

Kurviger retains all valuable placed waypoints Shaping and Via in both navigation and file transfers.

Kurviger is a Motorcycle route planner, not intended nor optimised for cyclists nor for walks !

Demo method.

https://youtu.be/253IwAHQ0T4

So for this demo I did add some false positioned waypoints by intention of course ;-)

Pretty hard to quickly spot some errors on a map.

Imagine that this is a much longer track.

- In the instruction list look for the U-turns.

- Click and note false waypoint positions.

- Correct the waypoint placement. Ready.

The original template (red dot line) allows you to quickly restore it if you do corrupt the design by accidentally deleting a waypoint.

Hi guys,

I believe > improvement.

In next version 4.2/3.53, app will try to detect and warn in case of any suspissious shaping points like you may see on the screenshot.

Ok nice, ready to test.

Quickly "noticing" "slopily" placed planner positions is certainly valuable.

It is desirable to keep ALL valuable planner input also in the gpx file.

Planner point transfers in Kurviger can be done by gpx point type Shaping and Via.

Simple clear and good !

Shaping: Route planner reference. Name is possible but not necessary. Not announced in navigation.

Via: Route planner reference. Name is possible but not necessary. Announced in navigation

Benefit:

1. No user input is lost on file sharing. Reopen in the external Route Planner without planner point data loss.

2. Use of sym or "no sym" is so free. Shaping or Via Point promotion is by the gpx point type.

"Optimal compatibility for existing Locus versions?".

- It is advisable to also place sym "pass_place" at a Via Point."

The attached gpx file.

- Locus compatible track. Locus actual only imports Via Points, NO Shaping points.

Positions of Planner Shaping Points are labeled (Informative) by sym "name_change".

- Kurviger compatible Planner Waypoints.

Only coordinates and type. = Enough.