My post about Maryland is here.GizmoGuy411 wrote:I recall someone previously posted a link to Maryland too.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
I don't know. But if it is/has, "Dr" as "drive" and "Dr." and "doctor" should get the same request.Timbones wrote:Is this going happen? Did the request get put in to HQ?AlanOfTheBerg wrote:If we make it a standard that "St" is "street" and "St." is "saint" then we know exactly how it will be pronounced regardless of where it is in the street name.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
The last time I checked Int'l was sounded out as "Intel" as well.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
"Pkwy" with the initial capitalization and no punctuation (as used here) gives me TTS of "parkway."
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
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.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
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 wrote: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?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Not that I know of. But I kind of like waze being quick about it.Wajo357 wrote: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.
Maybe. I'll try it again.orbitc wrote:Maybe, it's changed?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
So I think I can confirm that "'E' St NW" is now pronounced "ee street northwest."* Unfortunately, I tested E St and I'm finding it really difficult to hear the difference between "ee" and "east." I'll try 'N' now.
* Oddly, when I route to a destination on "'E' St NW" my phone then has a sound file "ee street en double you Washington." I don't recall actually having heard "en double you" when reaching my destination. I wonder why this file is there.
* Oddly, when I route to a destination on "'E' St NW" my phone then has a sound file "ee street en double you Washington." I don't recall actually having heard "en double you" when reaching my destination. I wonder why this file is there.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
My gut reaction is just to change E, N, S and W. My vote would be to use the capital letter inside single quotes, but GizmoGuy stated that the recommendation to waze was to use double quotes. I don't remember (if I ever knew) why the preference for double quotes.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
OK, I can confirm that the sound file is used as the destination location if you select your destination by press and holding the location on the map. If you search for a destination, the announced destination location appears to be the search result you select. However, if you press and hold to give the destination, waze creates the destination location announcement. However, as waze gives the street name anyway this is redundant.CBenson wrote:Oddly, when I route to a destination on "'E' St NW" my phone then has a sound file "ee street en double you Washington."
So if I press and hold to route to a location on F St NW, when I get there waze says: "You have reached your destination eff street en double you Washington at eff street northwest." Sometimes if waze determines the street number it seems to include the number: "You have reached your destination 601 eff street en double you Washington at eff street northwest."
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien