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

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

Postby R4CLucky14 » Fri Feb 17, 2012 3:56 pm

After reading this thread for the first time, I really like the notion of a separate TTS field. Would solve alot of the issues with overlapping abbreviations.
Tennessee Editors, paritipate in our Wikipage

Area Manager: Southeast Tennessee, USA. Includes Athens, Benton, Cleveland, Englewood, Greenback, Maryville, Madisonville, and surrounding areas.
Phone: HTC Thunderbolt, Verizon, Android 2.3.4.
R4CLucky14
 
Posts: 356
Joined: Fri Nov 25, 2011 10:21 pm
Has thanked: 0 time
Been thanked: 2 times

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

Postby qwaletee » Fri Mar 31, 2017 9:57 pm

Kartografer wrote:
DrDisaster wrote:Chili is not pronounced like the food or chilly weather. It should be a long I like eye. Ch-eye-l-eye

xanderb wrote:In most cases where a word or road name is very commonly pronounced a certain way, it is impossible to replace for a single road. Those TTS replacements are done for the whole country.

Yes, a word can only be pronounced one way. For example, I'm sure New Yorkers would like Waze to read Houston St as "hauston street," but since Houston is pronounced as "hyuston" in the rest of the US we can't change it without making the pronunciation incorrect to more people.



German hauston?
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: 2921
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 Feb 26, 2016 7:47 pm

Poncewattle wrote:Just last week I was routed to a doctor that ended in PA (search result pulled from Google since there is no Waze place for it) and it said "You have arrived at Dr. Alfieri PA" but Jane pronounced it Pennsylvania.


I believe that's destination TTS, which does not use the same code as seg name 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: 2921
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 Dec 20, 2015 5:31 am

https://www.waze.com/editor/?env=usa&lo ... 5,82859798

Secaucus is pronounced correctly when it is at the end of the segment name, (se-CAW-cuss, segment on the upper right), but mispronounced when there is text following (se-CAW-keez, segment on lower left connecting to eastbound local lanes).
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: 2921
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 Dec 20, 2015 1:37 am

Really? I thought we followed whatever street signs said. 11 vs 11th seems like NBD for real estate, and "eleven avenue" sounds awkward to me.

PesachZ wrote:
G_W1Z wrote:Sorry if this has been discussed/posted before.

I have looked over the standard suffix abbreviations page and am left with a question: should numbered street names which appear on signs as letters be named with a number? Example: 11th Ave in Springettsbury PA (York). In WME (Permalink) it is given the digit name instead of the lettering.

This isn't really a TTS question both options "Eleventh" and "11th" will be spoken the same by TTS. However for uniformity, simplicity, and the smaller space on the screen it uses, we prefer the numerical digits when the sign is spelled out.

Sent from Android using Tapatalk
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: 2921
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 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: 2921
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 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: 2921
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 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: 2921
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 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: 2921
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 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: 2921
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