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 taco909
PesachZ wrote:Such intricate edits deserve to locked to prevent 'fixing'. If I ever (and it's rare) make an intentionally overlapping segment, I all my RC to lock it at rank 6.
Good point, though on something like that I would generally only lock it to my level and test operation on the map and on the road... and every now and then I'll encounter an L3 where I think "An L3 did this?"

I do think it would be helpful if L3 and higher editors were allowed to lock their work at higher levels to help reduce the workload of the local champs.
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich

Post by taco909
PesachZ wrote:
roadtechie wrote:Maybe this has been brought up before. But, I would love for validator to flag any cameras that are in states that do not allow cameras. I live in Indiana which does not allow any cameras at all in the state except for toll booth enforcement. If Validator would flag all of the cameras it would make my daily deletion of cameras a LOT easier!
Are the cameras you are deleting being confirmed by other editors, or just reported?

Besides if all cameras are illegal isn't the presence of the icons enough of a 'flag', unless you are looking for a list of cameras in a report.
Like me, probably tired of seeing the clutter on the map, but not wanting to turn the layer off because inevitably some well-meaning and misinformed editor WILL approve the things.

Supposedly, they drop from the map after 30 days, but I've seen some just outside of my editable area hang around longer than that, OR they are being reported regularly.

And speed cameras are not legal in California... yet to look at the map you'd think we were on "Persons of Interest"
Illegal camera types should not even appear in the app through the localization.

Thankfully, the combination of URO+ allowing cameras to display at Zoom-1 and 2 and the invalid mass camera deleter script makes life easier.
https://greasyfork.org/scripts/2377-wme ... ass-eraser
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich

Post by taco909
True true... easy to forget that this isn't the Toolbox thread ;)
The two work together so well for the most part.
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich

Post by taco909
SuperDave1426 wrote:
Taco909 wrote:Thankfully, the combination of URO+ allowing cameras to display at Zoom-1 and 2 and the invalid mass camera deleter script makes life easier.
https://greasyfork.org/scripts/2377-wme ... ass-eraser
How do you set URO+ to adjust how far out cameras show up? I can't seem to find a setting for that...
There's no setting... it does it automatically.

It is a bit "iffy" in that if you have your browser zoom level set to allow for a larger editor view, it won't reliably display at the wider angles.
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich

Post by taco909
Twister-UK wrote:
Taco909 wrote:
SuperDave1426 wrote: How do you set URO+ to adjust how far out cameras show up? I can't seem to find a setting for that...
There's no setting... it does it automatically.
Something might be doing it automatically, but it isn't URO+...
I started getting cams wider than Zoom-3 when I installed it.
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich

Post by taco909
I only get them at 0 if they were already visible at 3 and I zoom out. If I pan around the map, new ones don't appear at 0.

I'll see if I can find the thread where I complained about them only being visible at 3+ and the suggestion.
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich

Post by taco909
Confirmed... it's JNF, but not at "0"... just "1" or higher.
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich

Post by taco909
Looks like the latest Toolbox may have broken Validator.
I loaded Firefox and decided to run a report to pick up the Revcons that we couldn't see the last couple of weeks.
It began the auto-scan but only got through one or two tile sets before locking up.

I moved to Chrome and it scanned fine at zoom-0, then I realized that I had not forced the Toolbox update.
After updating, I ran another report and the same thing happened.
I've tried this all the way down to Zoom-4 and it'll scan the first tile set, then lock up on the 2nd set.

When running in normal mode, it of course does not report the Toolbox Revcon error... which is why I wanted to run the report. I like it picking up Toolbox errors.

Strange because another local editor is running without a problem, but mine consistently "broke" after the Toolbox update.
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich

Post by taco909
mikenit wrote:then staff is run the search/replace "service road" by street type. So, the change may be transparent, without need to search, manually edit, and change this type in WME.
Until the URs start coming in because roads that are currently penalized will become routable.

Most "service roads" that I have encountered should be classified as PLR, Private, Walking Trail, Dirt/4x4... or not even mapped. They are generally behind locked gates and never available for the public to drive on.
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich

Post by taco909
That is a Chrome memory management problem, Validator just makes it happen more quickly.
Even without Validator running, constantly opening and closing new tabs (like from URO+ links) would cause Chrome to slow to a crawl and crash after working 15 or 20 URs.

On detecting Revcons, it used to, but has not yet been updated to reflect the new changes in WME.
Toolbox does now pick up on them so Validator is redundant, however, Validator does NOT report Revcons identified by Toolbox in the report the way it used to, so they have to be manually searched for.
taco909
Map Editor - Level 4
Map Editor - Level 4
Posts: 2230
Has thanked: 716 times
Been thanked: 646 times
-- Rich