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.

Moderator: MapSir

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

Postby PhantomSoul » Tue Oct 14, 2014 4:08 pm

It seems like N isn't being pronounced correctly as North if it doesn't appear as the very last word of a road's entire entered name. Maybe it's related to the slash thing mentioned. "NJ Turnpike N / I-95 N" first N is pronounced incorrectly as N instead of North. "to Garden State Pkwy EXPRESS N / Woodbridge / North Jersey" the N after EXPRESS is incorrectly pronounced as N instead of North.
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 times

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

Postby PhantomSoul » Mon Aug 11, 2014 5:16 pm

Can we identify conflicting legacy abbreviations case by case and just not use those?
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 times

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

Postby PhantomSoul » Mon Aug 11, 2014 4:20 pm

I would say go by what the GS says, unless you have a good case for deviating from that. For example, most of the Turnpike entrance signs in NJ have the word turnpike written out as a whole, with New Jersey abbreviated as NJ. So the Turnpike should be referenced as "NJ Turnpike" except when it appears on a BGS with lots of other roads, where it makes sense to shorten it to "NJ Tpk" to maximize how much of the ramp name will show in the client navigation banner. Both names are read the same way by TTS, but the difference just tries to improve the visual experience.

We have BGSes on I-287 in northern NJ that reference the Thruway in NY as "N.Y. Thruway" with the periods in N.Y. Southbound on the Garden State Pkwy approaching the Turnpike near Woodbridge, the sign still says "Del. Mem. Br." for the Delaware Memorial Bridge, and that exact phrase still will not be read by TTS correctly in Waze (I don't know if Mem. is a recognized abbreviation for Memorial). We have many old signs with legacy abbreviations all over the state here because according to NJDOT, a mere change to naming standards is not enough reason to replace an entire BGS. Even name changes often just get patched on the BGS with like a small plate that covers the old name with the new one.
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 times

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

Postby PhantomSoul » Tue Aug 05, 2014 4:34 pm

Conn. = Connecticut

Mass. = Massachusetts

N.H. = New Hampshire

R.I. = Rhode Island

Del. = Delaware

Tenn. = Tennessee

Ala. = Alabama

Fla. = Florida
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 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...
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 times

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

Postby PhantomSoul » Tue Jun 03, 2014 5:25 pm

I'm not sure if this has been resolved yet or not, but I'm still getting the letter N pronounced as the letter N (instead of North) when it is the last word of a name and follows either the word Pkwy or Tpke, as in Garden State Pkwy N or New Jersey Tpke N. I have not seen this happen with S/South when used the same way.
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 times

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

Postby PhantomSoul » Wed Jan 01, 2014 1:56 am

I'll try the new voice if you still need testers. iPhone here.
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 times

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

Postby PhantomSoul » Fri Dec 27, 2013 6:04 pm

Is it possible that frequently encountered TTS data - like, say, reading the same phrases over and over again because you keep driving to work the same way - causes that TTS data to be accessed from a local cache?

In an unrelated observation, we seem to have a bunch of Tnl abbreviations on the Turnpike in northern NJ being read as its letters (tee en el), as opposed to Tunnel. This makes the Turnpike's references to the Holland and Lincoln Tunnels sound really weird. Is this a known bug/limit of the TTS and the Tnl abbreviation?
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 times

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

Postby PhantomSoul » Thu Nov 14, 2013 2:43 pm

To further the 9W phenomenon, I've seen the portion of this road in New Jersey named US-9w, with a lowercase w. I'm not sure, however, if this is a workaround for the west problem or whether it even causes the w to be read as a w instead of west.
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 times

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

Postby PhantomSoul » Wed Nov 13, 2013 4:36 pm

qwaletee wrote:
GizmoGuy411 wrote:
orbitc wrote:I have a few instances as well:

to Garden State Pkwy N wasn't correct. It read as "enn" not as "North"
Also, it's reading "Dr" as Doctor.


Is "Dr" being pronounced as "Doctor" wide spread or isolated?

Can you send me some examples?

I want to know if there is any correlation to the occurrence of "Sulgrave Dr" being pronounced as "Sulgrave Doctor" that we have found before in multiple locations.


Yeah, love those. Been bitten by them a few times. And why I say bite, I mean by a fit of laughter.

I also saw a UR flaming Waze for 9W. I'm not sure exactly what Waze spoke, but the complaint was that there are two separate NY highways, 9 and 9W, and blah blah blah east and west of Hudson River. UR was on 9W, maybe Waze said "to route 9 west," which he took to mean "state route 9, direction west."

There ought to be a way to flag a piece of text as being "non-abbreviated," so that Waze pronounces it exactly as-is. Or, alternatively, a way to type in the pronounced version of a segment name, so that Waze speech in fine tuned for a problematic reading.


I've actually seen exactly what you were talking about when I was up in Newburgh last week. My guess would be that someone (I didn't look at the segments in WME) made the road US-9 instead of US-9W (what it probably should be) in order to get the shield to render correctly. Currently shields do not draw correctly for any highway that has a letter as part of its number (this occurs a lot in New York). In any case, this is a bad reason, because the shield rendering engine is being fixed to accommodate highway markers with letters on them.

Also, I believe at one time the TTS would read US-9W as You Ess Nine West, so the W may have been removed to prevent confusion on the road that actually runs north/south. I think that's supposed to be fixed now - so as if the W is in the same word (not separated by a space) as a highway number (in this case, US-9), it will be read as W and not West. So I would imagine the road should be changed back to US-9W.

Any thoughts from Hudson Valley area managers?
ImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Local Champ Mentor
Local Champ Mentor
 
Posts: 1706
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 316 times
Been thanked: 524 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users