Personally if it isn't confusing, or obviously wrong, I don't bother.dsfargeg wrote:So driving around, i've found 3 more TTS problems. It seems like this could get out of hand easily. Do we have a "good enough" threshold, or do we want to report everything?
Sent from my XT830C using Tapatalk
First of all you are looking at an outdated page which no longer applies to the USA. For the USA please see guidance on the Abbreviations and acronyms/USA page (item #4).bummerdude69 wrote:https://wiki.waze.com/wiki/Abbreviations_and_acronymsDoes this apply to all abbreviations? If so, should that be noted on the page?When 'N', 'S', 'E', or 'W' should NOT be pronounced as compass directions, enclose the letter in single quotes.
Should it be named with VA in the primary name, or would it be more appropriate to use the full Veterans Affairs, and put VA as an alt name.bummerdude69 wrote:Thanks, I missed the difference between the two pages.PesachZ wrote: First of all you are looking at an outdated page ...
Second this does NOT apply to all abbreviations, it is specific to cardinal directions.
Third is there a specific use case, or abbreviation which is being an issue for you that you are trying to override?
VA in "Southern Arizona VA Medical Center" is being pronounced as Virginia rather than just VA ("vee" "aa").
The '.' does not work, it is exclusively for cardinals. For most others we just try not to have abbreviations which cause conflicts with real names, that's why we like to be informed when those conflicts are discovered. This allows to reevaluate whether the abbreviation should be modified to avoid conflicts. We can generally find ways around it when necessary, but there is no one size fits all solution.bummerdude69 wrote: Trying not to highjack this thread too much, so I'll chase down those other options in other places.
But my main question (confusion?) still stands. What is the best way to avoid the TTS Abbreviation translation? Using '.' for the cardinals works, but what about for everything else? Or is there not, just one best way? [Which, looking at the Big List, seems more likely]
I fixed the spelling, but can't say I hear the difference of what the UR reporter is complaining of in the al sound pronounced.t0cableguy wrote:https://www.waze.com/editor/?env=usa&lo ... st=4639452
ALT SR-A1A
The ur explains it all. I am trying to find out if they are using Jane, but since Sam has been retired i cannot imagine they are using anything else.
Also Alt - Alternate is spelled wrong in the wiki sheet for US abbreviations.
The fact that the same phrase (if it is truly the same phrase, eg same turn prompt (right/left) to the same segment) is changing over time may indicate that the vendor is tweaking the tts engine and trying to fix the bug. Who knows?TheLastTaterTot wrote:Hi there,
I've been having on-and-off issues with Jane oddly adding an unknown [long] ē sound at the end of "Gano" of "Gano St".
First question – is this a context specific rule that can be permanently fixed? I personally can't think of any words that end in an 'o' and is followed by a long 'e' sound. Second, why is this issue inconsistent from month to month? It seems to disappear only to reappear several weeks later? Currently, she does not produce the ē after Gano, but she did just a week ago.
To be specific,
The incorrect pronunciation by Jane just a week ago is: gone-no-ee or gän-nō-ē
In the past, she has also incorrectly pronounced it as: gan-nō
As of the time of this post, she is incorrectly pronouncing it as: gän-nō
The correct pronunciation is: gane-no or gā-nō
PL to example "Gano St" segment: https://www.waze.com/editor/?env=usa&lo ... s=43506010
any fix on our end will have to be specific to an individual spelling of a word, and repeating for each similar word to ensure it works properly. Our vendor can fix the logic, which it seems they may be working on, which would then fix all such similar words.TheLastTaterTot wrote:is it possible to get a permanent fix for this pronunciation rule? Or can anyone think of a word that ends with "no" that produces any other sound other than nō?PesachZ wrote: The fact that the same phrase (if it is truly the same phrase, eg same turn prompt (right/left) to the same segment) is changing over time may indicate that the vendor is tweaking the tts engine and trying to fix the bug. Who knows?
The reason TTS is failing here is because the road is not named correctly according to our standards.TheChrisK wrote:It is consistent to a degree. The L, S and R are always present, followed by a dash (-) then the county number in which the road exists in, followed by a letter designation. The county numbers are alphabetical so Adams county is '1' (not 01), the above example is Douglas County (28)... and so on. There are only 93 counties in Nebraska so no three numerical digit L, S or R roads exist.qwaletee wrote:Is this consistent across all L-nnX / S-nnX / R-nnX roads? Or have you found a single exception? The state wiki page claims that three formats are supported in TTS, but seems to indicate that there is always a 3-digit number, not 2-digits and a letter. If that's the format, then L-28B violates it.TheChrisK wrote:Hello!
Nebraska has three auxilliary state highway types, Links (L-##X), Spurs (S-##X) and Recreation Roads (R-##X). Recently I noticed that Nebraska Link 28B (L-28B) is translated by Jane as "EL TWO EIGHT BEE" instead of "NEBRASKA LINK TWENTY-EIGHT BEE"
I imagine the spurs and rec roads are being translated the in the same fashion but I have not navigated to one recently to know for sure.
PL: https://www.waze.com/editor/?env=usa&lo ... s=76193133
Let me know if you need more information.
For example:
Recreational Roads are typically unsigned but listed in FC diagrams. Here is a link to a list of Spurs, Links and Rec Roads for more info.
- L-7E
- S-55X
- R-27B
L-28B is the only highway that I typically travel on in the state. It is a freeway for its entire length in the outskirts of Omaha. I could definitely field scout another that is close by to check for consistency.
Thank you for the response qwaletee!
It's common for BGS to be placed before an actual Exit, however our guidance is still to make the fork at the actual legal divergence. This is because of how it affects prompt timing. Once you pass the junction you see the next prompt, which in this case would be 175 meters before you have to choose a lane. That means if as you approach the actual gore, you glance at your device to see which way you are supposed to go, you'll already be seeing the next prompt displayed.TheChrisK wrote:Thank you for the information PZ, we will make that change here shortly. I think the reasoning behind the location of the wayfinder was the location of the of the exit sign. I will discuss that with my SM.PesachZ wrote:To fix the issue here you need to replace the missing slash (/) between the two spaces in the name before the word "to".
"L-28B / to US-6 / Omaha via W Dodge Rd"
The state page does misrepresent the names a bit, the correct format is supported and listed in the USA abbreviations list. It should be (and will soon be fixed) on the state wiki as "L-##X"
PS that wayfinder is placed way too early on the fwy. It should be placed where the solid line for the fork starts (approximately 175 m [575 ft] south of where it is now) as per wiki guidance.
I will make the appropriate changes in the NE Wiki as well. I didn't notice that until you pointed it out.
Thanks again!
Follow the guidance for Exit ramp geometry and complexity. (This is an exit, only here both sides are exits)TheChrisK wrote:
What you are saying makes perfect sense. Is there specific guidance noted in the wiki somewhere for the wayfinder distance? I am not seeing it here.
Re: Test of Text-to-Speech (TTS) Abbreviations in Waze Clien