Fabianotkd wrote:Too short U-turn connector (slow) (#79)
I noticed that in this case Validator doesn't report both segment.
https://www.waze.com/it/editor/?zoom=8& ... =243691492
Validator reports #79 at H-shaped intersections with no left/right connections (i.e. when just 3 segments connected to a single node). The permalink you provided is not such an intersection and the U-turn might be disabled deliberately, so Validator does not report it.
The U-turn nearby is reported: permalink
lg1992 wrote:I want to define a custom rule to mark segments with undefined elevation.
Sorry, I just noticed the elevation is converted into a number, so try to match undefined elevations with NaN (not a number). It will be fixed in the next version.
You can add D at the beginning of RegExp (D/NaN/) and then check a JS console for debug log.
lg1992 wrote:my custom rule defeated other rules
It's not a bug. Custom checks have higher priority than the notes/warnings/errors. IMO if you're looking for something special it's more important than the rest of Validator checks.
lg1992 wrote:BTW, it would be nice to allow naming the custom checks.
Once your custom check is ready, you can click Settings->About->Wizard button and generate your own localization pack (specify EN language to skip translations).
At the moment checks #130-134 are reserved for the custom checks, so you should add the following lines into the package:
- Code: Select all
,
"130.enabled": true, // to enable check #130
"130.severity": "warning", // to set the severity
"130.title": "Undefined elevation", // check name
"130.problem": "The segment has undefined elevation", // optional description
"130.problemLink": "http://...", // optional link
"130.solution": "Set the elevation to Ground", // optional solution
"130.solutionLink": "http://...", // optional link to detailed instructions
"130.params": {
"template": "${elevation}", // paste your template here
"regexp": "NaN", // paste your RegExp here
},
The localization package is a ready to install Greasemonkey/Tampermonkey script, so you just copy the whole package into the clipboard, then click Tampermonkey->Add a new script and paste your package there. Save, reload WME. Here is the post with the detailed instructions: forum post
You can also share your localization package with other editors. The package might be hosted on userscripts.org, so once you update the package, the rest of the editors will get the update as well.
It might sound a bit complicated, so do not hesitate if you have any questions!
Once you provide me a permalink to a segment with undefined elevation, the check will be implemented.
Validator never changes segment's properties, but I heard some other scripts do "mask" null elevations.