Switch to full style
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.

Forum rules

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

DO NOT START a new thread unless it is about a new idea. Keep discussion of existing tools within the main thread for that tool.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.
Post a reply

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Mon Jan 12, 2015 3:41 am

taco909 wrote:Keep in mind that not everything on the list needs to be fixed... depending on how you have Highlighter and Toolbox set.
I generally disable one-way in Highlighter and leave Toll checked, because 90% of the time, if a segment shows up as toll AND I have editing rights to it, it is not a valid flag.

When you say Highlighter, do you actually mean WME Highlighter or the Validator? Since both of them do highlights, correct?

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Mon Jan 12, 2015 5:41 am

taco909 wrote:WME Highlighter.
Validator, AFAIK, does not report on unknown direction

Well, I've never had the WME Highlighter plugin installed on either one of my laptops, and, until sometime last week, the list included "Unknown direction on road/street" (or something like that) section of segments in the list produced by Validator scan. I run into some roads that haven't been touched since they've been imported in 2009 and don't have any direction set yet, and it doesn't highlight them anymore. I have to look for them manually.

Maybe the fix for my problem would be to install WME highlighter and allow Validator to "include external highlights" or use the section for custom searches... I'll give those a shot.

EDIT: VME Validator still highlights the segments and gives you the description when you hover over them or select them, it just doesn't include them in the scan results as it used to, so you have to pan and zoom for them manually.

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Mon Jan 12, 2015 7:04 am

So after a bit of scanning around different areas, it looks like it highlights some of the segments with unknown driving directions, but only if the road has been set to street or above. Not the segments that have been set to dirt roads, private roads, etc during the initial import from Google maps. I am able to get them selected using Validator "custom check" script ${direction} /0/ or !/1/ if I want it to highlight and list all but two way roads (good thing to review roads that haven't been touched at all) since some of the imported one way roads are really two way.
Hope that helps whoever is trying to accomplish this too.

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Tue Jan 20, 2015 3:58 am

no problems or complaints to report, just wanted to chime in and thank you guys for an awesome script. It's a great and invaluable tool. 8-)

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Sun Feb 22, 2015 11:18 pm

SuperDave1426 wrote: Does anyone know what regexp value needs to be used with ${typeRank} to select a parking lot road type? 'Cause I can't seem to find it. :-)


Just did a quick search of this thread for "type plr" and came up with this post. ;)

Hope this helps.


qwaletee wrote:Just FYI, here is the list of codes for each ${type}:

1 Street
2 Primary Street
3 FW
4 Ramp
5 Walking trail
6 MH
7 mH
8 Dirt
9 Unassigned?
10 Boardwalk
11-15 Unassigned?
16 Stairway
17 Private
18 Railroad
19 Runway
20 PLR
21 Service rd

Putting it at the end (the $ says there can't be anything after it, so 1-Street is not confused with 10-Boardwalk or 16-Stairway, etc.):

template: ${street}:${length}:${type}
expression: /^:[0-9]{3,}:[1-46-8]$/

This says street name is blank (nothing between start and first colon), length has at least 3 digits ([0-9] is any digit, {3,} means 3 or or of that), and [1-46-8] means any single digit except 0, 5, or 9, which most of the common types that you would expect to have a name, except that ramp may not have a name. Railroad should probably also be included, in which case:

expression for nameless >=100m of types expecting a name (which EXCLUDES ramps): /^:[0-9]{3,}:([1-36-8]|18)$/

Excuse the RegEx tutorial :)

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Mon Feb 23, 2015 12:57 am

maybe pm qwaletee?

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Wed Feb 25, 2015 9:30 pm

ispyisail wrote:Do we need a wiki page for validator custom searches

Its getting hard to find stuff in this thread

Yes we do! +1

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Thu Feb 26, 2015 6:46 pm

Man, you make me feel like I'm kindergartner in here.. :-D

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Sat Feb 28, 2015 9:33 am

crazycaveman wrote:If you have the experimental road layer enabled and the legacy roads disabled, no roads will be displayed because the experimental layer does not yet get enabled through a permalink. Might be best to enable the roads layer before running a scan so you don't have to enable them with every permalink to follow

Good point. Thank you.

I've sent a few permalinks that way and they arrived with both of them disabled. Took me a couple of tires to figure out what's wrong.

Re: [Script] WME Validator 1.1.6 / 06.01.2015

Sat Feb 07, 2015 3:50 pm

Not creating reports in w/ Firefox 35.0.1 Win 7


Now it's working. :roll: User option issue.
Post a reply