[Script] WME Validator v2020.11.1 (PLACES BETA)

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.

Moderators: Unholy, bextein, Glodenox, JustinS83

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.8 (BETA) / 31.01.2014

Postby sketch » Sat Feb 01, 2014 8:01 pm

myriades wrote:Hi
Maybe a minor enhancement could be done.
When you select multiple segments, you got something like that.
WME_multiple_seg_sel.png

Maybe you can disable the report when multiple select is performed or at least grouping errors by #type?

That's what I'd like to see: something like "Soft turns on drivable road (12) // Unterminated drivable road (5)" etc.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: [Script] WME Validator 0.5.9 (BETA) / 02.02.2014

Postby sketch » Mon Feb 03, 2014 5:38 pm

SuperDave1426 wrote:
berestovskyy wrote:If this one-way Ramp has a turn enabled to another one-way Ramp. Here is an example: permalink

I fail to see why that is an "unneeded name," given the length of the ramp. I've seen lots of named segments of that nature out here, and have been doing it that way all along, since it helps to provide guidance to drivers making their way to the freeway.

Because it will automatically take the name of the next named ramp. They have the same name, so there's no need* to name the first one as it'll already give the second one's name as the instruction. It makes zero difference* client-side, so there's no reason* to have the extraneous name taking up space in the Waze database. It's just streamlining.

* I will qualify this by saying that there is actually a reason to name this ramp—if you want the "keep right" command here, but no corresponding command for staying to the left. Because both of these segments are unnamed, the left side of the fork will be considered the "best continuation" and no instruction will be given. On the other hand, if the right side of the fork is left unnamed, there will be no best continuation and an instruction will be given either way.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: [Script] WME Validator 0.5.10 (BETA) / 03.02.2014

Postby sketch » Mon Feb 03, 2014 5:44 pm

SuperDave1426 wrote:
berestovskyy wrote:03.02.2014 v0.5.10:
- NEW for ALL 'Too short segment' (less than 2m long)


Just a "point of curiosity" question, but how does a segment less than 2 meters in length (which is a bit over 6 feet) cause a problem? I agree, it's kinda pointless to put in a segment that's that short, but I'm wondering why there's a check for it (not opposed; just curious).

We were told just a week or two ago by Waze staff that any segment under 5 meters can cause problems—specifically with the calculation of average times.

So, this check should probably be adjusted to alert for any segment under 6 m long.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: elevation -5 must be used exclusively for railroads

Postby sketch » Mon Feb 03, 2014 5:57 pm

dbraughlr wrote:Why is it wrong for walking trails, boardwalks, and runways to be elevation -5?
I hadn't heard that -5 means railroad. -5 is just a convention that mean do not connect to roadway.

I don't see why a walking trail with elevation -5 is an error. What else should it be?
"Rails to trails" are very popular. Many trails follow old RR rights-of-way.

A useful check is a non-drivable type junctioned with a drivable type.

Some communities have been using Walking Trails at elevation -5 to signify railroads as a matter of editor policy. Remember that a lot of the checks in Validator are not necessarily wrong, they're just things that might need a look.

SuperDave1426 wrote:
sketch wrote:(ramp stuff)
Ok, I see what you're saying there.

Although there are still times where naming individual segments apply (as you mentioned further in your message), so it seems that a check of that type is probably still not a good idea. Both in the case that we're talking about and which you acknowledge, but also times when the name changes to provide directional information.

I.E., an offramp that splits; the split segments have information about what they're taking you to beyond simply the road name that they're connecting you to.

I'll reiterate the point I made, that many of these are just checks. Not everything needs action. Some extraneous nodes are there because of temporary disconnections for closures, for example. There are some cases where the directions are different depending on which side you're coming from, yes. But there are plenty cases where they're the same. It's still worth looking at.

dbraughlr wrote:
sketch wrote:So, this check should probably be adjusted to alert for any segment under [X] m long

... for any drivable segment except a terminal (dead-end) segment under [X] m long ...

Very nice. I agree with this completely.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: [Script] WME Validator 0.5.9 (BETA) / 02.02.2014

Postby sketch » Mon Feb 03, 2014 6:19 pm

dbraughlr wrote:
sketch wrote:there's no reason* to have the extraneous name taking up space in the Waze database. It's just streamlining.

Whether the name takes up space is the database is a matter of how the database is designed. It doesn't affect routing. Regardless, it should not be the rationale driving this change.

Map simplicity is cited as a rationale by people around here pretty often. I don't personally always agree with it—accurate reflection of reality is more important—but I do understand that there is an interest in keeping the data size smaller, thereby reducing the amount of data that needs to be pulled by the client. A small difference, yes, but the kind of thing that adds up if it's taken as a matter of course.

Really, though, I'm not the one to rationalize that. It's not a cause my heart's really in. The example used is the kind of case where I wouldn't remove a ramp name if I came across it.

The better rationalization for this is simplicity in editing. For ramp segments like these, it's a lot easier to deal with if the only one you have to fix the name on is the long one that the two smaller segments lead into. The example shown earlier, on the other hand, may be easier to edit if the name is kept. Here's another example of that.

dbraughlr wrote:
sketch wrote:Remember that a lot of the checks in Validator are not necessarily wrong, they're just things that might need a look.
...
I'll reiterate the point I made, that many of these are just checks. Not everything needs action.


In practice, you are mistaken. There are many editors that expect the Validator to give their area a clean bill of health. Come to chat and talk to them. Editors have been deleting the loops flagged with "Same endpoints drivable segments" error. I recommended installing the updated Validator instead.

Any arbitrary "rules" like this should be turned off by default, clearly marked as informational when turned on, and marked with green or some color never used for errors.

Many editors also landmark Best Buys and Burger Kings, doesn't mean they're right. Instead of disallowing them from landmarking, we should be teaching them not to landmark. Likewise, we should be teaching editors to take much of what they see in Validator with a grain of salt.

But yes, I agree that this particular check should be a "note". Notes are blue, informational, and turned off by default.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: [Script] WME Validator 0.5.10 (BETA) / 03.02.2014

Postby sketch » Mon Feb 03, 2014 9:17 pm

Timbones wrote:Two ramps with the same name does NOT take up any more space in the database. It will be exactly the same as if one had no name. There's no advantage in removing names from ramps, even of they're not needed.

You've also hinted that ramp names are sometimes carefully created by editors to get the right instructions. This is another reason not to have this check....

Then I will respectfully concede. Like I said, my heart wasn't really in it anyway. :D

Perhaps we could use a "Note" for when the name on ramps going into a single ramp does not match. This would help in those situations where someone fixed one ramp to say "to I-75 N / Toledo" but left the other two as "to I- 75 N".
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: Validation

Postby sketch » Tue Feb 04, 2014 5:24 pm

dbraughlr wrote:Rule Walking Trail elevation = -5 is arbitrary. I did not see where anyone came forward to explain why he cares.

I did, two pages ago. "Some communities have been using Walking Trails at elevation -5 to signify railroads as a matter of editor policy."

So while no, it shouldn't be enabled for all regions, there are places where it is a useful check.

I can't fathom any reason an actual walking trail would be set to elevation -5.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: Validation

Postby sketch » Tue Feb 04, 2014 7:13 pm

dbraughlr wrote:That isn't an explanation of the error. Of what is this a useful check?

Railroads are not currently displayed in the client. That's why editors in some areas started marking railroads as "walking trails", so they'd be displayed in the client. But now we are told by staff that railroads will soon be displayed in the client, so all those -5 walking trails should be changed to railroads. Did I leave some of that out?

As a matter of editor policy, all non-drivable road types (including railroads, runways, boardwalks, stairs, and walking trails) have elevation set to -5 per established convention. -5 indicates that the segment is not to be attached to the drivable roadways "to prevent false system reporting that think the roads should be connected.".

I don't know of this convention, other than with railroads. Perhaps it is not so widespread as you think. In my area, pedestrian boardwalks are marked using normal elevation rules.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: [Script] WME Validator 0.6.0 (BETA) / 04.02.2014

Postby sketch » Tue Feb 04, 2014 7:52 pm

Where?

Road Types (USA) does not mention elevation for non-drivable roads other than (1) it must be different from any road it crosses, and (2) it should be -5 for railroads.

https://www.waze.com/wiki/Road_Types_(USA)#Non-drivable
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: elevation -5 must be used exclusively for railroads

Postby sketch » Tue Feb 04, 2014 11:14 pm

dbraughlr wrote:Yes, I quoted from the Railroad section. Of course, -5 is guaranteed to be different from any road it crosses.

OK, and I don't doubt that it isn't guaranteed. But that doesn't mean it's the rule. You're extrapolating a new rule from two existing rules. "Set every undrivable road to a different level than every road it crosses" and "set every railroad to -5" do not combine to mean "set every undrivable road to -5", because not every undrivable road is a railroad.

Walking trails at elevation -5 to represent railroads, on the other hand, was a rule (in some places), and is now an obsolete rule. Hence the check (which should be limited to some places).
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: G_W1Z, jm6087, Mapman44, Mythdraug

cron