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 PhantomSoul » Mon May 20, 2013 2:53 pm

I guess so, but I still think turning what is now a nice guided form, that I'm sure a lot of effort was put into making it that way, into a general command console is a bad idea. Besides this being a giant step backwards for where the WME system appears to be headed, I don't care what cone level/rank an editor is; he/she should not have to learn an entire set of cryptic (by cryptic, I mean anything not written in a natural human language - with spacing, punctuation, and capitalization that you would expect in normal narrative text of a human language) to control their input. At the end of the day, we're map editing volunteers - that have real professions outside of Waze - not some sort of system administrators.

Look, this is just my $0.02 for what it's worth. From my experience as a UI developer, there will always be people who want to bypass the UI development process with hacks like this to get quicker immediate returns. But in the long run, unless Waze creates some kind of administrator certification program to teach people these backdoor hacks - and limits such editing to only those people, it will create confusion, which will compromise the accuracy, reliability, and ultimately the overall usefulness of the data, reducing it to just meaningless clutter in the database, something that many other conversation threads, as well as established editing policies clearly suggest is a major concern.
ImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Country Manager
Country Manager
 
Posts: 1609
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 294 times
Been thanked: 470 times

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

Postby sketch » Mon May 20, 2013 3:48 pm

Agreed. The nuances of map editing are confusing enough already. We don't need more of them, especially just for pronunciation.

Every GPS system on the market pronounces street names wrong all the time. Waze does some better, some worse than others. Yes, we like to be better than everyone, but the benefit we'd gain from this is small compared to the pain of editing this into every segment of the map Waze might get wrong.

People can figure out that "Arnoo" means "Arnoult" and not "Severn" or "Hessmer" or any of the streets nearby. It isn't crucial that Waze says it with the T like everybody in town. It's good enough not to have to worry about it THIS much.


Sent from my iPhone using Tapatalk 2
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5745
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1307 times
Been thanked: 1766 times

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

Postby berestovskyy » Mon May 20, 2013 6:28 pm

PhantomSoul wrote:But in the long run, unless Waze creates some kind of administrator certification program to teach people these backdoor hacks [...]

"Certification program" for "backdoor hacks"? Oh, come on! :lol: Every single system or game has settings. They are confusing sometimes, that is why UI developers hide them under the "Settings" ;)

Yes, I really think the feature we use for one of a 100 road segments really deserve "to bypass the UI development process" like you said. And it's not only about immediate returns, but also about cluttering WME interface.

Examples?
  1. "Toll roads". There are many countries with no toll roads at all. But the option is there, easily accessible.
  2. "Lock", now with a dropdown box. How often do we use this feature? New editors especially.
  3. On the other hand, every single segment has an address. But we have to click "Edit" next to "Unnamed segment" and then "Apply".
So no, I don't like the way "WME system appears to be headed" :(
berestovskyy
 
Posts: 925
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 254 times
Been thanked: 703 times

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

Postby PhantomSoul » Mon May 20, 2013 6:30 pm

Like I said, I think it's confusing, and a dedicated text control marked with a phonetic pronunciation label is the best way to go, assuming such input is needed.
ImageImageImageImage
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS (latest) / Waze (latest/beta)
PhantomSoul
Country Manager
Country Manager
 
Posts: 1609
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 294 times
Been thanked: 470 times

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

Postby AlanOfTheBerg » Mon May 27, 2013 8:33 pm

Here's a report of Waze properly pronouncing "County Rd" for the "Co" abbreviation. User is from Michigan.

https://twitter.com/sorcererdale/status ... 8604571648

It's the first I've heard of this.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 10.1.1 | Waze v4.14
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23501
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1091 times
Been thanked: 4641 times

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

Postby jondrush » Wed May 29, 2013 6:40 pm

Two recent abbreviations I've seen are L for lower and O for old. Anyone know how TTS would handle these?
Keeping the Waze maps tidy since 2009
jondrush User Page
Image
jondrush
Waze Global Champs
Waze Global Champs
 
Posts: 2641
Joined: Tue Sep 22, 2009 10:20 pm
Location: South Eastern Pennsylvania, USA
Has thanked: 193 times
Been thanked: 504 times

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

Postby AlanOfTheBerg » Wed May 29, 2013 6:57 pm

jondrush wrote:Two recent abbreviations I've seen are L for lower and O for old. Anyone know how TTS would handle these?

I think those should just be spelled out.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 10.1.1 | Waze v4.14
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23501
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1091 times
Been thanked: 4641 times

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

Postby AlanOfTheBerg » Wed May 29, 2013 7:37 pm

AlanOfTheBerg wrote:Here's a report of Waze properly pronouncing "County Rd" for the "Co" abbreviation. User is from Michigan..

Looks like this road is using the abbreviation of "CR" and not "Co" per the original tweet. Road is "CR-480": https://www.waze.com/editor/?zoom=4&lat ... s=19400448 south of Harvey, MI.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 10.1.1 | Waze v4.14
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23501
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1091 times
Been thanked: 4641 times

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

Postby dctdye » Wed May 29, 2013 8:14 pm

I'm assuming this is a known bug/naming problem with the spacing but today i was told to stay right onto us-280 instead of U.S. I *think* it was this ramp:

https://www.waze.com/editor/?zoom=6&lat ... nts=956781
Area Manager- Tuscaloosa/Northport, AL

Image
dctdye
 
Posts: 166
Joined: Tue Jul 24, 2012 3:27 am
Location: AL, USA
Has thanked: 58 times
Been thanked: 13 times

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

Postby AlanOfTheBerg » Wed May 29, 2013 8:15 pm

dctdye wrote:I'm assuming this is a known bug/naming problem with the spacing but today i was told to stay right onto us-280 instead of U.S. I *think* it was this ramp:

https://www.waze.com/editor/?zoom=6&lat ... nts=956781

You need to have spaces on both sides of the slash characters, per the naming guidelines.
Wiki Resources: Map Editing Manual | alanoftheberg@gmail.com
Oregon-based US Country Manager | iPhone6 - VZ - iOS 10.1.1 | Waze v4.14
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23501
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1091 times
Been thanked: 4641 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users