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 txemt » Fri Aug 15, 2014 7:01 pm

Si
txemt
Area Manager
Area Manager
 
Posts: 4764
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

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

Postby sketch » Fri Aug 15, 2014 5:37 pm

txemt wrote:Rev.

For "Reverend"?
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5924
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1422 times
Been thanked: 1949 times

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

Postby pjlasl » Fri Aug 15, 2014 4:47 pm

PesachZ wrote:
pjlasl wrote:Looking at TxDOT guide to sign elements, they don't recommend abbreviating Branch and Bridge isn't even on the list.

Based on the earlier discussion I've recommended removing the branch abbreviation, and making Br expand to bridge as well to match the MUTCD.


I voted ;)
pjlasl
Area Manager
Area Manager
 
Posts: 378
Joined: Tue Nov 13, 2012 2:41 pm
Location: Weatherford, TX
Has thanked: 31 times
Been thanked: 110 times

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

Postby PesachZ » Fri Aug 15, 2014 4:44 pm

pjlasl wrote:Looking at TxDOT guide to sign elements, they don't recommend abbreviating Branch and Bridge isn't even on the list.

Based on the earlier discussion I've recommended removing the branch abbreviation, and making Br expand to bridge as well to match the MUTCD.
PesachZ
Wiki Master
Wiki Master
 
Posts: 4395
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1990 times
Been thanked: 2225 times

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

Postby pjlasl » Fri Aug 15, 2014 4:41 pm

Looking at TxDOT guide to sign elements, they don't recommend abbreviating Branch and Bridge isn't even on the list.
pjlasl
Area Manager
Area Manager
 
Posts: 378
Joined: Tue Nov 13, 2012 2:41 pm
Location: Weatherford, TX
Has thanked: 31 times
Been thanked: 110 times

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

Postby txemt » Fri Aug 15, 2014 2:31 pm

Rev.
txemt
Area Manager
Area Manager
 
Posts: 4764
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

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

Postby sketch » Wed Aug 13, 2014 4:39 pm

Guys, that's why we would be submitting them with periods exclusively. So "Pa." can be used for Pennsylvania, but "Pa" can still be used for country roads named after grandfathers. "Ct." is fine for Connecticut because "Ct" with no period is used for Court. "Del." can be used for Delaware while "Del" can be used for Del Rey Blvd. "Neb." can be used for Nebraska, leaving "NE" for northeast.

I don't know why you'd need to capitalize "IN" or "OR" in a road name, but still, the English word should be expected behavior. Instead, we should use "Ind." and "Ore.", leaving "IN", "OR", "Ind", and "Ore" for other uses.

None of these will cause a conflict at all, because as of today, the ONLY places we use periods in road names in the US are "St." and "Ste." and maybe "Dr." Maybe one or two others. Nothing else should have a period anyway, so we are by nature adding zero conflict here.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5924
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1422 times
Been thanked: 1949 times

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

Postby jondrush » Mon Aug 11, 2014 7:25 pm

We strongly recommend that Penna be used in place of Penn to avoid that particular conflict.
jondrush
Waze Global Champs
Waze Global Champs
 
Posts: 2647
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 194 times
Been thanked: 513 times

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

Postby PhantomSoul » Mon Aug 11, 2014 5:16 pm

Can we identify conflicting legacy abbreviations case by case and just not use those?
PhantomSoul
US Waze Champs
US Waze Champs
 
Posts: 1660
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 300 times
Been thanked: 498 times

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

Postby CBenson » Mon Aug 11, 2014 4:34 pm

PhantomSoul wrote:I would say go by what the GS says, unless you have a good case for deviating from that.

Sure, but that doesn't address the problem that sometimes you only know what the meaning is by context. Should "Ct." be voiced as "Connecticut" or "court"? Should "NE" be voiced as "Nebraska" or "northeast"? Should "Penn" be voiced as "Pennsylvania" or "Penn"? Should "LA" be voiced as "Louisiana" or "Los Angles"? Should "Me" be voiced as "Maine" or "me"? Should "IN" be voiced as "Indiana" or "in"? Should "OR" be voiced as "Oregon" or "or"?

Thus, the idea that
sketch wrote:The reason to standardize on a particular list of abbreviations is that we can get that list set up as TTS abbreviations and guarantee that it will work that way.

remains valid even if you typically use what's on the GS. This would help if only to identify those circumstances where there is a good case for deviating from the GS.
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 10330
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 1069 times
Been thanked: 2355 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users