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

[ img ] 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: MapSir

Col. H. Weir Cook Drive - Indianapolis International Airport

Postby HossCartwright59 » Tue Apr 04, 2017 2:57 pm

Could someone direct me on how to get the pronunciation of this road fixed? See below from my posting to Waze map editor. Thank you in advance.

You received a comment on the map issue you reported, from 04.03.2017 on E 56th St, Lawrence - “The word "Col." in Col. H. Weir Cook Memorial Drive at the Indianapolis International Airport is not being pronounced correctly in Waze directions. It should be pronounced "Colonel" (i.e., same as "kernel"). He was a World War I flying ace and aviation pioneer from the Indianapolis area. Thank you. ”.

An editor from the Waze mapping community wants to solve the problem, but needs some more information.

enfcer74 on 04.03.2017 08:46 PM:

Thank you for the report on this. But the in app reports comes to the Volunteer Map Editing Community, and we have no access to change the Text To Speech Algorithms. You will need to submit that to the Forum Pages, and hopefully someone there can take it to the Developers, or have a solution for it. I believe the correct forum section is here https://www.waze.com/forum/viewforum.php?f=3
HossCartwright59
 
Posts: 1
Joined: Tue Apr 04, 2017 2:54 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby hpbna2 » Wed Oct 21, 2015 7:22 pm

Is it possible to change the pronunciation of Briley Parkway in Nashville TN to "Briley" with a long i vs. "Brilly," the way it is currently pronounced?
hpbna2
 
Posts: 1
Joined: Wed Oct 21, 2015 7:18 pm
Has thanked: 0 time
Been thanked: 0 time

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 invented » Fri Mar 30, 2012 9:41 pm

I found that Waze is pronouncing the acronym "QEW" as "cue". This is incorrect. Also, contrary to the wiki, Waze pronounces "WB" as "westbound" properly.

I'm also looking to see if there is an appropriate abbreviation for "Line".
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

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

Postby invented » Fri Apr 27, 2012 3:48 am

Does TTS say "1st" "2nd" "3rd" et al as expected?
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

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

Postby invented » Mon May 07, 2012 11:48 pm

So it seems putting single quotes around a cardinal letter gets it to say the letter? what about multiple, capitalized letters put together? eg.
Code: Select all
'NEWS' Rd
would be North East West South Road or Enn Eee Doubleyou Ess Road?

edit: seems that uppercase anything produces the cardinal direction in your testing. boo-urns.
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

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

Postby invented » Tue May 08, 2012 8:56 pm

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

Do the parenthesis insert spaces before and after the cardinal direction?

eg.

Hwy 900 (W) / Anytown

= "Highway nine hundred [pause] west [pause] anytown"

?
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

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

Postby invented » Wed May 09, 2012 11:56 pm

Confirmed that "3rd Street" comes out as "Third street"
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

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

Postby invented » Sat Jul 28, 2012 4:29 am

Waze still won't fix "QEW" to just say the letters. They don't have some kind of substitution power? Like when the software encounters "QEW" it feeds "cue eee double you" to the TTS engine?
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users