OpenStreetMap
Stumbled upon this mistakenly dragged node thats been hanging around Sheffield for the last two months. Considering its not fixed despite having a highly active mapping community, wonder if some tooling could have helped flagged this to local mappers sooner.
Ideas on how to prevent such edits in future? Any existing QA tools that highlight this?
Discussion
Comment from tyr_asd on 17 February 2017 at 14:11
Tools like keepright often indirectly show such cases by detecting the non-intersecting overlapping highways.
Comment from Vincent de Phily on 17 February 2017 at 15:25
Osmose and OSMI both also catch self-intersecting ways and multipolys. Don’t think it would catch that particular problem, but they catch many others. Those QA tools will keep you busy. http://wiki.openstreetmap.org/wiki/Quality_assurance
Comment from Alan Trick on 17 February 2017 at 18:30
The “highway kinks” check that TO-FIX does would catch that, since Wood Lane is very kinked. Off course it won’t catch short accidental drags, bug I don’t think that’s practical to catch.
Comment from SK53 on 17 February 2017 at 19:58
OSM-GB a project at the University of Nottingham which ran over 2011-2013 provided all these type of error checking for Great Britain, but like every other OSM error checking routine it tended to produce too many false positives. Many of the TO-FIX reported errors may indeed be errors but many are one-or-more of a) trivial; b) unimportant (eg in service roads); or c) require too much time to investigate. Eyeballing a list of contributors in a region is still often the best way to identify changes which need checking.
One kind of check we have relatively little of is dramatic changes in geometry for something which has been stable for a long time. Of course this wouldn’t work in the US with TIGER fixup, or with re-drawing NPE waterways in the UK, but it would make it easier to see potentially regressive edits.
Comment from BCNorwich on 18 February 2017 at 08:19
Hello, “Intersections without Junctions” in “Keep right!” shows those problems. Please see here :- https://tinyurl.com/gvoescq As you can see you’ve corrected them.