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 Jpere » Sun Oct 13, 2013 12:20 pm

sketch wrote:
taddison1 wrote:
jasonh300 wrote:What was the exact name of the expressway, as named on the Waze map? It's working fine at the expressway near me.


It's "N Central Expy".

Whatever this TTS problem is, it doesn't seem to be consistent. Most streets announce fine, there seem to be just a few that don't.

I haven't figured out if it's always the same streets that fail to announce the abbreviations correctly, or if it's just a random failure that can occur on any street. Unfortunately, the streets that I've heard fail are far from my house so I can't easily go and drive them again.

All the examples I saw with the "N" problem seem to be where Waze doesn't expect a "north", that is, wherever the N is not preceded by a street abbreviation or a numerical highway designation. So it didn't work on "Cesar Chavez N" or "I-35W N", while I assume it would work on "Cesar Chavez Dr N" or "I-35 N".


You could be on to something. There are some ramps I need to fix in the Miami area that read out as "Florida's Turnpike N" instead of "Florida's Turnpike North" and it might be because it's not expecting that N to be there.
Jpere
Beta tester
Beta tester
 
Posts: 206
Joined: Tue May 10, 2011 3:52 am
Has thanked: 42 times
Been thanked: 8 times

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

Postby Kandralla » Fri Sep 14, 2012 8:34 pm

GizmoGuy411 wrote:Penn for Pennsylvania was moved from the main list to the State abbreviation list where it belongs, along with other alternate state abbreviations. Yes we definitely want it removed from the TTS!


Am I correct in my assumption that this means that William Penn Highway will now be called "William Penn Highway" as oppoesed to "William Pennsylvania Highway"?

If so thanks, that was annoying.
Area Manager for Pittsburgh and Erie, PA
Kandralla
 
Posts: 67
Joined: Wed Jan 18, 2012 7:15 am
Has thanked: 0 time
Been thanked: 0 time

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

Postby karlcr9911 » Thu Aug 06, 2015 2:33 am

FM is not included on the abbreviations and acronyms list and is short for Farm to Market.

FM with no dash after it.
Country Manager: USA
State Manager: Texas | New Hampshire
Area Manager: New York City

iOS Beta Tester | WME Beta Tester
Image Image Image
Texas wiki | Welcome wiki | WME Extensions
karlcr9911
Waze Mentor
Waze Mentor
 
Posts: 938
Joined: Fri Aug 23, 2013 2:05 am
Location: North East Texas, USA
Has thanked: 95 times
Been thanked: 454 times

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

Postby karlcr9911 » Thu Aug 06, 2015 2:52 am

Yes please. It's used extensively throughout TX, much like RM. FM with no dash though. If you add a dash it changes it to Federation of Micronesia. THAT we do know. :)
Country Manager: USA
State Manager: Texas | New Hampshire
Area Manager: New York City

iOS Beta Tester | WME Beta Tester
Image Image Image
Texas wiki | Welcome wiki | WME Extensions
karlcr9911
Waze Mentor
Waze Mentor
 
Posts: 938
Joined: Fri Aug 23, 2013 2:05 am
Location: North East Texas, USA
Has thanked: 95 times
Been thanked: 454 times

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

Postby karlcr9911 » Thu Aug 06, 2015 2:56 am

PesachZ wrote:FM with a dash will no longer say Federated States of Micronesia either any more.


Good to know...Thank you!
Country Manager: USA
State Manager: Texas | New Hampshire
Area Manager: New York City

iOS Beta Tester | WME Beta Tester
Image Image Image
Texas wiki | Welcome wiki | WME Extensions
karlcr9911
Waze Mentor
Waze Mentor
 
Posts: 938
Joined: Fri Aug 23, 2013 2:05 am
Location: North East Texas, USA
Has thanked: 95 times
Been thanked: 454 times

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

Postby Kayos_On_The_Road » Wed Aug 06, 2014 3:12 pm

Hi,

A couple of TTS issues experienced in Canada (waze V3.8.0, Android 4.4.2, Navigation guidance English (US) (Tom)). The Canada Post abbreviation guidelines are what we are supposed to be using as a naming convention. The two issues are:

Full Name Abbreviation
Diversion Divers
Point Pt

Currently the TTS engine states "Divers" and "P T". On the wiki page the Point abbreviation is listed as untested, so I guess it doesn't work...

Thanks,
Kayos
Samsung Galaxy SIII, waze version 3.9.5.4
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 776
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 324 times
Been thanked: 52 times

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

Postby Kayos_On_The_Road » Wed Aug 06, 2014 8:40 pm

There are a few diversions around the Vancouver area and we recently had a bit of a debate about whether to stick with "Divers" or switch to "Diversion". I thought I would post the two issues I was aware of here to get some feedback and see if it would be something to change in the next version or not.

Thanks,
Kayos
Samsung Galaxy SIII, waze version 3.9.5.4
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 776
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 324 times
Been thanked: 52 times

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

Postby Kayos_On_The_Road » Tue Aug 19, 2014 4:39 pm

GizmoGuy411 wrote:After over two years, the Big List, finally now has every entry tested.

The list may not yet include all of the latest suggestions we are preparing to submit to Waze.


Can you please provide a link to the "Big List" the last time I looked at a list, Pt for point didn't work (verified about a month ago) and Divers for Diversion does not work and was not on the list.

Thanks,
Kayos
Samsung Galaxy SIII, waze version 3.9.5.4
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 776
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 324 times
Been thanked: 52 times

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

Postby Kayos_On_The_Road » Tue Aug 19, 2014 6:48 pm

Reading GizmoGuy411's post, it indicates everything has been tested. The list on the first post in this thread has not been updated, hence the request to see the current list.

Thanks,
Kayos
Samsung Galaxy SIII, waze version 3.9.5.4
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 776
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 324 times
Been thanked: 52 times

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

Postby Kayos_On_The_Road » Wed Aug 20, 2014 5:14 pm

Thanks GizmoGuy411. I was using the wiki link immediately above the google spreadsheet link. The current list actually shows entries for both PTS (Points) and PT (Point), but neither work as they show as n/a.

Looking forward to having these resolved as "Divers" is fairly common in my driving area and sounds pretty dumb when the signposts show Diversion. :)

Kayos
Samsung Galaxy SIII, waze version 3.9.5.4
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 776
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 324 times
Been thanked: 52 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users