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

This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderators: Jackson, krankyd, rondesta, adriansinger

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

Postby harling » Fri Jul 20, 2012 11:13 pm

Upon arrival, TTS announces, "arriving at [name], at [address]", where [name] is the name of the favorite and [address] is the street address. For example, if my "Home" favorite is set to 23 Main St, Boston MA, it will announce, "arriving at home, at twenty-three main street." So far, so good.

For destinations that are not named favorites, [name] is the street address followed by the city. So if 23 Main St, Boston MA is not a favorite and I just navigate to it by address or via a History entry, it announces, "arriving at twenty-three main saint boston, at twenty-three main street". Oops!

I said over and over, and others said over and over, that the TTS rendering of abbreviations should not be positional. This is why.
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 111 times

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

Postby harling » Thu Aug 23, 2012 3:16 am

AlanOfTheBerg wrote:I think it would still be worth it to verify things like 41st St, 141st St, and other combinations that combine "rd" and "Rd" like 33rd Rd, 63rd Rd, etc. I would figure if one or two pass, others will too.

I'm willing to bet that "33rd Rd" and "33 rd Rd" will be pronounced differently.

Finally, no post of mine to this thread would be complete without an appeal, yet again, to make all TTS pattern-matching non-positional. When navigating by address to (for example) 52 Main St in Boston, upon arrival, TTS says "Arriving at fifty-two main saint boston, at fifty-two main street." Note that the same "St" that is pronounced as "street" when it is the last word in the text, is pronounced "saint" when another word is appended to the string.
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 111 times

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

Postby harling » Wed Sep 12, 2012 10:44 am

AndyPoms wrote:
AlanOfTheBerg wrote:I don't think we should have Waze relying on positional pronunciation. It's just bound to fail. If we make it a standard that "St" is "street" and "St." is "saint" then we know exactly how it will be pronounced regardless of where it is in the street name.
+1 for ease of use...

Been recommending that all along.
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 111 times

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

Postby harling » Wed Oct 31, 2012 4:38 pm

GizmoGuy411 wrote:This sounds like another one of those positional issues. I think I recall jasonh300 saying something before about a similar situation.

I'm not even sure how show in the list that "Br" is sometimes "Bridge" and sometimes "Branch" for the very same road segment, depending on how Samatha feels at the moment. I'll have to think on it.

Whether in the middle or the end of the ramp name, "Tobin Br" (as it appears on the signs) went from "Tobin Bridge" to "Tobin Branch" within the past year. Never mind that it also pronounces it "Tobbin" rather than "Toe-bin"... :-p
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 111 times

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

Postby harling » Wed Oct 31, 2012 9:55 pm

AlanOfTheBerg wrote:I spell out "Branch" and "Bridge" because Br is a valid abbreviation for both. I've see Brg for bridge, but haven't looked at the list to see if Waze pronounces it properly. It probably does.

I can tell you definitively that Brg = "bridge".
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 111 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 S3 (4.3)
Waze Version: 3.7.9.909 (Beta)
Country Manager: Canada
Area Manager: Greater Toronto Area
Android Beta Tester
hmarian
Waze Local Champs
Waze Local Champs
 
Posts: 273
Joined: Mon Jan 25, 2010 4:46 pm
Location: Toronto, Ontario, Canada
Has thanked: 4 times
Been thanked: 23 times

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

Postby hmarian » Tue May 14, 2013 3:33 pm

I support jasonh300 and think it is not such a great suggestion.
Working with Waze to fix this is the way to go.

Hagay.

Device: Samsung Galaxy S3 (4.3)
Waze Version: 3.7.9.909 (Beta)
Country Manager: Canada
Area Manager: Greater Toronto Area
Android Beta Tester
hmarian
Waze Local Champs
Waze Local Champs
 
Posts: 273
Joined: Mon Jan 25, 2010 4:46 pm
Location: Toronto, Ontario, Canada
Has thanked: 4 times
Been thanked: 23 times

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

Postby image619 » Tue Jul 17, 2012 6:36 pm

I tried to browse the thread and didn't see an answer to this, but I apologize if I'm treading on covered ground.

Is there any way to force the client to not translate a road name? In San Diego, we have a road names Upas St, and the client calls in Underpass St. (according to a problem report).

Here it is, in case you're interested:
https://www.waze.com/editor/?zoom=5&lat ... ts=6989588
image619
 
Posts: 5
Joined: Mon Jun 25, 2012 3:22 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby image619 » Wed Jul 18, 2012 4:53 pm

It is on Gizmoguy's spreadsheet, and listed as USPS standard abbreviation, so it's probably correct. However, it has an unwanted side effect in this case.
image619
 
Posts: 5
Joined: Mon Jun 25, 2012 3:22 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby imajica12345 » Thu Jan 03, 2013 2:04 pm

I live in Quebec and often we have streets with directions like east/west, but here it is spelled est/ouest. it pronounces the ouest as west which is fine, but it pronounces est as "Estate".

Something to eventually fix i assume
imajica12345
 
Posts: 15
Joined: Sun Dec 04, 2011 11:20 pm
Has thanked: 0 time
Been thanked: 1 time

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users