waze.com

AlanOfTheBerg wrote:

PesachZ wrote:

AlanOfTheBerg wrote:Sheesh, I can't even get Validator to load at all. The only line in the console on load is "WME Validator v1.1.8: login AlanOfTheBerg". Win7/Chrome 46.0.2490.71 m. Ideas?

Are you in WME Beta? Validator is broken in the latest beta.

Nope, I wish it was that simple. I knew that it wasn't working in beta.

Are you using a localization package?

Sent from Android using Tapatalk

whatnt wrote:v 1.1.10 is flagging "Expy" as an incorrectly abbreviated street name.

This is for the US, Expwy is our recommended abbreviation for Expressway

whatnt wrote:Another apparent incorrect flagging: "Int'l", though Jane TTS does say "international".

This was my mistake, I will send a message to the author with a fix for this.
Thanks for bringing it up

the regex for rule #171 in the US will have to be updated to this to fix it.

Code: Select all

"regexp": "/((?!(\\bPhila|\\bPenna|.(\\bWash|\\bCmdr|\\bProf|\\bPres)|..(Adm|\\bSte|\\bCpl|\\bMaj|\\bSgt|\\bRe[vc]|\\bR\\.R|\\bGov|\\bGen|\\bHon|\\bCpl)|...(\\bSt|\\b[JSD]r|\\bLt|\\bFt)|...(#| )[NEWSR])).{5}\\.|(?!(hila|enna|(\\bWash|\\bCmdr|\\bProf|\\bPres)|.(\\bAdm|\\bSte|\\bCpl|\\bMaj|\\bSgt|\\bRe[vc]|\\bR\\.R|\\bGov|\\bGen|\\bHon|\\bCpl)|..(\\bSt|\\b[JSD]r|\\bLt|\\bFt)|..(#| )[NEWSR])).{4}\\.|(?!(ila|nna|(ash|mdr|rof|res)|(\\bAdm|\\bSte|\\bCpl|\\bMaj|\\bSgt|\\bRe[vc]|\\bR\\.R|\\bGov|\\bGen|\\bHon|\\bCpl)|.(\\bSt|\\b[JSD]r|\\bLt|\\bFt)|.(#| )[NEWSR])).{3}\\.|(?!(la|na|(sh|dr|of|es)|(dm|te|pl|aj|gt|e[vc]|\\.R|ov|en|on|pl)|(\\bSt|\\b[JSD]r|\\bLt|\\bFt)|(#| )[NEWSR])).{2}\\.|(#|^)[^NEWSR]?\\.)|(((?!\\b(D|O)).|#|^)\'(?![sl]\\b)|(?!\\b(In|Na)t).{3}\'l|(#|^).{0,2}\'l)|(Dr|St)\\.(#|$)|,|;|\\\\|((?!\\.( |#|$|R))\\..|(?!\\.( .|#.|$|R\\.))\\..{2}|\\.R(#|$|\\.R))|[Ee]x(p|w)y|Tunl|Long Is\\b|Brg/",

whatnt wrote:

Fredo-p wrote:

whatnt wrote:Does this mean we need to change the tens of thousands of segments in the area that have "Expy".

And which of the many abbreviations charts are we supposed to use?

That's something your SM/CM can answer.

I have. They think "Expy" is acceptable. But PesachZ's reply suggests otherwise, as do the thousands of flags and highlighted segments from Validator.

By the way, this is a new flag from Validator since the latest update. Expy wasn't flagged prior.

The list in the USA abbreviations wiki is the definitive list. It is still being updated, and expwy will be added to it shortly. Once complete that will the all inclusive source for recommended abbreviations.

As to changing them, its not urgent but something you do as you work on other things.

Sent from Android using Tapatalk

Fredo-p wrote:

Glodenox wrote:Would it be possible to add the recently added speed limits and tunnel indications to the custom template list? I propose the names ${speedAB}, ${speedBA} and ${tunnel}.

Let's say, hypothetically, roads that haven't had speed limits entered after XX time frame are entered automatically by waze_bot via third party source. Will TB be able to pick that up if there is no edit name attached to it?

This is the Validator thread, but to answer your question based on previous behaviors:
After an import is done any speeds entered by editors should display as "verified". Scripts will most likely be able to detect the " verified " flag.

Sent from Android using Tapatalk

kentsmith9 wrote:

PesachZ wrote:

whatnt wrote:v 1.1.10 is flagging "Expy" as an incorrectly abbreviated street name.

This is for the US, Expwy is our recommended abbreviation for Expressway

After 3+ years of it being an accepted abbreviation across the US, why did it change to unaccepted?

It wasn't my decision, and I don't want to speak for others, or put words in their mouths. What follows is my assumption of the issue.
"Expy" was included as the road names on the basemap, and was grandfathered into acceptance for lack of an initiative to use better naming.
With the restructuring of the TTS engine, a concerted effort was led by several champs to generate a comprehensive list of recommended abbreviations which are a better for a navigation app.
They relied heavily on several official sources, primarily the MUTCD.

The MUTCD lists "Expwy" as the exclusive acceptable abbreviation for expressway.

I believe most BGS where expressway is abbreviated it appears as "Expwy", and not "Expy".

Our goals are to help wazers match instructions as easily as possible with what they see around them. That said if the BGS does not use "Expy", and the MUTCD recommends against it, there's no reason we should be using it.

Now if the BGS in your area do actually use Expy as an abbreviation then that may be a factor worth reconsidering. If this is the case in a large area please bring it up so we can evaluate it.

Sent from Android using Tapatalk

I want to add that although Expy is not recommended, it will still work with our current TTS engine, so there is no urgent rush to fix them all immediately. However it should be something you fix when you see it.

Sent from Android using Tapatalk

The wiki was supposed to be updated to point to the US page https://wiki.waze.com/wiki/Abbreviations_and_acronyms/USA#Recommended_abbreviations

Sent from Android using Tapatalk

kentsmith9 wrote:OK. That is the page I did find the working text, so is there already a thread to propose the global page change to the current US page?

No the global page is global, this is the USA version so it meant stay local. However validator should be updated so that in the US I shows the link to the USA version of the page.

Sent from Android using Tapatalk

The comma is causing the flag, "&" is not checked for.

I'm also included to not worry about naming check #171 for a RR, they will never be used for TTS (if all goes as planned).

FYI You can see the regex by looking at available checks in validator settings.

Sent from Android using Tapatalk