Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

[ img ] 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 AlanOfTheBerg » Mon Mar 31, 2014 4:12 pm

CBenson wrote:I still get "Street Stephens Church Road" here without the period. (with Samantha)

Well, it does need the period. :)
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Apr 14, 2014 8:20 pm

Quick testing today showed these results. Only one failure.

Dr. MLK Jr. Pkwy = doctor em ell kay junior parkway
St. Penn Pkwy W = saint pen parkway west
Dr. St. John St = doctor saint jon street
St. Dr. St N = saint doctor street north
S Penn Dr = south pen drive
Penn Dr S = pen drive south
SH-219 = state highway two nineteen
US-410 BUS S = you ess four ten business south
I-84 BUS = eye eighty four bus
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Apr 14, 2014 8:35 pm

sketch wrote:Interesting. Wonder if it's relevant that it's the last word in the string.

My thought exactly. I defined the rule similarly to how N=north is defined, which is different than all the other cardinals, which may also explain why @txemt has noted that is seems "xyz Pkwy N" pronounces "enn" rather than "north." I will be checking on this.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Apr 14, 2014 9:11 pm

DwarfLord wrote:Can I suggest adding "Mt." (or Mt?) for "Mount" to the "usual suspects" list? Rarer than the others perhaps, but even in my neighborhood there is a "Mount Hermon Rd". We spell it out now and nobody's in a hurry to change that, but it would be nice to know if we could abbreviate if we wanted to.

Edit: In Washington there must be a "Mt St Helens Dr" or something like it somewhere :)

I can't believe that "Mt" or "Mt." is not in the BIG list at all. Unless we need to differentiate, I suggest just "Mt" = "mount"

Already, MT = "mountain" according to the big list.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Apr 14, 2014 9:41 pm

DwarfLord wrote:
AlanOfTheBerg wrote:Already, MT = "mountain" according to the big list.
Does this mean "Mt St Helens Dr" would TTS as "Mountain Saint Helens Drive"? In that case street names beginning with "Mount" should probably continue to spell it out.

Yes. When in doubt, spell it out is the mantra. I've added "Mt" to our request list to Waze.

DwarfLord wrote:I am curious about this topic but as I do not quite know where the "big list" is officially documented...

This is the community-built list which merely documents how TTS has been heard to work. It is a Drive document, link is at the top of this thread.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Apr 14, 2014 10:09 pm

sketch wrote:Is that only for MT in caps though? I'm rather certain "Exit 2xx: N River Rd / Mt Clemens" is pronounced properly, as of late last year.

The list is case sensitive so I don't think "Mt" had ever been officially tested.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Tue Apr 15, 2014 3:54 pm

Further testing has revealed a couple issues, possibly with exception programming, possibly with the base Nuance system in how it implements grep:
  • "St" at the beginning of a segment name is pronounced "saint"
  • "N" which follows another programmed abbreviation exception is pronounced "enn" (E, W, S are all OK after abbreviations)
  • "BUS" fails to expand to "business" if it is at the segment end.

Notes:
I confirmed my supposition based on the rule structure that in order to pronounce the letter name rather than the cardinal, you just need a non-spoken non-whitespace character in front of the letter. So, in our current naming standard, the closing single quote isn't required by the rules, but I think we keep it in place because it looks more correct:
  • S E St = "south east street"
  • S 'E' St = "south ee street"
  • S 'E St = "south ee street"

The following full test results from today (still have a couple more to do during lunch):
SH-219 S = "state highway two nineteen south"
SH-411 N = "state highway four eleven north"
S 'E St = "south ee street"
SH-8 BUS N = "state highway 8 business enn"
SH-8 BUS S = "state highway 8 business south"
CR-699 BUS N = "county road six ninety nine business enn"
I-5 BUS N = "eye five business enn"
St A St. = "saint a saint"
Hello Natl Thwy S = "hello national throughway south"
'W St. 'N N = "double you saint enn enn"
I-82 BUS E = "eye eighty two business east"
Jr. B St. Dr. = "junior bee saint doctor"
CR-12 BUS S = "county road twelve business south"
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Tue Apr 15, 2014 6:17 pm

sketch wrote:
AlanOfTheBerg wrote:"St" at the beginning of a segment name is pronounced "saint"

I don't believe this to be a problem. As long as "St" is still pronounced "Street" at the end, before a slash, and before another abbreviation, it's fine. There are so many instances of "St", no period, meaning "saint" on the map that it would be a mistake to change the way "St" behaves without addressing them all.

Besides, wasn't the problem that "St"/"St." was being pronounced "Street" in the wrong places, not the other way around?

It may not be a problem generally but 1) we want 100% positional independence, and 2) I bet there is one street named street somewhere. :)
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Tue Apr 15, 2014 8:18 pm

sketch wrote:
AlanOfTheBerg wrote:It may not be a problem generally but 1) we want 100% positional independence, and 2) I bet there is one street named street somewhere. :)

Ehhh... do we really though, in this case? Maybe, but it's going to be a mess. And if there's a street named Street, "Street" wouldn't be abbreviated anyway.

Perhaps not. I was going by our guidelines which have been "abbreviations do not vary based on where they are." We can start making a list of exceptions to this rule, or can stick to it.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Wed Apr 16, 2014 3:26 pm

sketch wrote:I don't doubt that there is a legitimate interest in divorcing TTS expansion from position. And I'm not saying "St" should never be location-independent. But the map isn't ready.

If "St." is now "saint" we can get going on that sort of edit-a-thon. But I think some time should be allowed to pass before the change to the TTS is made. There should be some sort of balance here.

I say start renaming everything starting with "St" which should be 'saint' now to avoid problems. As it is now, 'saint' is pronounced both at the beginning and sometimes in the middle of a segment name, eg. "Mt St Helens"
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users