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 » 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: 3495
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 455 times
Been thanked: 521 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: 3495
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 455 times
Been thanked: 521 times

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

Postby sketch » Thu Apr 17, 2014 7:00 pm

GizmoGuy411 wrote:Didn't you know you are now an island to yourselves? :shock:
Tell everyone it is a late Apri Fools joke.

Actually we are looking at what can be done short of just reverting "FM" back.

Would the format "FM-xxx" work, or are you way too invested in "FM xxx" without the hyphen?

So FM - Fed States of Micronesia was a purposeful change? Is "FM" ever used on a road to mean Fed States of Micronesia?

"SR" and "SH" don't depend on whether there's a hyphen, do they? Relying on the hyphen is too opaque 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: 3495
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 455 times
Been thanked: 521 times

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

Postby sketch » Thu Apr 17, 2014 7:28 pm

AlanOfTheBerg wrote:And, yeah, IMO, I don't know why we would ever really need any state name in segment names, but I'm sure it exists somewhere.
There's definitely an exit on I-59 in Mississippi (or maybe Georgia) that lists "Something, Ala." as one of its destinations served.


Sent from my iPhone using Tapatalk 2
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: 3495
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 455 times
Been thanked: 521 times

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

Postby sketch » Thu Apr 17, 2014 11:46 pm

Other considerations too, like do we really want LA to say "Louisiana"? Everyone here says "L A one", "L A forty-eight", and so forth.

I believe the idea was to get this done so we could use state abbreviations for state highways. Not that that's perfect. Some states would prefer SR or SH I'm sure — but the benefit of that is that we could get state-specific shields for every state. BUT of course it won't work for Nebraska.
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: 3495
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 455 times
Been thanked: 521 times

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

Postby sketch » Fri Apr 18, 2014 1:59 pm

All I'm saying is that we should consider each state abbreviation individually. If it's best that MD say Maryland, so be it. If people say "N C x" for NC state highways, keep the letters for that state.

We also don't want to be using "MI" instead of "M" for Michigan state highways because they're unequivocally referred to as "M-x". But for other states, it would be useful, like Maryland.

Obviously we can't achieve full parity because of Nebraska/northeast, so we might as well be accommodating.
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: 3495
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 455 times
Been thanked: 521 times

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

Postby Spil » Sun Jan 27, 2013 10:41 pm

Sorry, no input on the first one, but I'll take up this one for you:
Wajo357 wrote:2) On some of the ramps I've seen, the ramp name is "Exit 70A-B:...", but it is read as "exit 70ayybee" without any break between the ayy and bee. If I add a space before and after the dash Waze says "Exit 70ayy to bee. What do you guys recommend in such a situation?
In most such situations, the "Exit 70A-B" part of the ramp should be left unnamed, allowing TTS to use the appropriate "Exit 70A" or "Exit 70B" ramp name from the upcoming offramp. There may be some instances where the "Exit 70A-B" might be needed, though -- can you provide a Permalink to the interchange in question here?
I'm Spil, and I approve this message! :D
~ ~ AM: Upstate NY; CM: USA/Canada ~ ~
Wazing the I-86 Corridor with my Casio C771 G'zOne Commando
New York Editors: To-Do List!
Image
Spil
Waze Global Champs
Waze Global Champs
 
Posts: 1318
Joined: Sat Jul 16, 2011 12:11 pm
Location: Upstate NY, USA
Has thanked: 105 times
Been thanked: 27 times

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

Postby spock7230 » Thu Aug 22, 2013 5:41 pm

I've skimmed through the topic so far and have found a few entries that match the "street" vs "saint" problem with the "St" abbreviation, but haven't seen a clear answer yet on a best practice.

As part of my routing directions the other day, I was told to turn onto "Mechanic Saint Bypass," which has the street name label of "Mechanic St Byp" Is the best practice to spell out "St" as "Street" in the case where "street" isn't the last word in the street name? (Permalink) Otherwise, "St" is spoken "street" so far for me.

Thanks.
Image
iPhone 4 (Sprint) : iOS 6.1.3 : Waze Client 3.7.3.0
spock7230
 
Posts: 7
Joined: Tue Aug 20, 2013 5:57 pm
Location: Lowell, Massachusetts
Has thanked: 4 times
Been thanked: 0 time

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

Postby taddison1 » Thu Aug 22, 2013 2:40 am

A street near me, called "Ira E Woods" was/is being pronounced "Ira East Woods". The "E" is a middle initial, not a direction, so it needs to say "eee" instead of "East".

I looked at the spreadsheet, and it seems to suggest that adding a period after the E would cause it to say "eee", but then there's an accompanying note that says "n/a See East" which seemed contradictory.

Regardless, I recently added the the period, but last time I drove there it still said "East". Should this have worked? Do I just need to clear my tts cache and try again? If it makes a difference, I'm on IOS, not Android.

Perhaps the answer is already in this thread; I've skimmed through some of it but there are 53 pages so forgive me if I missed it :?

Thanks,
taddison1
taddison1
 
Posts: 55
Joined: Mon Oct 08, 2012 4:55 pm
Location: Dallas Ft. Worth
Has thanked: 13 times
Been thanked: 2 times

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

Postby taddison1 » Thu Aug 22, 2013 4:02 am

OK, thanks, I'll try the upper and lower case in single quotes.
taddison1
 
Posts: 55
Joined: Mon Oct 08, 2012 4:55 pm
Location: Dallas Ft. Worth
Has thanked: 13 times
Been thanked: 2 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users

cron