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

This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

Moderators: Jackson, krankyd, rondesta, adriansinger

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

Postby sketch » Tue Apr 15, 2014 12:23 am

That was my suspicion — I couldn't check the spreadsheet earlier.

Test again before taking my word on it — it appears I spelled out "Mount" on the exit I was thinking of back in June. But I do recall seeing "Mt Clemens" and hearing it pronounced "Mount Clemens", correctly, perhaps before that.
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

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

Postby sketch » Tue Apr 15, 2014 5:08 pm

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?
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

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

Postby sketch » Tue Apr 15, 2014 6:45 pm

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.
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

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

Postby sketch » Tue Apr 15, 2014 8:17 pm

Alan, have we included "BL" and "BS" for "Business Loop" and "Business Spur", or have we elected just to use "BUS" for Interstate business routes?

Also, how about "CONN" for Connector?

Related: Wiki update discussion for Road names/USA
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

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

Postby sketch » Tue Apr 15, 2014 8:25 pm

AlanOfTheBerg wrote:
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.

Perhaps this should be the sole exception, simply because of the prevalence of "St Whatever Ave" and similar roads throughout the country. It's not worth causing such a storm of problems just so that we can stick to a principle.

Not that it's a bad principle, but when a principle applied too strictly leads to absurd results, its application should be reconsidered.
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

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

Postby sketch » Tue Apr 15, 2014 11:07 pm

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.
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

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

Postby sketch » Wed Apr 16, 2014 3:55 pm

AlanOfTheBerg wrote:I have also noted that "Mt" and "Mt." both say "mount" but "Mt." sounds ... strange. It takes longer to say "mount" and there's a longer space after the word. "Mt" should be the standard.

Periods should be generally avoided unless necessary for differentiation ("St."; "Dr.").
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

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

Postby sketch » Wed Apr 16, 2014 9:14 pm

GizmoGuy411 wrote:I agree that we should reserve the period only for cases of ambiguity.

We do have "MT" in caps that is intended to say "Montana".

So while I think that is sufficient to differentiate it from "Mt", we can still add "Mt." to say "Mount", but only list "Mt" in our recommended abbreviation list.

Agreed.

Similarly, Alan also questioned my submission of "BUSN" for "Business" along with his prior submission of "BUS". I replied that we could indicate in the recommended list, that "BUS" should be used if signage says "BUS" or "BUSINESS", and only use "BUSN" when signage dictates.

Agreed mostly on this as well, but perhaps we should just use "BUS" to keep it consistent?

Aside: I also think we should maybe make "Expwy" the standard for "Expressway" — best to stick with the MUTCD where possible, IMO.
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

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

Postby sketch » Wed Apr 16, 2014 9:24 pm

CBenson wrote:But the MUTCD doesn't approve of BUS does it?

No, but road signs are more spacious than the Waze display. The MUTCD also forbids abbreviating "North", "South", "East", and "West" when they refer to compass direction, but we do it because it saves considerable space on the client. Better to see "Exit 234A: US-90 BUS W / Westbank" than have "Exit 234A: US-90 Business West / Westbank" be cut off on the screen.

As long as "BUS" is pronounced "business" by TTS, I don't believe it'll be confusing. "BUS" for "business" has been asked for kinda often.
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

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

Postby sketch » Thu Apr 17, 2014 4:44 pm

According to Chat, apparently "FM" and "RM", which are used by the state of Texas to designate "farm-to-market" and "ranch-to-market" roads, are being pronounced "Federated States of Micronesia" and "Room".

FM and RM roads in Texas are essentially a supplemental state highway system, like Missouri's "lettered" supplemental routes. They are all paved, with speed limits up to 75 mph, and many of them serve as major highways. They are named such as "FM 1234".

Can we have "FM" added as "farm-to-market" and "RM" as "ranch-to-market"?
iphone 5 • ios 7.1 • waze 3.7.9.914 • mac os 10.9.2
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Global Champ Mentor
Global Champ Mentor
 
Posts: 3542
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 462 times
Been thanked: 550 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users