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 Thortok2000 » Tue Feb 11, 2014 12:31 pm

Look at the road.

Point at it.

Begin the sentence: "That is a..."

If your sentence ends with 'interstate' make sure that's in the name. If your sentence ends with 'state highway' or 'state route' make sure that's in the name. Etc.

Would you really say "that is a forest service"? I would think the sentence would make more sense by saying "That is a forest service road."

Essentially, the standard is for the type of road to be fully given, and THEN the number. Is it a 'forest service' or is it a 'forest service road'?

It's like the difference between saying 'state highway 291' and 'state 291'.

I personally vote the 'road' as being necessary for standardization purposes. Do I think it'd work fine without it? Yup. I think '291' is all that's needed and we could drop the 'state hwy' part. But for standardization purposes, I don't think it harms anything to have the couple extra words.
Thortok2000
Area Manager
Area Manager
 
Posts: 722
Joined: Tue Oct 15, 2013 1:01 am
Location: Greenville, SC
Has thanked: 190 times
Been thanked: 141 times

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

Postby Thortok2000 » Tue Feb 11, 2014 12:52 am

What's ironic, sketch, is around here we don't call them state route or state hwy. We just call it '291.' MAYBE 'highway 291' and very, very rarely 'route 291.' But it's usually just '291.'

I've even caught newbie editors around here changing it to say that as well. =/
Thortok2000
Area Manager
Area Manager
 
Posts: 722
Joined: Tue Oct 15, 2013 1:01 am
Location: Greenville, SC
Has thanked: 190 times
Been thanked: 141 times

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

Postby qwaletee » Mon Feb 10, 2014 8:26 pm

vectorspace wrote:I'd like to add another item to the spreadsheet, if it make sense. I've had two ongoing projects, one to work Indian Reservations and the other to work Forest Service Roads. I've interacted quite a bit with GIS people at Bureau of Indian Affairs and the US Forest Service and am continuing to do so.

Indian Service Road/Route (ISR-xxx) seems to be in the TTS spreadsheet already from a prior effort, without the xxx part at least. I am working on other abbreviations that would be more universal or as well.

I would now like to add FS-xxxxx to the TTS now as it is something that has cross-country applicability. The base map and subsequent edits have a variety of standards such as "Forest Service Road xxx," "Forest Rd xxx," "F S xxx," and others that include Route. We could standardize on this FS-xxxx as a way to simplify and make more sound the travel of Wazers on these roads.

I have quite a bit of information from the US Forest Service, particularly functional classifications, name standards and conventions for forest service roads, access to actual GIS data for anywhere in the nation, and a policy of where USFS wants people to use their roads and where not. I will start simplifying and posting this information elsewhere soon, but it would be good to get FS-xxx into the TTS list now.

I would suggest not using FSR-xxx for Forest Service Road/Route because it is longer and somewhat redundant. Just "Forest Service XXXX" would suffice as is done for "State Route xxxx," etc.


Vector, to the uninitiated, a state route is still an obvious road designation. But to the uninitiated ear, being asked to turn onto "Forest Service 123" sounds strange and a little confusing . It may be a bit longer, but I would prefer Forest Service Road.
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2880
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 229 times
Been thanked: 1114 times

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

Postby vectorspace » Sun Feb 09, 2014 10:56 pm

I'd like to add another item to the spreadsheet, if it make sense. I've had two ongoing projects, one to work Indian Reservations and the other to work Forest Service Roads. I've interacted quite a bit with GIS people at Bureau of Indian Affairs and the US Forest Service and am continuing to do so.

Indian Service Road/Route (ISR-xxx) seems to be in the TTS spreadsheet already from a prior effort, without the xxx part at least. I am working on other abbreviations that would be more universal or as well.

I would now like to add FS-xxxxx to the TTS now as it is something that has cross-country applicability. The base map and subsequent edits have a variety of standards such as "Forest Service Road xxx," "Forest Rd xxx," "F S xxx," and others that include Route. We could standardize on this FS-xxxx as a way to simplify and make more sound the travel of Wazers on these roads.

I have quite a bit of information from the US Forest Service, particularly functional classifications, name standards and conventions for forest service roads, access to actual GIS data for anywhere in the nation, and a policy of where USFS wants people to use their roads and where not. I will start simplifying and posting this information elsewhere soon, but it would be good to get FS-xxx into the TTS list now.

I would suggest not using FSR-xxx for Forest Service Road/Route because it is longer and somewhat redundant. Just "Forest Service XXXX" would suffice as is done for "State Route xxxx," etc.
vectorspace
 
Posts: 1183
Joined: Sat Dec 17, 2011 7:05 pm
Location: Albuquerque, NM, USA
Has thanked: 173 times
Been thanked: 420 times

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

Postby GizmoGuy411 » Sun Feb 09, 2014 11:14 am

4. The exception to the above is abbreviations for states and or territories; and countries with their three character abbreviation. These contain correct punctuation. Other regions do not fall under this category.
For example: California would be abbreviated to C.A. not CA and Victoria to VIC.


If I am reading this correct, I have an exception to this.

We have been pushing for 2 years now for Waze to adopt the USPS (and others) two letter (without punctuation) for the US States, and Canadian Provinces.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1406
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 654 times
Been thanked: 430 times

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

Postby kentsmith9 » Wed Feb 05, 2014 1:01 am

It looks like one of our Australian editors was making some changes for the Australian pages and then came in making changes here as well.

sketch wrote:
bgodette wrote:
qwaletee wrote:That page needs serious copyediting.
Go right ahead, and be sure to submit it to a new page or sandbox so others can review your work.

It's not copyediting that page needs, it's a full rewrite, and maybe just a removal of that first section. Those are not the rules, at least in the US, and they don't belong on a country-nonspecific page. (They are, indeed, also pretty difficult to understand.)

I would agree and I am fine if qwaletee wants to take a first crack at it.

I created a separate page linked to the original just for easy locating if we all forget about it. Whoever holds up their hand first should be given initial control over the page and then ask for input from this forum. I have temporarily assigned it to qwaletee, but if someone else steps up or wants it just change the name at the top of the page linked above.

Once we all agree or get enough consensus we can just cut and paste the new content over the old. No need to track our session edits before the final. The history will hold the original page changes for reference.
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 5282
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 1381 times
Been thanked: 1595 times

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

Postby sketch » Tue Feb 04, 2014 11:18 pm

bgodette wrote:
qwaletee wrote:That page needs serious copyediting.
Go right ahead, and be sure to submit it to a new page or sandbox so others can review your work.

It's not copyediting that page needs, it's a full rewrite, and maybe just a removal of that first section. Those are not the rules, at least in the US, and they don't belong on a country-nonspecific page. (They are, indeed, also pretty difficult to understand.)
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 bgodette » Tue Feb 04, 2014 10:27 pm

qwaletee wrote:That page needs serious copyediting.
Go right ahead, and be sure to submit it to a new page or sandbox so others can review your work.
bgodette
Waze Global Champs
Waze Global Champs
 
Posts: 3418
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 109 times
Been thanked: 507 times

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

Postby qwaletee » Tue Feb 04, 2014 9:10 pm

kentsmith9 wrote:In reviewing this page on Abbreviations and acronyms the first section seems out of place in the flow. I propose that we move it after the standard abbreviations section. However since the standard section is so long, I will include a note in that section pointing people to the "non-standard" section if they don't see what they are looking for.


That page needs serious copyediting. Language is very sloppy and unclear. As an example, look at the info on abbreviating "tunnel," which doesn't make any sense. One refers to a tunnel, but the other refers to a roadway that is a tunnel?! Perhaps if you are familiar with the roads in question (which aren't linked), you might know that one isn't actually a tunnel, but is an access roadway. But that's just a guess, and even if correct, still raises serious questions about the policy espoused there.

It would be really nice if policy-setting text, anywhere in the wiki, linked to the discussion that finalized said policy. That would allow us to determine if it is truly a global standard, country-specific, or other region-specific, and whether it is good as-is or might need re-examination in light of new developments or occasional sanity.
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2880
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 229 times
Been thanked: 1114 times

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

Postby CBenson » Tue Feb 04, 2014 6:02 pm

I'm not sure I've ever seen that page before. What is the providence of this:
For example: California would be abbreviated to C.A. not CA and Victoria to VIC.
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