All the examples I saw with the “N” problem seem to be where Waze doesn’t expect a “north”, that is, wherever the N is not preceded by a street abbreviation or a numerical highway designation. So it didn’t work on “Cesar Chavez N” or “I-35W N”, while I assume it would work on “Cesar Chavez Dr N” or “I-35 N”.
Was “N Central Expy” only a problem with the “expressway” portion, or with the north as well? I would expect N at the front to work for North; I take “N Causeway Blvd” all the time and it always works.
Maybe “Expwy” would work for expressway where “Expy” does not. “Expwy” is the preferred abbreviation under the MUTCD. “Expy” is a USPS abbreviation we chose to prefer because (1) it’s shorter and (2) some states use it on their signs anyway.
Looks like taddison beat me to the punch (it was my post). But this just happened for the very first time last week. I am clearing my TTS cache right now just in case. The frontage road is signed as N Central Expy (not Expwy). I always did Expwy until I realized it was technically wrong per signage. The N is not directional but is part of the actual street name based on where in the city it falls (northern part or southern). I can tell you exactly where it happened if you would like. I was really surprised since other frontage roads using the same name were pronounced just fine. Here is the section in question and you can even see my UR https://www.waze.com/editor/?zoom=6&lat=32.82098&lon=-96.78684&layers=TBFTFFTTTTFTTTTTTTTFTTTTFT
I was making a turn heading east on Armstrong (actually in the parking lot) and making a right on N Central Expy. Thanks for the help. Now I know it’s not just me!!!
I recently noticed this as well with Pkwy and Blvd and all the directional labels on roads like Sam Rayburn Tollway N. Also, up until recently, I-35E N actually was spoken correctly. What gives!? Been happening for probably 10 days now…
Jason, but you turned off a different street, not Armstrong Ave on to Central Expy. I wonder if it has something to do with that particular segment. Any how, I definitely heard it, I am not crazy!! :lol:
You could be on to something. There are some ramps I need to fix in the Miami area that read out as “Florida’s Turnpike N” instead of “Florida’s Turnpike North” and it might be because it’s not expecting that N to be there.
The other segments in the area leading to the Goethals have mostly been changed to say Brg instead of Br, but the fact remains that all the signs actually say Br, and any editor attempting to duplicate the text of the signs is bound to introduce more Br’s.
It would be interesting to know the distribution of signs using Br for Bridge versus using Br for Branch, so that we could know which to assign causing the fewest issues.
I set a destination on Casey Avenue. When it said to turn onto it, it said Casey Avenue. When I arrived at my destination, it said ‘Casey Ave’, like the word ave, rhymes with have. That was weird. Any way to fix?
I thought we only found “Br” = “Branch” in the USPS abbreviations, not in the MUTCD. I know in CT (there’s a link to the state listing in the TTS spreadsheet) that “Br” is officially “Bridge” (and it’s used extensively in the northeast US that way too).
To be honest, I thought so too, and in fact I originally said that in my post before editing it. The spreadsheet hints that its Br for branch in both, but I’d thought I remembered reading that Br = Bridge in the MUTCD itself. It’s possible I read the spreadsheet wrong yesterday.
Either way, the point I was originally gonna make is that Waze’s TTS pulls from both the USPS and MUTCD abbreviations. Usually this means we just get lots of alternatives, but of course where there’s conflict we have to pick one. I figure Waze chose to incorporate “Br” for “Branch” and “Brg” for “Bridge” because it’s the only way to resolve the conflict while still having an abbreviation for each.
This is a known issue that Waze is working on. Quite a few destinations are pronounced different than what is said in route. Look at the spreadsheet linked in the opening post of this thread to see several examples.
I read through the first few pages, and last few pages of this thread, and didn’t see this mentioned.
Is Waze in the process of adopting standard USPS two letter state identifiers to TTS? As I’m sure everyone is aware, Waze currently just says the letters individually, it would be nice to have it actually pronounce the actual state name, either when used as part of a highway name, or as a City, State type reference.
This has been requested. However Waze doesn’t say the letters in all cases, “CT” is pronounced “Court”, “NY” is pronounced “North Why”, etc.
We’ve also made a request to have things such as “CA-##”, “NY-##”, “MI-##”, “LA-##” translate into the local “Route”/“Highway”/“El Ay”/etc name as well. This one is much longer term.
But this just happened for the very first time last week. I am clearing my TTS cache right now just in case. The frontage road is signed as N Central Expy (not Expwy). I always did Expwy until I realized it was technically wrong per signage. The N is not directional but is part of the actual street name based on where in the city it falls (northern part or southern). I can tell you exactly where it happened if you would like. I was really surprised since other frontage roads using the same name were pronounced just fine. Here is the section in question and you can even see my UR