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.

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

Postby GizmoGuy411 » Fri Sep 07, 2012 9:14 pm

vectorspace wrote:I'm sorry for posting this so late, but have been occupied with other things. I looked at the first post with the link to the document and didn't see a couple of things. I might have missed some.

Obvious:
== Cll (or CLL) is used all over NM for Calle (Street in Spanish). While Calle was in the first post spreadsheet, someone seemed to suggest "C" represent it. That seems too simple and might lead to confusion.

Indian Reservations:

I posted some of this on other threads I believe---that western US states especially have a lot of Indian reservations.

== Indian Service Route --or-- Indian Service Rte --or-- Indian Svc Rte

It would be nice to have ISR be placed in the TTS. This is relatively common. If there is some other standard, I don't care what it is. I am just worried that Indian reservations are under represented.

== Navajo Service Route --or-- other variant per above

This is less common, but I would imagine that each Indian tribe reservation may have their tribe name on some of these roads. While one could suggest NSR, I would wonder how many other tribes have special names. In New Mexico, it seems most tribes use the Indian Service Rte (or Route) on the map, but we have a large population of Navajos, so they may get special treatment.

== Indian Road

I have no idea if it is worth putting this in the mix, but have seen it a bit as well.



I agree that "C" is too simple of an abbreviation for "Calle".

At the moment however we are hesitating from making any more actual suggestions until we actually learn more about what is already recognized.

Since as you point out "Cll" and CLL" is commonly used for "Calle", I'll be sure to add those to the test list.

I was not entirely clear on your other suggestions however. Can you clarify which abbreviations are currently in use? I'll add them to the test list. I will also add any suggestions that you may not have actually seen on signs, but feel are likely being used. If you could check other mapping services, including state government sites, it may be helpful. I had no luck with a Google search nor in Wikipedia.

Later we can start making suggestions for abbreviation changes. That also probably also need an entire new forum thread to handle.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 times

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

Postby GizmoGuy411 » Sat Sep 08, 2012 2:18 am

Alice2 wrote:I just discovered how TTS treats one of the exits and streets here. On printed maps, the street is written as UTSA Blvd. The Waze map has it as Utsa Blvd. It is supposed to be pronounced as 'you tea ess aaa' sounding out each letter. TTS tries to say the name as a word - "ootsa Blvd". The exit signs for this street have it as 'UTSA Blvd / University of Texas at San Antonio', and TTS announces "ootsa Blvd / University of Texas at San Antonio". I see in this thread that to be pronounced as letters, they should be written as lower case surrounded by single quotes. That would probably look awkward -- 'u' 't' 's' 'a' -- and unmanageable if you have to write it very many times. How should this be handled to get the right announcement?



Since there is an "s" in name there is no was to just use spaces between the letters as "s" is currently the abbreviation for "South". And you are right that using the letters surrounded by single quotes would look awkward when displayed in the client.

Using U T 's' A would not be much better, although it would probably sound correct.

I'm afraid until we get that exception field that mapcat mentioned, the only way to handle it is to just spell it out.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 times

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.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 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.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 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 1169 times
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 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.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 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.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 times

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

Postby GizmoGuy411 » Sun Sep 16, 2012 6:08 am

jemay wrote:Another example abbreviation problems...

Type: General error
Description: voice calls this "west avenue north" but it is "west avenue N"
Reported on: Yesterday

N is the letter of the street (A,B,C,...L,M,N,O) So it is not North.... So what do I do with the request UR

https://www.waze.com/editor/?zoom=4&lat ... FTTTTTTTFT

Thanks


Unfortunately there is only one solution at the moment, and that is to rename the road [West Avenue 'n']. You could also name it [W Ave 'n'] however I would opt to be as close to however the local signage displays it.

Note that 'N' will not work, only a lower case 'n' works so far that we have found for TTS to actually pronounce the letter instead of the cardinal direction. So same holds, 'e', 's', and 'w'.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 times

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

Postby GizmoGuy411 » Sun Sep 16, 2012 4:59 pm

jemay wrote:...
Ok, I changed the four segments to be W Ave 'n', so when exiting the freeway the navigation would announce the street name correctly?


Yes it should, but please report back to let us know how the TTS sounds.
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 times

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

Postby GizmoGuy411 » Tue Sep 18, 2012 6:00 am

simonhowes wrote:...
We do get streets called "All Saints", However, as there are not many streets with this name it might be a good if we use "saint" in full rather than abbreviated.


That's our motto here. "When in doubt, spell it out!"
ImageImageImageImage

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 S4 w/ Android 4.4.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1325
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 411 times
Been thanked: 273 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users