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 » Fri Nov 13, 2015 8:27 pm

mrsmith66 wrote:United States, New Jersey, Mercer County, Hamilton Township

"Gropp Ave" is read as "Grant Ave". Gropp rhymes with crop.


That's surprising since it is such a great discrepancy. Have you heard it yourself on multiple tries?
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: 1128 times

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

Postby qwaletee » Wed Nov 11, 2015 1:09 am

14-1 has been there since forever - at least two years. The nearby 14B-61 reads the dash as a short pause. I'd be fine with either that or "fourteen dash one."
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: 1128 times

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

Postby qwaletee » Tue Nov 10, 2015 9:21 pm

"Exits 14-1:" says "Exits 14 to 1" - yes, I know this should say Exit, not Exits. Nearby Exit 14B-61 works correctly. It is possible that there are special rules for ^Exit \d+-d+: ... if so, I can make the fix, drop the s, and test, before proceeding.
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: 1128 times

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

Postby qwaletee » Mon Oct 26, 2015 7:30 pm

voludu2 wrote:https://www.waze.com/editor/?env=usa&lon=-75.32026&lat=40.04081&zoom=5&segments=76507634&mapUpdateRequest=4816115

"Ithan" should be pronounced "Eye-thən". Jane says "Ee-thən"


Jane is clearly a Heathen.
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: 1128 times

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

Postby qwaletee » Sun Oct 25, 2015 1:38 am

voludu2 wrote:A UR reports that hoffmansville was mispronounced as "Houseman"

https://www.waze.com/editor/?env=usa&lo ... st=4801572

The UR will disappear soon. It states:
The diagonal Road is not houseman Road and is not straight across from New Hanover Square, Road


That's incorrect.

There was a BC to Hoffmansville before you fixed it, so at the time of the UR, there was no instruction for Hoffmansville. If you look, there's a nearby Houseman Rd to the northwest. That was probably part of the route.

Therefore, the driver was prompted for Houseman as the next turn, possibly as they approached the beginning of Hoffmansville. Due to the similarity of the names and the timing and the lack of instruction for Hoffmansville, the driver interpreted "Houseman" as a "bad Hoffmansville." They reported this as a bad road name, but apparently didn't notice that their expected keep/turn left was a turn right instruction!

Edit: Corrected a reference to Houseman - it had been written "Hoffman" (not Hoffmansville). Also corrected a misspelling of Houseman (Hoseman). The analysis is still the same.
Last edited by qwaletee on Sun Oct 25, 2015 9:43 pm, edited 2 times in total.
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: 1128 times

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

Postby qwaletee » Thu Oct 08, 2015 5:30 am

TheChrisK wrote:Hello!

Nebraska has three auxilliary state highway types, Links (L-##X), Spurs (S-##X) and Recreation Roads (R-##X). Recently I noticed that Nebraska Link 28B (L-28B) is translated by Jane as "EL TWO EIGHT BEE" instead of "NEBRASKA LINK TWENTY-EIGHT BEE"

I imagine the spurs and rec roads are being translated the in the same fashion but I have not navigated to one recently to know for sure.

PL: https://www.waze.com/editor/?env=usa&lo ... s=76193133

Let me know if you need more information.


Is this consistent across all L-nnX / S-nnX / R-nnX roads? Or have you found a single exception? The state wiki page claims that three formats are supported in TTS, but seems to indicate that there is always a 3-digit number, not 2-digits and a letter. If that's the format, then L-28B violates it.
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: 1128 times

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

Postby qwaletee » Mon Feb 23, 2015 11:32 pm

Rich,

City names do not go to TTS. If they appear as control cities in BGS, those would indeed go TTS.
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: 1128 times

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

Postby qwaletee » Mon Feb 23, 2015 10:32 pm

I see at least 14 states that have at least one street with Buena in it.
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: 1128 times

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

Postby qwaletee » Thu Sep 04, 2014 6:51 pm

Just waiting for the first international conflict with a dotted state abbreviation. Bwaaahhahha.

Seriously though, we have more than enough international conflict, I shouldn't jest. But I do. Coping mechanism.
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: 1128 times

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

Postby qwaletee » Tue Aug 26, 2014 4:22 am

Better safe than sorry, especially as we don't know how responsive they'll be if it comes out wrong and we ask for additional changes.
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: 1128 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users