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

[ img ] 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 » Sun Mar 04, 2012 7:14 pm

jasonh300 wrote:Fortunately, I learned to drive a stick-shift when I was about 11. :lol:

I taught myself when i was 13. It is amazing how much one can learn by watching very, very closely...

So, still no map update? At this rate, I'm thinking I should have kept adding more and more roads to my TTS playground!
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: 11 times

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

Postby jasonh300 » Sun Mar 04, 2012 7:09 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.


Was it a parking lot? I want to see a link to this.

I remember when I was about 8, and my dad taught me to how to operate a car, I had a hard time understanding why we put the car in Park when we're in the Driveway, but the car is in Drive when we're on the Parkway.

Fortunately, I learned to drive a stick-shift when I was about 11. :lol:
jasonh300
 
Posts: 7567
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 403 times
Been thanked: 978 times

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

Postby CBenson » Sun Mar 04, 2012 12:20 pm

I see that you have a abbr. source column now. The ones I originally suggested were found in section 1.A.15 of the Manual on Uniform Traffic Control Devices.
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2355 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!
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1411
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 663 times
Been thanked: 433 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.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1411
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 663 times
Been thanked: 433 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.
banished
Waze Global Champs
Waze Global Champs
 
Posts: 783
Joined: Mon Sep 28, 2009 11:03 am
Has thanked: 229 times
Been thanked: 170 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"?
jasonh300
 
Posts: 7567
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 403 times
Been thanked: 978 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.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5982
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1452 times
Been thanked: 2011 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.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1411
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 663 times
Been thanked: 433 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?
R4CLucky14
 
Posts: 356
Joined: Fri Nov 25, 2011 10:21 pm
Has thanked: 0 time
Been thanked: 2 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users