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

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

Moderators: Jackson, krankyd, rondesta, adriansinger

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

Postby GizmoGuy411 » Thu Apr 17, 2014 11:18 pm

CBenson wrote:Its not uncommon around here for BGS near state boaders to include the state for a destination. Thus ramp names that copy the BGS crop up with state abbreviations around here.


sketch wrote:There's definitely an exit on I-59 in Mississippi (or maybe Georgia) that lists "Something, Ala." as one of its destinations served.


Alan raised a good question. I started to wonder myself why I had them all tagged as "A"dd in the test list, and if I did so years ago, just because I thought it was a good idea at the time, or if there were other reasons I don't remember, like possibly for use with route numbers.

In any case, can you guys provide a couple examples? Meanwhile I'll try to start from page one here and see if I can find a better rationale for "A"dding them.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1107
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 170 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Fri Apr 18, 2014 2:37 am

sketch wrote:Other considerations too, like do we really want LA to say "Louisiana"? Everyone here says "L A one", "L A forty-eight", and so forth.

I believe the idea was to get this done so we could use state abbreviations for state highways. Not that that's perfect. Some states would prefer SR or SH I'm sure — but the benefit of that is that we could get state-specific shields for every state. BUT of course it won't work for Nebraska.


Well if we did make "LA" another exception to say the letters "L A" then it would also work for Los Angles.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1107
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 170 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Fri Apr 18, 2014 2:18 pm

sketch wrote:All I'm saying is that we should consider each state abbreviation individually. If it's best that MD say Maryland, so be it. If people say "N C x" for NC state highways, keep the letters for that state.

We also don't want to be using "MI" instead of "M" for Michigan state highways because they're unequivocally referred to as "M-x". But for other states, it would be useful, like Maryland.

Obviously we can't achieve full parity because of Nebraska/northeast, so we might as well be accommodating.


Would we ever want "NE-" used for "Northeast-[something]"?

If not, then we actually maybe we can even accommodate Nebraska if the RegEx can be wrote to use "NE-xxx" to say "Nebraska xxx", instead of "Northeast xxx".

That is of course if that is how they refer to them.

And yes. Agreed on "M-xxx" for Michigan.

We should probably take this discussion off to another topic thread, and just point to it from here, since we have almost 70 abbreviations for State/Provinces, etc.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1107
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 170 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Sun Apr 20, 2014 1:41 am

I'm out of the loop for 12 hours. Alan and I both told Waze that "BUS" failed in several tests, and Alan told them of the "Saint vs Street" failures. So the request for corrections are in the loop.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1107
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 170 times
Been thanked: 105 times

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

Postby GizmoGuy411 » Sun Apr 20, 2014 1:44 am

And for full disclosure, you can all blame me for the "NE" and "FM" oversights. I was over confident that they had been cross checked a long time ago against any conflicts.
ImageImageImageImage
CM: U.S.
RC: Great Lakes - IL, IN, MI, OH, WI
AM: NW OH, NE IN, & SE MI
Wiki Profile
Verizon: Galaxy S4 w/ Android 4.3 & iPad "3" w/ iOS 7.1
GizmoGuy411
Waze Global Champs
Waze Global Champs
 
Posts: 1107
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 170 times
Been thanked: 105 times

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

Postby harling » Thu Jan 19, 2012 1:58 pm

Having written my share of regexps and parsers, it occurrs to me that if we are going to use the period/full-stop '.' character to differentiate 'N' ("north") from 'N.' ("enn") or 'St' ("street") from 'St.' ("saint"), we also need to decide whether it should have to be followed by a space. For example, should it recognize 'St.Louis' (no space) as "Saint Louis"?

Unless someone can think of a good reason to allow '.' mid-word, I think the '.' should double as a delimiter (i.e., a space should not be required), if only for the sake of saving screen real estate. "N Street" would be written as either 'N.St' or 'N. St'.
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 114 times

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

Postby harling » Thu Jan 19, 2012 2:49 pm

WeeeZer14 wrote:And I think the period after the single letter indicating that it should be the letter is confusing. Plenty of signs out there that use N. to mean North and S. to mean South etc.

For the sake of clarity and reliability, you are right that we should try to minimize overloading (e.g., 'N' vs. 'N.'), and try to minimize positional semantics (e.g., handling "St" differently depending on where it appears). The more "common sense" we try to build into it, the more complicated the code is to implement it, and the more likely fixing one problem will break something else.
BTW, maybe we should find out how these are handled:
So. (South)
No. (North)

Those would be good options to reduce overloading in street names, but we still need to address how to write "enn street" in a way that is readable, without breaking the existing database that uses 'N' for "north".
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 114 times

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

Postby harling » Thu Jan 19, 2012 6:29 pm

bgodette wrote:Basically there needs to be positional awareness for handling things like St, Dr, N/S/E/W. Can anyone think of a name where St isn't Saint unless it's at the end of the name and therefore Street? Same thing for Dr.

'Storrow Dr E' is supposed to be "storrow drive east", not "storrow doctor east" or "storrow doctor ee". And each time someone comes up with an example that we haven't anticipated, the rules (and code) become messier and harder to maintain.

All these conditions and exceptions are easy enough for a human to follow, but to a computer, context-sensitive grammars are brittle. Trust me, I have done this for a living. Better to start now with as straightforward and literal a system as possible, or it will turn into a perpetual problem, where fixing one case will break several others.
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 114 times

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

Postby harling » Sat Jan 21, 2012 2:26 pm

dmcconachie wrote:You can find the engine being used in the preferences file. One of our users (Xteejx) located it and tried sending commands manually but it didn't even adjust for "St" as "Street". Waze is clearly intervening in the command before it is sent to the engine!

That's how I heard it explained (by Ehud IIRC). The routing engine parses the street names into phrases, and passes them to the client along with the original names. When the time comes to announce a street, the client displays the un-parsed name, but sends the parsed name to the TTS engine. So, changing how Waze "reads" street names does not require a client update, as it's all done on the server side.
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 114 times

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

Postby harling » Wed Feb 15, 2012 3:35 am

bgodette wrote:
jenncard wrote:Then there is also the case where X<>number, like "F 1/2 Rd" :roll:
Isn't that F#?
Should be, yes. :lol:
Image
Area Manager, Eastern MA & Southern NH. Country Manager, USA.
Help wanted. Drop me a line!
Wiki Resources: Area Manager Wiki | Map Editing | Best Practices | Known Issues List
harling
Waze Global Champs
Waze Global Champs
 
Posts: 1730
Joined: Wed Oct 27, 2010 8:42 pm
Location: Eastern MA
Has thanked: 16 times
Been thanked: 114 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users