Hey guys,
The script is finally updated everywhere to v2022.8.25.

Sorry, it took Google support more than a month to fix the issue on the WebStore
On the positive side, let's hope it will be flawlessly working another few years!

The latest changes are:

v2022.8.25:
- DaveAcincy: update US and default wiki links

v2022.8.23:
- DaveAcincy: fix for coordinates not transforming for PLs
 

v2023.2.13:
- DaveAcincy: New checks for US:
  * #54 "No city on segment with HNs"
  * #55 "No city on named segment"

Plus some fixes on top also thanks to Dave.

turbomkt wrote: ↑Mon Feb 27, 2023 9:48 pmThat's a horrible interface

Sorry to hear that. The idea behind the interface is that you should never need to manage the checks manually. They should normally come from your country/region localization pack...

Anyway, it's an open source project, so any changes are welcome!


New release:

v2023.3.8:
- justins83: Minor fixes in #29 to match USA naming guidance
 

turbomkt wrote: ↑Wed Mar 08, 2023 8:57 pm As an interface, it certainly is less work for the scripter.

 

Haha, certainly!

The actual list of checks is available under Settings (gear) > About (question mark) > Available checks... The forum engine has been updated, so now the generated BBCode has small glitches. This prevents me from updating the list of check on the forum.

Would you like to contribute some of your time and fix those glitches, turbomkt? Ideally we should fix the BBCode generator in the Validator, but if you could fix the glitches manually, it would also help the community.
 

MatthieuF44 wrote: ↑Mon May 08, 2023 2:45 pm Currently then we check the box for non editables segments and we can't see high level locked segment and segment outside editable area.
I would like to seprate this two categories in two checkboxs options.

 

What's the use case for such a feature?
 
 

Holidays, sorry for the delay, Dave!

Holidays, sorry for the delay, Dave!
 

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

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

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