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 GizmoGuy411 » Mon Mar 12, 2012 2:37 pm

harling wrote:At present, the text on the display matches the signage, which I think is the best arrangement.
+1

harling wrote:Personally, I think it would be better for 'St.' to be "saint" anywhere, and "St" to be "street anywhere.
+1

harling wrote:But if the decision comes down that these abbreviations will remain positional as well as lexical, I'll start spelling them out.
+1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 647 times
Been thanked: 426 times

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

Postby harling » Mon Mar 12, 2012 6:08 am

jasonh300 wrote:
harling wrote:We have a "Summer St" in town. TTS correctly pronounces it "summer street". Off of that street is a court, named "Summer St Ct". TTS pronounces it as "summer saint court". Wait, what?
We have a "State Street Dr", which is an extension of State St in a different neighborhood. But the "Street" is always spelled out in "State Street Dr". I think there are other streets in that neighborhood that are the same way.

Around here, the signs never spell out the "street", just "St". (Many of them date from the '40s or earlier and are made of cast iron with raised letters, and are not likely to be replaced any time soon.) At present, the text on the display matches the signage, which I think is the best arrangement. Personally, I think it would be better for 'St.' to be "saint" anywhere, and "St" to be "street anywhere. But if the decision comes down that these abbreviations will remain positional as well as lexical, I'll start spelling them out.
harling
 
Posts: 1736
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 123 times

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

Postby GizmoGuy411 » Mon Mar 12, 2012 5:52 am

Based on harling's and jasonh300's last posts, I think our catch phrase when this is all said and done is going to have to be, "When in doubt, spell it out!" At least until we get an emulator.

Maybe that should be added to the Wiki now as the first rule of thumb for the use of abbreviations in WME.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 647 times
Been thanked: 426 times

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

Postby jasonh300 » Mon Mar 12, 2012 3:55 am

harling wrote:Here's a TTS issue that I noticed the other day.

We have a "Summer St" in town. TTS correctly pronounces it "summer street". Off of that street is a court, named "Summer St Ct". TTS pronounces it as "summer saint court". Wait, what?



We have a "State Street Dr", which is an extension of State St in a different neighborhood. But the "Street" is always spelled out in "State Street Dr". I think there are other streets in that neighborhood that are the same way.
jasonh300
 
Posts: 7567
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 402 times
Been thanked: 978 times

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

Postby harling » Mon Mar 12, 2012 3:52 am

Here's a TTS issue that I noticed the other day.

We have a "Summer St" in town. TTS correctly pronounces it "summer street". Off of that street is a court, named "Summer St Ct". TTS pronounces it as "summer saint court". Wait, what?

There are a lot of roads around here for which "St" and other abbreviations need to be pronounced the same regardless of position. I hadn't noticed this before because these are generally small side-streets not used for through-traffic, but people do live on them, and I can think of at least half a dozen examples off the top of my head in my own small town alone. (Smith St Ct off of Smith St, King St Ct off of King St, etc...)
harling
 
Posts: 1736
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 123 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
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 647 times
Been thanked: 426 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.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 647 times
Been thanked: 426 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.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 647 times
Been thanked: 426 times

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

Postby DonJ2 » Wed Mar 07, 2012 3:42 pm

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?
DonJ2
 
Posts: 281
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 46 times
Been thanked: 10 times

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

Postby CBenson » Tue Mar 06, 2012 10:09 pm

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).
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

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users