This object is in archive! 
BRouter says "Turn around" instead of "Turn sharp right"
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.
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
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
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 ?
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 ?
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)
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)
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!
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!
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
In other words, yes, it's a non-issue.
Thanks.
In other words, yes, it's a non-issue.
Thanks.
Replies have been locked on this page!