Confusing (U-) turn instruction

Ulrich Kiermayr shared this problem 1 year ago
Solved

On my way home there is a relatively sharp *right* turn (about 300°). At this turn the turn instruction shows a U-turn to the *left*. This is a bit confusing: not so much that it suggests a U-turn (which it almost is) but that the turn is shown as *left* instead of *right*. I think there should be separate U-turn to the left and to the right icons.


I use brouter as routing service.

Comments (16)

photo
1

By B-router Web ? Did you select: "assign turnInstructionMode = 2"

Can you attach track example ? (zip or change .gpx extension to .txt to upload here)

photo
1

No. Brouter app used by locus directly - with built in profile.

photo
1

I had not seen such an announcement by Brouter before. I had a look to test a similar situation.

A Sharp corner, at 2 different (named) streets, should only be announced as "Sharp turn".

Examples (By Brouter_web and Brouter_Locus) in attachment should not be announced as U-turn but only as "Sharp Right".

Brouter ?

photo
1

Attachment: A situation by Car and correct U-turn announcement. (180° return). A Left U-turn.

As Locus only known one standard U-turn. (No Left U-turn nor specific Right U-turn).

In Right driving countries a Left U-turn will be most used and advised direction,

So the standard symbol by the 'Praha' Locus design studio: U-turn = A Left U-turn sign.

Room for improvement ? U-turn by locus:rtePointAction>12 ( 13 ? 14 ?)

<name><desc><sym><wtype><extension>

f472a32130e4d7405c3fde5c0c4f8244

photo
photo
1

Hello guys,

thanks for a nice topic. Locus API already supports u-turn divided into left or right direction. Well, to be true, it is in API, but both "u-turn" use same icon. This will be fixed in next version.

Anyway, to make it work correctly with cooperation with BRouter, it is needed to improve this also on BRouter side. Is anyone in contact with Arndt? (developer of BRouter). There is need to not use action "12", but "13" for u-turn left and "14" for u-turn right as Willy mentioned in previous topic.

photo
1

Does that mean that action "12" is (can/could) be used for : <name> Return order ?

Different from a Left U turn and Right U turn order ?

photo
1

When you see in Locus "turn around" order, it is definitely reported by BRouter as action "12". Anyway in current Locus version, if there is order defined as action 13 or 14, result will be same, always the same icon. I've anyway improved it, so in next version, when BRouter update it's code and use codes 13 for left and 14 for right turn around, then it should have correct icon.

Same also for internal navigation generator > there will be also used left/right u-turn icons based on computed angle.

photo
1

I asked because a Return point (represented by a Down Arrow in the Navigation Button) is useful. I agree as such, this should only be used very rarely, and only at some special occasions/events.

An example:

And yes, I know very theoretical, but well, as Locus is THE hiking, walking and cycling app or not ?

A track design: On a special organised (walking) event, people has to visit a checkpoint that is located at a small street T deviation outside from the main track, and after getting a control stamp, should Return by using the same (small) road path to rejoin the main track and proceed further. Do you need an example (video) ? Or is this message clear ?

Of coarse actually such a manual "Return (point) Direction" creation is not possible by the already Locus powerful "route and measure" track creator and edit function.

But creating a "Return Direction" in a future Locus edition maybe should be possible by a flexible Locus "route and measure" edit function as proposed in next idea ?

http://help.locusmap.eu/topic/flexible-add-via-points-function-in-route-and-measure-track-design#comment-32987

photo
1

I raised the issue at Brouter Github issue pages, as asked by Willy, as it is the best place to address verified BRouter problem.

https://github.com/abrensch/brouter/issues/67

photo
1

Thanks Libor, appreciate it. So Ulrich, thanks for a bug-report, now it is more on work of Arndt, so we will see. Anyway next version of Locus Map will be ready to correctly handle these left/right u-turns.

photo
1

Thanks ;-)

photo
photo
1

This sounds identical to the issue I reported recently.


In North American English, "make a U turn" always always means, go back on the SAME road. In the brouter-web example link above, that's not a U turn, that's a "sharp right" because you're continuing on a different road.

photo
1

But this triggers a question, if the left/right U turns are needed at all, as U-turn alone should be enough.The driver would turn around in the direction expected by country or scenario specific.

if left/right U turn directions are to be used, BRouter would need to keep extra attention which one to use...

If you are on a trip with friends, that are ahead of you on the wrong way, you do not say them "do left/right turnaround/U-turn and return back".

photo
1

keep extra attention which one to use. I think so. A correct indicator, Turn around Left or Right is probably most appreciated also in the Left driving countries. Suppose 'our' standard indicator would have been a Right Turn indicator, that should really visually not match the turn advice by the follow track from the above link situation. The suggestion once 13, 14 is activated to reserve action 12 for a Return or Down Arrow indication, could possibly also be used when driving into the wrong opposite (one way street) direction. Where the driver immediately has to 'solve' a problem (warning) at place. (Such a solving also can mean, get of the bike and proceed by walk)

photo