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: Re: Test of Text-to-Speech (TTS) Abbreviations in Waze C

Postby GizmoGuy411 » Thu May 10, 2012 12:36 am

invented wrote:Confirmed that "3rd Street" comes out as "Third street"


That is good news. Now I wonder how far we should test to. I suppose a look at New York City would be the best guess for max.

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

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

Postby GizmoGuy411 » Thu May 10, 2012 5:33 am

xteejx wrote:Actually, enclosing N/E/S/W in brackets also makes it say the directions.


Types of brackets (quoted in part from Wikipedia):
( ) — round brackets, open brackets, brackets (UK), or parentheses (called parentheses by Microsoft)
[ ] — square brackets, closed brackets, or brackets (US), (called square brackets by Microsoft)
{ } — curly brackets, definite brackets, swirly brackets, curly braces, birdie brackets, Scottish brackets, squirrelly brackets, braces, gullwings, seagull, fancy brackets, or DeLorean Brackets, (called curly brackets by Microsoft; see Character Map - %windir%\system32\charmap.exe)

I hate to say it, but I guess we need to test N/E/S/W with all of them.
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 S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 426 times
Been thanked: 275 times

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

Postby GizmoGuy411 » Fri Aug 17, 2012 2:17 pm

kentsmith9 wrote:I have been thinking about adding the known codes into the Wiki. I started collecting what I could find in the forums. I can create the Wiki page (unless someone knows it is there and I missed it) and add what I have found so far.


If you do so, it may be helpful to also include the visual and audio response that the client gives after issuing the command.
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 S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 426 times
Been thanked: 275 times

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

Postby GizmoGuy411 » Mon Aug 20, 2012 12:40 pm

binkowski wrote:SIAP, but the abbreviation "Gd" for "Grand" is used quite a bit on Michigan highway signs. Any chance of adding this to the abbreviation list? For instance, "Gd" is used sometimes (but not always) for Grand Rapids and Grand River.


Thanks for the suggestion.

My test rig on Waze was inadvertantly deleted by a well meaning AM several weeks ago. And while I have not given up on the project, I currently do not have time to continue it.

I will however be sure to add it to the list to be tested in the future, when I rebuild the rig.

Do you happen to know how Waze handles the abbreviation currently?
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 S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 426 times
Been thanked: 275 times

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

Postby GizmoGuy411 » Tue Aug 21, 2012 1:27 am

Alan makes an important point. Just because we add an abbreviation to the list and test it, does not mean that we desire Waze to actually use it. In fact, there are a number of existing abbreviations that we feel should really be removed.

Note that very few abbreviations in the list are marked to be added to Waze. The decision on what we feel Waze should add is actually a bit beyond the scope of this thread, and remains to be something for future discussion.

And although Waze has shown interest in our opinions on these abbreviation, we do not know if they will or can make any of the changes that we may eventually submit.

There are many instances where local abbreviations abound, yet the best choice for us as editors is to just spell out name.

As we have stated before, "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 S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 426 times
Been thanked: 275 times

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

Postby GizmoGuy411 » Tue Aug 21, 2012 1:08 pm

txemt wrote:In Texas, we have three roads which I've never seen in any other state (and I've been to half of this country):

FM-Farm to Market
RM-Ranch to Market
PR-Park Road (this may be used inside parks throughout the country, but Texas names them for roads going to a park or through a national/state park).

Most people ....


banished and mapcat had noted FM and RM some time ago and they were added to the list to be tested. And while PR sounds familiar, it was not yet in the list, so I added it for completeness.

And RR - Ranch Road is another Texas thing that deepeddy mentioned some time ago that I just found while searching the forums. I just added it too.

FYI, Farm-to-Market Roads also exist in Iowa.

Here is a link to an article about FMs in Wikipedia:
http://en.wikipedia.org/wiki/Farm-to-market_road

Image Image
Curious that neither sign mentions "Market". Great way to confuse non-Texans!

I'll be sure to add your test results, if you find them before we build another test rig.
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 S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 426 times
Been thanked: 275 times

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

PreviousNext

Return to United States

Who is online

Users browsing this forum: Baidu [Spider]