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 » 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!
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1406
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 430 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
gettingthere
Waze Global Champs
Waze Global Champs
 
Posts: 6083
Joined: Fri Nov 05, 2010 5:30 am
Location: Southern California, USA
Has thanked: 42 times
Been thanked: 206 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.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1406
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 430 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.
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 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.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23599
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1124 times
Been thanked: 4782 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.
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 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.
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)

Postby dbraughlr » Wed Feb 12, 2014 5:54 am

sketch wrote:You read left to right, top to bottom. Line one, then line two. 80 Business and SR 99, to Reno and Fresno. Maybe "SR-99 S Reno" doesn't make sense, but neither does "Reno Fresno". The slash is a separator. Go this way if you need to get to any of the following: I-80 Bus E, SR-99 S, Reno, or Fresno. Route names are more important to GPS navigation than city names, so they're read first.


Perhaps you read that way. But I read column 1, then column 2. I read the left column, then the right column. But anyway, taking it as a single column is not the rule being applied here anyway. The rule is unrelated to any reading order.

The proper reading is "Biz I-80 E : Reno; or SR-99 S: Fresno". This is the only logical way to read the sign. But the next instruction comes so fast that "Keep right onto Biz I-80 E or SR-99 S" would suffice. It will be followed immediately be either "Keep left onto I-80 Bus E / Reno" or "Keep right onto SR-99 S / Fresno".

I also think that city names can be more important. A lot of road can be confusing for how they are name and numbered. But the name of a distant city rarely sends you onto the wrong road. So in this tangled interchange, I am looking for South Lake Tahoe, Reno, or Fresno.

I am not listening for what I need so much as Waze is suppose to tell me what sign I should follow. It doesn't do that. Perhaps the segment name should be blank so that Waze will read to me only the correct one of the two signs that I should follow.
Last edited by dbraughlr on Wed Feb 12, 2014 6:14 am, edited 1 time in total.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: Test of Text-to-Speech (TTS)

Postby sketch » Wed Feb 12, 2014 3:09 am

dbraughlr wrote:There are a few exits/wayfinders that I've come across more than once that are interrupted by the next instruction. I'll have to pin a map issue next time I hear one. I know that another announcement starts immediately after "to I-80 Bus E / SR-99 S / Reno / Fresno". (Disorganized to follow an unreasonable rule rather than read off the BGSs separately from left to right. The two signs are 'biz' I-80 E to Reno and SR-99 S to Fresno. "SR-99 S Reno" makes no sense and is a wasted instruction.)

You read left to right, top to bottom. Line one, then line two. 80 Business and SR 99, to Reno and Fresno. Maybe "SR-99 S Reno" doesn't make sense, but neither does "Reno Fresno". The slash is a separator. Go this way if you need to get to any of the following: I-80 Bus E, SR-99 S, Reno, or Fresno. Route names are more important to GPS navigation than city names, so they're read first.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5924
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1422 times
Been thanked: 1949 times

Re: Test of Text-to-Speech (TTS)

Postby dbraughlr » Wed Feb 12, 2014 2:33 am

"Interstate" is an adjective modifying the noun "highway". I-routes are numbered highways of the federal interstate highway system. "I" is an abbreviation for "interstate highway". The abbreviation suffices and makes the speech shorter. FS-whatever is a Forest Service route. "Eff ess" serves the same function as "eye". Turning it into more words really doesn't help anything.

Broadway is not merely in the name; Broadway is the name. It is not "Broad Way".

Thortok2000 wrote:I named the road into the parking lot where I live 'Really long name of absolutely no significance except for testing.'

Not much can be inferred from your test. Though it does appear to approximate the length of "Forest service road 16W02 point 2".

There are a few exits/wayfinders that I've come across more than once that are interrupted by the next instruction. I'll have to pin a map issue next time I hear one. I know that another announcement starts immediately after "to I-80 Bus E / SR-99 S / Reno / Fresno". (Disorganized to follow an unreasonable rule rather than read off the BGSs separately from left to right. The two signs are 'biz' I-80 E to Reno and SR-99 S to Fresno. "SR-99 S Reno" makes no sense and is a wasted instruction.)
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users