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.

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

Postby GizmoGuy411 » Wed Feb 22, 2012 4:30 am

A section on Abbreviations has been added to the Waze Wiki "Editing Manual" under "How to label and name roads":
http://www.waze.com/wiki/index.php/How_ ... reviations

The lead post here has also been edited and updated.
ImageImageImageImage

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Wed Feb 22, 2012 7:17 pm

That is just it. The signs do not say New York City. They just say NYC with no spaces or periods.

So my thinking was that for that abbreviation TTS should just say " en wye cee" to reflect the same brevity.

Sent from my Galaxy Nexus using Tapatalk
ImageImageImageImage

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 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

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 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

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Sun Mar 04, 2012 10:20 am

sketch wrote:Have you tried "Thwy" yet? That's how it's abbreviated up on the exit signs up in Baton Rouge.


CBenson suggested that some time ago, however it has not been tested yet.

Don't you or jasonh300 ever get a chance to hear it?

At the rate that our map tiles are getting updated, I could drive down to Baton Rouge and learn the results faster!
ImageImageImageImage

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Sun Mar 04, 2012 5:43 pm

BrianCanFixIT wrote:I've just encountered a sign with "Drwy" for Driveway. so I guess the other permutation for this would also be valid: drwy, drway.



Thanks Brian. Added. Did you happen to hear the TTS results for them? Or were you not actually there.

Sent from my Galaxy Nexus using Tapatalk
ImageImageImageImage

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Mon Mar 05, 2012 3:34 pm

In a rush to get as much of the TTS abbreviation testing into WME before the update, I've added every outstanding entry from the list to WME last night.

Thanks to CBenson's link, I've also added the relavant abbreviations from the "Manual on Uniform Traffic Control Devices, Section 1A.15 Abbreviations Used on Traffic Control Devices" list today.

Anyone want to drive to NW Ohio or to the ski mountains of Colorado to test all of our entries. Maybe Jen can come to farm country, and I can go skiing!
ImageImageImageImage

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Thu Mar 08, 2012 7:08 am

CBenson wrote:I see that "Pr" has been added to the spreadsheet. Please note that the entries I have heard are for "Pr." - with the period (if that makes a difference).


Added.

I have started to add more abbreviations with periods, and once future batch of abbreviations is tested, I may go back through the list and test those that failed again with periods to see if there is any change.
Last edited by GizmoGuy411 on Sun Mar 11, 2012 9:53 pm, edited 1 time in total.
ImageImageImageImage

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Thu Mar 08, 2012 7:10 am

DonJ2 wrote:Does anybody know if "Par" is announced as "Parade" via TTS?

I did not see it in the spreadsheet. I'm asking because of a UR that says "Par St" is not "Parade St". Not a single segment along "Par St" is or ever has been "Parade St", so I'm wondering if TTS says "Parade St" instead?



I've added "par" for "Parade" to the list and the test rig. It may be quite a while before we can actually test it of course.
ImageImageImageImage

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Sun Mar 11, 2012 9:50 pm

CBenson wrote: I would also note I was somewhat surprised (not having any use for the "Manual on Uniform Traffic Control Devices" except for waze map editing) at how much each state might change that list. Here is Maryland's for example.


Yes that is a surprise. Maryland has quite a few more abbreviations than the fed list too. I looked my state of Ohio, and our abbreviation list is a copy of the federal list.

I supposed to do the our list right we should look at these for EVERY state. I'm afraid however I'm not up to the task, as our current list represents a fair amount of effort to date, and with only 35% tested so far, there will be a lot more to test once the map tiles are updated again.

Would anyone like to compare the MUTCD list for every state against our list and submit any additional abbreviations we should add?

http://mutcd.fhwa.dot.gov/resources/sta ... /index.htm
ImageImageImageImage

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.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users