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: delilush

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

Postby vectorspace » Sat May 12, 2012 3:20 pm

Another topic: Indian Reservations in the US...

I've not been a part of this discussion and have searched the 18 pages on TTS without finding anything. This is also probably a topic for textual road abbreviations on the client.

There are a lot of American Indian reservations in the US Southwest. I am starting to address some of the roads there now in New Mexico. I see that these are not well represented in the material on Waze likely because they have fewer drivers. Some areas are high traffic from tourism or casino traffic. These regions actually have a large amount of autonomy from the US Government and therefore different road naming conventions than states or interstates.

One convention is "Indian Service Route XXX." Many times these are named inconsistently in the current map with the usual abbreviation "Indian Svc Rte XXX" being used, but sometimes other variations being used for highway-like roads. Other lesser streets have names like "Indian Rd XXX." Other states may use other naming conventions.

It would seem that the primary textual values on the map are displayed on an often-cramped client display, a much shorter version could be used. This would impact the TTS as well. Obviously the smallest abbreviation might be "ISR-XXX." That's one I prefer because it seems brevity is the primary driver due to a small client display.

It would be nice if we considered the US Indian reservations in both the textual abbreviations and the TTS.

As a relative outsider (6 months new) and pragmatist, I am often struck by how the Waze software team seems distant from the dedicated AM/editor group both dynamically and by setting standards. Maybe that is part of what makes a world-wide social app work. Efforts here are commendable. Client/Server software seems like the place to solve a lot of these issues with ability to parse a wide range of naming conventions and abbreviations. If Waze is truly successful in having a community-based editing crowd, many less-dedicated and formalized editors will name things however they want and that crowd will overwhelm dedicated editors.
vectorspace
vectorspace
 
Posts: 1184
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 usa_iv3ckt44 » Wed Jun 11, 2014 2:51 pm

What would you guys think of a cheap remote that wirelessly reports the most common/important incidents (crash/police/red light cameras)? I think if there was a device that you could clip on your steering wheel/air vent or anywhere in the car that doesn't require you to take your eyes off the road. I'm trying to do a DIY project at home so I don't have to spend 10 seconds with my eyes on my phone and off the road each time I want to report an incident.

Thanks guys!
usa_iv3ckt44
 
Posts: 3
Joined: Wed Jun 11, 2014 2:43 pm
Has thanked: 0 time
Been thanked: 0 time

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

Postby unlimited1808 » Tue Oct 27, 2015 9:03 pm

Cmns as an abbreviation for Commons is being pronounced as "C M N S" by Jane.

https://www.waze.com/editor/?env=usa&lo ... st=4698608

Has this abbreviation been deprecated since the update to Jane (and the original abbreviation wiki page) or is it being worked on for an update?
unlimited1808
State Manager
State Manager
 
Posts: 286
Joined: Fri Jul 04, 2014 1:05 am
Location: Eastern Pennsylvania, US
Has thanked: 65 times
Been thanked: 80 times

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

Postby txemt » Fri Aug 15, 2014 7:01 pm

Si
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4772
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 txemt » Fri Aug 15, 2014 2:31 pm

Rev.
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4772
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

Re: Roman numerals

Postby txemt » Fri Jun 06, 2014 6:19 am

dbraughlr wrote:
sketch wrote:Unless "Louis" is pronounced neither the English nor the French way, it cannot be "fixed". In some places one will be right, and in others the other, but no universal fix is possible.

Another proposal in another thread addressed this; I'm pretty sure you were there.


Same with Ponce de Leon.
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4772
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 txemt » Sat May 10, 2014 4:03 pm

They'll fix it "soon".
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4772
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 txemt » Sat Mar 29, 2014 9:56 pm

sketch wrote:This has been reported in a few places around the forums. There's been some kind of bug propagating over the past couple months where "N" is not pronounced "north" after certain words — "Pkwy" and "Expy", for example, and I think perhaps in "Cesar Chavez N" as well.


And Florida's Turnpike N
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4772
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

Re: BI- prefix for interstate business loops

Postby txemt » Tue Mar 04, 2014 7:47 pm

dbraughlr wrote:
txemt wrote:I've been spelling out "business". I'd rather have waze say "I-20 business" instead of "I-20 bus".


That's great if you want to do do that. Why don't you update the wiki so that we can update them all?

I propose that for a long-term solution for correct shields that we standardize a prefix ("BI-") for interstate business loops. Thus BI-20 would generate the correct shield and TTS (perhaps "biz loop twenty").


Talk to GizmoGuy on the TTS stuff. He's the goto for that.
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4772
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 txemt » Tue Mar 04, 2014 9:04 am

It'll say "bee elle" or "bl"
Just wazeting my time to help you waze your route smoothly.
txemt
 
Posts: 4772
Joined: Tue Jul 17, 2012 7:03 pm
Location: 26.1901 80.3659
Has thanked: 42 times
Been thanked: 1034 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users