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 Wajo357 » Sun Feb 03, 2013 12:17 am

orbitc wrote:
GizmoGuy411 wrote:Regarding "Avenue S", I feel that since the word "Avenue" is not used as a suffix, and that it is used in this case more as a proper noun and not as an adjective, that it probably should remain spelled out, which would mean the name entry would be [Avenue 'S'], even though it implicitly implies that the road is an avenue.


Agreed. I'll keep them as you suggested. Again, we'll wait for you before we do any changes.

Keep in mind current Brooklyn Ave names use Ave and not Avenue. Furthermore, I believe street signs say Ave not Avenue. Why fix it if it Ain't broke? My vote is to leave Ave as is and just deal with the s.
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Thu Jan 31, 2013 2:05 am

orbitc wrote:
I'm waiting for:
Sp
A.T.&T.
Alt
St. Middle St

Those were added last night, so in a couple of days, they'll hit the client and I can test them out. I'm going to try out some combos of "S 1st St W" to see what I get.


Are we getting mix messages?
Wajo357 tested with Avenue S. that yield South.
Someone else tested that it worked.
Perhaps, the reason for this is that we were testing a single letter. More concern with the directional letters. Not combinations of letters like A.T.T.


Correct.
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Thu Jan 31, 2013 12:39 am

txemt wrote:
I've tested the period, too and didn't get a direction. I'm waiting for my next test results to hit the client to find something else out about the period. I did have quotes around a lower case "s" and it looked really funny (had a few URs about it, too).


Agree that double quotes look weird. Did you try something like [Ave S.]? For me, it came up as [Ave South].
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Thu Jan 31, 2013 12:33 am

txemt wrote:
orbitc wrote:I agree with Alan. Few of us tested these with few different combination. The Best option, IMO, should be either with single quotes or double quotes.


I'd have to disagree. How many street signs or exit ramps do you see that have a "" or '' in them? I understand that we're trying to get Waze to say the actual letter instead of a direction, so I would advocate more of the period.


What I'm saying is that the period was tested, and with only one letter, the period still sounded out as the direction and not the letter.
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Thu Jan 31, 2013 12:22 am

AlanOfTheBerg wrote:
txemt wrote:
jemay wrote:But putting a period implies there is more to the letter (representing a word).


Huh?

A period means either the end of a sentence or that it is an abbreviation. One could argue E. is an abbreviation for East, but it cannot be an abbreviation for "ee" and therefore the dot method, I feel, should not be used.


When tested, S. is pronounced as "South".
Last edited by Wajo357 on Thu Jan 31, 2013 12:39 am, edited 1 time in total.
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Tue Jan 29, 2013 4:29 pm

jasonh300 wrote:
Wajo357 wrote:3) Would that screw up navigation search if someone just enters in 1304 Ave S, Brooklyn NY, since it is now only Ave "S"? Would adding an alternate name of Ave S help?


What you name a street currently has no bearing on address searches. The street names we assign in WME are only for TTS and display purposes.


Perfect. I'm just trying to make sure all basis are covered before we screw anything up :)
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Tue Jan 29, 2013 3:36 pm

GizmoGuy411 wrote:Single letters to be pronounced as letters when a capitalized letter is surrounded by double quotes was the suggestion made to Waze back in October 2012.

When I have not retested all the permutations, it looks like from those who have tested the letters, N, E, S, and W, that Waze has changed functionality so that upper or lower case letters surrounded by single or double quotes will now say the letter and not the cardinal direction.

I'll amend the list once I can test more permutations.


Sounds good. So now that your tests are done, here come the questions concerning Brooklyn, NY:

1) Should we change Ave N, E, W, S?
2) If yes, would you prefer single or double quotes?
3) Would that screw up navigation search if someone just enters in 1304 Ave S, Brooklyn NY, since it is now only Ave "S"? Would adding an alternate name of Ave S help?
4) Should we just blanket all of the letters in Brooklyn with the quotes specified in 2?
5) I assume we should lock the roads with the changes, correct?

Thanks!

Sincerely,
Joey
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Mon Jan 28, 2013 5:07 pm

CBenson wrote:
Wajo357 wrote:When waze says the "ayybee" it sounds like it is slurring the two letters together instead of saying simply "70 ayy bee". My question was if there was a way to write it such that voice TTS doesn't slur it.

Not that I know of. But I kind of like waze being quick about it.

orbitc wrote:Maybe, it's changed?

Maybe. I'll try it again.


Please do. Because we need you ready for a crazy toll behavior OrbitC and I are working on.
Hint - single penalty for multiple consecutive toll segments may be wrong! I'll be starting a new thread as we do more testing soon...
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Mon Jan 28, 2013 2:33 pm

CBenson wrote:This exit has been named "Exits 13A-B-C: US-301 / MD-3 Richmond / Crofton" to match the BGS for quite some time. I drive through it regularly. TTS says: "Exits thirteen ayybeesea...youess threeohone...emdee three Richmond...Crofton." It sounds fine to me. I've never seen or heard a complaint.


When waze says the "ayybee" it sounds like it is slurring the two letters together instead of saying simply "70 ayy bee". My question was if there was a way to write it such that voice TTS doesn't slur it.
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

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

Postby Wajo357 » Mon Jan 28, 2013 2:31 pm

CBenson wrote:
Wajo357 wrote:1) Most avenues in Brooklyn NY are letters, like Ave M . However, Waze reads Ave N, E, W, and S as the direction, not the letter. A few of us have tested that encapsulating the letters with either single or double quotes gets Waze to say the letter and not the direction. So what do you guys recommend? Single quotes? double quotes? All avenues? Just problematic avenues? Add alternate name with no quotes?

East/West streets in downtown Washington DC are also letters, like "K St." In the past, encapsulating the letters with either single or double quotes would not get waze to say the letter and not the direction (only lower case encapsulated in single quotes gave the letter). Maybe things have changed since I last tried this or maybe it matters whether the single letter starts the name.


This was tested over the weekend, and seems to be a new functionality. You may want to retest it for yourself.
Image
Area Manager: New York / New Jersey (in USA)
Wajo357
 
Posts: 363
Joined: Thu Dec 08, 2011 12:16 pm
Has thanked: 4 times
Been thanked: 7 times

PreviousNext

Return to United States

Who is online

Users browsing this forum: No registered users