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

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

Postby GizmoGuy411 » Tue Aug 21, 2012 3:24 pm

zombie16 wrote:I can confirm that FM roads are pronounced as 'Farm to Market'. I have not come across any RM roads or PR roads while driving. I have seen PR roads in the map editor, though.


Thanks, I edited the list to show that you confirmed that the abbreviation "FM" is pronounced "Farm to Market".
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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 times

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

Postby GizmoGuy411 » Wed Aug 22, 2012 4:38 am

DonJ2 wrote:What does TTS say when streets use the following formats (for example)?

SW 41st Way (as in 40 first, I'm guessing TTS will say "Forty One Street Way"?)
SW 42nd Way (as in 40 second)
SW 43rd Way (as in 40 third, I'm guessing TTS will say "Forty Three Road Way"?)
SW 44th Way (as in 40 fourth)
... etc.

I've seen this format used in the basemaps. I could not find these abbreviations in the spreadsheet, so I'm wondering what TTS will do?


Good point! We intended to add more numerically named combinations, but never did. We only had "3rd", with no suffix which Waze did handled properly according to "invented".

There are a number of numerically named streets across town from me that I should be close to tomorrow. I'll try to see how they are handled. I'm afraid however that they are all "Streets", so testing for the "Road" suffix may take a while unless someone else can find some existing ones to report on.

I've also added the following to the list for future testing:

1st Rd
1st St
2nd
2nd Rd
2nd St
3rd
3rd Rd
3rd St
4th
4th Rd
4th St
41st Rd
41st St
42nd Rd
42nd St
43rd Rd
43rd St

I did not add the suffix "Way" as I figured, if there would be issues, it would be with the above combinations.
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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 times

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

Postby GizmoGuy411 » Wed Aug 22, 2012 4:56 am

AlanOfTheBerg wrote:I'm pretty sure I've heard most of those abbreviations such as 22nd, 31st, 44th, etc., fully pronounced correctly. I know for certain that roads like "209th Ave" are correctly pronounced, in the US, as "two oh ninth avenue" and 175th and 185th are "one hundred seventy-fifth" and "one hundred eighty-fifth" as you would expect.


That is good to hear Alan. (pun intended)

Do you recall hearing any specific combinations such as "1st St" or "3rd Rd", as those type of combinations with similar suffixes are the ones that I think would be most likely to fail.
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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 times

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

Postby GizmoGuy411 » Wed Aug 22, 2012 6:46 pm

Just confirmed a "101st St" in my area. So far so good. I'll have to add it specifically to the list.

No luck finding any "xxxrd Rd" yet that I can drive to however.
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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 times

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

Postby GizmoGuy411 » Thu Sep 06, 2012 4:42 pm

Ill add it to the list to show obedience that actually works correctly. Is that the exact capitalization and punctuation?

Sent from my Galaxy Nexus using Tapatalk 2
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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 times

Strange TTS behavior

Postby GizmoGuy411 » Thu Sep 06, 2012 6:18 pm

jhfrontz reported to me that a street, called "Sulgrave Dr" was being pronounced "Sulgrace Dee Are" instead of "Sulgrave Drive".

I created two test roads with that name. One I cut and pasted the name directly from the original road, and the other I manually entered the name.

I finally got around to listening to the TTS, and my test roads produce the same results.

By coincidence, I also just discovered a road by the same name, on the other side of town from me. I'll have to drive it and see if it also produces the same results.
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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 times

Re: Strange TTS behavior

Postby GizmoGuy411 » Fri Sep 07, 2012 8:06 pm

AlanOfTheBerg wrote:
GizmoGuy411 wrote:jhfrontz reported to me that a street, called "Sulgrave Dr" was being pronounced "Sulgrace Dee Are" instead of "Sulgrave Drive".

I've had TTS do this to Dr before too, but then with the same segment two minutes later on a return trip, pronounced it as "drive."


Well that does not bode well for testing!

And every segment of my local "Sulgrave Dr" has the same problem as our test roads, they are pronounced "Sulgrave Dee Are". I renamed them from "Dr" to "Drive" for now.

A quick search with Google found a number of roads with this name around the country. Renaming them all might be a nice labor of love for someone who would like taking on such a task!

And just in case anyone has a desire to know where this name came from, here is probably where:
http://en.wikipedia.org/wiki/Sulgrave
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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 times

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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 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.1.1
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1277
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 344 times
Been thanked: 204 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: e-sarge