Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
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 CurtisNewton74
jm6087 wrote:
CurtisNewton74 wrote:Places with multiple entry points are also suggested for turning from area to point, which doesn't work.
--> Error message from WME that place has to many entry points when saving.
So any place with multiple entry points should not be suggested for conversion.
Why not? If a place is supposed to be a point and not an area, the fact that it currently has multiple entry points does not negate that fact.
You are right, the place should still be a point and not an area, you just can't edit that in combination with multiple entries. My very personal opinion here is that I don't want to see proposals that I cannot edit anyway (at least not without removing the multiple entries, and assuming the entries are correct and usefull, that might not be the best idea)
CurtisNewton74
Posts: 61
Has thanked: 22 times
Been thanked: 18 times
Send a message

Post by czar740
Good Night Wazers:

The current script Validator no longer works in the WME editor

:( :( :( :( :( :( :(
czar740
Country Manager
Country Manager
Posts: 922
Has thanked: 1087 times
Been thanked: 794 times
Send a message
Attachments

Post by czar740
I miss the Validator, we need it, please. :(
czar740
Country Manager
Country Manager
Posts: 922
Has thanked: 1087 times
Been thanked: 794 times
Send a message

Post by czar740
ldriveskier wrote:Thanks to markr4468 for detailed instructions on installation of dbcm's fix:

1) Go To Tampermonkey Dashboard
2) Click Utilities Tab
3) Paste http://dbcm.github.io/waze/valfix/valfix.js in the URL Box
4) Click Import
5) Click Install
6) Click Installed Userscripts Tab
7) Click On Waze Map Editor - Validator Fix
8) Click On Settings
9) Set Position to #1
10) Hard Refresh in WME
11) Enable Any Localization Files you have.

(Note: If you disabled Validator, don't forget to re-enable it!)

Thank you,
Now if to edit again without fear jejejejeje

:D :D :D :D :D :D
czar740
Country Manager
Country Manager
Posts: 922
Has thanked: 1087 times
Been thanked: 794 times
Send a message

Post by Daemonia
Hi,

I just noticed that rules are customized for some countries.

The built-in rule "Incorrect Freeway name" (#160) should be reviewed for Belgium.
As written on https://wiki.waze.com/wiki/Benelux_Freeway, "E42 - A15" is a valid name for this freeway.

Thanks for this good work ! :)
Daemonia
Posts: 111
Has thanked: 10 times
Been thanked: 5 times
Send a message
FR/EN - Région Huy-Waremme - Belgique
[img]https:///mSz3t[/img]

Post by DanCocoDotCom
I had to disable Validator for now because of the unconfirmed roads issue. I hope it's an easy fix.
DanCocoDotCom
Posts: 44
Has thanked: 12 times
Been thanked: 1 time
Send a message

Post by DanCocoDotCom
This would probably break every other script installed but would it be possible to create a script that takes the separate city variable and presents it to validator in the "legacy" method to create a workaround fix? Not sure if it would be possible to get the script to only do this for validator without being able to see validator's code.
DanCocoDotCom
Posts: 44
Has thanked: 12 times
Been thanked: 1 time
Send a message

Post by Daniel_Traian
It might have been previously discussed around here but, a bigger coverage area for the Validator would be highly desirable. For example, those of us who have large editable areas could check the whole area in just one one button push, without having to move the map around (the validator should do it instead).
Yes, that might take a while to scan and it could generate a huge report, but at least one would not have to regularly check if the current validation operation is done or not.
Thanks for the great tool!

PS: To ameliorate the situation, right I'm setting the zoom level to 75% while validating.
Daniel_Traian
Area Manager
Area Manager
Posts: 29
Has thanked: 2 times
Been thanked: 1 time
Send a message
[img]https:///mgUUB[/img][img]https:///JT4YvU[/img]

Post by Daniel_Traian
A feature that I, as an editor with quite a big editable area at my disposal, would greatly appreciate is the possibility to check an area as big as possible, maybe even my whole editable area, with as little effort as possible.
Right now, when I want to check my area (a rectangle), I set up a few tabs with WME, showing adjacent areas from the lower side of the rectangle. The zoom of the browser is set at 66% and toolbars and such are deactivated. Then, I slowly move upwards, until I reach the top edge of my editable area.
Problem is that this whole check - move map - check process can be very time consuming and repetitive.
So, if there would be a better way to simplify things (either to check the whole editable area at once, or check around the visible area too) I'd be very happy. Note that a huge report wouldn't scare me at all (it would actually be way smaller than the size of the combined reports for a given area).
Wish you a great day!
Daniel_Traian
Area Manager
Area Manager
Posts: 29
Has thanked: 2 times
Been thanked: 1 time
Send a message
[img]https:///mgUUB[/img][img]https:///JT4YvU[/img]

Post by Daniel_Traian
I've noticed that this script reports a lot of false positive Unconfirmed road, both in the scan reports and directly on the map (if this layer is active). For example this and this (and many other segments) were reported as unconfirmed although clearly this is not the case.

Am I missing something or something's really wrong?
Daniel_Traian
Area Manager
Area Manager
Posts: 29
Has thanked: 2 times
Been thanked: 1 time
Send a message
[img]https:///mgUUB[/img][img]https:///JT4YvU[/img]