Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.
Post by xanderb
Would it be possible to add the ability to use altState in Validator? Editor Dchary2418 pointed out that changing the Primary state does not change the state assigned to the alternate street. I wanted to add a check to my localization script to check that the altState matches the primary state, but it doesn't look like it is an option yet. Currently, the only way we can tell the issue exists is to show it in WMECH, but unless you know to look when a segment is on the screen, you won't know the issue is there.

Here is the way to recreate the issue in WME:

You normally need to be around a state border so that there are two states listed in the dropdown. For this example I am in New Albany, Indiana. Where I create this segment, Kentucky is the default state that populates, so I leave it as that.

http://imgur.com/iFYr3ca.jpg

Next save the name of the street and give it an alternate name and same city; there is no choice for state on alternate.



Realize you had the wrong state and change it on the primary name.



Now, WMECH shows there is still a segment with New Albany, Kentucky out there and highlights the new segment with a dashed line.

xanderb
Global Champ Mentor
Global Champ Mentor
Posts: 942
Has thanked: 313 times
Been thanked: 323 times
Last edited by xanderb on Thu Mar 19, 2015 6:04 pm, edited 1 time in total.

Post by xanderb
ispyisail wrote:My rule is getting so long that I might need to create a rule generator

I wonder what the max length is?
If there is a max, it is very long. I use one that has every Incorporated City name in Kentucky.
xanderb
Global Champ Mentor
Global Champ Mentor
Posts: 942
Has thanked: 313 times
Been thanked: 323 times

Post by xanderb
That isn't a validator issue. WME doesn't have a layer number to include the experimental roads yet. Just turn the old Roads layer on before running the report.
xanderb
Global Champ Mentor
Global Champ Mentor
Posts: 942
Has thanked: 313 times
Been thanked: 323 times

Post by xanderb
LeighGr wrote:I'm busy creating a WMEV localization pack for South Africa, but am bashing my head against a wall with some weird errors. The following code works fine for mH segments named R100 to R512, and then again from R516 onwards, but R513, R514 and R515 all get flagged as incorrect. WHY?????
I was taking a look at this and the typerank 13: at the beginning of the code is still catching the 13: in the street area for R513 and R413, etc. in PesachZ's code. Here is debug:

1. Expand template: ${typeRank}:${street}:${direction} -> 13:R513:3
2. Match RegExp: /(13):(?!R[0-9]{3} [NESW]:(1|2) ?|(R[0-9]{3}:(3))$)/ -> ["13:","13",null,null,null]
=> REPORT the segment as #129 'User-defined custom check (blue)'

1. Expand template: ${typeRank}:${street}:${direction} -> 13:R413:3
2. Match RegExp: /(13):(?!R[0-9]{3} [NESW]:(1|2) ?|(R[0-9]{3}:(3))$)/ -> ["13:","13",null,null,null]
=> REPORT the segment as #129 'User-defined custom check (blue)'

What I did to work around that is use a # as the initial separator in the template and regex. See if this works better for you.

Code: Select all

Custom template: ${typeRank}#${street}:${direction}
Custom RegExp: /13#(?!((R[1-9]\d\d):3|(R[1-9]\d\d [SNEW]):[12]))/
xanderb
Global Champ Mentor
Global Champ Mentor
Posts: 942
Has thanked: 313 times
Been thanked: 323 times

Post by xanderb
LeighGr wrote: PesachZ's code is in the middle of the reply, not the one at the bottom, which is exactly the same as my screwed one. It does work, and worked even better when I fixed the MH and FW custom checks with the same changes.
My mistake, I grabbed the wrong one then.
xanderb
Global Champ Mentor
Global Champ Mentor
Posts: 942
Has thanked: 313 times
Been thanked: 323 times

Post by xanderb
I would like to make a custom check that looks for missing speed limits on freeway segments. Is there a ${speed} available or coming to use?
xanderb
Global Champ Mentor
Global Champ Mentor
Posts: 942
Has thanked: 313 times
Been thanked: 323 times

Post by whatnt
Validator used to work with WME Color Highlights by noting all of the "Recently Edited" segments in its report. It doesn't seem to work anymore.

Validator 1.1.15
whatnt
Master Raider
Master Raider
Posts: 824
Has thanked: 265 times
Been thanked: 126 times

Post by whatnt
ispyisail wrote:anybody else having problem with validator not working as expected?
Yes. "Recently Edited...days" that are selected with HIghlighter are no longer listed in Validator reports. This has been broken for a while.
whatnt
Master Raider
Master Raider
Posts: 824
Has thanked: 265 times
Been thanked: 126 times

Post by wrocco
Hi everyone. Try using English version. The only pop-up I get is from WME Junction Node Fixer, so I disabled it.

Try this out.
wrocco
Waze Local Champs
Waze Local Champs
Posts: 2147
Has thanked: 183 times
Been thanked: 355 times
https://s.waze.tools/c5s.pnghttps://s.waze.tools/s0600.pnghttps://storage.googleapis.com/wazeoped ... anager.png https://storage.googleapis.com/wazeoped ... a-New1.gif

Area Manager Región de Arica y Parinacota, Chile
Android Beta Tester - Local Champ - Social Media Community Manager
Wilfred Rocco

Visita nuestros sitios oficiales:
Website - Twitter - Facebook - Instagram

Post by Wildour
Excellent tool, personally, I think the Magic still does not surpass the validator. We hope you continue to improve the validator, adding new features. It is my favorite. Thank you.
Wildour
Map Raider
Map Raider
Posts: 125
Has thanked: 203 times
Been thanked: 90 times