jasonh300 wrote:Fortunately, I learned to drive a stick-shift when I was about 11.
1: “E” Rd, 2: 'E' Rd, 3: E. Rd, 4: “E.” Rd, 5: 'E.' Rd,
1: “e” Rd, 2: 'e' Rd, 3: e. Rd, 4: “e.” Rd, 5: 'e.' Rd, 6: e Rd,
AlanOfTheBerg wrote:Jr. B St. Dr. = "junior bee saint doctor"
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".
GizmoGuy411 wrote:Penn for Pennsylvania was moved from the main list to the State abbreviation list where it belongs, along with other alternate state abbreviations. Yes we definitely want it removed from the TTS!
jasonh300 wrote:kentsmith9 wrote:Cord is what I will be wrapping around my neck if we go a second month with no map updates in NA.
A second month??? We're almost 3/4 of the way through the second month!
Users browsing this forum: PvilleT