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

Image This is the place to discuss issues that are relevant for locations in the US. For any other discussions, please use the main forums.

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

Postby GizmoGuy411 » Mon Mar 12, 2012 3:58 pm

I think CBenson also caught part of this "Saint" and "Street" issue in the past.

Since case has not seemed to be important based on our test results so far, I've only added a subset of those possibilities to the list.

For the use or not of a period in the abbreviation, I think I've add all possibilities.

Here are the iterations added to the list and test rig:
st middle st
St middle St
st middle st.
St middle St.
st. middle st
St. middle St
st. middle st.
St. middle St.
st st st
St St St
st st st
st st st.
st st. st.
st st. st
st st. st.
st. st st
st. st st.
st. st. st
st. st. st.


In each case we are hoping for "st" to say "street" and "st." to say "saint".
Last edited by GizmoGuy411 on Mon Mar 12, 2012 4:38 pm, edited 1 time in total.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1344
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 499 times
Been thanked: 315 times

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

Postby sketch » Mon Mar 12, 2012 4:23 pm

I feel it's probably best that "St" returns "saint" if it's at the beginning.
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5626
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1199 times
Been thanked: 1651 times

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

Postby AlanOfTheBerg » Mon Mar 12, 2012 4:31 pm

I thought we decided long(er) ago that differentiation should be with the period or without. Positional should make no difference. St=street, St.=saint, Dr=drive, Dr.=Drive, etc. Why make it more complicated?
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 9.2.1 | Waze v4.2b
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23416
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1074 times
Been thanked: 4507 times

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

Postby CBenson » Mon Mar 12, 2012 4:35 pm

AlanOfTheBerg wrote:I thought we decided long(er) ago that differentiation should be with the period or without. Positional should make no difference. St=street, St.=saint, Dr=drive, Dr.=Drive, etc. Why make it more complicated?

Did you mean Dr.=Doctor?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0, Waze 3.9.9.907
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9703
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 912 times
Been thanked: 2072 times

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

Postby AlanOfTheBerg » Mon Mar 12, 2012 4:46 pm

CBenson wrote:
AlanOfTheBerg wrote:I thought we decided long(er) ago that differentiation should be with the period or without. Positional should make no difference. St=street, St.=saint, Dr=drive, Dr.=Drive, etc. Why make it more complicated?

Did you mean Dr.=Doctor?

Yes. :oops: #Typingtoofast.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 9.2.1 | Waze v4.2b
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23416
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1074 times
Been thanked: 4507 times

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

Postby sketch » Mon Mar 12, 2012 5:23 pm

AlanOfTheBerg wrote:I thought we decided long(er) ago that differentiation should be with the period or without. Positional should make no difference. St=street, St.=saint, Dr=drive, Dr.=Drive, etc. Why make it more complicated?

No problem. I probably wasn't following at that time. Just looking to get out of a bunch of future edits :P
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5626
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1199 times
Been thanked: 1651 times

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

Postby GizmoGuy411 » Fri Mar 16, 2012 4:56 am

sketch wrote:
AlanOfTheBerg wrote:I thought we decided long(er) ago that differentiation should be with the period or without. Positional should make no difference. St=street, St.=saint, Dr=drive, Dr.=Drive, etc. Why make it more complicated?

No problem. I probably wasn't following at that time. Just looking to get out of a bunch of future edits :P


But just think of all the points you will get!
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1344
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 499 times
Been thanked: 315 times

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

Postby GizmoGuy411 » Fri Mar 23, 2012 6:50 am

The first batch of TTS abbreviation tests from yesterday's map updates have been tested.

This completed a third more of the 700 abbreviations to be tested.

As a summary of the results with this batch, it was learned that the letters of the alphabet can be represented in nearly every combination of upper and lower case, with and without any puncutaion and they will be promounced as letters.

The letters N, E, S, and W are the exceptions, however a particular combination of puncution will allow them to be promounced as letters instead of the cardnial directions of North, East, South and West. This will allow names such as "North N Street".

Since I did not correctly indentify which test segment in the rig produced which results, I will need to retest them in the field. Jenncard as confirmed this too with her test rig, and may have the answer tomorrow.

Unfortuneatly, no two letter abbreviations could be idendified for the states and provinces, territories, etc., in North America, except for "Ny" for New York. ("NY" says "en wye") We will have to petition Waze to add these.

Curiously while various capitalization and puncutuation combinations could not pronounce the states, they did impact how the two letter abbreviations where either pronounced as word or as letters. More details as the test segments are retested.

Unfortuneatly, several popular abbreviations failed, such as for Martin Luther King, Saint, and Senior. Positional tests for Saint are in the test rig, but will not be available until the next map update.

A few other abbreviations suggested by CBenson from the "Manual on Uniform Traffic Control Devices" were recognized.

Jenncard has many of the remaining third to be tested in her rig, plus a number of additional tests which we will merge once we have time to test them and compare our results.
ImageImageImageImage

U.S. based Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.1.1 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1344
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 499 times
Been thanked: 315 times

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

Postby AlanOfTheBerg » Fri Mar 23, 2012 2:54 pm

GizmoGuy411 wrote:The first batch of TTS abbreviation tests from yesterday's map updates have been tested.

This completed a third more of the 700 abbreviations to be tested.

Wow, you all are doing some great testing. I appreciate the time and effort you are putting in to this. Let us hope this bears good fruit with better and reliable abbreviations in the future!
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 9.2.1 | Waze v4.2b
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23416
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1074 times
Been thanked: 4507 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
tts setup.jpg (26.28 KiB) Viewed 1407 times
Image
Recovering Waze addict, occasional driver and editor in LA.
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: 8 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users

cron