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 loadbang » Mon Sep 17, 2012 10:52 am

AlanOfTheBerg wrote:
xteejx wrote:Any chance we can have Saint back the way it was, ie St at the start. Annoying work if we have to change them all!

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.

We do get streets called "All Saints", However, as there are not many streets with this name it might be a good if we use "saint" in full rather than abbreviated.
loadbang
 
Posts: 249
Joined: Mon Nov 28, 2011 7:12 pm
Has thanked: 4 times
Been thanked: 2 times

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

Postby GizmoGuy411 » Sun Sep 16, 2012 4:59 pm

jemay wrote:...
Ok, I changed the four segments to be W Ave 'n', so when exiting the freeway the navigation would announce the street name correctly?


Yes it should, but please report back to let us know how the TTS sounds.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 648 times
Been thanked: 427 times

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

Postby txemt » Sun Sep 16, 2012 6:51 am

jemay wrote:Ok, I changed the four segments to be W Ave 'n', so when exiting the freeway the navigation would announce the street name correctly?


Let's hope it does. :)
txemt
Area Manager
Area Manager
 
Posts: 4764
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

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

Postby jemay » Sun Sep 16, 2012 6:39 am

GizmoGuy411 wrote:
jemay wrote:Another example abbreviation problems...

Type: General error
Description: voice calls this "west avenue north" but it is "west avenue N"
Reported on: Yesterday

N is the letter of the street (A,B,C,...L,M,N,O) So it is not North.... So what do I do with the request UR

https://www.waze.com/editor/?zoom=4&lat ... FTTTTTTTFT

Thanks

Unfortunately there is only one solution at the moment, and that is to rename the road [West Avenue 'n']. You could also name it [W Ave 'n'] however I would opt to be as close to however the local signage displays it.

Note that 'N' will not work, only a lower case 'n' works so far that we have found for TTS to actually pronounce the letter instead of the cardinal direction. So same holds, 'e', 's', and 'w'.

Ok, I changed the four segments to be W Ave 'n', so when exiting the freeway the navigation would announce the street name correctly?
jemay
Waze Global Champs
Waze Global Champs
 
Posts: 1971
Joined: Tue Nov 09, 2010 1:26 am
Location: US South West - Lakewood, CA
Has thanked: 612 times
Been thanked: 896 times

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

Postby GizmoGuy411 » Sun Sep 16, 2012 6:08 am

jemay wrote:Another example abbreviation problems...

Type: General error
Description: voice calls this "west avenue north" but it is "west avenue N"
Reported on: Yesterday

N is the letter of the street (A,B,C,...L,M,N,O) So it is not North.... So what do I do with the request UR

https://www.waze.com/editor/?zoom=4&lat ... FTTTTTTTFT

Thanks


Unfortunately there is only one solution at the moment, and that is to rename the road [West Avenue 'n']. You could also name it [W Ave 'n'] however I would opt to be as close to however the local signage displays it.

Note that 'N' will not work, only a lower case 'n' works so far that we have found for TTS to actually pronounce the letter instead of the cardinal direction. So same holds, 'e', 's', and 'w'.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1402
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 648 times
Been thanked: 427 times

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

Postby jemay » Sun Sep 16, 2012 5:07 am

Another example abbreviation problems...

Type: General error
Description: voice calls this "west avenue north" but it is "west avenue N"
Reported on: Yesterday

N is the letter of the street (A,B,C,...L,M,N,O) So it is not North.... So what do I do with the request UR

https://www.waze.com/editor/?zoom=4&lat ... FTTTTTTTFT

Thanks
jemay
Waze Global Champs
Waze Global Champs
 
Posts: 1971
Joined: Tue Nov 09, 2010 1:26 am
Location: US South West - Lakewood, CA
Has thanked: 612 times
Been thanked: 896 times

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

Postby Kandralla » Fri Sep 14, 2012 8:34 pm

GizmoGuy411 wrote:Penn for Pennsylvania was moved from the main list to the State abbreviation list where it belongs, along with other alternate state abbreviations. Yes we definitely want it removed from the TTS!


Am I correct in my assumption that this means that William Penn Highway will now be called "William Penn Highway" as oppoesed to "William Pennsylvania Highway"?

If so thanks, that was annoying.
Kandralla
 
Posts: 67
Joined: Wed Jan 18, 2012 7:15 am
Has thanked: 0 time
Been thanked: 0 time

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

Postby vectorspace » Fri Sep 14, 2012 5:49 am

More on the Indian Reservations / Indian Nations...

Another road system in NM and AZ is the "Navajo Service Route XXX" roads. There are not a massive number of them, but they cover a lot of area. They are listed on http://www.navajotransit.com/, which is primarily some kind of bus system for those routes on the Navajo Nation.

I would suggest a short abbreviation as NSR-XXX. Others could take into account existing abbreviations as "Navajo Svc Rte XXX." I have not heard the TTS system pronounce "Navajo" to see if it comes out correctly either.

Regarding the BIA-XXX roads, which are more widespread, I would not suggest TTS expanding BIA to "Bureau of Indian Affairs," as that's rather long and one might have already passed a turn by the time it is spoken! Why can't the TTS system focus on cap letters and just say B. I. A.? I have not read this whole thread in detail, so I assume that has already been discussed for other acronyms.
vectorspace
 
Posts: 1183
Joined: Sat Dec 17, 2011 7:05 pm
Location: Albuquerque, NM, USA
Has thanked: 173 times
Been thanked: 420 times

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

Postby txemt » Fri Sep 14, 2012 2:55 am

I discovered, today, that "FM" reads "Farm to Market Rd." :D
txemt
Area Manager
Area Manager
 
Posts: 4764
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

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

Postby floppyrod84 » Thu Sep 13, 2012 1:40 pm

Two letters would have worked. I and A ;-)

Sent from my GT-I9100P using Tapatalk 2
floppyrod84
 
Posts: 2569
Joined: Wed Jan 19, 2011 3:17 pm
Location: Sheerness, Kent, UK
Has thanked: 46 times
Been thanked: 45 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users