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 doctorkb » Wed Aug 20, 2014 9:25 pm

CBenson wrote:
doctorkb wrote:"BUS" is also a proper word, but in all caps, it says "Business" -- how is that different?
Seriously? You answered in the question "but in all caps."
doctorkb wrote:If absolutely necessary, it could be set up as a "place in the string" sort of expansion:
Divers Lane is "Divers Lane"
whereas
Lane Divers becomes "Lane Diversion"
Sounds fine to me. But didn't this approach fail with St and Dr, thus we have St. for Saint and Dr. for Doctor?


I'm not sure what happened with the positioning approach. I have seen (and I'm fuzzy on specifics) where "N" doesn't become "North" -- perhaps it was "N Rd" was said "enn Road"? I assumed this was positioning...

I'm ok with DIVERS as the accepted abbreviation here, if we're going to be sticky on not having TTS follow the standard that has been published in the Waze wiki for YEARS... i.e. June 2011 ( https://wiki.waze.com/wiki/index.php?ti ... ldid=11667 ) because of a small handful of conflicts (spotted a half-dozen in the Livemap search)...

Nat, on the other hand shows:
Nat Washington Way
Nat Turner Boulevard
Nat Hoosier Lane
Nat Turner St (different from the Blvd)
Nat Ln

And the search runs out of spots to add more...
doctorkb
Coordinators
Coordinators
 
Posts: 8332
Joined: Wed Nov 04, 2009 9:17 am
Location: Edmonton, Alberta, Canada
Has thanked: 626 times
Been thanked: 1639 times

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

Postby doctorkb » Wed Aug 20, 2014 9:54 pm

sketch wrote:NA TTS doesn't apply just to Canada, we have to use it down here too. The Wiki isn't always right, and it was even less right the further back you go in its history.


That's fine, and it's just as possible for us to have a "Divers Lane" as you. The point being made is that this list was devised and was supposed to be followed for the last three years, with no-one bothering to point out this exception.

I'm actually more keen on establishing a standardized list of abbreviations that work in both the US and Canada (i.e. take official CanadaPost and USPS lists and resolve any differences), and making the result a Waze standard...

I will advocate for the removal of "Nat" as "National". I don't know why you are arguing as if I am saying that it should be there. The Big List is a compilation of test results. It is NOT a list of how we WANT things to be, it is a list of how things ARE.


Fair enough. Personally, I'd prefer to see the majority usage prevail... rather than pandering to the off-case situations. I have as many DIVERSIONS in Vancouver, BC as seem to be found in Livemap for all of NA with the string "Divers".
doctorkb
Coordinators
Coordinators
 
Posts: 8332
Joined: Wed Nov 04, 2009 9:17 am
Location: Edmonton, Alberta, Canada
Has thanked: 626 times
Been thanked: 1639 times

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

Postby doctorkb » Tue Sep 02, 2014 2:50 pm

That makes sense, sketch.

I'd recommend keeping something similar like SD- as having an expansion, but SD may need to go.

I'm reminded of when I tried using the Apple Maps when it first came out, and was directed on "Eh Bee Two" for "AB-2" -- multiple issues with it... one, we don't distinguish between provincial and national highways, as our system of federalism has delegated complete highway authority to the provinces... it should have just been "Hwy 2". Second, "AB" should be "Alberta".
doctorkb
Coordinators
Coordinators
 
Posts: 8332
Joined: Wed Nov 04, 2009 9:17 am
Location: Edmonton, Alberta, Canada
Has thanked: 626 times
Been thanked: 1639 times

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

Postby DonJ2 » Wed Mar 07, 2012 3:42 pm

Does anybody know if "Par" is announced as "Parade" via TTS?

I did not see it in the spreadsheet. I'm asking because of a UR that says "Par St" is not "Parade St". Not a single segment along "Par St" is or ever has been "Parade St", so I'm wondering if TTS says "Parade St" instead?
DonJ2
 
Posts: 562
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 46 times
Been thanked: 10 times

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

Postby DonJ2 » Tue Apr 03, 2012 1:22 pm

Does TTS expand "Mem" or "MEM" to "Memorial"?
DonJ2
 
Posts: 562
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 46 times
Been thanked: 10 times

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

Postby DonJ2 » Wed Aug 22, 2012 2:00 am

What does TTS say when streets use the following formats (for example)?

SW 41st Way (as in 40 first, I'm guessing TTS will say "Forty One Street Way"?)
SW 42nd Way (as in 40 second)
SW 43rd Way (as in 40 third, I'm guessing TTS will say "Forty Three Road Way"?)
SW 44th Way (as in 40 fourth)
... etc.

I've seen this format used in the basemaps. I could not find these abbreviations in the spreadsheet, so I'm wondering what TTS will do?
DonJ2
 
Posts: 562
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 46 times
Been thanked: 10 times

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

Postby DonJ2 » Wed Aug 22, 2012 12:30 pm

GizmoGuy411 wrote:
AlanOfTheBerg wrote:I'm pretty sure I've heard most of those abbreviations such as 22nd, 31st, 44th, etc., fully pronounced correctly. I know for certain that roads like "209th Ave" are correctly pronounced, in the US, as "two oh ninth avenue" and 175th and 185th are "one hundred seventy-fifth" and "one hundred eighty-fifth" as you would expect.


That is good to hear Alan. (pun intended)

Do you recall hearing any specific combinations such as "1st St" or "3rd Rd", as those type of combinations with similar suffixes are the ones that I think would be most likely to fail.


Thanks for the fast response guys. Glad to hear that I don't need to be concerned about it, at least for the combinations that I've seen so far. :)
DonJ2
 
Posts: 562
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 46 times
Been thanked: 10 times

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

Postby DonJ2 » Tue Sep 11, 2012 1:47 am

AlanOfTheBerg wrote:I don't think we should have Waze relying on positional pronunciation. It's just bound to fail. If we make it a standard that "St" is "street" and "St." is "saint" then we know exactly how it will be pronounced regardless of where it is in the street name.


+1, I agree.
DonJ2
 
Posts: 562
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 46 times
Been thanked: 10 times

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

Postby DonJ2 » Tue Sep 11, 2012 1:51 am

AndyPoms wrote:I can report that "Arpt" in Hartford, CT says "Airport" in TTS...

Yuke, It almost looks like apartment.
DonJ2
 
Posts: 562
Joined: Sat Oct 01, 2011 9:00 pm
Location: Central Florida, USA
Has thanked: 46 times
Been thanked: 10 times

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

Postby DrakeAnnDisorderly » Sun Jan 04, 2015 9:56 am

Just making a note for beating the 5 threads and a few hundred pages of posts dead horse.

So many cities begin with the word Saint here and are abbreviated as "St". So Saint Cloud or Saint Louis Park are read off as Street Cloud or "Keep right to Street Louis Park" and so very much a headache.
DrakeAnnDisorderly
 
Posts: 4
Joined: Thu Nov 13, 2014 10:44 pm
Location: Minnesota
Has thanked: 1 time
Been thanked: 1 time

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users