Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

[txemt]

(FYI: I also will often take the first ramp and leave it unnamed because no driver who should be driving should be confused when they here "Exit to the right at exit 70A...." or "70B" when the sign says "70A-B". It's just clearly obvious.)

What if there's only one ramp, though:

https://www.waze.com/editor/?zoom=5&lat ... s=20927386

[xteejx]

Just Exit 70, then A or B where it splits? That's what we do here.

Sent from my GT-I9100 using Tapatalk 2

[CBenson]

This exit has been named "Exits 13A-B-C: US-301 / MD-3 Richmond / Crofton" to match the BGS for quite some time. I drive through it regularly. TTS says: "Exits thirteen ayybeesea...youess threeohone...emdee three Richmond...Crofton." It sounds fine to me. I've never seen or heard a complaint.

[CBenson]

1) Most avenues in Brooklyn NY are letters, like Ave M . However, Waze reads Ave N, E, W, and S as the direction, not the letter. A few of us have tested that encapsulating the letters with either single or double quotes gets Waze to say the letter and not the direction. So what do you guys recommend? Single quotes? double quotes? All avenues? Just problematic avenues? Add alternate name with no quotes?

East/West streets in downtown Washington DC are also letters, like "K St." In the past, encapsulating the letters with either single or double quotes would not get waze to say the letter and not the direction (only lower case encapsulated in single quotes gave the letter). Maybe things have changed since I last tried this or maybe it matters whether the single letter starts the name.

[Wajo357]

1) Most avenues in Brooklyn NY are letters, like Ave M . However, Waze reads Ave N, E, W, and S as the direction, not the letter. A few of us have tested that encapsulating the letters with either single or double quotes gets Waze to say the letter and not the direction. So what do you guys recommend? Single quotes? double quotes? All avenues? Just problematic avenues? Add alternate name with no quotes?

East/West streets in downtown Washington DC are also letters, like "K St." In the past, encapsulating the letters with either single or double quotes would not get waze to say the letter and not the direction (only lower case encapsulated in single quotes gave the letter). Maybe things have changed since I last tried this or maybe it matters whether the single letter starts the name.

This was tested over the weekend, and seems to be a new functionality. You may want to retest it for yourself.

[Wajo357]

This exit has been named "Exits 13A-B-C: US-301 / MD-3 Richmond / Crofton" to match the BGS for quite some time. I drive through it regularly. TTS says: "Exits thirteen ayybeesea...youess threeohone...emdee three Richmond...Crofton." It sounds fine to me. I've never seen or heard a complaint.

When waze says the "ayybee" it sounds like it is slurring the two letters together instead of saying simply "70 ayy bee". My question was if there was a way to write it such that voice TTS doesn't slur it.

[orbitc]

1) Most avenues in Brooklyn NY are letters, like Ave M . However, Waze reads Ave N, E, W, and S as the direction, not the letter. A few of us have tested that encapsulating the letters with either single or double quotes gets Waze to say the letter and not the direction. So what do you guys recommend? Single quotes? double quotes? All avenues? Just problematic avenues? Add alternate name with no quotes?

East/West streets in downtown Washington DC are also letters, like "K St." In the past, encapsulating the letters with either single or double quotes would not get waze to say the letter and not the direction (only lower case encapsulated in single quotes gave the letter). Maybe things have changed since I last tried this or maybe it matters whether the single letter starts the name.

On my test here putting single or double quotes helped.
In both situations;
Waze said: Avenue enn when I put Avenue "N" or Avenue 'N' for the Avenue "Avenue N" in NY and not Avenue north.

Maybe, it's changed?

[CBenson]

When waze says the "ayybee" it sounds like it is slurring the two letters together instead of saying simply "70 ayy bee". My question was if there was a way to write it such that voice TTS doesn't slur it.

Not that I know of. But I kind of like waze being quick about it.

Maybe, it's changed?

Maybe. I'll try it again.

[Wajo357]

When waze says the "ayybee" it sounds like it is slurring the two letters together instead of saying simply "70 ayy bee". My question was if there was a way to write it such that voice TTS doesn't slur it.

Not that I know of. But I kind of like waze being quick about it.

Maybe, it's changed?

Maybe. I'll try it again.

Please do. Because we need you ready for a crazy toll behavior OrbitC and I are working on.
Hint - single penalty for multiple consecutive toll segments may be wrong! I'll be starting a new thread as we do more testing soon...

[orbitc]

1) Most avenues in Brooklyn NY are letters, like Ave M . However, Waze reads Ave N, E, W, and S as the direction, not the letter. A few of us have tested that encapsulating the letters with either single or double quotes gets Waze to say the letter and not the direction. So what do you guys recommend? Single quotes? double quotes? All avenues? Just problematic avenues? Add alternate name with no quotes?

East/West streets in downtown Washington DC are also letters, like "K St." In the past, encapsulating the letters with either single or double quotes would not get waze to say the letter and not the direction (only lower case encapsulated in single quotes gave the letter). Maybe things have changed since I last tried this or maybe it matters whether the single letter starts the name.

Just a thought: Is it possible that K comes before the st? unlike what we have here is: Avenue N.