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 DonJ2 » Wed Aug 22, 2012 12:30 pm

GizmoGuy411 wrote:
AlanOfTheBerg wrote:I'm pretty sure I've heard most of those abbreviations such as 22nd, 31st, 44th, etc., fully pronounced correctly. I know for certain that roads like "209th Ave" are correctly pronounced, in the US, as "two oh ninth avenue" and 175th and 185th are "one hundred seventy-fifth" and "one hundred eighty-fifth" as you would expect.


That is good to hear Alan. (pun intended)

Do you recall hearing any specific combinations such as "1st St" or "3rd Rd", as those type of combinations with similar suffixes are the ones that I think would be most likely to fail.


Thanks for the fast response guys. Glad to hear that I don't need to be concerned about it, at least for the combinations that I've seen so far. :)
USA Country Manager
Area Manager: Florida - Brevard, Lake, Osceola, Orange, Seminole, Volusia
Motorola Droid RAZR - Verizon - Android 4.1.2
DonJ2
Beta tester
Beta tester
 
Posts: 280
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 30 times
Been thanked: 10 times

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

Postby DonJ2 » Tue Sep 11, 2012 1:47 am

AlanOfTheBerg wrote: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.


+1, I agree.
USA Country Manager
Area Manager: Florida - Brevard, Lake, Osceola, Orange, Seminole, Volusia
Motorola Droid RAZR - Verizon - Android 4.1.2
DonJ2
Beta tester
Beta tester
 
Posts: 280
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 30 times
Been thanked: 10 times

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

Postby DonJ2 » Tue Sep 11, 2012 1:51 am

AndyPoms wrote:I can report that "Arpt" in Hartford, CT says "Airport" in TTS...

Yuke, It almost looks like apartment.
USA Country Manager
Area Manager: Florida - Brevard, Lake, Osceola, Orange, Seminole, Volusia
Motorola Droid RAZR - Verizon - Android 4.1.2
DonJ2
Beta tester
Beta tester
 
Posts: 280
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 30 times
Been thanked: 10 times

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

Postby DwarfLord » Mon Apr 14, 2014 9:07 pm

AlanOfTheBerg wrote:Quick testing today showed these results. Only one failure.

Dr. MLK Jr. Pkwy = doctor em ell kay junior parkway
St. Penn Pkwy W = saint pen parkway west
Dr. St. John St = doctor saint jon street
St. Dr. St N = saint doctor street north
S Penn Dr = south pen drive
Penn Dr S = pen drive south
SH-219 = state highway two nineteen
US-410 BUS S = you ess four ten business south
I-84 BUS = eye eighty four bus

Talk about the "usual suspects"!

Can I suggest adding "Mt." (or Mt?) for "Mount" to the "usual suspects" list? Rarer than the others perhaps, but even in my neighborhood there is a "Mount Hermon Rd". We spell it out now and nobody's in a hurry to change that, but it would be nice to know if we could abbreviate if we wanted to.

Edit: In Washington there must be a "Mt St Helens Dr" or something like it somewhere :)
Image
DwarfLord
 
Posts: 183
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 97 times
Been thanked: 51 times

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

Postby DwarfLord » Mon Apr 14, 2014 9:27 pm

AlanOfTheBerg wrote:Already, MT = "mountain" according to the big list.
Does this mean "Mt St Helens Dr" would TTS as "Mountain Saint Helens Drive"? In that case street names beginning with "Mount" should probably continue to spell it out.

I am curious about this topic but as I do not quite know where the "big list" is officially documented and how TTS chooses from the "big list" as opposed to the list published in the Abbreviations and acronyms wiki -- I assume it involves the position of the abbreviation within the sequence but am not completely clear -- I should probably go back to lurking...!
Image
DwarfLord
 
Posts: 183
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 97 times
Been thanked: 51 times

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

Postby egnralnc » Sat Mar 29, 2014 3:24 pm

Hi all,
I have an issue in Raleigh NC with an exit ramp (https://www.waze.com/editor/?lon=-78.80 ... 12&env=usa). When approaching this exit, Samantha says "Aviation Parkway N" instead of "Aviation Parkway North". I've not seen anything in this forum to suggest that this shouldn't work. Any thoughts?
ImageImageImage
Homebase: NW Raleigh & RTP NC
Extended areas covered: Greenville SC, Lincolnton/Denver NC
Waze running on Samsung Galaxy S3
egnralnc
 
Posts: 23
Joined: Sat Mar 29, 2014 6:59 am
Has thanked: 8 times
Been thanked: 1 time

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

Postby egnralnc » Sun Mar 30, 2014 7:02 pm

sketch wrote:Possible, then, that instead of failing to pronounce it as "north" after certain words/abbreviations, it's failing to pronounce it as "north" except after certain words/abbreviations. Same result (as far as we know); different causation.

In other words, it seems more likely that something in there is telling it to say "north" after a given list of things (e.g., "St", "Blvd", any numbers) than it is that something in there is telling it not to say "north" after "Pkwy", "Expy", "Chavez", and "Turnpike".


So, if that's the case, how to we get this fixed for "Pkwy", "Expy", "Tpk", etc.? Add to the Google Docs table?
ImageImageImage
Homebase: NW Raleigh & RTP NC
Extended areas covered: Greenville SC, Lincolnton/Denver NC
Waze running on Samsung Galaxy S3
egnralnc
 
Posts: 23
Joined: Sat Mar 29, 2014 6:59 am
Has thanked: 8 times
Been thanked: 1 time

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

Postby gerben » Fri Jul 13, 2012 12:09 am

In The Netherlands, N roads are pronounced correctly, so this should be possible (we do write those as Nxxx, so without a space).
Nokia Lumia 920 (WP8 3.7.6 client)
Countrymanager The Netherlands
ImageImageImageImage
gerben
Waze Global Champs
Waze Global Champs
 
Posts: 4757
Joined: Sun Dec 13, 2009 10:42 pm
Location: Almelo
Has thanked: 31 times
Been thanked: 174 times

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

Postby gerben » Mon Feb 11, 2013 10:06 pm

As TTS abbreviations are language dependant, I guess this one belongs in the US subforum indeed.

Moved.
Nokia Lumia 920 (WP8 3.7.6 client)
Countrymanager The Netherlands
ImageImageImageImage
gerben
Waze Global Champs
Waze Global Champs
 
Posts: 4757
Joined: Sun Dec 13, 2009 10:42 pm
Location: Almelo
Has thanked: 31 times
Been thanked: 174 times

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

Postby gerben » Wed May 15, 2013 9:56 pm

Well, if they implement a filter for #tts, maybe it is better to implement a dedicated tts input field.
Nokia Lumia 920 (WP8 3.7.6 client)
Countrymanager The Netherlands
ImageImageImageImage
gerben
Waze Global Champs
Waze Global Champs
 
Posts: 4757
Joined: Sun Dec 13, 2009 10:42 pm
Location: Almelo
Has thanked: 31 times
Been thanked: 174 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: vectorspace