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: delilush

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

Postby qwaletee » Thu Aug 07, 2014 3:18 am

sketch,

Are you saying to use these abbreviations even when BGS doesn't (i.e., a different abbreviation or fully spelled out)?
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

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

Postby qwaletee » Wed Aug 06, 2014 8:26 pm

I can see Divers being an issue, as it is also a word unto itself.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

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

Postby qwaletee » Thu Jun 26, 2014 11:41 pm

I would say NY/NJ uses poo-LAS-key. More bad pronunciation key donations appreciated.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

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

Postby qwaletee » Fri Jun 13, 2014 9:30 pm

This is an old discussion.

Br can mean either Branch or Bridge in the real world. In TTS, unless there is some common pattern that would allow the TTS engine to differentiate the use cases, it has to be one or the other. Bridge is far more common, though Brg has much traction as well.

I'd be far more willing to sacrifice Branch to Bridge than the other way around. We can, perhaps, ask Waze to run us a report of every instance of "Br," and spell out all the Branch ones that we can find. It would be a big job, nonetheless, as each case would have to be examined, an determined to be Branch or Bridge.

Theoretically, yes, we could do it the other way around, and turn all Bridge instances of Br into Brg.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

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

Postby qwaletee » Fri May 23, 2014 1:12 am

Note that missing space before the first slash.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

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

Postby qwaletee » Tue May 20, 2014 3:59 am

How about one LESS space instead? Northern VA/Frederick instead of Northern VA / Frederick
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

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

Postby qwaletee » Sun May 18, 2014 8:57 pm

AlanOfTheBerg wrote:
qwaletee wrote:Have we ever had a problem with X=10th before? Per the UR below, the X in Malcolm X Blvd was being pronounced "tenth." I don't know if this is an isolated occurrence. I imagine if it is a problem, it could be resolved by changing "X" to "X." (with a period).

https://www.waze.com/editor/?zoom=5&lat ... 35&endshow

'X' should be sufficient to say "ex" instead of "tenth."


SHould be. In this case, apparently wasn't.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

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

Postby qwaletee » Thu May 15, 2014 3:14 pm

So TTS finds two-letter state names comma-cle?

I'll see myself out.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

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

Postby qwaletee » Mon May 12, 2014 5:34 pm

Have we ever had a problem with X=10th before? Per the UR below, the X in Malcolm X Blvd was being pronounced "tenth." I don't know if this is an isolated occurrence. I imagine if it is a problem, it could be resolved by changing "X" to "X." (with a period).

https://www.waze.com/editor/?zoom=5&lat ... 35&endshow
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

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

Postby qwaletee » Wed May 07, 2014 12:08 am

No, no, and no. When you have abbreviations that can easily conflict, you want to side with the most restrictive case which will produce the fewest false positives. I'm OK with LA-[0-9]{2-3] (regex match exactly LA- followed by exactly 2 digits or 3 digits), if it is asked for. But if you made LA by itself an abbreviation? You're asking for some road that abbreviates Los Angeles somewhere to be misread. I guarantee there are other similar issues for many abbreviations that would be nice to have.

Find a problem, solve the problem as narrowly as possible, and you will introduce the smallest number of false positive errors.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2924
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 231 times
Been thanked: 1127 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users