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.

Moderator: MapSir

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

Postby ehepner1977 » Sun Dec 13, 2015 9:55 pm

Permalink

Hannah St in Bloomington, IL. Han should be as in "Hand," is pronounced as in "HaHa"
LAM: Illinois Area 5 (IDOT District 5)
SM: Missouri
CM: USA
ImageImageImageImageImage
ehepner1977
Country Manager
Country Manager
 
Posts: 668
Joined: Sat Nov 06, 2010 1:14 pm
Location: Central Illinois
Has thanked: 234 times
Been thanked: 102 times

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

Postby ehcool68 » Sun Feb 05, 2017 4:53 pm

Wiki pages....are both of the these wiki pages known to be correct, or, which one needs a revision?

When 'N', 'S', 'E', or 'W' should NOT be pronounced as compass directions,


The global abbreviations wiki https://wiki.waze.com/wiki/Abbreviations_and_acronyms has
enclose the letter in single quotes.


The USA-specific wiki https://wiki.waze.com/wiki/Abbreviations_and_acronyms/USA has
the letter should be followed with a . (period)
Image Image Image
ehcool68
Beta tester
Beta tester
 
Posts: 22
Joined: Sun Apr 05, 2015 12:41 am
Location: Montgomery County, PA
Has thanked: 3 times
Been thanked: 2 times

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

Postby egnralnc » Sun Mar 30, 2014 7:02 pm

sketch wrote:Possible, then, that instead of failing to pronounce it as "north" after certain words/abbreviations, it's failing to pronounce it as "north" except after certain words/abbreviations. Same result (as far as we know); different causation.

In other words, it seems more likely that something in there is telling it to say "north" after a given list of things (e.g., "St", "Blvd", any numbers) than it is that something in there is telling it not to say "north" after "Pkwy", "Expy", "Chavez", and "Turnpike".


So, if that's the case, how to we get this fixed for "Pkwy", "Expy", "Tpk", etc.? Add to the Google Docs table?
ImageImageImage
Homebase: NW Raleigh & RTP NC
Extended areas covered: Greenville SC, Lincolnton/Denver NC
Waze running on Samsung Galaxy S3
egnralnc
 
Posts: 88
Joined: Sat Mar 29, 2014 6:59 am
Has thanked: 14 times
Been thanked: 4 times

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

Postby egnralnc » Sat Mar 29, 2014 3:24 pm

Hi all,
I have an issue in Raleigh NC with an exit ramp (https://www.waze.com/editor/?lon=-78.80 ... 12&env=usa). When approaching this exit, Samantha says "Aviation Parkway N" instead of "Aviation Parkway North". I've not seen anything in this forum to suggest that this shouldn't work. Any thoughts?
ImageImageImage
Homebase: NW Raleigh & RTP NC
Extended areas covered: Greenville SC, Lincolnton/Denver NC
Waze running on Samsung Galaxy S3
egnralnc
 
Posts: 88
Joined: Sat Mar 29, 2014 6:59 am
Has thanked: 14 times
Been thanked: 4 times

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

Postby e-sarge » Wed Jun 17, 2015 7:16 pm

e-sarge wrote:
e-sarge wrote:Here's another example. It's in Canada, but this is the best thread I found for drive being mis-pronounced doctor.

https://www.waze.com/editor/?env=usa&lon=-78.91376&lat=43.88275&layers=933&zoom=8&segments=80654014

    Segment is named "Glen Hill Dr S".
    Should be pronounced "Glen Hill Drive South".
    TTS said "Glen Hill Doctor South".

Please add this to the list.


Back in November I reported this one. I did some further testing, and discovered some additional information that could be crucial to resolving these. Obviously, the abbreviation "Dr" is working properly in most cases. However, there are a few places where it continues to be pronounced "doctor".

I discovered recently that when I approach the road from the east, and the expected voice instruction is to turn right, then it says "doctor". But if I approach from the west, the expected voice instruction is then to turn left, and then is says "drive". This is very interesting that the prefix of the turn direction is having an impact on "drive" versus "doctor".

I tested this at two different intersections along this short road, and I get the same result -- "doctor" when I turn right, "drive" when I turn left.

If you need me to do further testing, there is also a Glen Hill Dr N just 3 blocks north of here -- not sure whether the "north" versus "south" direction is relevant to the "doctor" versus "drive" decision, but based on this new finding, perhaps it might also be related. PM me if testing this becomes necessary.

Hopefully this new information can steer the people doing the debugging to finally find and fix this weird pattern.

I was able to test this last week and it works now. Fixed! 8-) :mrgreen:
ImageImage
Area Manager: Ontario, primary area: Municipal Region of Durham
Editing Resources: Editing Manual | Editing Best Practice
e-sarge
Area Manager
Area Manager
 
Posts: 872
Joined: Fri Mar 14, 2014 7:32 pm
Location: Oshawa, ON
Has thanked: 232 times
Been thanked: 51 times

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

Postby e-sarge » Wed Mar 25, 2015 10:38 pm

e-sarge wrote:Here's another example. It's in Canada, but this is the best thread I found for drive being mis-pronounced doctor.

https://www.waze.com/editor/?env=usa&lon=-78.91376&lat=43.88275&layers=933&zoom=8&segments=80654014

    Segment is named "Glen Hill Dr S".
    Should be pronounced "Glen Hill Drive South".
    TTS said "Glen Hill Doctor South".

Please add this to the list.


Back in November I reported this one. I did some further testing, and discovered some additional information that could be crucial to resolving these. Obviously, the abbreviation "Dr" is working properly in most cases. However, there are a few places where it continues to be pronounced "doctor".

I discovered recently that when I approach the road from the east, and the expected voice instruction is to turn right, then it says "doctor". But if I approach from the west, the expected voice instruction is then to turn left, and then is says "drive". This is very interesting that the prefix of the turn direction is having an impact on "drive" versus "doctor".

I tested this at two different intersections along this short road, and I get the same result -- "doctor" when I turn right, "drive" when I turn left.

If you need me to do further testing, there is also a Glen Hill Dr N just 3 blocks north of here -- not sure whether the "north" versus "south" direction is relevant to the "doctor" versus "drive" decision, but based on this new finding, perhaps it might also be related. PM me if testing this becomes necessary.

Hopefully this new information can steer the people doing the debugging to finally find and fix this weird pattern.
ImageImage
Area Manager: Ontario, primary area: Municipal Region of Durham
Editing Resources: Editing Manual | Editing Best Practice
e-sarge
Area Manager
Area Manager
 
Posts: 872
Joined: Fri Mar 14, 2014 7:32 pm
Location: Oshawa, ON
Has thanked: 232 times
Been thanked: 51 times

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

Postby e-sarge » Tue Mar 03, 2015 7:50 pm

voludu2 wrote:Rather than a difficult-to-maintain spreadsheet:

Why not a bugzilla (or other bug/issue/feature ) tracking software. One which allows users to vote for the most important feature requests.

And anyone can see the summary report of all or "all open" or "by oldest" or "most popular" and moderators would have the power to merge duplicate requests with a click of the button.

This would be easier to share with the team, too.

Waze editors frequently use space on different unofficial waze-related servers in different parts of the world. I bet it would be possible to find a little space for this.

(And while we are at it, to set up useful issue tracking for other things like road closures, for which the sheet is very cumbersome)


A couple of counter-points:

    TTS errors are bugs, and you don't 'vote' on bugs. All bugs, once confirmed as bugs, need to be fixed (eventually, given the restrictions of resources). Priority should be based on importance and capabilities, not popularity. New features we can vote on, but that's not what this thread is really about.

    And, a second TTS error that has a similar pattern as an existing is not a duplicate, in the same way that a typo might appear on two different Wiki pages -- not a duplicate, just two bugs to be fixed. A duplicate would be two users reporting the same TTS error on the same segment.

FYI, I'm not hung up on any particular tool. I personally don't find spreadsheets 'cumbersome', I find them 'useful' -- the closure spreadsheet works just fine for me. But we don't have to use a hammer if a screwdriver is more appropriate. In this case, we have a rather large list of TTS problems, so something tabular in nature is going to be the best fit.
ImageImage
Area Manager: Ontario, primary area: Municipal Region of Durham
Editing Resources: Editing Manual | Editing Best Practice
e-sarge
Area Manager
Area Manager
 
Posts: 872
Joined: Fri Mar 14, 2014 7:32 pm
Location: Oshawa, ON
Has thanked: 232 times
Been thanked: 51 times

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

Postby e-sarge » Tue Mar 03, 2015 3:12 pm

I think beej666 is on to something here, and it could be used to off-load some of the organization and research tasks from those who interface with the staffers.

If we had a public list (wiki page, google doc/google form, etc) where editors could report problems (with Permalinks), then we could unleash a small team of volunteer Waze editor geeks to do the research (possibly including estimated number of Wazers impacted based on the trip count of the affected segment, if we can get access to that), associate like problems together (all the mispronounced 'Bueno' together, Glen Hill 'doctor' South with Patriot 'doctor' East (same pattern for abbreviation problem), etc.).

Then we could all see the status of our requests, and enable the key players to strategize what to lobby the staffers for (most difficult, longest outstanding, largest group of impacted Wazers, some quick and easy fixes, etc.).

I'd be willing to help with the construction of something like this, if there's support from the senior editor community -- PM me!
ImageImage
Area Manager: Ontario, primary area: Municipal Region of Durham
Editing Resources: Editing Manual | Editing Best Practice
e-sarge
Area Manager
Area Manager
 
Posts: 872
Joined: Fri Mar 14, 2014 7:32 pm
Location: Oshawa, ON
Has thanked: 232 times
Been thanked: 51 times

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

Postby e-sarge » Fri Nov 07, 2014 6:16 pm

Here's another example. It's in Canada, but this is the best thread I found for drive being mis-pronounced doctor.

https://www.waze.com/editor/?env=usa&lon=-78.91376&lat=43.88275&layers=933&zoom=8&segments=80654014

    Segment is named "Glen Hill Dr S".
    Should be pronounced "Glen Hill Drive South".
    TTS said "Glen Hill Doctor South".

Please add this to the list.
ImageImage
Area Manager: Ontario, primary area: Municipal Region of Durham
Editing Resources: Editing Manual | Editing Best Practice
e-sarge
Area Manager
Area Manager
 
Posts: 872
Joined: Fri Mar 14, 2014 7:32 pm
Location: Oshawa, ON
Has thanked: 232 times
Been thanked: 51 times

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

Postby DwarfLord » Sat May 27, 2017 2:38 pm

Wayyyyy earlier in this thread there seemed to be resolution that the FS-xxx road-category prefix should pronounce as "Forest Service", similar to US-xxx, I-xxx, SR-xxx, CR-xxx, etc. The US even has a wiki article on Forest Service Roads (note, MVUM = Motor Vehicle Use Map published by the US Forest Service):

Current USA wiki article on Forest Service Roads wrote:
  • USFS roads on the MVUMs that are not named or with an alternative naming convention should be named "FS-XXXX" where XXXX is the USFS road name on the MVUM. For example, main FS-333 road might have stub roads FS-333A through FS-333E. (NOTE: THIS NAMING STANDARD IS CURRENTLY UNDER DISCUSSION/REVIEW 15 MAR 2015)
  • Fire Service Roads, roads designated for Forest Fire services, shall also use the "FS-XXX" designation

However, testing today with the Jane voice indicates FS-xxx is pronounced "eff ess".

Was there a decision that FS-xxx is not a supported road-category prefix after all? Or is it semi-supported, in the sense that it's considered OK to use, but not to voice?
DwarfLord
Wiki Master
Wiki Master
 
Posts: 4371
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 923 times
Been thanked: 1217 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users