Spoken waypoints prevent spoken route directions

[Makro]

With waypoints close to intersections, I have noticed some situations where waypoints are spoken, preventing route directions from being spoken.
With an intersection close by, I would prefer if route directions take priority.

[Rob Verhoeff]

@Makro The alternative is simply to place the shaping points a bit further down the road. There’s no need to put the shaping points so close to a junction. A via point is different, because it could very well be that your favorite rest stop is located there. But in that case, you obviously don’t need to hear route guidance, since you’ve reached your next stopover or final destination.

[Guzzist]

@Makro it's good practice, to set route points (no matter if shaping- or via point) after a junction, not before.

[Makro]

Even though it's not optimal, sometimes route points have to be set rather close to intersections, in order to make sure the route won't get calculated via the wrong streets.
Besides, people should have the freedom to set route points as they like, and not have to force themselves to use the software in a way the algorithms can handle.

You could also tell me not to use long text in waypoints, or not to have waypoint details spoken. But come on, the features are there to be used, right?

So, spoken route directions should always take priority. This is not the case, and I still believe this should be changed.

[Jörgen]

There are some rules to place WP correctly.
If you need a WP close to a junction, do it with shaping point and switch the notice off.
In case you have an explanation to the WP, then is the question of what is more important, your explanation or route direction?

[Con Hennekens]

@Makro said in Spoken waypoints prevent spoken route directions:

So, spoken route directions should always take priority. This is not the case, and I still believe this should be changed.

I disagree. If I deliberately set a waypoint close to a crossing, and I deliberately give it a text to be spoken, I think that it should have priority over route directions.

What I do agree on, is that a waypoint that has no text to be spoken, should not interfere with the route-directions being spoken.

It is what it is. No single app will be completely targeted at what what each individual thinks should have priority. You can adapt easily, by not placing WPs close to crossings, or not and keep being frustrated about it I think there are bigger fish to fry...