An Idiot's Guide to OSM Inspector
Posted by alexkemp on 1 November 2016 in English. Last updated on 8 February 2019.My target was to finish mapping a patch local to me in Nottingham, bounded (roughly) by The Wells Road, Woodborough Road, Westdale Lane West/East and Carlton Hill. It took 7 months & is now complete.
I’m a careful & thorough kind of chap and thought that I’d done a good job. Nevertheless, I was really pleased to recently come across OSM Inspector, which is provided by Geofabrik Tools to be able to quickly find a whole range of errors. There is a wiki page for it and, naturally, it provides virtually zero help in using the tool. I’ve used it for just a couple of days, so here is…
An Idiot’s Guide to OSM_Inspector
or, OSM Tools Considered Useful After Mapping
- Open OSM Inspector in a browser of your choice
- Type your desired map location into the Search box & click search
(for me “nottingham”) - Click on the desired link from the Results box
(for me, “Nottingham, East Midlands, England, United Kingdom”) - You will now dimly see your desired location on the map
[my view in your browser]
(there is a slider next to the Base Layer option box which will adjust the contrast of the base map) - Click the ‘+’ and/or drag the map until you have the correct territory before you in the screen
- Click on the View dropdown & choose “Addresses”
(there are a lot of other options, but that has been my activity all this year) - Click the “Buildings” checkbox OFF to allow the errors to be seen
- Click on an error within the map to show that selection in the RHS selection panel. If you use JOSM & have the RemoteControlPlugin installed (not needed if > v3715) + JOSM is already running, then clicking on the icon will switch JOSM to the current view + load the data (I haven’t tested that yet). Icons are also provided for iD + for Potlatch2.
It was mostly very useful for finding + fixing errors in my mapping. I found only 2 useless aspects:-