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 bmitch3020 » Fri Jan 20, 2012 5:29 pm

Any automated solution is going to result in a lot of one-off or edge cases that don't work correctly. I think the best solution is to provide a TTS input under the Label input. Use the default TTS rules if no values are provided, and show the expanded value. And if "customize TTS" or some other checkbox is selected, allow the map editor to put in plain English (or their language of choice) into the TTS box. E.g.:

Label: Dr. Martin Luther King Jr. St N
TTS: Doctor Martin Luther King Junior Street North

Label: N St.
TTS: N Street

Label: Geo Wash Pkwy
TTS: George Washington Parkway

This way the label can match the sign, but the editor can fix the TTS if we see the default isn't correct.
Brandon
Northern Virginia Area Manager
bmitch3020
 
Posts: 85
Joined: Mon Jan 16, 2012 1:22 am
Location: Fairfax, VA
Has thanked: 0 time
Been thanked: 0 time

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

Postby bmitch3020 » Mon Jan 23, 2012 7:15 pm

banished wrote:
bmitch3020 wrote:Label: Geo Wash Pkwy
TTS: George Washington Parkway.


Any abbreviation other than the standard N, E, W, S, St, Rd, Ave, Dr., etc., needs to include a period. For example,

Label: Dr = TTS: Drive
Label: Dr. (note the period) = TTS: doctor

Label: Geo. Wash. Pkwy = TTS: George Washington Pkwy

Rationale: "Wash" is not wholly uncommon word in street names.


I picked Geo Wash Pkwy on purpose because it's such a bad example. Trying to code the TTS for every situation like this would be a mistake. Like I said, we need a TTS override field where we can enter what is said, and still allow us to match the labels to the BGS.

(Sorry for not keeping up with the conversation, it seems that forum notifications are among the list of things that are breaking lately.)
Brandon
Northern Virginia Area Manager
bmitch3020
 
Posts: 85
Joined: Mon Jan 16, 2012 1:22 am
Location: Fairfax, VA
Has thanked: 0 time
Been thanked: 0 time

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

Postby bowieb2 » Tue May 13, 2014 2:44 pm

Any update on NE being pronounced "Nebraska"? My office is currently on the corner of "Nebraska 17th Court" and "Nebraska 14th Avenue" according to Waze.

"NE 38th St" does not have the issue any longer for some reason. Maybe because it's "St" rather than "Ave" or "Ct"?
bowieb2
 
Posts: 39
Joined: Mon Apr 08, 2013 2:14 pm
Has thanked: 8 times
Been thanked: 5 times

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

Postby bowieb2 » Tue May 13, 2014 4:32 pm

I just cleared the cache for the app. I'll see what it does at lunch and then send you a map link if the problem is still there.
bowieb2
 
Posts: 39
Joined: Mon Apr 08, 2013 2:14 pm
Has thanked: 8 times
Been thanked: 5 times

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

Postby bowieb2 » Mon May 19, 2014 1:42 pm

AlanOfTheBerg wrote:
bowieb2 wrote:Any update on NE being pronounced "Nebraska"? My office is currently on the corner of "Nebraska 17th Court" and "Nebraska 14th Avenue" according to Waze.

This is a cached street name. NE was fixed quite a while ago.


I am still getting the Nebraska pronunciation as of this morning. I cleared the cache before I left the house (Application Manager --> Waze --> Clear Cache). Is there something else I need to do?
bowieb2
 
Posts: 39
Joined: Mon Apr 08, 2013 2:14 pm
Has thanked: 8 times
Been thanked: 5 times

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

Postby bowieb2 » Mon May 19, 2014 1:52 pm

AlanOfTheBerg wrote:As noted above by bgodette, clearing tts cache is done by navigating to cc@tts (case sensitive).


Ah! I must have missed that. That's an odd way of doing things. I would have expected a button in the configuration or something.

Hopefully that will have fixed it. I'll test it in the morning (navigation does not speak those road names on the way home).
bowieb2
 
Posts: 39
Joined: Mon Apr 08, 2013 2:14 pm
Has thanked: 8 times
Been thanked: 5 times

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

Postby bowieb2 » Wed May 21, 2014 1:11 pm

bowieb2 wrote:
AlanOfTheBerg wrote:As noted above by bgodette, clearing tts cache is done by navigating to cc@tts (case sensitive).


Ah! I must have missed that. That's an odd way of doing things. I would have expected a button in the configuration or something.

Hopefully that will have fixed it. I'll test it in the morning (navigation does not speak those road names on the way home).


That worked! Thanks for the help!

Bowie
bowieb2
 
Posts: 39
Joined: Mon Apr 08, 2013 2:14 pm
Has thanked: 8 times
Been thanked: 5 times

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

Postby BrianCanFixIT » Sun Mar 04, 2012 4:51 pm

I've just encountered a sign with "Drwy" for Driveway. so I guess the other permutation for this would also be valid: drwy, drway.
Area Manager: Sacramento & rural California
iPhone 4s, iOS 5.0.1 JB
BrianCanFixIT
 
Posts: 37
Joined: Sun Dec 19, 2010 10:58 pm
Location: Northern California
Has thanked: 0 time
Been thanked: 0 time

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

Postby Bruce1224 » Thu Jul 17, 2014 3:23 pm

It's rare to see roads using just the letter "i" in the name but I have seen a couple.

I found a UR indicating that a county road, "CR-I-7" (that's the capital letter 'I') was pronounced "Interstate 7" by Waze tts directions. Can someone confirm if this can be alleviated by labeling the road "CR-'i'-7" similar to the convention, e.g., CR-'e' ?
Image
Bruce1224
Map Raider
Map Raider
 
Posts: 70
Joined: Fri Jul 12, 2013 2:20 pm
Location: Florida
Has thanked: 29 times
Been thanked: 4 times

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

Postby Bruce1224 » Fri Jul 18, 2014 1:22 pm

Re: the reply from Sketch two posts back -
I was able to drive to a county road late yesterday without going too many miles out of the way, properly labeled "CR-I" and tts did indeed pronounce it correctly as "eye". I'm too far from the road with the UR to check it out anytime soon, which is labeled "Rd I-7" but I put a message on the UR asking the reporter to confirm what he heard.
Image
Bruce1224
Map Raider
Map Raider
 
Posts: 70
Joined: Fri Jul 12, 2013 2:20 pm
Location: Florida
Has thanked: 29 times
Been thanked: 4 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users