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 » Mon May 07, 2012 4:22 pm

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.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1411
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 663 times
Been thanked: 433 times

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

Postby GizmoGuy411 » Mon May 07, 2012 3:09 pm

CBenson wrote:
GizmoGuy411 wrote:
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
Global Champ Mentor
Global Champ Mentor
 
Posts: 1411
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 663 times
Been thanked: 433 times

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

Postby invented » Fri Apr 27, 2012 3:48 am

Does TTS say "1st" "2nd" "3rd" et al as expected?
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

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

Postby mwhead2 » Fri Apr 20, 2012 3:20 pm

"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 :)
mwhead2
Area Manager
Area Manager
 
Posts: 45
Joined: Tue Sep 22, 2009 6:46 pm
Location: Athens, GA
Has thanked: 0 time
Been thanked: 1 time

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

Postby CBenson » Fri Apr 13, 2012 8:17 pm

GizmoGuy411 wrote:
CBenson wrote: 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.
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

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

Postby DonJ2 » Tue Apr 03, 2012 1:22 pm

Does TTS expand "Mem" or "MEM" to "Memorial"?
DonJ2
 
Posts: 281
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 46 times
Been thanked: 10 times

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

Postby AndyPoms » Mon Apr 02, 2012 9:57 pm

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
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7162
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1314 times

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

Postby invented » Fri Mar 30, 2012 9:41 pm

I found that Waze is pronouncing the acronym "QEW" as "cue". This is incorrect. Also, contrary to the wiki, Waze pronounces "WB" as "westbound" properly.

I'm also looking to see if there is an appropriate abbreviation for "Line".
invented
 
Posts: 618
Joined: Sat Mar 10, 2012 8:03 am
Location: Port Colborne, ON
Has thanked: 5 times
Been thanked: 11 times

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

Postby GizmoGuy411 » Mon Mar 26, 2012 8:18 pm

A few of jenncard's results were added to the list a couple of days ago. I had not announced it as I had hoped to complete the addition of all of her tests yesterday. However my schedule did not allow it, as some additional field testing is necessary to determine why a few of her results differ from mine.

Sent from my Galaxy Nexus using Tapatalk
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1411
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 663 times
Been thanked: 433 times

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

Postby jenncard » Fri Mar 23, 2012 6:07 pm

A few interesting observations from my testing:
- CASE vs. case definitely DOES matter
- use of ' or " has interesting (and unpredictable) results
- and testing these rigs isn't has hard as one might imagine :-)

Of the following segment names:
Code: Select all
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,

Some were "gobbledegook", many were "East Rd" and only one actually delivered "Eee Road"
Code: Select all
'e' Rd

And while "Wash Rd", and "Wash. Rd" were pronounced as the word, "WASH Rd" somehow or another came out as "Washington Rd"

For "unknown" words, the TTS engine has two different behaviors:
- spell out the letters, e.g. TR = "tee ar"
- attempt pronounciation, e.g. "Tline" = "t'line" (or whatever you might imagine that to sound like)
I thought that this was varied based on UPPER CASE = spell it out, Mixed Case = attempt to pronounce, but this is not consistent.

As far as this being easier than anticipated to actually test, here are the tips:
- spreadsheets are your friend (this is generally always the case)
- Name the segments as I've done above, with multiple test values identified numerically (with colo) and comma separated
- I set up segment names with up to 10 different test values, and still only had to replay one or two more than once
- create the segments in a radial, coming out from one junction
- attach a small segment at the end of the "test named" segment with a short name. This makes it easy to select the destination.
- Most important, it isn't actually necessary to HEAR the tts on your phone! If you are close enough to the junction with your test segment, the .tts file will be created. "Stop nav" to that destination, navigate to the next, and so on. Not even necessary to move your car.... or even be in your car. I sat at the dining room table (just in front of my big bad junction)

This is about what mine looks like at 100m/500ft zoom. The northern "radial" was more than adequate for me to be able to select the destination segments
Attachments
tts setup.jpg
(26.28 KiB) Downloaded 1717 times
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

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users

cron