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 sketch » Sun Jul 20, 2014 5:41 am

I still think the two letter state abbreviations on their own (not followed by a hyphen) should be removed from the custom abbreviation list. Have we asked for that yet? Too much potential for conflict.


Sent from my iPhone using Tapatalk 2
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5849
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1387 times
Been thanked: 1882 times

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

Postby KB_Steveo » Sun Jul 20, 2014 3:20 am

I was doing some testing for some updates I was planning on for the WI wiki page. I named my street CR-CT and Waze said to turn on County Road Connecticut.

Totally caught me off guard.
KB_Steveo
State Manager
State Manager
 
Posts: 317
Joined: Wed Jan 25, 2012 5:26 pm
Location: Wisconsin
Has thanked: 57 times
Been thanked: 28 times

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

Postby Bruce1224 » Fri Jul 18, 2014 1:22 pm

Re: the reply from Sketch two posts back -
I was able to drive to a county road late yesterday without going too many miles out of the way, properly labeled "CR-I" and tts did indeed pronounce it correctly as "eye". I'm too far from the road with the UR to check it out anytime soon, which is labeled "Rd I-7" but I put a message on the UR asking the reporter to confirm what he heard.
Bruce1224
Map Raider
Map Raider
 
Posts: 73
Joined: Fri Jul 12, 2013 2:20 pm
Location: Florida
Has thanked: 33 times
Been thanked: 7 times

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

Postby PesachZ » Fri Jul 18, 2014 2:15 am

This exact segment was working correctly after the recent fix and now has reverted to saying https://dl.dropbox.com/s/9go11bsygidhg73/1405607204-246504-3.mp3"... Bronx River Parkway enn, White Plains". This file was just downloaded from server at 10:26 am today, on android 3.8.0.0

In other news I just got a "and then turn right" approximately 75 feet after making the right turn I was being instructed about. This was on the new new production android v3.8.1.0 this was during my first drive on new version
PesachZ
Wiki Master
Wiki Master
 
Posts: 4339
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC} {ARC}
Has thanked: 1979 times
Been thanked: 2174 times

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

Postby sketch » Thu Jul 17, 2014 3:24 pm

That would be seriously unusual, considering normal interstate names are pronounced "i" (like I-10, "i ten").


Sent from my iPhone using Tapatalk 2
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5849
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1387 times
Been thanked: 1882 times

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

Postby Bruce1224 » Thu Jul 17, 2014 3:23 pm

It's rare to see roads using just the letter "i" in the name but I have seen a couple.

I found a UR indicating that a county road, "CR-I-7" (that's the capital letter 'I') was pronounced "Interstate 7" by Waze tts directions. Can someone confirm if this can be alleviated by labeling the road "CR-'i'-7" similar to the convention, e.g., CR-'e' ?
Bruce1224
Map Raider
Map Raider
 
Posts: 73
Joined: Fri Jul 12, 2013 2:20 pm
Location: Florida
Has thanked: 33 times
Been thanked: 7 times

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

Postby GizmoGuy411 » Thu Jul 10, 2014 3:40 pm

DwarfLord wrote:While perusing the "big list" I came upon a misspelling. It should be "crescent" with a c after the s. This is so minor it hardly seems worth mentioning, but it is a reference...


Done.
Thanks. Corrections however small appreciated.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 648 times
Been thanked: 427 times

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

Postby DwarfLord » Wed Jul 09, 2014 9:11 pm

While perusing the "big list" I came upon a misspelling. It should be "crescent" with a c after the s. This is so minor it hardly seems worth mentioning, but it is a reference...
DwarfLord
Wiki Master
Wiki Master
 
Posts: 2019
Joined: Sat Dec 07, 2013 4:01 pm
Location: Santa Cruz Mountains, California USA
Has thanked: 863 times
Been thanked: 1113 times

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

Postby PhantomSoul » Fri Jun 27, 2014 2:56 pm

Being that Pulaski is a foreign name (Polish), I would imagine that Waze would need some kind of rule to read the final i as the 2 e's in feet. Foreign names have always been a challenge for TTS systems everywhere...
PhantomSoul
US Waze Champs
US Waze Champs
 
Posts: 1651
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 299 times
Been thanked: 497 times

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

Postby qwaletee » Thu Jun 26, 2014 11:41 pm

I would say NY/NJ uses poo-LAS-key. More bad pronunciation key donations appreciated.
qwaletee
US Waze Champs
US Waze Champs
 
Posts: 2866
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro - Active throughout NE^2 (Northeast & New England)
Has thanked: 227 times
Been thanked: 1109 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users