BRouter says "Turn around" instead of "Turn sharp right"

Viajero Perdido shared this problem 11 months ago
Solved

Hi. I'm finding BRouter is working better all the time with Locus. Great job guys!


But a couple of times I've encountered a strange prompt. An upcoming turn is a sharp right turn on the ground, and shows as such on the map display. However, the turn icon shows a swooping leftward U-turn, and the voice prompt says "turn around". (In the version of English we speak here in North America, "turn around" means retrace your steps on the same route, not a different one.)


I'm using up-to-date versions of Locus Pro and BRouter, but older BRouter data files. So, apologies if this is a data file issue that has already been fixed.

Comments (15)

photo
1

I suppose BRouter decides according to calculated angle, and the angle may have seemed closer to 180 degrees ( turn around or make a U turn ) than to 135 degrees ( turn sharply right/left ).


But anyway, such a post fits rather to BRouter support Google group

https://groups.google.com/forum/#!forum/osm-android-bikerouting

photo
1

...unless possibly BRouter outputs a sharp right turn (notice it's shown as such on the map), and Locus interprets it incorrectly. I don't know enough about the interface to be sure.


Anyway, I don't use that particular social network, so I'm posting it here.

photo
1

Navigation instructions are generated by Brouter, Locus just shows/says, what is written in the route data.


So Locus has nothing to do with the problem and you are "crying at the wrong grave". :-)


I have never heard Google Groups to be called a social network.. I use it as a maillist.

photo
1

I had a look at the XML output from the same route which I'd run through the BRouter web interface. The output was simply a list of nodes, so it would seem it's Locus that has the task of creating turn instructions from that list.


Well, G+ is/was a social network, and over in Google land I use my real name out of necessity. I like to keep my two lives separate...

photo
1

What profile and how old profile diid you use ? Does it have correctly set turnistructrions variable and other related variables ? If not, you need an update.

What about GPX route generated by BRouter app ? Does it contain waypoints with instructions ? if not, you may have BRouter misconfigured, the easiest way is to reinstall.

If there are no instructions from BRouter, then as you say, Locus generates its own instructions. And then the topic subject "BRouter says.." is wrong. It says nothing.

Locus generates instructions based on the route shape. It uses no other info and does not see road network context. A crossroad turning in near U-turn shape may not be distinguished from turning around.

G+ is/was a social network, but GG is not G+. I use for Usenet and GG(part of it is Usenet archive and Usenet web interface) dedicated google email address, same as I use a dedicated address for all web registrations and web forums like Locus helpdesk and forum.

photo
photo
1

The navigation track is probably not correctly generated by Brouter (web). Has no generated navwaypoints, but only track ? Or Locus selects his own navgenerator based on the trackshape and so generates the "turn around" message.

Actual B-router web routing generation with navigation instructions mode 2. (assign turnInstructionMode = 2); In a last few tests selecting mode 2 did not generate any navigation waypoints but only a track. Only after first selecting mode 3 (OSMAnd) and then reselect to mode 2 generates navwaypoints and extensions for Locus. Someone to confirm a possible issue ?

photo
1

When testing the current Trekking profile template, the Brouter web does not generate navigation instructions, if turnInstructionMode = 1 ( auto-choose as default) , as it is intended for Android use.

But if it is edited to 2=locus-style or 3=osmand-style, the Brouter -web DOES generate the instructions for me.

So do generate instructions profiles derived from this template in the latest Brouter 1.4.5.

( Or rather BRouter using these profiles)

photo
1

This odd behavior happened using older profiles (maybe a year old, from before the recent changes to BRouter), the trekking and car-test profiles respectively, I think. I guess I need to update my profiles, and the data files as well.


If updating files is all it takes to fix this, that's great. But I wanted to point it out in case there's a bug even with the newest stuff.


Thanks guys!

photo
1

In such a case, you may find a use for some my profiles https://github.com/poutnikl/Brouter-profiles/wiki

photo
photo
1

Hello guys,

not sure if I may help here somehow. As Libor correctly mentioned, problems in "navigation commands" are most probably in BRouter itself, not in Locus. If there is something I may help, please let me know.

photo
1

What I understood, his old profiles did generate no instructions, so the instructions were of Locus, based of the track shape.

In such a case, it may be near impossible to distinguish turning around and very sharp turns.

photo
1

Ah it was older profiles. In this case you are correct. Correct detection of "sharp turn" vs "turn around" is impossible in this case, sorry.

photo
1

Even though brouter-web with its default profiles spits out only a simple list of nodes?


Okay, I'll update everything anyway and try again. Sorry if this has already been fixed and I'm only wasting your time. Cheers.

photo
1

By Brouter web: In field "Options": See Profile trekking Alternative original.

Left down field "Profile" search for text assign turninstructionMode = 1 Change text into turninstructionMode = 2

Push upload. Notice message = temporary !

In field "Options" is shown now: Profile <custom> Alternative original.

Design you a short test circuit. End by 'esc' or 'q'. Push Download GPX....see downloaded file: brouter.gpx

This gpx has nav instructions in wpt's.

To be imported into Locus for Navigation and also accepted by app Track Navigator.

Quick test: See instructions in the wpt's in downloaded gpx file by freeware pc program "gpx editor".

Open gpx file . Select Waypoints and see the details in the Point list.

photo
1

In other words, yes, it's a non-issue.


Thanks.