Segments WITH HN (driveable or not) are different from segments WITHOUT HN in that they are a legit navigationtarget. Often walkingtrails are used to connect houses to the correct street, disconnecting these trails would send the wazers to the wrong side of the block...

You wouldn't need the complete list of HN, just the confirmation that a segment has HN. Is that a separate/faster query?

berestovskyy wrote:
But still we have plenty of options for 'Non-drivable connected to drivable' check:
1. We can exclude dead-ends up to 300 m long.
2. Or we can enable check #115 just for some countries by request.
3. Or we can report just railroads connected to drivable roads.

I would go for #1; but the summum would be a recursive dead-end-check

Railroads are ALWAYS to be reported if connected to something drivable. As there are a number of countries that have substituted railroads by walking trail (with a distinctive name like "spoorlijn" or "railroad") those should be treated equivalent to RR.

berestovskyy wrote:

bgarch wrote:Enable "report railroads connected to drivable roads" for any country.

Force update the script, it's done few versions back:
24.02.2014 v0.7.2:
- UPD 'Non-drivable connected to drivable':
excluded short dead-end segments and segments with house numbers

19.02.2014 v0.7.0:
- NEW for ALL: 'Non-drivable connected to drivable'

Wow! So you DO check HN, though slow? Great!

Some dev READS this thread, maybe? Hello! Welcome!

In chrome you can have setups synced across multiple machines - by using the same google-id.

In Brazil, your script are giving alert to narrows streets giving the #131 error. It's a problem about highway. Narrow street are not error, don't need to show this error.

berestovskyy wrote:Could you please add a permalink?

Yes, sure. Here's the link.

And are some pics.

Now it works in Hebrew again!
Thanks Glodenox and dbcm

Latest WME production build v2.180 seems to have broken WME Validator...

Validator is broken in WME and fails to start.