Page 36 of 159

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

Posted: Tue Sep 02, 2014 2:50 pm
by doctorkb
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".

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

Posted: Wed Mar 07, 2012 3:42 pm
by DonJ2
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?

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

Posted: Tue Apr 03, 2012 1:22 pm
by DonJ2
Does TTS expand "Mem" or "MEM" to "Memorial"?

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

Posted: Wed Aug 22, 2012 2:00 am
by DonJ2
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?

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

Posted: Wed Aug 22, 2012 12:30 pm
by DonJ2
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. :)

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

Posted: Tue Sep 11, 2012 1:47 am
by DonJ2
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.

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

Posted: Tue Sep 11, 2012 1:51 am
by DonJ2
AndyPoms wrote:I can report that "Arpt" in Hartford, CT says "Airport" in TTS...
Yuke, It almost looks like apartment.

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

Posted: Sun Jan 04, 2015 9:56 am
by DrakeAnnDisorderly
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.

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

Posted: Thu Mar 30, 2017 6:38 pm
by DrDisaster
Chili Ave.

Chili is not pronounced like the food or chilly weather. It should be a long I like eye. Ch-eye-l-eye

https://www.waze.com/editor/?env=usa&lo ... ,505210403

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

Posted: Thu Mar 30, 2017 6:39 pm
by DrDisaster
.