No turn message in navigation

Waldemar Wawoczny shared this problem 3 months ago
Not a Problem

Hi
it is increasingly common for the navigation to not provide turn announcements.
I am giving an extreme example, because the turn is 90 degrees from the route I drove on 10/07/2022, and it was already the 2nd turn, where there was no message. But there are also messages about a turn when it is not there.
Waldek

Replies (13)

photo
1

Hi,

- is the route planned in the Locus route planner or is it imported?

- what router do you use?

- do you have the navigation commands turned on in settings > Navigation > Advanced settings > Frequency of commands (medium or high)

photo
1

I always use BRouter-Web for route creation and from there I download .GPX file which I import to Locus.
And somehow so far there have been no problems.
The number of messages is high.
Note that there is no white arrow showing the right turn in the figure I have posted.

Waldek

photo
1

If BRouter does not create hints, Locus cannot make announcements. The error probably lies with BRouter or in the OSM data.
Try to create the same route in the route planner in the Locus app.
Places with U-turn is often an operator error. If the point is created shortly after the intersection (but in the wrong direction). Locus detects such errors in the route planner and makes a red circle around it.
You can also try Locus WEB planner once.

photo
1

Hi,

this is probably a problem of BRouter. Locus web planner generates the right turn correctly:

65884000265e73ff1a0859e45ec8d46a 17bcc8b7656c64310a69c8353221cc7c

photo
1

I will say this,
For now, your Planner is a baby to an adult BRouter, and you shouldn't be offended by it. Moreover, OSM - this is what Brouter uses and I guess ... I'm not mistaken and Locus, right?
By the way, I would like to know what Planner will shock me with in the future, because so far it is one of many routings.

Waldek

photo
2

Nobody is offended. LoRouter in the app and in the web planner uses OSM data too. Use any router you want but the only one we can do anything with is LoRouter.

photo
2

CHi,

I made a route through the intersection (as it was in the attached drawing) in the bikerouter (BRouter clone) and in the Locus Planner. In both cases, navigation was ok.

From this conclusion: navigation does not have to be trusted.

Hence, the map is still visible on my bike, and when hiking in the mountains, I always check the direction of the route at the forks.

waldek

photo
1

I always check the map, too. There are often 2 ways right off. So I see which one. When cycling I have the phone on the handlebars. Screen turns on and off automatically when announced. I have set via Tasker so that when announced briefly zoomed to level x and then back to the old zoom. So I see the intersection more accurately.

photo
1

The same here. Only that I use just Locus - it switches the screen on automatically before the turn and zooms in according to my speed even without Tasker.

photo
1

Could you please share your solution with me?

photo
1

- Settings > Controlling > Display > Screen on/off control > Enable > Turn on when notified during navigation (more at https://docs.locusmap.app/doku.php?id=manual:user_guide:settings:control#screen_on_off_control)

- Settings > Controlling > Map screen > Automatic zooming > Enable (more about the setting https://docs.locusmap.app/doku.php?id=manual:user_guide:settings:control#automatic_zooming)

photo
photo
1

Such various interesting solutions should be generally available on the Locus website, the number of interested parties will certainly increase

photo
1

Automatic screen turn on is built into Locus.
Automatic zoom is also available in Locus. But when I drive down the hill and I am very fast, the automatic zoom is not enough.
Therefore I have implemented a fixed value via Tasker. It is published on the Locus page. https://forum.locusmap.eu/index.php?board=66.0
But you should know something about Tasker. Otherwise you have to deal with the basic functions of Tasker.

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

photo
1

There is a problem with zooming here, because there will be many variants, incl.
are you at the intersection with the main road, or
you are going downhill but you have to brake before the intersection etc.
So maybe the values of these magnification for the indicated speeds (screenshot)

photo
1

It's worst when I need to find a detour.
When I have navigation turned on - the screen aligns with the direction of navigation - and this is a nightmare for me, because I have problems with orientation. So I have to turn off the navigation.
Later I enlarge, etc.
Overall, the "fun" is a bit over time, which is not OK anymore.

photo
1

"It's worst when I need to find a detour."

- set up automatic route recalculation with route priority (see more at https://docs.locusmap.app/doku.php?id=manual:user_guide:functions:navigation:settings#automatic)

"the screen aligns with the direction of navigation"

- turn off the map rotation (https://docs.locusmap.app/doku.php?id=manual:user_guide:maps_mainscr_ctrl#rotating)

photo
1

Actually, when the route is mapped but not passable - the navigation doesn't know it.
Will adding a ban cause the navigation to find a detour?

photo
1

"route is mapped but not passable - the navigation doesn't know it" - each route segment in OSM has passability attributes. If these attributes are wrong or missing, that's definitely not a problem of Locus. Each such problem should be reported to the OSM community either via Locus OSM notes or directly at OpenStreetMap.org

"Will adding a ban cause the navigation to find a detour?" - if you know in advance that some road/path is closed you can place a "no-go" point on it and the router will render a detour, see https://docs.locusmap.app/doku.php?id=manual:user_guide:tracks:planning#define_areas_to_avoid

photo
photo
1

If a road is in OSM as not passable and they know but so they can drive. Or if no path is marked at all, but they want to drive there. Then you can set the router at this point to manual. A turn instruction they have to create manually. Simply convert a shaping point as a waypoint and name it there. This name will then come as a voice hint.

photo
1

BRouter has a nice "no-go" option - I set the radius and routes avoid it.
Maybe the option from navigation >> "Add a ban" should behave like that.

photo
1

As I wrote yesterday, there is an option to add a "Add no-go" in Locus route planner, see https://docs.locusmap.app/doku.php?id=manual:user_guide:tracks:planning#define_areas_to_avoid, behaving exactly as you describe.

photo
photo
1

There are many paths on the map that can be seen as passable. In fact, it turns out that they are impassable (overgrown forest road, dug road, etc.). After routing, I do not know about it, only when I go it turns out that there is a problem.

And a detour must be found quickly.

And it should be like this.

I show this point as impassable. Then I show the waypoint which should be OK and the navigation should tell me to detour to it.

photo
1

This is a problem of the OSM data - if a road is impassable, inform the OSM community or repair it yourself. Anybody can become an OSM mapper, see LearnOSM.

photo
1

In the Map Content Panel there is a button to report an OSM problem.
When I don't have time, I do it this way. But most of the time I make a note and fix it myself later in OSM.

photo
photo
1

Hi,
I am coming back to the problem because I have reconsidered the problem.
1) It turns out that neither BRouter (Picture_1) nor Locus (Picture_2 - the route marked in the Planner) can see the right turn.
2) This problem occurs in this case, i.e. this straight section coincides with the same route (Picture_2 point 1) when I was returning - point 2.
3) there is no problem when the route is without a section - point 1 - then both BRouter and Locus showed a right turn and it was OK. I wrote about it before.

So I'm waiting for a satisfactory answer.

Waldek

photo
1

If no hint is generated this is a problem of BRouter. And Locus also has BRouter working in the background. So you should report the problem to BRouter.

photo
1

I can't replicate this problem even with BRouter in the app (bike touring profile) and on the route exported from BRouter.de web (road cycle low traffic profile)... All is correct including your usecase with the "coinciding" section:

9d1c7c2849f2dc71ddcb5bd238ea09a6

So maybe just re-generating the route could help...

photo
1

Hi,

I got a solution to this problem from BRouter:

applies to the route made in BRouter, export to GPX and import to Locus

1) before exporting to GPX in routing (BRouter, bikerouter.de and clones) select the option as in Fig01.

2) When importing to Locus, mark it as in Fig02.

Waldek

photo
Leave a Comment
 
Attach a file