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

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

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

Postby GizmoGuy411 » Wed Jan 18, 2012 7:07 pm

[Please note that this lead post is edited periodically to reflect updated information, with any changes highlighted in the color of the date that follows:]

Post edit history:
2014-08-24 The Big List is now maintained entirely as a Google document and it no longer sourced from an Excel file.
2014-08-16 Every entry in the Big List has now finally been tested. A number of new entries also added.
2014-03-06 Column added to List to differentiate ROUTING TTS from DESTINATION TTS results.
2013-09-16 Minor rewrites of various paragraphs.
2012-10-31
2012-09-24
2012-09-06
2012-08-20
(earlier post edit history not maintained)



This is a list of abbreviations and acronyms that are being added to two sandbox test rigs, to be tested in the Waze clients to learn their TTS output results for North America. (Jenncard maintained a second test rig.)

All tests are with the Nuance female "Samantha" voice only as used in North America. While we expect that the other English voice choice for NA, "Tom", is likely to use the same TTS databases, we have not tested for it.

The list includes all the official and alternate abbreviations of the United States Postal Service, all the English abbreviations for Canada Post, a subset of the French abbreviations for Canada Post, a subset from the U.S. Federal Manual on Uniform Traffic Control Devices plus a number of others suggested by Waze users. (Additional abbreviations from the MUCCD for individual U.S. States and from any equivalent list for Canadian Provinces, have not yet been compiled.)

Official abbreviation list sources for specific states or providences are linked from their respective names in the test list.

If you already know or learn any TTS results, please post them here. Please submit only results that you are absolutely sure of, with the exact spelling (including any capitalization) of the abbreviation, and the confirmed TTS output result.

Also submit any additional abbreviations that you feel should be part of the list for testing and/or for future inclusion in the TTS system.

Some current abbreviations such as "Penn" (which generates "Pennsylvania") should probably be removed from the TTS system in favor of using the capitalized two letter State and Province abbreviation standards. We should also discuss others for consideration that may need to be removed from the TTS.

To hear the most current TTS results from your Waze client device, it may be necessary to clear your current TTS cache. Enter "cc@tts" without quotes in the Navigation search to clear the cache. Waze should reply with a "TTS cache has been cleared!" popup box. Then wait for "Searching ..." to end.

This list will be updated periodically. (The initial list was submitted 2012-01-18, which took a month for Waze to process, and for us to test in the Waze Clients.)

Once we learn what the TTS currently knows, we can add the results of this list to the Wiki, plus
we can use it to submit our requested TTS "wishlist" changes to Waze. Please note that entries in this are for testing purposes and do NOT automatically imply that we endorse them. This list is primarily to research as many possible abbreviations that we can test to learn what Waze currently recognizes or not.

To learn how to hear the TTS files on your Android device manually, read the side notes in the following post: viewtopic.php?f=10&t=15178&p=144296#p144296

A section on Abbreviations has been added to the Waze Wiki. The link below takes you to a selection of countries. Select your country from the list and follow the links to the abbreviations in your country:
Editing Manual > How to label and name roads (by country)

In the United States you can go directly to the US Abbreviations and acronyms list.

Google Drive Spreadsheet:
Text-to-Speech (TTS) Abbreviations in Waze Clients - Test List for North America aka the "Big List" or the "Big TTS Test List".

Last edited by GizmoGuy411 on Wed May 09, 2012 6:42 pm, edited 32 times in total.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1344
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 499 times
Been thanked: 315 times

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

Postby CBenson » Wed Jan 18, 2012 7:54 pm

I'm not sure how waze plans to handle regional/national/language diffences, but I am assuming that currently we are dealing with US English. If that is the case I would add in the state abbrieviations. For instance "MD" is pronounced "emm-dee" by waze. "Penn" is a problem and is pronounced "Pennsylvania."

I would also add the following:
Alternate - ALT
Bound - BND
Crossing - X-ING
Expressway - EXPWY
International - INTL
National - NATL
Route - RT
Throughway - THWY

I would also note that some abbrieviations are ambiguous: ST for Saint or Street and DR for Doctor or Drive. Also some streets are lettered thus there are "E St (or Ave, Blvd etc.)," "N St," "S St" and "W St" out there. Ultimately, there will need to be a method for distinguishing "St" when it means Saint and "St" when it means Street and "N" when it means North and "N" when is should just be "N." If this is done with punctuation then we need to test "St" and "St." etc. If this is done by parsing the phrase, that is "N" is N if followed by a road designation, but north otherwise, then we will need to indicate the different results depending on the phrase.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0, Waze 3.9.9.907
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9703
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 912 times
Been thanked: 2072 times

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
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 196 times

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

Postby AlanOfTheBerg » Wed Jan 18, 2012 8:04 pm

Was this also to end up being an official list to help them differentiate things like Penn vs. Pennsylvania, St vs. St. (saint) and Dr vs Dr. (doctor)? I think we need to add those too, unless I'm missing the purpose of the full abbreviation list.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 9.2.1 | Waze v4.2b
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23416
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1074 times
Been thanked: 4507 times

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

Postby jasonh300 » Wed Jan 18, 2012 8:59 pm

EXPY also works for Expressway.
Image
New Orleans, Louisiana
Regional Coordinator, South-Central Region
Waze FAQ ... Best Map Editing Practice
Ask me about Louisiana or Mississippi Editors Chat in Google Hangouts!
jasonh300
Waze Global Champs
Waze Global Champs
 
Posts: 7450
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA USA
Has thanked: 371 times
Been thanked: 920 times

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

Postby GizmoGuy411 » Wed Jan 18, 2012 11:12 pm

CBenson:
Excellent points CBenson. Some of the words you mentioned were already in the list I believe, however I'll be sure to add the ones you mentioned. At the Palo Alto Meet-Up there was discussion about many of the issues you mentioned. We did kick around the idea of using "St." for "Saint" and "St" for "Street" as you mentioned. I'll be sure to add "St." The list does have NE. NW, SE, & SW to see what they generate, but I forgot about the issue of differentiating roads named with a letter such as "E" from "east" as the current "E" abbreviation currently says. Since there are fewer roads named with a letter than roads that include a direction, we will have to think of a way to make them different. Maybe with quotes? Anyone else have ideas here?

I suppose I should test every letter of the alphabet to see what they say. N, E, S, & W may not be the only ones that produce a word.

mapcat:
Your welcome... altough I don't think I got any points for making that list did I? :)

AlanOfTheBurg:
Actually Alan, the list was to be multipurposed. Intially to learn what abbreviations the TTS already knows, and secondly to be a basis for creating our TTS "wishlist" for Waze. I'll see if I can make that clearer in the lead post. Thanks.

jason300
Thanks Jason.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1344
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 499 times
Been thanked: 315 times

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

Postby gettingthere » Wed Jan 18, 2012 11:18 pm

Request to add (does not work currently)

C - Calle - The abbreviation would be the first word in the street name

We'll need to add a bunch of Spanish abbreviations since there are loads of streets in many states where the street name is in Spanish.

Pso - Paseo - confirmed working in TTS
Av - Avenue - confirmed working in TTS
San Diego, California USA and Tijuana, Mexico
iPhone 6s Plus, iOS 9.2.1, Waze 4.1
Waze - PLEASE ADD CARPLAY SUPPORT
gettingthere
Waze Global Champs
Waze Global Champs
 
Posts: 6065
Joined: Fri Nov 05, 2010 5:30 am
Location: Southern California, USA
Has thanked: 37 times
Been thanked: 186 times

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

Postby GizmoGuy411 » Thu Jan 19, 2012 12:08 am

gettingthere wrote:... We'll need to add a bunch of Spanish abbreviations since there are loads of streets in many states where the street name is in Spanish. ...


Geez, I wonder who we could ask that might know those!
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1344
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 499 times
Been thanked: 315 times

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

Postby banished » Thu Jan 19, 2012 3:28 am

Jr. = Junior in TTS, as in Martin Luther King Jr. Blvd. I didn't see it in your list. I found that without the period, "Jr" induces TTS to say "jay are".

I expect the same result for "Dr." as in "Dr. Martin Luther King Jr. Blvd". Since most every town has a street honoring MLK, it's appropriate to include it in your extensive list. Nice work, by the way.
Fish don't know they're in water.
banished
Waze Global Champs
Waze Global Champs
 
Posts: 747
Joined: Mon Sep 28, 2009 11:03 am
Location: Florida
Has thanked: 185 times
Been thanked: 147 times

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

Postby bgodette » Thu Jan 19, 2012 4:38 am

Basically there needs to be positional awareness for handling things like St, Dr, N/S/E/W. Can anyone think of a name where St isn't Saint unless it's at the end of the name and therefore Street? Same thing for Dr.

N/S/E/W is the letter name if it's in the middle of the street name, or the only "word" before the St/Rd/Blvd/etc. So you can have "W N St" for "West Enn Street" and "N St" for "Enn Street", if you need "West North Street" you'll just have to use "W North St".

CR-### should be County Road, I'm not sure what we should use for State/County Route, maybe RT-### and TTS be "Route ###". (Rowwt or Root? it's regional)
SH-### should be State Highway ###.
US-### should be You Ess ### or You Ess Highway ### (I'd prefer to not have Highway but that's just me)
I-### should be Eye ###
ImageImage
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3343
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 87 times
Been thanked: 457 times

Next

Return to United States

Who is online

Users browsing this forum: gertbroos