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 0.9.4 (BETA) / 30.03.2014

Fri Apr 04, 2014 12:33 pm

How do you define invalid elevation?

Re: [Script] WME Validator 0.9.4 (BETA) / 30.03.2014

Fri Apr 04, 2014 4:15 pm

Yes, I am just trying to find out if lg1992 means the same thing as we did earlier.

Anyway, the template would be ${elevation} and the regexp would be !\-[1-5]|^[0-9]$ , if you want to test if the elevation is outside of -5 and 9. And I trust you would manage to tune that to a range you are looking for.

Re: [Script] WME Validator 0.9.7 (BETA) / 08.04.2014

Fri Apr 11, 2014 11:31 am

sketch wrote:Is there a way to change the severity of a custom check from Note? I don't see one in the Wizard example.

There are some nice instructions in this post.

Re: [Script] WME Validator 0.9.7 (BETA) / 08.04.2014

Mon Apr 14, 2014 6:43 pm

Maybe we are talking about different checks, but this piece of code works fine for me just now:

Code:
  "130.enabled": true,
  "130.severity": "warning",
  "130.params": {
    "titleEN": "Segment with alternative name",
    "solutionEN": "Delete the alternative name(s)",
    "problemEN": "The segment has at least one alternative name",
    "template": "${altStreet[0]}",
    "regexp": "^.+$"
  },

(I left away the localized parameters in my example)

If you put this into a localization script, the severity setting will only become active if you set WME to the correct language (so it won't if WME is set to English). On an english WME the same custom check will be a note, so one might call that part a bug, yes.

Re: [Script] WME Validator 0.9.7 (BETA) / 08.04.2014

Mon Apr 14, 2014 7:41 pm

Yes, I think we mean the same thing. It doesn't work for English, but it does work for all other languages.

Re: [Script] WME Validator 0.9.8 (BETA) / 15.04.2014

Wed Apr 16, 2014 10:18 pm

Please keep in mind that this is a thread about WME Validator.

Re: [Script] WME Validator 0.9.8 (BETA) / 15.04.2014

Thu Apr 24, 2014 5:15 am

You can add the following custom check:

Template:
Code:
${street}

Custom RegExp:
Code:
[A-Z][0-9]{3}
Last edited by BellHouse on Thu Apr 24, 2014 5:17 am, edited 1 time in total.

Re: [Script] WME Validator 0.9.9 (BETA) / 27.04.2014

Tue May 13, 2014 11:55 am

I don't quite understand why E773 is continuing through the roundabout? This is not visible in the sat pic, nor in GMaps, nor in OSM.

Re: [Script] WME Validator 0.9.9 (BETA) / 27.04.2014

Tue May 13, 2014 12:22 pm

OK, I see. But the constellation I see in StreetView is not a roundabout, but a major road with 2 half-circle extensions. There's no roundabout sign to be seen.

I think the solution is to simply remove the roundabout status of these segments.

Re: [Script] WME Validator 1.0.1 / 25.06.2014

Sat Jun 28, 2014 2:53 pm

ctpoole wrote: If I put in a node I eliminate the same segment warning but in its place I get an unneeded node warning.

This used to be a problem, but in the current Validator version this should not happen any more (the unneeded node warning).
Post a reply