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 AlanOfTheBerg » Thu Mar 01, 2012 6:37 pm

I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Mar 12, 2012 4:31 pm

I thought we decided long(er) ago that differentiation should be with the period or without. Positional should make no difference. St=street, St.=saint, Dr=drive, Dr.=Drive, etc. Why make it more complicated?
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Mar 12, 2012 4:46 pm

CBenson wrote:
AlanOfTheBerg wrote:I thought we decided long(er) ago that differentiation should be with the period or without. Positional should make no difference. St=street, St.=saint, Dr=drive, Dr.=Drive, etc. Why make it more complicated?

Did you mean Dr.=Doctor?

Yes. :oops: #Typingtoofast.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Fri Mar 23, 2012 2:54 pm

GizmoGuy411 wrote:The first batch of TTS abbreviation tests from yesterday's map updates have been tested.

This completed a third more of the 700 abbreviations to be tested.

Wow, you all are doing some great testing. I appreciate the time and effort you are putting in to this. Let us hope this bears good fruit with better and reliable abbreviations in the future!
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Apr 02, 2012 10:27 pm

GizmoGuy411 wrote:
AndyPoms wrote:...does anyone know a way to keep some form of "N. Y." (NY, N.Y., etc) for the display and get it to read "New York" in the TTS?


Look at the abbreviation list linked in the lead post of this thread. I think it has been updated to include the abbreviation for New York that works.

Or don't keep the form and spell out New York...
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Fri Aug 03, 2012 9:24 pm

There is an update request here which suggests that "cord" is being pronounced "county road" by Waze TTS. That's utterly ridiculous. Too bad map updates take so long to allow us to verify.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Aug 13, 2012 5:20 pm

invented wrote:I think it's pronouncing "(E)" as "Eee" again. -.-

Really? That'd be nice. I've been changing many to 'e' (and 'n', 'w' or 's') as that was the only option which worked. Where did you hear/see this?
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Mon Aug 20, 2012 4:00 pm

binkowski wrote:SIAP, but the abbreviation "Gd" for "Grand" is used quite a bit on Michigan highway signs. Any chance of adding this to the abbreviation list? For instance, "Gd" is used sometimes (but not always) for Grand Rapids and Grand River.

(Do the) The signs actually read "Gd Rapids" and "Gd River"? Either way, I don't see a good reason why we should abbreviate it. It's not like it takes up a lot of screen space to spell out Grand vs Gd and who knows if/when Waze will ever update the abbreviations list. It's better to have it read it out loud correctly than have the text match the sign 100%, IMO.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Wed Aug 22, 2012 4:49 am

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.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

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

Postby AlanOfTheBerg » Wed Aug 22, 2012 6:36 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.

I have not found a "3rd Rd" but I do have a "E 1st St" in my town and it does pronounce it "east first street" as we would hope.

I think it would still be worth it to verify things like 41st St, 141st St, and other combinations that combine "rd" and "Rd" like 33rd Rd, 63rd Rd, etc. I would figure if one or two pass, others will too.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23615
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4828 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users