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 GizmoGuy411 » Sat Sep 08, 2012 2:18 am

Alice2 wrote:I just discovered how TTS treats one of the exits and streets here. On printed maps, the street is written as UTSA Blvd. The Waze map has it as Utsa Blvd. It is supposed to be pronounced as 'you tea ess aaa' sounding out each letter. TTS tries to say the name as a word - "ootsa Blvd". The exit signs for this street have it as 'UTSA Blvd / University of Texas at San Antonio', and TTS announces "ootsa Blvd / University of Texas at San Antonio". I see in this thread that to be pronounced as letters, they should be written as lower case surrounded by single quotes. That would probably look awkward -- 'u' 't' 's' 'a' -- and unmanageable if you have to write it very many times. How should this be handled to get the right announcement?



Since there is an "s" in name there is no was to just use spaces between the letters as "s" is currently the abbreviation for "South". And you are right that using the letters surrounded by single quotes would look awkward when displayed in the client.

Using U T 's' A would not be much better, although it would probably sound correct.

I'm afraid until we get that exception field that mapcat mentioned, the only way to handle it is to just spell it out.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1410
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 661 times
Been thanked: 433 times

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

Postby mapcat » Sat Sep 08, 2012 1:00 am

Alice2 wrote:I just discovered how TTS treats one of the exits and streets here. On printed maps, the street is written as UTSA Blvd. The Waze map has it as Utsa Blvd. It is supposed to be pronounced as 'you tea ess aaa' sounding out each letter. TTS tries to say the name as a word - "ootsa Blvd". The exit signs for this street have it as 'UTSA Blvd / University of Texas at San Antonio', and TTS announces "ootsa Blvd / University of Texas at San Antonio". I see in this thread that to be pronounced as letters, they should be written as lower case surrounded by single quotes. That would probably look awkward -- 'u' 't' 's' 'a' -- and unmanageable if you have to write it very many times. How should this be handled to get the right announcement?

I don't think it's saying you're supposed to use lower case in quotes, just that that style will produce the desired result. It may prove valuable if Waze provides us with a TTS override field at a later date. But for now I don't think there's a way to get it to work; even leaving spaces in between the letters might get you a "south" where you don't want it.

On a related note, one of my job sites has the acronym OSUM, and that's how I entered it in my favorites list. At some point recently, Waze began announcing "Arriving at Awesome" as soon as I pull into the parking lot. Which is awesome.
mapcat
 
Posts: 2444
Joined: Mon Dec 20, 2010 5:29 am
Has thanked: 95 times
Been thanked: 196 times

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

Postby Alice2 » Sat Sep 08, 2012 12:54 am

I just discovered how TTS treats one of the exits and streets here. On printed maps, the street is written as UTSA Blvd. The Waze map has it as Utsa Blvd. It is supposed to be pronounced as 'you tea ess aaa' sounding out each letter. TTS tries to say the name as a word - "ootsa Blvd". The exit signs for this street have it as 'UTSA Blvd / University of Texas at San Antonio', and TTS announces "ootsa Blvd / University of Texas at San Antonio". I see in this thread that to be pronounced as letters, they should be written as lower case surrounded by single quotes. That would probably look awkward -- 'u' 't' 's' 'a' -- and unmanageable if you have to write it very many times. How should this be handled to get the right announcement?
Alice2
 
Posts: 29
Joined: Wed Oct 05, 2011 3:30 pm
Has thanked: 2 times
Been thanked: 0 time

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

Postby GizmoGuy411 » Fri Sep 07, 2012 9:14 pm

vectorspace wrote:I'm sorry for posting this so late, but have been occupied with other things. I looked at the first post with the link to the document and didn't see a couple of things. I might have missed some.

Obvious:
== Cll (or CLL) is used all over NM for Calle (Street in Spanish). While Calle was in the first post spreadsheet, someone seemed to suggest "C" represent it. That seems too simple and might lead to confusion.

Indian Reservations:

I posted some of this on other threads I believe---that western US states especially have a lot of Indian reservations.

== Indian Service Route --or-- Indian Service Rte --or-- Indian Svc Rte

It would be nice to have ISR be placed in the TTS. This is relatively common. If there is some other standard, I don't care what it is. I am just worried that Indian reservations are under represented.

== Navajo Service Route --or-- other variant per above

This is less common, but I would imagine that each Indian tribe reservation may have their tribe name on some of these roads. While one could suggest NSR, I would wonder how many other tribes have special names. In New Mexico, it seems most tribes use the Indian Service Rte (or Route) on the map, but we have a large population of Navajos, so they may get special treatment.

== Indian Road

I have no idea if it is worth putting this in the mix, but have seen it a bit as well.



I agree that "C" is too simple of an abbreviation for "Calle".

At the moment however we are hesitating from making any more actual suggestions until we actually learn more about what is already recognized.

Since as you point out "Cll" and CLL" is commonly used for "Calle", I'll be sure to add those to the test list.

I was not entirely clear on your other suggestions however. Can you clarify which abbreviations are currently in use? I'll add them to the test list. I will also add any suggestions that you may not have actually seen on signs, but feel are likely being used. If you could check other mapping services, including state government sites, it may be helpful. I had no luck with a Google search nor in Wikipedia.

Later we can start making suggestions for abbreviation changes. That also probably also need an entire new forum thread to handle.
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1410
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 661 times
Been thanked: 433 times

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

Postby vectorspace » Fri Sep 07, 2012 2:50 am

I'm sorry for posting this so late, but have been occupied with other things. I looked at the first post with the link to the document and didn't see a couple of things. I might have missed some.

Obvious:
== Cll (or CLL) is used all over NM for Calle (Street in Spanish). While Calle was in the first post spreadsheet, someone seemed to suggest "C" represent it. That seems too simple and might lead to confusion.

Indian Reservations:

I posted some of this on other threads I believe---that western US states especially have a lot of Indian reservations.

== Indian Service Route --or-- Indian Service Rte --or-- Indian Svc Rte

It would be nice to have ISR be placed in the TTS. This is relatively common. If there is some other standard, I don't care what it is. I am just worried that Indian reservations are under represented.

== Navajo Service Route --or-- other variant per above

This is less common, but I would imagine that each Indian tribe reservation may have their tribe name on some of these roads. While one could suggest NSR, I would wonder how many other tribes have special names. In New Mexico, it seems most tribes use the Indian Service Rte (or Route) on the map, but we have a large population of Navajos, so they may get special treatment.

== Indian Road

I have no idea if it is worth putting this in the mix, but have seen it a bit as well.
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 AndyPoms » Thu Sep 06, 2012 4:59 pm

GizmoGuy411 wrote:Ill add it to the list to show obedience that actually works correctly. Is that the exact capitalization and punctuation?


That's why I permalinked it, so others could look... It is "St Mary St" without the quotes... 2 of the 3 segements were last updated on Mon Jun 25 2012 & the 3rd (middle) was last touched even earlier (Thu Mar 08 2012)...
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7161
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1314 times

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

Postby GizmoGuy411 » Thu Sep 06, 2012 4:42 pm

Ill add it to the list to show obedience that actually works correctly. Is that the exact capitalization and punctuation?

Sent from my Galaxy Nexus using Tapatalk 2
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1410
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 661 times
Been thanked: 433 times

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

Postby AndyPoms » Thu Sep 06, 2012 3:34 pm

I can report that "St Mary St" in Hamden, CT says "Saint Mary Street" in TTS... I drove it twice to confirm... (Permalink)
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7161
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1314 times

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

Postby AndyPoms » Tue Sep 04, 2012 3:43 pm

"Int'l" for "International" added to WME on 8/28/2012... Made map update on 9/4/2012... TTS reads it the same as "Intl" saying "untell"...
AndyPoms
Waze Global Champs
Waze Global Champs
 
Posts: 7161
Joined: Tue Dec 27, 2011 1:34 pm
Location: Hartford, CT
Has thanked: 129 times
Been thanked: 1314 times

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

Postby Binky71 » Mon Aug 27, 2012 3:43 am

AlanOfTheBerg wrote:(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.


The point is well taken. The signs often do say "Gd" instead of "Grand". I've been putting them in as Grand. But if we want them to match the signs, then we should eventually make the change.
Binky71
 
Posts: 38
Joined: Fri Sep 24, 2010 10:00 pm
Location: Troy, Michigan, USA
Has thanked: 4 times
Been thanked: 1 time

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users