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 txemt » Fri Jan 11, 2013 9:23 am

I have confirmed, today, that "SH" for "State Highway" is NOT working. :(
Just wazeting my time to help you waze your route smoothly.
txemt
Area Manager
Area Manager
 
Posts: 4769
Joined: Tue Jul 17, 2012 7:03 pm
Location: Miami, Fl
Has thanked: 42 times
Been thanked: 1032 times

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

Postby GizmoGuy411 » Fri Jan 11, 2013 12:56 pm

txemt wrote:I have confirmed, today, that "SH" for "State Highway" is NOT working. :(


Correct. Along with "SH" I have also just tested for "SH-123" also, and can re-confirm that is still does not work either.

I've also tested for various forms of abbreviations for "Township" and "Township Road" and did not find any that worked.

I'll add these results to the list shortly.

What I did discover was another anomaly, for differing results between the two audio files that are created for any given segment. One file always says just the "Street Name" property contents, while the other file says, the word "At" followed by "Street Name" property contents.

The test for "SH-123" resulted in one audio file that said "At ess-aitch one two three" and the other file said, "ess-aitch one hundred twenty three". Very curious.

The last such similar anomaly was with a test of “Borough”, “Parade”, and “Parish”, by using the abbreviations of "Boro par ph".

One file said "At borough parade phone, and other other said, "borough par pea-aitch".
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1357
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 527 times
Been thanked: 342 times

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

Postby AndyPoms » Fri Jan 11, 2013 1:13 pm

Pkwy confirmed by several people as Parkway.
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7064
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 127 times
Been thanked: 1283 times

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

Postby GizmoGuy411 » Fri Jan 11, 2013 2:07 pm

AndyPoms wrote:Pkwy confirmed by several people as Parkway.


Andy, do you happen to know which capitalization variations were confirmed?

Unfortunately, the TTS results are often defendant on capitalization, punctuation, and position with other words, not to mention the other issue I just mentioned in my previous post.

These make the TTS list that much larger and complicated, as most of the early tests did not take any of these depandancy issues into consideration.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1357
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 527 times
Been thanked: 342 times

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

Postby CBenson » Fri Jan 11, 2013 2:33 pm

"Pkwy" with the initial capitalization and no punctuation (as used here) gives me TTS of "parkway."
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.1.0.1
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10006
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 982 times
Been thanked: 2205 times

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

Postby hmarian » Fri Jan 11, 2013 3:49 pm

The same for me.
"Pkwy" is reading out "Parkway" on the client and is more consistent with road signage.
Could someone finish this test and add to the TTS Log FIle?

Once it is done there will be some work to change the segments to Pkwy.

Thanks,
Hagay.

Device: Samsung Galaxy S5 (5.1.1)
Waze Version: 4.1.0.1
Country Manager: Canada
Area Manager: Greater Toronto Area, Buffalo (NY), Binyamina (Israel)
Android/WME Beta Tester
-----------------------------------------------------------------------------------------
Editing Manual | Editing Best Practice | @Waze_Canada
hmarian
Waze Global Champs
Waze Global Champs
 
Posts: 2979
Joined: Tue Sep 24, 2013 9:08 pm
Location: Toronto, Ontario, Canada
Has thanked: 119 times
Been thanked: 1279 times

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

Postby rcenteno_davis » Fri Jan 11, 2013 4:17 pm

We also have some usage of "Pkwy" in my area and TTS does say "parkway" as expected. The doc has an entry for PKWY (in all caps). Do we need to add a separate row?
Area Manager: Union City, Fremont, Newark CA
Image
rcenteno_davis
 
Posts: 30
Joined: Sun Jul 22, 2012 2:53 pm
Has thanked: 0 time
Been thanked: 1 time

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

Postby GizmoGuy411 » Fri Jan 11, 2013 4:32 pm

hmarian wrote:The same for me.
"Pkwy" is reading out "Parkway" on the client and is more consistent with road signage.
Could someone finish this test and add to the TTS Log FIle?

Thanks,
Hagay.


rcenteno_davis wrote:... Do we need to add a separate row?


I've added "PARKWY, parkwy, Parkwy, PKWAY, pkwy, Pkway, PKWY, pkwy, Pkwy, PKY, pky, Pky, PKWAYS, pkways, Pkways" to the test rig for completeness, and will update the list in a couple of days, once the map tiles update and I can listen to the results.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1357
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 527 times
Been thanked: 342 times

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

Postby rcenteno_davis » Fri Jan 11, 2013 5:43 pm

GizmoGuy411, I still don't see the entry for "Pkwy" (only P capitalized), but for "PKWY" (all caps).
Area Manager: Union City, Fremont, Newark CA
Image
rcenteno_davis
 
Posts: 30
Joined: Sun Jul 22, 2012 2:53 pm
Has thanked: 0 time
Been thanked: 1 time

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

Postby AndyPoms » Fri Jan 11, 2013 7:41 pm

Only tested "Pkwy" (first letter capitalized, rest lowercase) in response to another thread...

On a side note "Waze" isn't pronounced correctly - not even close.
Image
Waze Champ & Forum Moderator
USA Country Manager
Senior Area Manager: State of Connecticut
Wiki: Editing | Best Practices | FAQ
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7064
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 127 times
Been thanked: 1283 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users