Gizmo,
I already sent you a PM but since this is an issue of potential public interest I will follow up on the forum too. I can confirm that while the TTS for CONST ZN worked previously, it no longer does. I am not sure how to send the TTS file. I will search around the wiki, etc. but if you can point me in the right direction, that would be helpful. I need very basic step-by-step instructions...unfortunately.
Thanks,
LL (and yes, I have a Droid 4)

Co Rd is now pronounced as "Coe Road" and not "County Road". Also contrary to naming conventions on the wiki. Again, this is a new issue, not a problem up until this release...

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".

Gizmo, I guess it's possible but I know for sure that CONST ZN and Co Rd happened at the same time. I cannot say for sure about the release prior to 3.5 b/c I had so many GPS issues that I went back to the release before last....

Regardless, I will start using CR. Thanks for the hint.

Regarding the infamous Coe Roads, I am almost positive that up until a couple of months ago, everything was pronounced correctly. Perhaps I am going a little nutty though. Either way, thanks for the tip on CR, etc.

So, just heard "Bus" (for Business) pronounced Bus...again, this is new for me, as of a month or two ago. I did clear out my cache at the recommendation of others but that never made a difference. Sorry if this is a repeat. I haven't been on the forums as much lately.

Wow, I guess I used a more out-dated version of Waze longer than I realized. I can confirm it worked before, as did CONST ZN and Co Rd but I only recently noticed otherwise. Again, must be using an older release. I am so behind the times.

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.

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 ... TTTFTTTTFT

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...

jasonh300 wrote:Worked for me...TTS at 0:23

https://www.dropbox.com/s/9wkkfh1ao3yw1 ... .53.08.mov

(Look at all the illegal landmarks!)

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!!

AlanOfTheBerg wrote:

xteejx wrote:Any chance we can have Saint back the way it was, ie St at the start. Annoying work if we have to change them all!

I don't think we should have Waze relying on positional pronunciation. It's just bound to fail. 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.

We do get streets called "All Saints", However, as there are not many streets with this name it might be a good if we use "saint" in full rather than abbreviated.