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

[berestovskyy]

Hi guys!

A minor update:

v2020.10.25:
- davidakachaos: updated Wiki links for BE/NL

[berestovskyy]

The source code and built in localization files are all on GitHub:
https://github.com/WMEValidator/

I’ll help if you have any questions.

[berestovskyy]

Any fixes are welcome from anyone. If the links are broken, we should fix them.

Any other changes are welcome from anyone if they’re based on community documents/guidelines.

Any new features from anyone also bring value, with maybe some minor tweaks from the community once the feature is publicly available under a feature flag.

Fork the Validator, play with it, change it, contribute back!

[berestovskyy]

Minor update:

v2020.11.1:
- paulvdwyn: update Motorway naming for BE

[bgodette]

User BellHouse found the source of the problem related to Elevation Being Set to Null, it is caused by JNF (Junction Node Fixer). Just disable it and the problem is gone.

Except that it's not. It's a side effect of eventual consistency and has nothing to do with anything but WME's backend's current propagation delay at the time you save modification(s) to a segment(s).

Normally this is masked by JNF's issuing a second reload after a successful save, but sometimes you might get data served from a different server that isn't yet consistent.

[bgodette]

All such a filter does is help someone to see who's been editing a given set of roads, NOT where they live.

Um actually about that... While there usually isn't enough information available directly in WME to determine where someone lives, it does provide a really large side-channel.

[bgodette]

Figure out where I live (more specifically than just what city) based on my edits and I'll send you a box of cookies.

Half a residential block close enough? Because that's how close info in WME can usually get you.

It's been a known issue for four years and unofficially discussed at each NA meet. It's not really something that can be solved either without hamstringing the community's ability to police the map under the current system of edits with no approval. It's not particularly high-priority issue either since editing is voluntary and a public activity.

[bgodette]

I value my privacy (what little of it there is, these days), but half a residential block isn't something that would make me too terribly nervous for someone to figure out (I realize that others might not feel that way).

So no concerns about someone sitting around to see who gets into a car with a phone mount?

[bgodette]

I value my privacy (what little of it there is, these days), but half a residential block isn't something that would make me too terribly nervous for someone to figure out (I realize that others might not feel that way).

So no concerns about someone sitting around to see who gets into a car with a phone mount?

Heck, someone can do that now, completely unrelated to Waze.

Well yeah, but that's looking for just anyone, not a specific someone.

[bgodette]

"#74 The drivable roundabout node A has more than one segment connected"

Hi berestovskyy, please take a look of this situation concerning "Rule #74: The drivable roundabout node A has more than one segment connected". The script reports roundabout nodes with multiple connections, but I don't think there is another way to do this. Or there it is? Thanks.

https://www.waze.com/editor/?lon=27.249 ... =252358268

Hamburger roundabouts are a special case. I believe there's a good discussion about them in the UK forums. IIRC one solution is to have the "meat" connect to the segments outside of the RB if turns from inside onto the RB aren't allowed.