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 GizmoGuy411 » Tue Feb 21, 2012 4:16 am

WeeZer14 just found an issue in New York City with signs that say "NYC". Waze does not pronounce it properly at all.

I'm adding them all the list, however which of the following should we request:
a) NYC = "New York City"
b) NYC = "NYC" (the letters)
c) N.Y.C. = "New York City"
d) N.Y.C. = "NYC" (the letters)
e) other

I'm thinking b and c.

(As a side note, Excel says "New York City" for "NYC" and says the letters "N", "Y", "C" for "N.Y.C")
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 GizmoGuy411 » Tue Feb 21, 2012 3:59 am

jasonh300 wrote:Do you have "Trace" on your list? I drew in a new subdivision yesterday and two of the new street names were "Natchez Trace" and "Memphis Trace". I had no idea how to abbreviate them, so I just spelled them out.


Yep the confirmed abbreviation for "Trace" is "Trce", which is not much of a savings. I think I would just stick with "Trace".
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 jasonh300 » Tue Feb 21, 2012 1:49 am

Do you have "Trace" on your list? I drew in a new subdivision yesterday and two of the new street names were "Natchez Trace" and "Memphis Trace". I had no idea how to abbreviate them, so I just spelled them out.
jasonh300
 
Posts: 7567
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 402 times
Been thanked: 978 times

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

Postby jenncard » Tue Feb 21, 2012 1:08 am

Timbones wrote:It seems that "Cr" is being now pronounced as "Country Road", so what would be an acceptable abbreviation for "Crescent"?

Gizmo has confirmed that "CRES" is pronounced as Crescent... at least on the NA server :?
jenncard
 
Posts: 737
Joined: Sat Jul 02, 2011 10:00 pm
Location: Somewhere in Los Angeles, but probably on my bicycle
Has thanked: 9 times
Been thanked: 11 times

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

Postby GizmoGuy411 » Mon Feb 20, 2012 11:10 pm

jenncard wrote:Trwy = "Trueway", definitely.

Here's what I have set up to test so far (all variations on the letter E and then working backwards alphabetically):
....


Now that the initial entries are complete, a number of those you have set to test have already been tested.

With some your punctuation is different, so that will be a good alternative test. Given how hard it is to hear the results, you still may want to weed out the ones that are exactly the same. And however I show the abbreviation in the list for case is exactly the way I tested it.

I've used your numbering method on few new submissions to see how they work.
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 jenncard » Mon Feb 20, 2012 9:36 pm

Trwy = "Trueway", definitely.

Here's what I have set up to test so far (all variations on the letter E and then working backwards alphabetically):
[*]1: “E” Rd, 2: 'E' Rd, 3: E. Rd, 4: “E.” Rd, 5: 'E.' Rd,
[*]1: “e” Rd, 2: 'e' Rd, 3: e. Rd, 4: “e.” Rd, 5: 'e.' Rd, 6: e Rd,
[*]1: Wash, 2: Wash., 3: WASH, 4: WLS, 5: WELLS, 6: We., 7: UNS, 8: U.S., 9: US, 10: US-50,
[*]1: VALLY, 2: VLYS, 3: VIADCT, 4: VWS, 5: Villge, 6: VLGS, 7: VILLAGES, 8: VLGS, 9: VSTA,
[*]1: Tsse, 2: Thick, 3: Thwy, 4: Tline, 5: TRKS, 6: TR, 7: TRLS, 8: TUNLS, 9: Trnabt, 10: TRPK,
[*]1: St., 2: Sr, 3: Sr., 4: Sent, 5: SHR, 6: SHRS, 7: Smokey Mts,
[*]1: So., 2: SE Fir Dr, 3: Fir Dr SW, 4: SPRNG, 5: SPGS, 6: SPNGS, 7: SPRNGS, 8: SPUR, 9: SQRE,
[*]1: SQS, 2: SQRS, 3: SH-119, 4: STATN, 5: STN, 6: STRM, 7: STREME, 8: STS, 9: Sudiv, 10: So,
[*]1: RADIEL, 2: RADL, 3: RNCHS, 4: Rg, 5: RDGS, 6: RIVR, 7: RVR, 8: RT, 9: Rle, 10: ,
[*]1: PKS, 2: PKY, 3: PKWYS, 4: Pass, 5: Ptway, 6: PKE, 7: PKES, 8: PNE, 9: PLNS, 10: Plat,
[*]1: PLZA, 2: Pte, 3: PTS, 4: PORT, 5: PRTS, 6: Pvt, 7: Prom, 8: , 9: , 10: ,
jenncard
 
Posts: 737
Joined: Sat Jul 02, 2011 10:00 pm
Location: Somewhere in Los Angeles, but probably on my bicycle
Has thanked: 9 times
Been thanked: 11 times

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

Postby GizmoGuy411 » Mon Feb 20, 2012 9:31 pm

The first batch of abbreviations from "Alley" to "West" entered on Jan 18th are now tested and noted in the "List". These were primarily the official USPS abbreviations. A few need to be retested in the Client, and a couple may have never been actually edited into WME.

Out of 676 entries to be tested, just under half are now edited into WME, and a third of the entries are now tested in the Client.
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 GizmoGuy411 » Mon Feb 20, 2012 8:50 pm

sketch wrote:Have you tried "Thwy" yet? That's how it's abbreviated up on the exit signs up in Baton Rouge.


"Thwy" is on the list to test, but has not been edited into WME yet. Hopefully I'll get to it in the next batch to add. Then wait another three weeks to be able to test them in the client.

I had to come up with a new scheme as I was running out of room in my sand box to add more roads to the rig. The roads were getting too close together to be able to select when in the field on my Android. So I shortened the older roads, and as I add new ones between them I'll make them longer so that a handle extends to be able to select on.

I'm sure the local Wazers are scratching their heads when this mess pops up on their screens!
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 sketch » Mon Feb 20, 2012 6:56 pm

Have you tried "Thwy" yet? That's how it's abbreviated up on the exit signs up in Baton Rouge.
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5920
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1420 times
Been thanked: 1946 times

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

Postby CBenson » Mon Feb 20, 2012 6:49 pm

I recently passed through this ramp and noticed that "Hwys" does not work as an abbreviation. As far as the "trwy" goes, it sounds like "Trueway" to me.
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