# Test of Text-to-Speech (TTS) Abbreviations in Waze Clients
**URL:** https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949
**Category:** United States
**Created:** [January 18, 2012, 7:07pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949 "2012-01-18T19:07:25Z")
**Posts on this page:** 20
**Page:** 28
### Author:  [@sketch](https://www.waze.com/discuss/u/sketch)
#### Post date: [October 6, 2013, 2:41pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/541 "2013-10-06T14:41:16Z")
> [@taddison1](#):
>
> > [@jasonh300](#):
> >
> > 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.
---
### Author:  [@jasonh300](https://www.waze.com/discuss/u/jasonh300)
#### Post date: [October 6, 2013, 3:32pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/542 "2013-10-06T15:32:30Z")
> [@sketch](#):
>
> 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.
As of the last time I tried it, a couple of years ago, Expwy did not work with TTS.
---
### Author:  [@littlestlou](https://www.waze.com/discuss/u/littlestlou)
#### Post date: [October 6, 2013, 6:18pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/543 "2013-10-06T18:18:05Z")
> [@sketch](#):
>
> > [@taddison1](#):
> >
> > > [@jasonh300](#):
> > >
> > > 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=32.82098&lon=-96.78684&layers=TBFTFFTTTTFTTTTTTTTFTTTTFT](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!!!
---
### Author:  [@jasonh300](https://www.waze.com/discuss/u/jasonh300)
#### Post date: [October 6, 2013, 10:39pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/544 "2013-10-06T22:39:01Z")
Worked for me…TTS at 0:23
[https://www.dropbox.com/s/9wkkfh1ao3yw1xh/2013-10-06%2013.53.08.mov](https://www.dropbox.com/s/9wkkfh1ao3yw1xh/2013-10-06%2013.53.08.mov)
(Look at all the illegal landmarks!)
---
### Author:  [@bgodette1](https://www.waze.com/discuss/u/bgodette1)
#### Post date: [October 7, 2013, 6:36pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/545 "2013-10-07T18:36:16Z")
> [@jasonh300](#):
>
> I thought that was the voice of Siri. Samantha doesn’t sound like Siri at all.
>
> Personally, I wish I could change them over to [Jane Barbe](http://en.wikipedia.org/wiki/Jane_Barbe).
Siri is definitely Nuance Samantha, the reason Waze sounds different is Waze is using a lower bit rate and resolution than Siri.
---
### Author:  [@CBenson](https://www.waze.com/discuss/u/CBenson)
#### Post date: [October 11, 2013, 9:46pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/546 "2013-10-11T21:46:43Z")
> [@jasonh300](#):
>
> > [@txemt](#):
> >
> > > [@taddison1](#):
> > >
> > > I had a couple of odd abbreviation behaviors today:
> > >
> > > - In this street name: to Downtown / Cesar Chavez N, the “N” at the end was pronounced as the letter N instead of “North”. Any idea what could cause that, seeing as the N is not in quotes?
> > > Permalink: [https://www.waze.com/editor/?lon=-96.78599&lat=32.77489&zoom=7&layers=TBFTFFTTTTFTTFTTTTTTTTTFTT&segments=62245993](https://www.waze.com/editor/?lon=-96.78599&lat=32.77489&zoom=7&layers=TBFTFFTTTTFTTFTTTTTTTTTFTT&segments=62245993)
> >
> > I’ve just gotten a report about this today where the “N” was reading as “en” and not “north.” It is unknown if the other directional letters are doing the same thing or not.
>
> There’s a whole thread about this somewhere. It seems to be when roads have unconventional names. Such as US-11E N or Cesar Chavez N. If it was Cesar Chavez Dr N, it probably wouldn’t do it.
[Here’s a report](https://www.waze.com/forum/viewtopic.php?f=622&t=65361) that it is doing it after “Pkwy.”
---
### Author:  [@littlestlou](https://www.waze.com/discuss/u/littlestlou)
#### Post date: [October 12, 2013, 8:05pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/547 "2013-10-12T20:05:59Z")
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…
---
### Author:  [@littlestlou](https://www.waze.com/discuss/u/littlestlou)
#### Post date: [October 12, 2013, 8:07pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/548 "2013-10-12T20:07:58Z")
> [@jasonh300](#):
>
> Worked for me…TTS at 0:23
>
> [https://www.dropbox.com/s/9wkkfh1ao3yw1xh/2013-10-06%2013.53.08.mov](https://www.dropbox.com/s/9wkkfh1ao3yw1xh/2013-10-06%2013.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!! :lol:
---
### Author:  [@Jpere](https://www.waze.com/discuss/u/Jpere)
#### Post date: [October 13, 2013, 12:20pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/549 "2013-10-13T12:20:56Z")
> [@sketch](#):
>
> > [@taddison1](#):
> >
> > > [@jasonh300](#):
> > >
> > > 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”.
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.
---
### Author:  [@AndyPoms](https://www.waze.com/discuss/u/AndyPoms)
#### Post date: [October 22, 2013, 1:43am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/550 "2013-10-22T01:43:17Z")
Seems like “Dr.” may not work on forcing a “Doctor” - see the UR [HERE](https://www.waze.com/editor/?zoom=7&lat=41.38934&lon=-73.45714&layers=TBTTFFTTTTFTTTTTTTTTTTTTT&env=usa) ([BETA](https://editor-beta.waze.com/editor/?zoom=7&lat=41.38934&lon=-73.45714&layers=TBTTFFTTTTFTTTTTTTTTTTTTT&env=usa) for Conversation)
---
### Author:  [@qwaletee](https://www.waze.com/discuss/u/qwaletee)
#### Post date: [November 4, 2013, 10:43pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/551 "2013-11-04T22:43:06Z")
Br is commonly used for Bridge in my area. Disconcerting to frequently be told to bear left onto XYZ Branch. Example: [https://www.waze.com/editor/?lon=-74.20933&lat=40.64194&zoom=6&layers=TBFTFFTTTTTTTFTTTTTTTTTTT&env=usa&segments=31973592](https://www.waze.com/editor/?lon=-74.20933&lat=40.64194&zoom=6&layers=TBFTFFTTTTTTTFTTTTTTTTTTT&env=usa&segments=31973592)
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.
---
### Author:  [@AlanOfTheBerg](https://www.waze.com/discuss/u/AlanOfTheBerg)
#### Post date: [November 4, 2013, 11:04pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/552 "2013-11-04T23:04:41Z")
> [@qwaletee](#):
>
> 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.
As noted elsewhere, when in doubt, spell in out.
---
### Author:  [@Thortok2000](https://www.waze.com/discuss/u/Thortok2000)
#### Post date: [November 5, 2013, 1:25am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/553 "2013-11-05T01:25:11Z")
Weird bug happened today.
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?
---
### Author:  [@sketch](https://www.waze.com/discuss/u/sketch)
#### Post date: [November 5, 2013, 6:23am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/554 "2013-11-05T06:23:40Z")
> [@AlanOfTheBerg](#):
>
> > [@qwaletee](#):
> >
> > 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.
>
> As noted elsewhere, when in doubt, spell in out.
“Br” is apparently the abbreviation for “Branch” according to both the USPS and MUTCD. This is what Waze’s TTS abbreviations are apparently based on.
If a local authority disagrees with the USPS and the MUTCD, well, what can we do.
---
### Author:  [@AndyPoms](https://www.waze.com/discuss/u/AndyPoms)
#### Post date: [November 5, 2013, 9:56am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/555 "2013-11-05T09:56:41Z")
> [@sketch](#):
>
> > [@AlanOfTheBerg](#):
> >
> > > [@qwaletee](#):
> > >
> > > 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.
> >
> > As noted elsewhere, when in doubt, spell in out.
>
> “Br” is apparently the abbreviation for “Branch” according to both the USPS and MUTCD. This is what Waze’s TTS abbreviations are apparently based on.
>
> If a local authority disagrees with the USPS and the MUTCD, well, what can we do.
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).
---
### Author:  [@sketch](https://www.waze.com/discuss/u/sketch)
#### Post date: [November 5, 2013, 2:32pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/556 "2013-11-05T14:32:27Z")
> [@AndyPoms](#):
>
> 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.
Sent from my iPhone using [Tapatalk](http://tapatalk.com/m?id=1) 2
---
### Author:  [@GizmoGuy411](https://www.waze.com/discuss/u/GizmoGuy411)
#### Post date: [November 6, 2013, 3:41am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/557 "2013-11-06T03:41:31Z")
> [@Thortok2000](#):
>
> Weird bug happened today.
>
> 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?
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.
---
### Author:  [@bart99gt](https://www.waze.com/discuss/u/bart99gt)
#### Post date: [November 10, 2013, 6:05pm UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/558 "2013-11-10T18:05:06Z")
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.
---
### Author:  [@AndyPoms](https://www.waze.com/discuss/u/AndyPoms)
#### Post date: [November 11, 2013, 12:26am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/559 "2013-11-11T00:26:12Z")
> [@bart99gt](#):
>
> 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.
---
### Author:  [@orbitc](https://www.waze.com/discuss/u/orbitc)
#### Post date: [November 11, 2013, 2:13am UTC](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949/560 "2013-11-11T02:13:30Z")
I have a few instances as well:
to Garden State Pkwy N wasn’t correct. It read as “enn” not as “North”
Also, it’s reading “Dr” as Doctor.
[Previous page](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949.md?page=27)
[Next page](https://www.waze.com/discuss/t/test-of-text-to-speech-tts-abbreviations-in-waze-clients/57949.md?page=29)