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 bart99gt » Sun Nov 10, 2013 6:05 pm

I read through the first few pages, and last few pages of this thread, and didn't see this mentioned.

Is Waze in the process of adopting standard USPS two letter state identifiers to TTS? As I'm sure everyone is aware, Waze currently just says the letters individually, it would be nice to have it actually pronounce the actual state name, either when used as part of a highway name, or as a City, State type reference.
ImageImageImage
Mississippi State Manager
Memphis, TN Area Manager

Mississippi Wiki Page https://wiki.waze.com/wiki/Mississippi
bart99gt
State Manager
State Manager
 
Posts: 419
Joined: Mon Apr 15, 2013 9:53 pm
Location: Olive Branch, MS
Has thanked: 58 times
Been thanked: 148 times

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

Postby bart99gt » Mon Nov 11, 2013 12:55 pm

AndyPoms wrote:
bart99gt wrote:I read through the first few pages, and last few pages of this thread, and didn't see this mentioned.

Is Waze in the process of adopting standard USPS two letter state identifiers to TTS? As I'm sure everyone is aware, Waze currently just says the letters individually, it would be nice to have it actually pronounce the actual state name, either when used as part of a highway name, or as a City, State type reference.
This has been requested. However Waze doesn't say the letters in all cases, "CT" is pronounced "Court", "NY" is pronounced "North Why", etc.

We've also made a request to have things such as "CA-##", "NY-##", "MI-##", "LA-##" translate into the local "Route"/"Highway"/"El Ay"/etc name as well. This one is much longer term.


Very good, I figured that it probably had been, but sifting through 50 some pages would have been a bit tedious.
ImageImageImage
Mississippi State Manager
Memphis, TN Area Manager

Mississippi Wiki Page https://wiki.waze.com/wiki/Mississippi
bart99gt
State Manager
State Manager
 
Posts: 419
Joined: Mon Apr 15, 2013 9:53 pm
Location: Olive Branch, MS
Has thanked: 58 times
Been thanked: 148 times

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

Postby Baysidelass » Tue Aug 11, 2015 3:29 am

Hello, R2 editor here. A Point Place is named Pass & ID PAX NAS. When I navigated to it today, Jane said it as, "Pass and Idaho Paz Naz". Is there an acceptable abbreviation for "Identification"? PL is https://www.waze.com/editor/?env=usa&lo ... 107.645656 Thank you.
Baysidelass
Area Manager
Area Manager
 
Posts: 7
Joined: Mon Jun 01, 2015 4:36 am
Location: California MD USA
Has thanked: 13 times
Been thanked: 5 times

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

Postby Baysidelass » Wed Aug 12, 2015 6:40 am

PesachZ wrote:
Baysidelass wrote:Hello, R2 editor here. A Point Place is named Pass & ID PAX NAS. When I navigated to it today, Jane said it as, "Pass and Idaho Paz Naz". Is there an acceptable abbreviation for "Identification"? PL is https://www.waze.com/editor/?env=usa&lo ... 107.645656 Thank you.

Just to be sure I understand, is PAX an abbreviation as well, and what should it say? ( It sounds like pax to me now)
You can use "I.D." to say the letters I D


Hi, PesachZ, Thank you for clarifying "I.D." will work. "PAX" is short for Patuxent; for this location, usual abbreviation is "PAX RIV". Full name is Naval Air Station Patuxent River. I think this would work best for TTS; what do you think? "Pass & I.D. Office N.A.S. Patuxent River"
Baysidelass
Area Manager
Area Manager
 
Posts: 7
Joined: Mon Jun 01, 2015 4:36 am
Location: California MD USA
Has thanked: 13 times
Been thanked: 5 times

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

Postby Baysidelass » Wed Aug 12, 2015 10:39 pm

PesachZ wrote:
Baysidelass wrote:Hi, PesachZ, Thank you for clarifying "I.D." will work. "PAX" is short for Patuxent; for this location, usual abbreviation is "PAX RIV". Full name is Naval Air Station Patuxent River. I think this would work best for TTS; what do you think? "Pass & I.D. Office N.A.S. Patuxent River"

Depends on the desired result. "N.A.S." will say the letters NAS, whereas "NAS" will say Naval Air Station.


I think then it should be "NAS" because Naval Air Station will sound more familiar to new personnel and visitors looking for routing to the pass office. Thank you!
Baysidelass
Area Manager
Area Manager
 
Posts: 7
Joined: Mon Jun 01, 2015 4:36 am
Location: California MD USA
Has thanked: 13 times
Been thanked: 5 times

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

Postby beej666 » Mon Feb 23, 2015 7:35 pm

hi all,

one of my country managers (USA), kentsmith9, suggested i seek feedback here. i made a post at https://www.waze.com/forum/viewtopic.php?f=3&t=129244 because i'm trying to figure out the procedure for getting a TTS failure addressed.

i recently made a UR about the fact that a street named "Buena Vista Ave" has the "Buena" pronounced "Byoonah" by the TTS. the map editor who handled the UR uploaded this video demonstrating it: https://www.youtube.com/watch?v=EJ2Iw-L9__A

cheers,
marc
beej666
 
Posts: 33
Joined: Fri Nov 25, 2011 8:22 pm
Has thanked: 11 times
Been thanked: 1 time

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

Postby beej666 » Tue Feb 24, 2015 1:10 am

i still don't understand how the fix gets made. i've been made to understand that somebody from the Google Waze team will need to fill out some sort of request upstream with the TTS provider. who is that person? how does my request get in their inbox?
beej666
 
Posts: 33
Joined: Fri Nov 25, 2011 8:22 pm
Has thanked: 11 times
Been thanked: 1 time

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

Postby beej666 » Tue Mar 03, 2015 1:45 am

thanks for the responses.

forgive me if i sound presumptuous, but the current "system" for getting mispronunciations fixed sounds extremely error-prone, at best. even if the current mess were the best we could do given the current circumstances, some sort of order should be made of the chaos. at the very least, it would be nice if there were somewhere to go for users to see if their particular TTS gripe is already in process for getting fixed.

are either GizmoGuy411 or sketch up for putting up a wiki page documenting the current system and what is being fixed and what won't be fixed?

sending community members to this depressingly long thread when they report TTS problems just isn't a good idea, IMNSHO. it's a turnoff :-/
beej666
 
Posts: 33
Joined: Fri Nov 25, 2011 8:22 pm
Has thanked: 11 times
Been thanked: 1 time

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

Postby beej666 » Thu Mar 05, 2015 10:21 pm

sketch wrote:Trust me, it's no less disappointing waiting for months at Waze staff's toes


i feel your pain

sketch wrote:with a long list of desired pronunciations.


since you already have the list, why not post it somewhere? i guess this dead horse is tired of being kicked, but i just hate to see all this back and forth yield nothing tangibly good :-/

cheers,
marc
beej666
 
Posts: 33
Joined: Fri Nov 25, 2011 8:22 pm
Has thanked: 11 times
Been thanked: 1 time

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

Postby berestovskyy » Tue May 14, 2013 2:45 pm

Hi!
We have an idea how to improve TTS pronunciation and how to deal with abbreviations. Basically we suggest to use Alt City/Street name to correctly pronounce names and/or to specify a short (abbreviated) street name.

Please support if you like the idea! ;)

Thanks!
Last edited by berestovskyy on Tue May 14, 2013 9:20 pm, edited 1 time in total.
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users