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 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.4 RC
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 621
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 254 times
Been thanked: 46 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.4 RC
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 621
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 254 times
Been thanked: 46 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.4 RC
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 621
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 254 times
Been thanked: 46 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.4 RC
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 621
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 254 times
Been thanked: 46 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.4 RC
AM - Vancouver, BC and surrounding cities
Waze Beta Tester (Android)
ImageImage
Kayos_On_The_Road
Area Manager
Area Manager
 
Posts: 621
Joined: Tue Feb 25, 2014 2:05 am
Location: Surrey, BC, Canada
Has thanked: 254 times
Been thanked: 46 times

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

Postby Kayos_On_The_Road » Wed Aug 20, 2014 7:12 pm

Is it possible to apply the same logic as St. for Saint vs St for Street? This would make it Divers for Divers and Divers. for Diversion... doctorkb may also want to have some input on what to do here.

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

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

Postby Kayos_On_The_Road » Tue Sep 30, 2014 4:16 pm

I found a couple of TTS errors:

"to Hwy 91A N / Annacis Island" is translated as "to highway nighty one eh en" pause "annacis island"
"to Hwy 13 / 264 St / Aldergrove" is tanslated as "to highway thirteen thousand two hundred sixty four street" followed by the pause for the second slash an "aldergrove"

These are both segments starting with "to" Could this be what is causing the issue?

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

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

Postby Kayos_On_The_Road » Tue Dec 23, 2014 4:49 pm

For the last few months (I don't know exactly how long as I don't take this route often) this exit has been voiced as "to highway ninety one eh en, annacis island". Segment name is "to Hwy 91A N / Annacis Island"

https://www.waze.com/editor/?env=usa&lo ... s=59598325

and this one as "exit eleven, highway ninety one eh en, annacis island, new westminster". Segment name is "Exit 11: Hwy 91A N / Annacis Island / New Westminster"

https://www.waze.com/editor/?env=usa&lo ... s=59586780

Do these segments need to be changed to have the N voiced as "north"?

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

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

Postby KB_Steveo » Wed Nov 28, 2012 2:56 am

Tlwy says something like "Tl-whY"

(Line 622)
ImageImage
NE Wisconsin Area Manager (Green Bay / Appleton / Sturgeon Bay)
Wisconsin mapping resources
KB_Steveo
State Manager
State Manager
 
Posts: 258
Joined: Wed Jan 25, 2012 5:26 pm
Location: Wisconsin
Has thanked: 28 times
Been thanked: 17 times

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

Postby KB_Steveo » Wed Nov 28, 2012 3:01 am

GizmoGuy411 wrote:
LittlestLou wrote:Co Rd is now pronounced as "Coe Road" and not "County Road". Also contrary to naming conventions on the wiki. Again, this is a new issue, not a problem up until this release...



Are you sure, because I could swear that it has been that way for a while. We have a ton of county roads in NW Ohio, and we have slowly been changing them to "CR xxx" as we canvas the rural areas. "CR" does get pronounced correctly as "County Road", and not to be confused with "Country Road".

+1

Wisconsin county roads have been pronounced "Coh Road" since I started using Waze 10 months ago. We've been changing them to CR-xxx though (still works with the dash)
ImageImage
NE Wisconsin Area Manager (Green Bay / Appleton / Sturgeon Bay)
Wisconsin mapping resources
KB_Steveo
State Manager
State Manager
 
Posts: 258
Joined: Wed Jan 25, 2012 5:26 pm
Location: Wisconsin
Has thanked: 28 times
Been thanked: 17 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users