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 bgodette » Sat May 17, 2014 11:21 pm

mdavidsonjr wrote:How about the fm roads. Has that been fixed yet, still getting a few reports around houston on this one.


Sent from my iPhone using Tapatalk
FM #### is confirmed as saying Farm to Market, FM-#### likely does the same. If you're still getting reports, advise them to clear TTS cache by "navigating" to cc@tts in the app.
ImageImage
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3250
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 63 times
Been thanked: 393 times

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

Postby bgodette » Tue Aug 19, 2014 4:12 pm

GizmoGuy411 wrote:"Co" says "co" as in the word "cooperate"
"Cor" says "Corner"
"CR" says "County Road"
and now you have found that
"Cord" also says "County Road"

This will be added to the "Big List" and we will also add it the submission list to Waze for removal as an abbreviation.
Seems like Cord should be put into whatever the list is of "needs updating" so that it says Cord instead of County Road.
ImageImage
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3250
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 63 times
Been thanked: 393 times

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

Postby Bigbear3764 » Mon Jun 16, 2014 12:10 am

Chicagoans pronounce it Pull-as-kee


Sent from my iPhone using Tapatalk
Image Image
AM Chicagoland Area ILL Functional Class Map
CM North America
ILL Wiki
ILL To-Do
Bigbear3764
State Manager
State Manager
 
Posts: 2301
Joined: Fri Feb 10, 2012 8:02 pm
Location: Island Lake, IL USA
Has thanked: 141 times
Been thanked: 775 times

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

Postby bigtexun » Sat May 24, 2014 10:36 pm

So I'm getting very tired of hearing all of the Farm to Market roads called out as "Federated Micronesia"... Texas road names are weird, but in all fairness, it is impacting a lot of people that use waze.

In Texas
FM= Farm to Market (Farm to Market Road)
RR= Ranch Road
RM= Ranch to Market (Ranch to Market Road)

I see RM and RR used interchangeably on some roads, so it is not clear to me that both names aren't really the same.

In general it would be best not to expand abbreviations, just leave them as is.

But this Federated Micronesia stuff needs to stop, it has been going on for months.
bigtexun
 
Posts: 2
Joined: Sat Mar 10, 2012 12:23 am
Has thanked: 0 time
Been thanked: 0 time

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

Postby Binky71 » Mon Aug 20, 2012 4:29 am

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.
Rank 4 Editor
Location: Troy, Michigan, USA
Binky71
 
Posts: 38
Joined: Fri Sep 24, 2010 10:00 pm
Location: Troy, Michigan, USA
Has thanked: 4 times
Been thanked: 1 time

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

Postby Binky71 » Mon Aug 27, 2012 3:43 am

AlanOfTheBerg wrote:(Do the) The signs actually read "Gd Rapids" and "Gd River"? Either way, I don't see a good reason why we should abbreviate it. It's not like it takes up a lot of screen space to spell out Grand vs Gd and who knows if/when Waze will ever update the abbreviations list. It's better to have it read it out loud correctly than have the text match the sign 100%, IMO.


The point is well taken. The signs often do say "Gd" instead of "Grand". I've been putting them in as Grand. But if we want them to match the signs, then we should eventually make the change.
Rank 4 Editor
Location: Troy, Michigan, USA
Binky71
 
Posts: 38
Joined: Fri Sep 24, 2010 10:00 pm
Location: Troy, Michigan, USA
Has thanked: 4 times
Been thanked: 1 time

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

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users