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

[sketch]

I feel it's probably best that "St" returns "saint" if it's at the beginning.

[sketch]

I thought we decided long(er) ago that differentiation should be with the period or without. Positional should make no difference. St=street, St.=saint, Dr=drive, Dr.=Drive, etc. Why make it more complicated?

No problem. I probably wasn't following at that time. Just looking to get out of a bunch of future edits

[sketch]

I tested for "Par" and "Ph" in hopes that one would be an abbreviation for "Parish" as that is what Louisiana calls their counties.

Sorry Jason and Sketch... no love for LA yet.

No biggie. I can't think of any roads named after parishes in particular.

...well, except for "Parish" Road—it's actually called Paris Rd, but try convincing residents of St Bernard ("Da Parish") they're wrong!

[sketch]

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.

That's how it should be done (more or less — it should be "Exit" rather than "Exits", if that's what the big green sign says). Read the fifth bullet point in this section of the road naming wiki: http://www.waze.com/wiki/index.php/Road ... n-ramps.29

[sketch]

it should be "Exit" rather than "Exits", if that's what the big green sign says

Just to clarify, you are saying it should be what the big green sign says, correct?

Correct. I think this varies by state. In Louisiana, it'll say "Exit 232A-B", for example.

[sketch]

Would you put Avenue S as Ave 'S' or just leave it as Avenue 'S'?

Not sure. Is it "Avenue Ess" or "Avenue South"? Which is the noun? Does it really need to be abbreviated at all? Maybe it's time to get rid of them altogether. Devices have much higher resolutions these days, and there's plenty of space on the screen for full road names... [/rant]

I don't think so. Resolutions are getting higher but not all screens are getting bigger. I think you'll have a tough time justifying spelling out "Boulevard" or "Throughway" in any case.

[sketch]

Agreed. The nuances of map editing are confusing enough already. We don't need more of them, especially just for pronunciation.

Every GPS system on the market pronounces street names wrong all the time. Waze does some better, some worse than others. Yes, we like to be better than everyone, but the benefit we'd gain from this is small compared to the pain of editing this into every segment of the map Waze might get wrong.

People can figure out that "Arnoo" means "Arnoult" and not "Severn" or "Hessmer" or any of the streets nearby. It isn't crucial that Waze says it with the T like everybody in town. It's good enough not to have to worry about it THIS much.


Sent from my iPhone using Tapatalk 2

[Spil]

Sorry, no input on the first one, but I'll take up this one for you:

2) On some of the ramps I've seen, the ramp name is "Exit 70A-B:...", but it is read as "exit 70ayybee" without any break between the ayy and bee. If I add a space before and after the dash Waze says "Exit 70ayy to bee. What do you guys recommend in such a situation?

In most such situations, the "Exit 70A-B" part of the ramp should be left unnamed, allowing TTS to use the appropriate "Exit 70A" or "Exit 70B" ramp name from the upcoming offramp. There may be some instances where the "Exit 70A-B" might be needed, though -- can you provide a Permalink to the interchange in question here?

[Timbones]

Does TTS not say "saint" when St is at the beginning, and "street" when it is at the end? This is how I'd expect it to work...

via TapaTalk

[Timbones]

It seems that "Cr" is being now pronounced as "County Road", so what would be an acceptable abbreviation for "Crescent"?

via TapaTalk