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

[GizmoGuy411]

I have several exits here in CT that say "N. Y. City"... I was listening closely today and I got "North Why City" through the TTS... Without me testing 75 variations, does anyone know a way to keep some form of "N. Y." (NY, N.Y., etc) for the display and get it to read "New York" in the TTS?

Thanks for your help,
Andrew

Look at the abbreviation list linked in the lead post of this thread. I think it has been updated to include the abbreviation for New York that works.

Sent from my Galaxy Nexus using Tapatalk

For New York the doc says:

New York NY CU 2012-02-19 n/a. Says the letters 2012-03-22 GizmoGuy411 A
New York Ny CU 2012-02-19 New York 2012-03-22 GizmoGuy411 R

If I read that correctly, "NY" says "enn why" (and it should be Added) and "Ny" says "New York" but the recommendation is to Remove it?

The other thing I noticed while looking at the State List (and if I'm reading this wrong, please let me know) is that you want to add "Ct" to be "Connecticut" instead of "court" which is currently does. Being from Connecticut, we have many roads named "Something Court" and the USPS abbreviation is "Ct" for "Court" (but it's also missing from the "C" section of the list...

Since I am mobile at the moment I can't answer in sufficient detail.

We are looking for all the state abbreviations to be two letter abbreviations in caps and no periods.

So "Ct" would be "court" and "CT" would be the state.

As far as New York goes I don't think you should use the current working abbreviation.

So until the TTS issues are addressed , my best advice at the moment is "when in doubt, spell it out"!



Sent from my Galaxy Nexus using Tapatalk

[DonJ2]

Does TTS expand "Mem" or "MEM" to "Memorial"?

[GizmoGuy411]

Does TTS expand "Mem" or "MEM" to "Memorial"?

Look in the list linked in the lead post to see if we are testing for it, and if so, if we have results yet.

I'll check too when I have time and computer access.

It will be added to list for testing if not there now.

Sent from my Galaxy Nexus using Tapatalk

[CBenson]

I would also note I was somewhat surprised (not having any use for the "Manual on Uniform Traffic Control Devices" except for waze map editing) at how much each state might change that list. Here is Maryland's for example.

Yes that is a surprise. Maryland has quite a few more abbreviations than the fed list too. I looked my state of Ohio, and our abbreviation list is a copy of the federal list.

I supposed to do the our list right we should look at these for EVERY state. I'm afraid however I'm not up to the task, as our current list represents a fair amount of effort to date, and with only 35% tested so far, there will be a lot more to test once the map tiles are updated again.

Would anyone like to compare the MUTCD list for every state against our list and submit any additional abbreviations we should add?

http://mutcd.fhwa.dot.gov/resources/sta ... /index.htm

It appears that Maryland is the only state to add a bunch to the fed list. So this doesn't look to be such a problem.

[mwhead2]

"Alt" (as in "SR-15 Alt") is correctly said as "Alternate" (though pronounced as "alterneight")

"Conn" ("connector") and "Sp" ("spur") are also used in Georgia so it'd be nice if those were added to the list

[invented]

Does TTS say "1st" "2nd" "3rd" et al as expected?

[GizmoGuy411]

Does TTS say "1st" "2nd" "3rd" et al as expected?

Good question. It looks like we never tested for them.

My testing is on hold for a while as I need to catch up with other matters.

I'll have to at least add them to the list for future testing.

Sent from my Galaxy Nexus using Tapatalk 2

[GizmoGuy411]

Yes that is a surprise. Maryland has quite a few more abbreviations than the fed list too. I looked my state of Ohio, and our abbreviation list is a copy of the federal list.

I supposed to do the our list right we should look at these for EVERY state. I'm afraid however I'm not up to the task, as our current list represents a fair amount of effort to date, and with only 35% tested so far, there will be a lot more to test once the map tiles are updated again.

Would anyone like to compare the MUTCD list for every state against our list and submit any additional abbreviations we should add?

http://mutcd.fhwa.dot.gov/resources/sta ... /index.htm

It appears that Maryland is the only state to add a bunch to the fed list. So this doesn't look to be such a problem.

Whew! Thanks for checking on that! Yes that will make things easier.

[GizmoGuy411]

I have several exits here in CT that say "N. Y. City"... I was listening closely today and I got "North Why City" through the TTS... Without me testing 75 variations, does anyone know a way to keep some form of "N. Y." (NY, N.Y., etc) for the display and get it to read "New York" in the TTS?

Thanks for your help,
Andrew

Look at the abbreviation list linked in the lead post of this thread. I think it has been updated to include the abbreviation for New York that works.

Sent from my Galaxy Nexus using Tapatalk

For New York the doc says:

New York NY CU 2012-02-19 n/a. Says the letters 2012-03-22 GizmoGuy411 A
New York Ny CU 2012-02-19 New York 2012-03-22 GizmoGuy411 R

If I read that correctly, "NY" says "enn why" (and it should be Added) and "Ny" says "New York" but the recommendation is to Remove it?

The other thing I noticed while looking at the State List (and if I'm reading this wrong, please let me know) is that you want to add "Ct" to be "Connecticut" instead of "court" which is currently does. Being from Connecticut, we have many roads named "Something Court" and the USPS abbreviation is "Ct" for "Court" (but it's also missing from the "C" section of the list...

You were correct to point out that in the State list that "Ct" was tagged as to be "Added". That was clearly a copy and paste error!

"CT" should be Connecticut, and "Ct" should be Court.

Yes "Ct" was missing from the "C" section as the official USPS abbreviations are all in upper case. When the list was initially created, the entire USPS list was imported as is into the spreadsheet, and everything was left in upper case, and the mixed case variation of "Ct" was never added.

USPS actually use "CT" for both the state and the word! Not a problem for them, as they don't have to worry about TTS. Yes a problem for Waze!

Similarly, "NY" should be "New York" and "Ny" should removed as the current TTS abbreviation for New York, and we should avoid using it in Waze, as Harlan reiterated.

And again for now, our motto of "when in doubt, spell it out" is often the best advice as Alan said.

So thanks Andy for pointing out the errors/omissions in the list. I'm sure there are more if anyone cares to help proof it!

[GizmoGuy411]

I have still not had time to merge the remainder of Jencard's excellent work into the list.

(see: viewtopic.php?f=10&t=15178&start=140#p158721)

She has sure bested me with her test method and with her radial layout of her test rig.

Based on her results, I have begun to wonder if I could revise my own rig to be a variation of hers.

However since I don't own a vacation home in a remote location adjacent to a ski area, I can't sit in my computer room and test the rig roads that are a mile away from me. I have to drive to my test rig.

To overcome that slight issue, it occurred to me that I MAY be able to change the test roads to railroads and intersect them all in front of my house. They could follow a single path from that intersection to my rig area, where I could then fan them out and create non railroad naming stubs as Jen has done for visibility to select on the client. (For those who are not aware, railroads are visible in the editor but not on the client maps.)

So does anyone know if it is possible to still route to a named railroad or route to a road via a railroad? I don't know of any near me to test with, as I have long ago removed any intersecting nodes of railroads from the drive-able roads. I will add a test for this, however it would be nice to know before waiting for the edit to live turn around time to elapse.