Waypoint announcing

[Herman Veldhuizen]

I have noticed that announcing waypoints doesn't always work while navigating. Both the 'Upcoming waypoint' message and the 'Reached waypoint' message are sometimes absent (for some points) and sometimes both. Is this a known issue? My waypoints are shaping points. I have not found a pattern yet but can make a test route where this occurs.

[Jörgen]

Hi,

I got this from the forum here and translated it for me into German. I have translated it back into English and hope it still makes sense.

There are no written instructions for using text to speech.
It is possible to speak text in response to SHAPING points and in response to Viapoints.
For both SHAPING points and Viapoints, text can be spoken by entering it in the renamed ‘Text’ field and/or in the ‘Note’ field. The ‘Text’ field normally contains the address of the SHAPING point or waypoint. Numbers and letters are used for this. Such texts are therefore never spoken. Except!!! if a ‘Note’ has also been filled in
‘Texts’ must not contain numbers or punctuation marks unless a “note” has also been filled in!!!
So digits / numbers must be written out.
I also saw a comment that a number/digits are allowed if they are in inverted commas?
To hear text, the ‘Via’ or ‘All’ box must be ticked in the Navigation app under Navigation settings > Audio > Waypoint notifications.
The text in the ‘Text’ field can be up to 101 characters long.
The text in the ‘Note’ field can be up to 512 characters long.
The text of a SHAPING point is pronounced approximately 750 metres before the SHAPING point. Please note that there must be no other SHAPING points or VIA points in between. Otherwise, the text is spoken at the last point before it.
For waypoints, the standard distance is approximately 2 kilometres before the waypoint. Also with the restriction that there is no other point in between.
For waypoints, the standard distance is approximately 2 kilometres before the waypoint. Also with the restriction that there is no other point in between.

[Herman Veldhuizen]

@Jörgen Thanks. The distance is definitely one of the reasons why some of my announcement are skipped. But I suspect that there might be more and will investigate. Waypoint names have no numbers in my case so that's not the problem.
It's a pitty that the distance cannot be configured somewhere in settings yet.

[Herman Veldhuizen]

@Herman-Veldhuizen
My test route:
https://www.myrouteapp.com/route/open/10551424

On this route with 8 waypoints I have seen the following behaviour and the behavior is constant, driving at approximately 50km/h. Listed below are the waypoint numbers, the distances from the previous waypoint, the message spoken before or at that waypoint (or not in strikehrough )

• 1
• 2, 1130m, "Upcoming", "Reached"
• 3, 440m, "Upcoming", "Reached"
• 4, 780m, "Upcoming", "Reached"
• 5, 630m, "Upcoming", "Reached"
• 6, 2100m, "Upcoming", "Reached"
• 7, 600m, "Upcoming", "Reached"
• 8, 3220m, "Upcoming", "Reached" 150m TOO early

I can understand that I don't get the "Upcoming" message at 3, 4, 5 and 7 if the minimal distance is hard coded to be 750m (waypoint 4 is on the edge of this distance).
However I do not understand that I do not get the "Upcoming" message for waypoints 6 and 8. The distance to their previous waypoints is quite large.
Also I would have expected the "Reached" message for 3 and 7. When driving slowly (or cycling) there is plenty of time to speak this message.
The other thing which is strange is that I get the "Reached" message far too early for the last waypoint. And I get this too early each time.