[Script] WME Validator 1.1.8 / 07.05.2015

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.

Moderator: Unholy

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.

Re: [Script] WME Validator 0.5.0 (BETA) / 20.01.2014

Postby levin » Tue Jan 21, 2014 9:27 am

I would like to suggest two new checks:
  • Two-way freeway segment
    severity: warning
    problem: Freeways are almost always split into two one-way roads. A two-way segment is probably a mistake.
  • Two-way ramp
    severity: warning
    problem: Most ramps are one-way. A two-way ramp is possible, but should be examined.
OnePlus One - Android 5.1.1 - Waze 3.9.4
Israel country manager
levin
Waze Global Champs
Waze Global Champs
 
Posts: 143
Joined: Wed May 29, 2013 12:38 pm
Location: Israel
Has thanked: 125 times
Been thanked: 193 times

Re: [Script] WME Validator 0.5.3 (BETA) / 23.01.2014

Postby levin » Sun Jan 26, 2014 10:25 am

Another suggested check: U-turn at roundabout entrance

When a road is entering a roundabout, there must not be a u-turn on the node connecting to the round-about. The driver must make a full round around the roundabout instead of a U-turn just ahead of it.

For example, The marked U-turn should not be allowed:
Capture.PNG
Capture.PNG (18.6 KiB) Viewed 1750 times
OnePlus One - Android 5.1.1 - Waze 3.9.4
Israel country manager
levin
Waze Global Champs
Waze Global Champs
 
Posts: 143
Joined: Wed May 29, 2013 12:38 pm
Location: Israel
Has thanked: 125 times
Been thanked: 193 times

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Postby levin » Tue Feb 18, 2014 7:31 am

lg1992 wrote:I suggest disabling the "Less than 3 letters long street name" note for Israel. There are quite a few 2-letters words in Hebrew, and some of them are used for street names. So far I met 3 such names.

That's true, but we also have many old streets with spaces instead of names - a remnant from older days when you could not have empty street names. This check helps to locate these cases, and since it's only a note, you can easily ignore it for the few cases with real two-letter names.

I say we better keep it.
OnePlus One - Android 5.1.1 - Waze 3.9.4
Israel country manager
levin
Waze Global Champs
Waze Global Champs
 
Posts: 143
Joined: Wed May 29, 2013 12:38 pm
Location: Israel
Has thanked: 125 times
Been thanked: 193 times

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Postby levin » Tue Feb 18, 2014 9:00 am

Well, as noted by berestovskyy, there actually is a check for names with spaces only.
Can we change the check to be "Streets with only 1 letter in their name" for Israel? - so 2-letters will be OK but 1-letter will still be flagged.
OnePlus One - Android 5.1.1 - Waze 3.9.4
Israel country manager
levin
Waze Global Champs
Waze Global Champs
 
Posts: 143
Joined: Wed May 29, 2013 12:38 pm
Location: Israel
Has thanked: 125 times
Been thanked: 193 times

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Postby lg1992 » Fri Feb 14, 2014 5:28 am

I suggest disabling the "Less than 3 letters long street name" note for Israel. There are quite a few 2-letters words in Hebrew, and some of them are used for street names. So far I met 3 such names.
Leonid, Region Manager, Israel
lg1992
Beta tester
Beta tester
 
Posts: 38
Joined: Thu Aug 22, 2013 7:42 am
Has thanked: 5 times
Been thanked: 15 times

Re: [Script] WME Validator 0.9.0 (BETA) / 20.03.2014

Postby lg1992 » Sat Mar 22, 2014 5:40 am

I want to define a custom rule to mark segments with undefined elevation. The problem is that I haven't found a way to define a proper regular expression for that.

While playing with regular expression I got sometimes a lot of segments colored green and noticed that my custom rule defeated other rules, even in a very small area with few segments. Segments with warnings are colored green, not yellow. The button "Show report" is also green. Moreover, the report only lists the "User-defined custom check 1". I think it's a bug.

BTW, it would be nice to allow naming the custom checks.
Leonid, Region Manager, Israel
lg1992
Beta tester
Beta tester
 
Posts: 38
Joined: Thu Aug 22, 2013 7:42 am
Has thanked: 5 times
Been thanked: 15 times

Re: [Script] WME Validator 0.9.0 (BETA) / 20.03.2014

Postby lg1992 » Sat Mar 22, 2014 10:55 am

No success with NaN rule for the elevation. Debugging also doesn't help - JS console only shows "RegExp: /NaN/ -> skip the segment".
Leonid, Region Manager, Israel
lg1992
Beta tester
Beta tester
 
Posts: 38
Joined: Thu Aug 22, 2013 7:42 am
Has thanked: 5 times
Been thanked: 15 times

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

Postby lg1992 » Fri Apr 04, 2014 12:16 pm

Are there plans to enable checking for invalid elevation? If not, can I enable this checking just for me? If not, what's the correct rule to define custom condition for that?
Leonid, Region Manager, Israel
lg1992
Beta tester
Beta tester
 
Posts: 38
Joined: Thu Aug 22, 2013 7:42 am
Has thanked: 5 times
Been thanked: 15 times

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

Postby lg1992 » Sat Apr 05, 2014 3:48 am

BellHouse wrote: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.

I mean cases when elevation of a selected segment is shown empty. I see a lot of such segments in my region in Israel. I've applied a custom check as berestovskyy advised.
Leonid, Region Manager, Israel
lg1992
Beta tester
Beta tester
 
Posts: 38
Joined: Thu Aug 22, 2013 7:42 am
Has thanked: 5 times
Been thanked: 15 times

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

Postby lg1992 » Sat May 10, 2014 3:06 am

I use the following custom condition to mark dead-ends without U-turn:
template ${deadEnd}:${Uturn}:${direction}
RegExp 1:0:3
It usually works properly, but fails to mark segments which have U-turn on the second end. Here's an example of such segment https://www.waze.com/editor/?zoom=7&lat ... nts=240202

Can anybody suggest a condition that will also cover such segments?
Leonid, Region Manager, Israel
lg1992
Beta tester
Beta tester
 
Posts: 38
Joined: Thu Aug 22, 2013 7:42 am
Has thanked: 5 times
Been thanked: 15 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: Yahoo [Bot]