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 AlanOfTheBerg » Wed Apr 16, 2014 3:29 pm

Latest testing results, failed items in red.

Mt. St. Helens Rd E = "mount saint helens road east"
Mt St Helens Dr = "mount saint helens drive"
Mt. St Helens Rd N = "mount saint helens road north"
Marx Ste. Marie = "marks sweet maree"


I have also noted that "Mt" and "Mt." both say "mount" but "Mt." sounds ... strange. It takes longer to say "mount" and there's a longer space after the word. "Mt" should be the standard.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Thu Apr 17, 2014 7:15 pm

sketch wrote:"SR" and "SH" don't depend on whether there's a hyphen, do they? Relying on the hyphen is too opaque imo.

They do. Hyphens are important, if only at least to ensure proper abbreviation usage.

As of this moment, we need to immediately remove the custom abbreviation for "FM" and "NE" as they are both being incorrectly pronounced as state/territory name. Are there any other problematic state abbreviations which conflict with other existing abbreviations that we need to work on in a more detailed manner?

And, yeah, IMO, I don't know why we would ever really need any state name in segment names, but I'm sure it exists somewhere.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Apr 21, 2014 1:14 pm

A couple thoughts which may already be addressed: 1) saying the full name of a state for the two letter abbreviation is different than saying the appropriate phrase for "XY-###" where XY is the state abbreviation (or just M for michigan). The key is defining the abbreviation with and without the hyphen. I think we should all agree, and it won't cause too much angst, that state routes should use a hyphen to help with abbreviation rule; 2) as noted above and later "BUS" only fails if it begins or ends a segment name; 3) "N" failing to say "north" happens when it is preceded by a custom abbreviation.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Wed Apr 30, 2014 11:36 pm

CBenson wrote: Is the expansion of state abbreviations like "MD" now universal? This was with Samantha.

With the update of all state abbreviations submitted a couple weeks ago, yes. Possibly. Yes. Personally, I think we may need to pull them all back and rethink each, one at a time, including their usage within strings so we can say letter names or full state name in specific circumstances.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Wed Apr 30, 2014 11:56 pm

Yes, noted in the thread with pkwy example specifically.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Thu May 01, 2014 12:20 am

PesachZ wrote:
AlanOfTheBerg wrote:Yes, noted in the thread with pkwy example specifically.

In the meantime should the name be changed to spell out 'parkway' or 'north'?

No. Honestly, it's been this way for quite some time. The impact to drivers is fairly minimal. Many more drivers are hearing "nebraska" instead of northeast. I've got an email in to the abbreviations queen at Waze as well as Noam, our US community manager to give us an update about it. Tomorrow is their last day before the weekend, so if I don't hear from them by 4am PDT, I will contact them again.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Thu May 01, 2014 6:16 am

I think that TTS was being updated this evening as I had several minutes of no street names at all, and then NE started saying "northeast."
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Fri May 09, 2014 4:32 pm

I now have more problems with "N" being pronounced "enn" instead of "north" on segments which have never had a problem before. It's getting worse instead of better. And communication from Waze has all but completely disappeared again. Despite assurances to the contrary.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Fri May 16, 2014 9:51 pm

qwaletee wrote:Have we ever had a problem with X=10th before? Per the UR below, the X in Malcolm X Blvd was being pronounced "tenth." I don't know if this is an isolated occurrence. I imagine if it is a problem, it could be resolved by changing "X" to "X." (with a period).

https://www.waze.com/editor/?zoom=5&lat ... 35&endshow

'X' should be sufficient to say "ex" instead of "tenth."
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Fri May 16, 2014 9:51 pm

bowieb2 wrote:Any update on NE being pronounced "Nebraska"? My office is currently on the corner of "Nebraska 17th Court" and "Nebraska 14th Avenue" according to Waze.

This is a cached street name. NE was fixed quite a while ago.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users