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 GizmoGuy411 » Wed Sep 12, 2012 12:25 pm

AndyPoms wrote:I can report that "Arpt" in Hartford, CT says "Airport" in TTS... I drove these ramps all the time... (Permalink & Permalink as well as a few other ramps in the area)


Ick... what a crappy abbreviation! Never would have thought of that one.

It is added to the list.
Image

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: 1386
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 609 times
Been thanked: 408 times

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

Postby GizmoGuy411 » Wed Sep 12, 2012 12:32 pm

xteejx wrote:Any chance we can have Saint back the way it was, ie St at the start. Annoying work if we have to change them all!

Sent from my GT-I9100P using Tapatalk 2


Just to be clear, we have not requested any change in the way it currently works. Others have reported in the past that they have seen inconsistent results, including the same road being pronounced different at different times.

And as many of us have said before, positional abbreviation awareness is a bad idea. We would much prefer using the period for "St." to be Saint, "St" to be Street, "Dr." to be Doctor, and "Dr" to be Drive as examples.

The "Sulgrave Dr" being pronounced as "Sulgrave Doctor" issue (see previous posts) is probably another example of why we don't want positional abbreviation awareness! (This could also be a specific exception rule that Waze used for some reason, and not a positional awareness issue.)


xteejx wrote:So we have to change everything? I'll let our lot know :'-(

Sent from my GT-I9100P using Tapatalk 2


I would hesitate doing that for now. We have not made any suggestions to Waze for changes yet, and we have no idea which if any they will make or even can make.

While we know they have a tool to create specific exceptions, the TTS package is a delivered product from Nuance and they may be the ones who will need to make the changes we suggest and not Waze.
Image

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: 1386
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 609 times
Been thanked: 408 times

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

Postby GizmoGuy411 » Wed Sep 12, 2012 12:54 pm

The latest list contains several changes suggested by Wazers in the last couple of weeks.

Airport=Arpt was added.

Penn for Pennsylvania was moved from the main list to the State abbreviation list where it belongs, along with other alternate state abbreviations. Yes we definitely want it removed from the TTS! While in the State list, I also added a link for alternate State abbreviations and another for Canadian Providences that we should pull from to add to the list in the future.

vectorspace has done some good research on abbreviations that should be considered for our western States. The following were added to the list:

Bureau of Indian Affairs=BIA
Calle=Cll
Camino=Cam
Grande=? (no suggested abbreviations were found yet)
Indian Service Route=ISR
Service=Serv
Service=Svc
Valle=Vll

2 BIA 13.jpg
2 BIA 13.jpg (36.25 KiB) Viewed 1284 times
Image

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: 1386
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 609 times
Been thanked: 408 times

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

Postby mapcat » Wed Sep 12, 2012 1:41 pm

Is it essential to have TTS say "Bureau of Indian Affairs Thirteen" for that road? What's wrong with calling it "be eye ay thirteen"? Or would TTS call that "by-ah thirteen" instead?
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
mapcat
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 196 times

Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

Postby GizmoGuy411 » Wed Sep 12, 2012 3:58 pm

mapcat wrote:Is it essential to have TTS say "Bureau of Indian Affairs Thirteen" for that road? What's wrong with calling it "be eye ay thirteen"? Or would TTS call that "by-ah thirteen" instead?


I would think that the letters "BIA" would be fine if the TTS results were predictable for letters. However even when all caps are used, results can be either the letters spoken or an attempt to make it a word. Adding spaces works with exception of the N E S W letters which result in the cardinal directions. So "B I A" should work for now at least. I suppose I should add a test for "B.I.A." too, so as to match the signage.
Image

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: 1386
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 609 times
Been thanked: 408 times

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

Postby AlanOfTheBerg » Wed Sep 12, 2012 4:22 pm

GizmoGuy411 wrote:..."bee eye aye" ...

FYI, in my area of the country "eye" and "aye" are both pronounced the same. :lol:

Phonetic representation of that would be "eɪ" as in "say," but that makes me realize there is no real easy was to represent vowel-only sounds without resorting to "as in" or using the phonetic characters.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 10.1.1 | Waze v4.14
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23501
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1090 times
Been thanked: 4639 times

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

Postby GizmoGuy411 » Thu Sep 13, 2012 12:03 am

AlanOfTheBerg wrote:
GizmoGuy411 wrote:..."bee eye aye" ...

FYI, in my area of the country "eye" and "aye" are both pronounced the same. :lol:

Phonetic representation of that would be "eɪ" as in "say," but that makes me realize there is no real easy was to represent vowel-only sounds without resorting to "as in" or using the phonetic characters.


Just checked to see what phonetic representations I used in the list for the letters, and even they could get pronounced differently by various English speakers. Not sure where I even found them at the moment.
Image

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: 1386
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 609 times
Been thanked: 408 times

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

Postby floppyrod84 » Thu Sep 13, 2012 1:40 pm

Two letters would have worked. I and A ;-)

Sent from my GT-I9100P using Tapatalk 2
floppyrod84
 
Posts: 2582
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 45 times

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

Postby txemt » Fri Sep 14, 2012 2:55 am

I discovered, today, that "FM" reads "Farm to Market Rd." :D
Just wazeting my time to help you waze your route smoothly.
txemt
Area Manager
Area Manager
 
Posts: 4770
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

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

Postby vectorspace » Fri Sep 14, 2012 5:49 am

More on the Indian Reservations / Indian Nations...

Another road system in NM and AZ is the "Navajo Service Route XXX" roads. There are not a massive number of them, but they cover a lot of area. They are listed on http://www.navajotransit.com/, which is primarily some kind of bus system for those routes on the Navajo Nation.

I would suggest a short abbreviation as NSR-XXX. Others could take into account existing abbreviations as "Navajo Svc Rte XXX." I have not heard the TTS system pronounce "Navajo" to see if it comes out correctly either.

Regarding the BIA-XXX roads, which are more widespread, I would not suggest TTS expanding BIA to "Bureau of Indian Affairs," as that's rather long and one might have already passed a turn by the time it is spoken! Why can't the TTS system focus on cap letters and just say B. I. A.? I have not read this whole thread in detail, so I assume that has already been discussed for other acronyms.
vectorspace
vectorspace
 
Posts: 1184
Joined: Sat Dec 17, 2011 7:05 pm
Location: Albuquerque, NM, USA
Has thanked: 173 times
Been thanked: 420 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users