Data quality is as important a function for any contributor to know as is adding large quantities of detailed data to OpenStreetMap. If we were talking one or two individuals editing, quality assurance would be straightforward, but what about with 2.4+ million registered users adding 2,000,000+ nodes a day?

Luckily, the tireless vigilence of active contributors is a source of some consolation but nearly not sufficient by itself. The important question then becomes, how can we detect and remedy mistakes and acts of vandalism as and when they happen? In trying to find answers we’ve put together a “Validating OpenStreetMap Guide” which aims share our learnings to working with OpenStretMap. The guide covers the basics of handling data validation in OpenStreetMap by defining problematic data, tools for detection, methods for investigation, and avenues for resolution for individual and community mapping efforts.

History panel showing different details about users and versions

By sharing this we’d love to get your feedback on if we’re on the right track, and suggestions on how this guide can be improved to help bring an unparalleled level of data completeness that OSM users worldwide can benefit from.