Test of Text-to-Speech (TTS) Abbreviations in Waze Clients

Image 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 jasonh300 » Tue May 14, 2013 3:01 pm

berestovskyy wrote:Hi!
We have an idea how to improve TTS pronunciation and how to deal with abbreviations. Basically we suggest to use Alt City/Street name to correctly pronounce names and/or to specify a short (abbreviated) street name.

Please support if you like the idea! ;)

Thanks!


This would be a very bad idea and would defeat the true purpose of Alt Name fields (which is for search results).

However, it wouldn't be a bad idea for a new dedicated field in which a phonetic spelling of names could be entered.
Image
New Orleans, Louisiana, USA
South-Central Regional Coordinator
(LA/MS/AR...contact karlcr9911 for TX/OK related issues)
U.S. Champ, Global Champ
Waze FAQ ... Best Map Editing Practice
Ask me about Louisiana Editors Chat in Google Hangouts!
jasonh300
Waze Global Champs
Waze Global Champs
 
Posts: 7560
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA, USA
Has thanked: 399 times
Been thanked: 967 times

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

Postby hmarian » Tue May 14, 2013 3:33 pm

I support jasonh300 and think it is not such a great suggestion.
Working with Waze to fix this is the way to go.

Hagay.

Device: Samsung Galaxy S5 (6.0.1)
Waze Version: 4.5.0.1
Country Manager: Canada
Area Manager: Greater Toronto Area, Buffalo (NY), Binyamina (Israel)
Android/WME Beta Tester
-----------------------------------------------------------------------------------------
Editing Manual | Editing Best Practice | @Waze_Canada
hmarian
Waze Global Champs
Waze Global Champs
 
Posts: 3354
Joined: Tue Sep 24, 2013 9:08 pm
Location: Toronto, Ontario, Canada
Has thanked: 141 times
Been thanked: 1408 times

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

Postby kentsmith9 » Tue May 14, 2013 3:39 pm

This conversation has been launched in two separate threads. This one and viewtopic.php?f=8&t=47255&start=10#p440213
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 5049
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 1277 times
Been thanked: 1496 times

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

Postby berestovskyy » Tue May 14, 2013 6:58 pm

hmarian wrote:Working with Waze to fix this is the way to go.

Sure! This is just a suggestion :)

jasonh300 wrote:This would be a very bad idea and would defeat the true purpose of Alt Name fields (which is for search results).

No, it's not. For instance:
Street: Northeast Kentucky Industrial Parkway <- this would be used by default (for search in this case)
Alt City: #short Alt Name: Northeast Pkwy <- this would be used to display and for TTS

Correction of pronunciation:
Street: John Paul IV Street <- this would be used by default (for search and to display)
Alt City: #tts Alt Name: John Paul 4th St <- this would be used for TTS

The #tts name could be a transcription (phonetic spelling) of the street name.

Having a prefix (#) it's easy to disting those properties and not use them for search if you like. But its not such a bad idea if one could find both '4th' and 'IV' IMO.

jasonh300 wrote:However, it wouldn't be a bad idea for a new dedicated field in which a phonetic spelling of names could be entered.

You see! They call it a brainstorming ;)
berestovskyy
 
Posts: 925
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 254 times
Been thanked: 693 times

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

Postby gerben » Wed May 15, 2013 9:56 pm

Well, if they implement a filter for #tts, maybe it is better to implement a dedicated tts input field.
Nokia Lumia 920 (WP8 3.7.6 client)
Countrymanager The Netherlands
ImageImageImageImage
gerben
 
Posts: 4779
Joined: Sun Dec 13, 2009 10:42 pm
Location: Almelo
Has thanked: 33 times
Been thanked: 194 times

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

Postby vectorspace » Sun May 19, 2013 12:54 am

From a number of visits with government agencies responsible for roads (see other threads) I have a few requests for addition to the TTS system.

(1) BIA-xxxxxx

Pronounced "B.I.A" then the following characters which will usually be a number, but could be a letter followed by a number in the future. This comes from a visit with Dept of Interior, Bureau of Indian Affairs, Supervisory Road Engineer.

(2) TR-xxx

Pronounced "Tribal Route" followed by the characters (up to six, but could just be one). This would be a generic tribal route designation for any tribal land that would accommodate it. This is not intended to be mandatory for use on all tribal lands, but rather a common form similar to "SR-xxx" for state routes.

(3) FSR-xxx

Pronounced "Forest Service Route" followed by a set of characters that would name the road, typically numbers and letters. This comes from talking to a US Forest Service GIS specialist that will be providing us forest road data, first for a few forests, and if that works we can have the forest data for the whole US.
vectorspace
vectorspace
 
Posts: 1184
Joined: Sat Dec 17, 2011 7:05 pm
Location: Albuquerque, NM, USA
Has thanked: 173 times
Been thanked: 419 times

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

Postby mapcat » Sun May 19, 2013 2:23 pm

vectorspace wrote:(2) TR-xxx

Pronounced "Tribal Route" followed by the characters (up to six, but could just be one). This would be a generic tribal route designation for any tribal land that would accommodate it. This is not intended to be mandatory for use on all tribal lands, but rather a common form similar to "SR-xxx" for state routes.

The spreadsheet lists TR-xxx as a proposed abbreviation for Township Road.
CM, USA/Canada ∙ iPhone 5 ∙ iOS 7.1
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 vectorspace » Sun May 19, 2013 3:55 pm

mapcat wrote:The spreadsheet lists TR-xxx as a proposed abbreviation for Township Road.


Thanks. I looked at the spreadsheet to check but missed that. If so, I'll seek an alternative abbreviation with BIA.
vectorspace
vectorspace
 
Posts: 1184
Joined: Sat Dec 17, 2011 7:05 pm
Location: Albuquerque, NM, USA
Has thanked: 173 times
Been thanked: 419 times

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

Postby PhantomSoul » Sun May 19, 2013 5:41 pm

Frankly, introducing a hash tag syntax to names just further complicates a UI that already appears overwhelming for many new editors. Further, from my understanding, Twitter-style hash tags are intended for indexing hot words and related topics, not for altering the way input is handled. The WME is a guided input form that instructs you to make specific inputs for specific purposes, not a general command prompt.

If phonetic names are that important to have different behavior from the alternate street names (which appear to be intended for a future address resolution system; no TTS or banner display involved) then we should get Waze to add a text control that actually prompts for phonetic input. A bigger caveat to this, however, might be how many editors are familiar with universal phonetic spelling, and how many of those are familiar with how to produce many of its whacky characters on a keyboard?
ImageImageImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS 9.3.2 / Waze 4.6
PhantomSoul
Country Manager
Country Manager
 
Posts: 1506
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 279 times
Been thanked: 453 times

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

Postby berestovskyy » Mon May 20, 2013 8:22 am

PhantomSoul wrote:Frankly, introducing a hash tag syntax to names just further complicates a UI that already appears overwhelming for many new editors.

So we have suggested it works/appears for 3 or even 5 cones editors only. Also we can use Key-Value pairs "just like Alt names", not abusing alt names.

PhantomSoul wrote:A bigger caveat to this, however, might be how many editors are familiar with universal phonetic spelling, and how many of those are familiar with how to produce many of its whacky characters on a keyboard?

In fact, in Nuance it looks like this:

b a k w *r d z -> backwards

Here is the Nuance Grammar Developer's Guide (PDF), page 85.

A separate TTS field would encourage people to put there something. On the other hand, a Key-Value pairs would allow to fix TTS/shields etc for experienced editors only. And we know, the majority of the segments do not need any TTS correction or shields at all.
berestovskyy
 
Posts: 925
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 254 times
Been thanked: 693 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users