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: TTS and shield for FS-

Postby davielde » Tue Feb 11, 2014 9:15 pm

sketch wrote:Haha, well, of course business routes and spurs are often going to have the same number.

It's not fair to explain the rules after the game is already underway... :o

@All re: forest service roads. Just call it "Forest Service" and be done with it. Vectorspace put the time in for the research, has spoken with FS personnel, and obviously has the experience to back up his initial recommendation of just using "Forest Service". Even though FS personnel use FSR and vectorspace doesn't care either way, a quick search yields five road maintenance levels. They are all called "Forest Service Roads" in the sense that the Forest Service maintains them, and they are probably so busy maintaining them that they likely don't have time to waste behind a desk arguing about what they are called... Level 5 is what we would typically think of as a road while Level 1 is the scary, vegetation-covered, overgrown trail no one wants to walk down let alone drive down (if they could...) at night. In addition to redundancy and the other arguments for using "Forest Service" instead of "Forest Service Road" with TTS, hearing "road" is a disservice to the standard driver because we already have a preconceived idea of what a "road" should be. And these "roads" run the gamut from highways to non-existent.

Sketch referenced "emm" for Michigan state highways, so maybe my ear is just trained differently, but when I hear something like "M-36", I know that it is a road maintained by the state even if it is not announced as a state highway. In this case, it is just an entity maintained by the forest service. Once someone hears "Forest Service" more than once, they'll get used to the instruction even if it initially sounds foreign to their ear. And chances are they won't have cell reception for many of these roads, so they won't hear it anyway...
Image
CM: USA
SM: Michigan, Vermont
AM: Ann Arbor, MI & Thunder Bay, ON
WME Michigan
davielde
Country Manager
Country Manager
 
Posts: 1218
Joined: Tue Sep 17, 2013 2:01 pm
Location: Michigan, USA
Has thanked: 466 times
Been thanked: 750 times

Re: BI- prefix for interstate business loops

Postby davielde » Tue Mar 04, 2014 2:35 pm

dbraughlr wrote:I would expect BI- to be pronounced bee eye without a TTS abbreviation translation.
My proposal is to add "BI-" to the TTS translation so that it is read how ever it is that we want it to be read, and to the shield translation to get a green shield.

When I first started Wazing, I was very frustrated with numerous "Bus" TTS instructions where I drove. When I ranked high enough and became an AM, anything in my assigned area with "Bus" (per the Road Naming (USA) wiki page...) transitioned to "Business" spelled out like txemt stated.

"Business" is understandable to the ear whether it is a loop or a spur. I know that "Business Interstate" encompasses both loops and spurs, but in my region, that term is not used. We just say "Business Loop" and "Business Spur" depending on the route. Is "Business Interstate" used in common speech and signage outside of the Midwest? If so, I would be fine with "BI" but would likely still retain "Business" on local route names so as not to interfere with "loop" and "spur" signage and local speech. Perhaps add "BL" and "BS" to supplement?
Image
CM: USA
SM: Michigan, Vermont
AM: Ann Arbor, MI & Thunder Bay, ON
WME Michigan
davielde
Country Manager
Country Manager
 
Posts: 1218
Joined: Tue Sep 17, 2013 2:01 pm
Location: Michigan, USA
Has thanked: 466 times
Been thanked: 750 times

Re: BI- prefix for interstate business loops

Postby davielde » Tue Mar 04, 2014 7:31 pm

dbraughlr wrote:
davielde wrote:"Business" is understandable to the ear whether it is a loop or a spur. I know that "Business Interstate" encompasses both loops and spurs …

How about "BI-" → business eye to be generic for loops and spurs?

We could use "Business Loop 94", and "Business 94", and "Business I-94" ("eye") interchangeably without sounding strange and still follow signage. "Business Eye" would work.

I was focused solely on interstates this morning after reading the last few posts. After thinking more about it though, business routes for US highways are also common, and Michigan even has a few business routes for state trunklines (i.e. "Business M-60"). I wouldn't propose anything state-specific, but where would "Business US-[#]" routes fall? In making things convenient from a TTS and shield-generating standpoint for interstate business routes only using "BI-", are we sacrificing consistency with US business routes, or should potential abbreviations be discussed with those in mind as well? "BUS-[#]" likely wouldn't work as we know how that is pronounced...
Image
CM: USA
SM: Michigan, Vermont
AM: Ann Arbor, MI & Thunder Bay, ON
WME Michigan
davielde
Country Manager
Country Manager
 
Posts: 1218
Joined: Tue Sep 17, 2013 2:01 pm
Location: Michigan, USA
Has thanked: 466 times
Been thanked: 750 times

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

Postby davielde » Tue Apr 15, 2014 1:33 am

AlanOfTheBerg wrote:The list is case sensitive so I don't think "Mt" had ever been officially tested.

I could not find any reference to "Mt Clemens" quickly, but "Mt" pronounces as "Mount" for me: "at Mt Olivet Cemetery" < voice file

Permalink
Image
CM: USA
SM: Michigan, Vermont
AM: Ann Arbor, MI & Thunder Bay, ON
WME Michigan
davielde
Country Manager
Country Manager
 
Posts: 1218
Joined: Tue Sep 17, 2013 2:01 pm
Location: Michigan, USA
Has thanked: 466 times
Been thanked: 750 times

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

Postby davielde » Wed Aug 06, 2014 8:29 pm

qwaletee wrote:I can see Divers being an issue, as it is also a word unto itself.

I may just be easier to spell out "Diversion". I have not encountered too many in Canada, but I'm not sure how popular it is outside of Ontario.
Image
CM: USA
SM: Michigan, Vermont
AM: Ann Arbor, MI & Thunder Bay, ON
WME Michigan
davielde
Country Manager
Country Manager
 
Posts: 1218
Joined: Tue Sep 17, 2013 2:01 pm
Location: Michigan, USA
Has thanked: 466 times
Been thanked: 750 times

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

Postby davielde » Sun Dec 07, 2014 3:14 am

PesachZ wrote:
miked_64 wrote:Speaking of problems with letter abbreviations - this UR in Michigan for West "AB" Ave (W AB Ave in the editor) reports that it's pronounced as West Alberta Avenue.

edited url

you may have to change the name of the segments in waze to "W 'AB' Ave", unless the street sign says something different.

If that doesn't pronounce as Alberta, won't it pronounce as "ab" and not the intended "aye bee"? Local usage is to distinguish each letter as this is used in a north to south mile grid. Kalamazoo county would also have a similar issue with "DE Ave" pronouncing as Delaware instead of "Dee Eee" (although that is not as long of a street or in as populated of an area as AB Ave). Maybe use "A B" and "D E" instead?
Image
CM: USA
SM: Michigan, Vermont
AM: Ann Arbor, MI & Thunder Bay, ON
WME Michigan
davielde
Country Manager
Country Manager
 
Posts: 1218
Joined: Tue Sep 17, 2013 2:01 pm
Location: Michigan, USA
Has thanked: 466 times
Been thanked: 750 times

Re: TTS abbreviations which are standalone words outright

Postby dbraughlr » Mon Feb 03, 2014 3:35 am

GizmoGuy411 wrote:Penn for Pennsylvania was moved from the main list to the State abbreviation list where it belongs

Penn => Pennsylvania belongs on the list to be deleted.

GizmoGuy411 wrote:Camino=Cam


This is another conflict. You cannot use a combination of letters of a real word as an abbreviation for another word. If you want to do that, you'll have to include the period or something which makes it distinct. See Penn => Pennsylvania above.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: TTS and shield for FS-

Postby dbraughlr » Mon Feb 10, 2014 11:00 pm

In case this is a poll, I vote for "Forest Service". It doesn't seem strange or confusing to me, certainly not as strange as "Turn right onto Old William Pennsylvania Highway" or "Turn left onto Tee 800".

People who aren't familiar with these "roads" should have think about it before turning onto one.

Many of the roads have a normal name ending in "Trl" which is what will be pronounced in most cases. FS-nnxnn should be used to generate a shield because the route # is always important.

Let's just suppose that someone is uninitiated, lost, and confused. What's the difference between "Turn right onto [unintelligible] road 123" and "Turn right onto [unintelligible] 123"?

Half the time, I don't know what Waze is saying anyway. When it says turn, either I see the road and I turn, or I glance at the map to see where Waze thinks I should turn.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: TTS and shield for FS-

Postby dbraughlr » Tue Feb 11, 2014 2:50 am

qwaletee wrote:To me, there is. When you hear the word road, you have better mental context.


Is this in contrast to the mental context you have when Waze tells you to turn onto a river, railroad, boardwalk, or runway?

When Waze says, "Turn left on Broadway", I don't wonder whether that means to enter stage left or stage right. I know that it means a street not a theater.

Lots of roads don't have "road" in the name. The point is that regardless of whether Waze says, "State route 99", "C A 99", "California 99", "Highway 99", "State Highway 99", "The 99", or plain "99", the driver should understand it in context.

"Forest Service" is going to be a trail in that context. There are a finite number of turn instructions that Waze gives. I dare say that all are in the context of being on a road.

qwaletee wrote:And when you're already nervous because you aren't sure where you're going, ...

I admit to not knowing what you mean by this. But that is the wrong mental state for operating a motor vehicle at all. Such a person needs to pull over safely somewhere and park. Review the route. Be familiar with the names ahead and the turns to be made. Do whatever it takes to remove the uncertainty. It is so easy with Waze to drag the map to see what is ahead. The turn instruction text is prominently displayed on the screen.

And above all, if Waze tries to route you across a FS-nnxnn road and you don't know what it is, select fastest route or drive somewhere else first. You probably shouldn't be on such a road if it wasn't your intended destination.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Re: TTS and shield for FS-

Postby dbraughlr » Tue Feb 11, 2014 3:00 am

davielde wrote:
sketch wrote:Unless that state's DOT is particularly sadistic, there aren't going to be three roads with the same number at that intersection.

So...close...


Image

On I-70 W before Clear Spring, MD, that there is a disambiguation sign clarifying that the exit is for MD-68, so to get to I-68 / National Freeway, remain on I-70.

I-68 is a newer freeway (thanks to the late Sen Byrd). The MD-68 number greatly predates the designation of I-68 in 1991.
Last edited by dbraughlr on Tue Feb 11, 2014 3:59 am, edited 3 times in total.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users