Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

[GizmoGuy411]

I've asked Jenn to help me listen to this file to better determine how one of the abbreviations is being pronounced. But after I sent her the request, I thought I would just asked here and let a few people listen to it and see what they think.

The abbreviation in question, "trway" is for "Throughway". To me is sounds more like "Trueway".

I use Windows Media Player to listen to the file. In my version, I right click within the player, and in "Enhancements", I select the "Play speed setttings" to slow down the speech without distorting the pitch.

I've renamed the dot TTS from my Android to a dot MP4 file to allow the player to have the above speed control.

Here is a list of the abbreviations in this file, so that you can better know the placement of what is being spoke:
strvnue / strm / str / strt / smt / sumit / ter / terr / trwy / trce / trak / trk / trfy / tunl


I've uploaded it here as a ZIP file, since the forum would not allow the dot TTS or dot MP4 file types.

[GizmoGuy411]

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]

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]

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]

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

via TapaTalk

I remember at least one abbreviation for Crescent is in the list. I'm mobile so I can't check right this second. Also I just checked CR earlier today and I could swear I swear I heard "County Road" not "Country Road".



Sent from my Galaxy Nexus using Tapatalk

[GizmoGuy411]

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]

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]

A section on Abbreviations has been added to the Waze Wiki "Editing Manual" under "How to label and name roads":
http://www.waze.com/wiki/index.php/How_ ... reviations

The lead post here has also been edited and updated.

[GizmoGuy411]

That is just it. The signs do not say New York City. They just say NYC with no spaces or periods.

So my thinking was that for that abbreviation TTS should just say " en wye cee" to reflect the same brevity.

Sent from my Galaxy Nexus using Tapatalk

[GizmoGuy411]

With all this conflicts, why are we doing this? Wouldn't it be better to simply ask Waze to implement a TTS field, so we can actually follow the goal of making it simple to the user: matching the BGS?

Yes we have asked for an exception field, and Waze has said here in the forums that a solution is coming. (can't find the post at the moment). It may also come along with the ability to test the results immediately.

However the issues with TTS abbreviations, and TTS for full words are not exactly the same.

There are multiple layers to how the TTS engine works. Waze uses a product from Nuance that is sold customized for mobile use. Waze also has the ability to further customize what the TTS can say.

When they provide us with an exception field, was can over-ride the delivered TTS and have it say what we want for all the special cases we encounter, such as alternate local pronunciations, non English language words, and other similar infrequent cases.

Abbreviations however are used very frequently, and need to be available without always needing to use an exception field.

The abbreviation list we are building here is intended to test what Waze currently recognizes and to test future possibilities. Everything that we test is NOT necessarily what we would like Waze to actually use for TTS.

As others have mentioned above. we hope to get Waze to change the TTS for those abbreviations that we feel are most likely to be encountered in North American that are commonly used on signs.

The exception field can then be primarily for full words and hopefully only needed for abbreviations in rare exceptions.

So the combination of a Waze customized set of abbreviations, along with our ability to further customize anything in an exception field should provide the best solution.

While this will be important for North America, the exception field will be even more important for the rest of the world. The ROTW may well need their own custom abbreviation list too. And that is best left for discussion in another forum!