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.

Moderator: MapSir

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

Postby jenncard » Thu Mar 01, 2012 6:07 pm

I just encountered a "Ste" (someone had intended as state) which I am pretty sure was pronounced as "suite"
Image
Recovering Waze addict, occasional driver and editor in LA.
jenncard
 
Posts: 737
Joined: Sat Jul 02, 2011 10:00 pm
Location: Somewhere in Los Angeles, but probably on my bicycle
Has thanked: 9 times
Been thanked: 8 times

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

Postby AlanOfTheBerg » Thu Mar 01, 2012 6:37 pm

I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."
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: 23422
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1074 times
Been thanked: 4512 times

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

Postby banished » Fri Mar 02, 2012 4:15 am

AlanOfTheBerg wrote:I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."


I am uncertain if spelling or standard abbreviations is taught at Street Sign School. :lol:

Normally, Trail would be Trl, Terrace would be Ter

https://www.usps.com/send/official-abbreviations.htm (click on the Street Suffixes tab).
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 R4CLucky14 » Fri Mar 02, 2012 4:19 am

banished wrote:
AlanOfTheBerg wrote:I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."


I am uncertain if spelling or standard abbreviations is taught at Street Sign School. :lol:

Normally, Trail would be Trl, Terrace would be Ter

https://www.usps.com/send/official-abbreviations.htm (click on the Street Suffixes tab).


With all this conflicts, why are we doing this? Wouldn't it be better to simply ask Waze to
implement a TTS field, so we can actually follow the goal of making it simple to the user: matching the BGS?
Tennessee Editors, paritipate in our Wikipage

Area Manager: Southeast Tennessee, USA. Includes Athens, Benton, Cleveland, Englewood, Greenback, Maryville, Madisonville, and surrounding areas.
Phone: HTC Thunderbolt, Verizon, Android 2.3.4.
R4CLucky14
 
Posts: 356
Joined: Fri Nov 25, 2011 10:21 pm
Has thanked: 0 time
Been thanked: 1 time

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

Postby jasonh300 » Fri Mar 02, 2012 5:36 am

I think the idea is to test and figure out which abbreviations aren't pronounced properly and then get Waze to fix them.

If Waze pronounces "Main St" - "Main Saint", we aren't going to start spelling it "Main Str" to get it to work. TTS needs to work with the standardized abbreviations.

So if you think something is being pronounced strangely, post it here, GizmoGuy will put it into his test rig, and he'll spend the weekend following the next map update driving around a cow pasture listening to TTS and determining which ones need to be reported.


I'm not drunk...I'm using Tapatalk.
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 » Sat Mar 03, 2012 9:24 am

R4CLucky14 wrote:With all this conflicts, why are we doing this? Wouldn't it be better to simply ask Waze to implement a TTS field, so we can actually follow the goal of making it simple to the user: matching the BGS?


Yes we have asked for an exception field, and Waze has said here in the forums that a solution is coming. (can't find the post at the moment). It may also come along with the ability to test the results immediately.

However the issues with TTS abbreviations, and TTS for full words are not exactly the same.

There are multiple layers to how the TTS engine works. Waze uses a product from Nuance that is sold customized for mobile use. Waze also has the ability to further customize what the TTS can say.

When they provide us with an exception field, was can over-ride the delivered TTS and have it say what we want for all the special cases we encounter, such as alternate local pronunciations, non English language words, and other similar infrequent cases.

Abbreviations however are used very frequently, and need to be available without always needing to use an exception field.

The abbreviation list we are building here is intended to test what Waze currently recognizes and to test future possibilities. Everything that we test is NOT necessarily what we would like Waze to actually use for TTS.

As others have mentioned above. we hope to get Waze to change the TTS for those abbreviations that we feel are most likely to be encountered in North American that are commonly used on signs.

The exception field can then be primarily for full words and hopefully only needed for abbreviations in rare exceptions.

So the combination of a Waze customized set of abbreviations, along with our ability to further customize anything in an exception field should provide the best solution.

While this will be important for North America, the exception field will be even more important for the rest of the world. The ROTW may well need their own custom abbreviation list too. And that is best left for discussion in another forum!
Last edited by GizmoGuy411 on Sun Mar 11, 2012 9:33 pm, edited 2 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 sketch » Sat Mar 03, 2012 7:26 pm

For the record:

"Intl" is pronounced like "Entull". It would be nice to have it pronounced as "International".

The example that led me here is doubly problematic, in fact: an exit is signed as "N.O. Intl Airport". If I label it "N.O. Intl", it'll say "North Oh Entull", but if I say "NO" it'll just be "No Entull". I'm going to label this segment "New Orleans International" for now, but it would be nice to have it somehow workable.
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5628
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1199 times
Been thanked: 1651 times

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

Postby jasonh300 » Sat Mar 03, 2012 7:38 pm

How about "Int'l"?
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 banished » Sat Mar 03, 2012 7:52 pm

jasonh300 wrote:How about "Int'l"?


I found the difference in TTS pronunciation between "Jr" and "Jr." (note the period), was "jay-are" and "junior" with the later being correct. I do not know if the difference between "Intl" and "Intl." would produce similar results, but though it worth mentioning in case it hasn't been tried, yet.
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 GizmoGuy411 » Sun Mar 04, 2012 8:58 am

sketch wrote:For the record:

"Intl" is pronounced like "Entull". It would be nice to have it pronounced as "International".

The example that led me here is doubly problematic, in fact: an exit is signed as "N.O. Intl Airport". If I label it "N.O. Intl", it'll say "North Oh Entull", but if I say "NO" it'll just be "No Entull". I'm going to label this segment "New Orleans International" for now, but it would be nice to have it somehow workable.


Thanks guys. I'll add your results sketch, plus another test with the abbreviations as banished, and jasonh300 suggested plus a few more of my own.


I previously added some common abbreviations for New York City to test, but I guess we should add a few others like for New Orleans, and Los Angles. But my mind is blank at the moment for other very large metro areas that are likely to have frequent such abbreviations on their local signs.

Any other suggestions anyone?
Last edited by GizmoGuy411 on Sun Mar 04, 2012 10:29 am, edited 2 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

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users