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?

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.

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.

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

I've seen both happen, but only intermittently and only in some places. It seems like sometimes in some places, it would say Garden State Parkway North and other times in other places Garden State Parkway En.

Also, any updates on Br being read as branch despite many places using Br to mean Bridge? Or should we be using Brg for bridge, even though it conflicts with local signage?

I guess so, but I still think turning what is now a nice guided form, that I'm sure a lot of effort was put into making it that way, into a general command console is a bad idea. Besides this being a giant step backwards for where the WME system appears to be headed, I don't care what cone level/rank an editor is; he/she should not have to learn an entire set of cryptic (by cryptic, I mean anything not written in a natural human language - with spacing, punctuation, and capitalization that you would expect in normal narrative text of a human language) to control their input. At the end of the day, we're map editing volunteers - that have real professions outside of Waze - not some sort of system administrators.

Look, this is just my $0.02 for what it's worth. From my experience as a UI developer, there will always be people who want to bypass the UI development process with hacks like this to get quicker immediate returns. But in the long run, unless Waze creates some kind of administrator certification program to teach people these backdoor hacks - and limits such editing to only those people, it will create confusion, which will compromise the accuracy, reliability, and ultimately the overall usefulness of the data, reducing it to just meaningless clutter in the database, something that many other conversation threads, as well as established editing policies clearly suggest is a major concern.

Frankly, introducing a hash tag syntax to names just further complicates a UI that already appears overwhelming for many new editors. Further, from my understanding, Twitter-style hash tags are intended for indexing hot words and related topics, not for altering the way input is handled. The WME is a guided input form that instructs you to make specific inputs for specific purposes, not a general command prompt.

If phonetic names are that important to have different behavior from the alternate street names (which appear to be intended for a future address resolution system; no TTS or banner display involved) then we should get Waze to add a text control that actually prompts for phonetic input. A bigger caveat to this, however, might be how many editors are familiar with universal phonetic spelling, and how many of those are familiar with how to produce many of its whacky characters on a keyboard?

skreidle wrote:This may affect all NA users, or at least a sigificant number. When the app announces the road hazard, "Object on road ahead"; it seems to consistently speak "obJECT" rather than "OBject".

iOS, app v4.7.0.2

ehepner1977 wrote:

skreidle wrote:This may affect all NA users, or at least a sigificant number. When the app announces the road hazard, "Object on road ahead"; it seems to consistently speak "obJECT" rather than "OBject".

iOS, app v4.7.0.2

Confirmed, Android, Jane is a lawyer who has a problem with something in the court room.

Sent from my SAMSUNG-SM-G920A using Tapatalk

This is a known long standing issue, unfortunately we are still waiting for the fix.