GizmoGuy411 wrote:Are you sure, because I could swear that it has been that way for a while. We have a ton of county roads in NW Ohio, and we have slowly been changing them to "CR xxx" as we canvas the rural areas. "CR" does get pronounced correctly as "County Road", and not to be confused with "Country Road".
sketch wrote:taddison1 wrote:jasonh300 wrote:What was the exact name of the expressway, as named on the Waze map? It's working fine at the expressway near me.
It's "N Central Expy".
Whatever this TTS problem is, it doesn't seem to be consistent. Most streets announce fine, there seem to be just a few that don't.
I haven't figured out if it's always the same streets that fail to announce the abbreviations correctly, or if it's just a random failure that can occur on any street. Unfortunately, the streets that I've heard fail are far from my house so I can't easily go and drive them again.
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.
jasonh300 wrote:Worked for me...TTS at 0:23
https://www.dropbox.com/s/9wkkfh1ao3yw1 ... .53.08.mov
(Look at all the illegal landmarks!)
Users browsing this forum: No registered users