Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderators: Jackson, krankyd, rondesta, adriansinger

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby LittlestLou » Sun Oct 06, 2013 6:18 pm

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!!!
ImageImage
LittlestLou
Beta tester
Beta tester
 
Posts: 237
Joined: Sat Jan 22, 2011 7:13 pm
Location: Dallas/Fort Worth Metro, North Texas
Has thanked: 5 times
Been thanked: 0 time

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby LittlestLou » Sat Oct 12, 2013 8:05 pm

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...
ImageImage
LittlestLou
Beta tester
Beta tester
 
Posts: 237
Joined: Sat Jan 22, 2011 7:13 pm
Location: Dallas/Fort Worth Metro, North Texas
Has thanked: 5 times
Been thanked: 0 time

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby LittlestLou » Sat Oct 12, 2013 8:07 pm

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!! :lol:
ImageImage
LittlestLou
Beta tester
Beta tester
 
Posts: 237
Joined: Sat Jan 22, 2011 7:13 pm
Location: Dallas/Fort Worth Metro, North Texas
Has thanked: 5 times
Been thanked: 0 time

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby mapcat » Wed Jan 18, 2012 7:57 pm

Thanks for putting together the list. Very thorough. I look forward to seeing the results as they come in.
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 193 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby mapcat » Thu Jan 19, 2012 7:01 pm

jenncard wrote:Per The Chicago Manual of Style, the correct abbreviation for Doctor is "Dr." and Saint is "St." (just as Ph.D. and NOT PhD is the correct abbreviation for that which I seek) :geek:

I must have left my Chicago Manual of Style in my other office, so I can't check, but what does it recommend for Drive or Street?
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 193 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby mapcat » Sun Jan 22, 2012 3:42 pm

banished wrote:
bmitch3020 wrote:Label: Geo Wash Pkwy
TTS: George Washington Parkway.


Label: Geo. Wash. Pkwy = TTS: George Washington Pkwy

Rationale: "Wash" is not wholly uncommon word in street names.

In cases such as this it makes much more sense to change the street name, IMO. If we acknowledge that some street names can be shortened, and not just commonly abbreviated prefixes/suffixes/directionals, we'd only over-complicate things, with little upside.
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 193 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby mapcat » Mon Jun 18, 2012 1:13 pm

AndyPoms wrote:
Webs101 wrote:Est is east in Quebec. It's grating to hear Waze say "estate" all the time.

Isn't that because it's French? (i.e. Nord, Sud, Est, Ouest = North, South, East, West)

Wouldn't it just be easier to use N, S, E, W as the cardinal (compass) directions in Waze? And then you can change the language in the app to either Engilsh (and get North, South, East, West) or French (and get Nord, Sud, Est, Ouest) - I think, I'm not about to change my Waze to French as I may never get it back to English.

No, he's saying that Waze pronounces roads like "Autoroute 20 Est" as "Autoroute Twenty Estate" instead of the preferred "Autoroute Vingt Est".

Unfortunately, the North America server (USA+Canada) only has English TTS at the moment, and until all the Anglo pronunciations are correct, I doubt they'll be able to work on the other languages.
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 193 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby mapcat » Sun Aug 26, 2012 1:57 pm

Someone pointed out that TTS has no idea what to do with "Trfwy", an abbreviation used for "Trafficway" in the Kansas City area. Trfwy is used on BGS, so even though it's geographically limited, it's still worth adding to the list.
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 193 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby mapcat » Sat Sep 08, 2012 1:00 am

Alice2 wrote:I just discovered how TTS treats one of the exits and streets here. On printed maps, the street is written as UTSA Blvd. The Waze map has it as Utsa Blvd. It is supposed to be pronounced as 'you tea ess aaa' sounding out each letter. TTS tries to say the name as a word - "ootsa Blvd". The exit signs for this street have it as 'UTSA Blvd / University of Texas at San Antonio', and TTS announces "ootsa Blvd / University of Texas at San Antonio". I see in this thread that to be pronounced as letters, they should be written as lower case surrounded by single quotes. That would probably look awkward -- 'u' 't' 's' 'a' -- and unmanageable if you have to write it very many times. How should this be handled to get the right announcement?

I don't think it's saying you're supposed to use lower case in quotes, just that that style will produce the desired result. It may prove valuable if Waze provides us with a TTS override field at a later date. But for now I don't think there's a way to get it to work; even leaving spaces in between the letters might get you a "south" where you don't want it.

On a related note, one of my job sites has the acronym OSUM, and that's how I entered it in my favorites list. At some point recently, Waze began announcing "Arriving at Awesome" as soon as I pull into the parking lot. Which is awesome.
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 193 times

Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien

Postby mapcat » Wed Sep 12, 2012 1:41 pm

Is it essential to have TTS say "Bureau of Indian Affairs Thirteen" for that road? What's wrong with calling it "be eye ay thirteen"? Or would TTS call that "by-ah thirteen" instead?
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
Waze Global Champs
Waze Global Champs
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 193 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users

cron