Improvement of OSM data quality using osmlint and to-fix
In this way mappers are solving thousands of connectivity errors, overlapping ways, unclosed ways, incorrect tags or adding missing tags on the data using satellite imagery daily. Most issues are caused by inexperienced users who may be unaware of how to use the map editor and tags correctly and can be easily fixed by experienced remote mappers. Task descriptions and instructions to fix are provided in the Github repository.
Fixing issues using To-Fix JOSM plugin
To make it even easier to cycle through a task of interest, experienced mappers can solve issues much faster using the To-Fix JOSM plugin.
Progress of fixes
The community along with the data team at Mapbox has helped cleanup many thousands of issues in the last 2 years.
To-Fix errors fixed in the last two years
During the course of making these fixes remotely, our team has tried to minimize making incorrect fixes by montioring all changeset comments and taking appropriate steps to improve the algorithm and processing. Now countries with active mapping communities are ignored, changeset comments more descriptive and we recently made a fix to prevent the creation of large changesets that clutter the history view on OSM.
Our workflow to solve to-fix issues
The data team constantly monitors and fixes to-fix errors every day to clean up OpenStreetMap data.
Issues solved in July
A task is assigned to one specific data team member after its completion so that it is constantly monitored for new errors. These new errors are detected and fixed immediately thus reducing the response time to fixing bad edits on the map. Every week, the corresponding tracker on Github is updated with
total detected errors and total resolved errors to monitor and document any sudden spikes in issues.
Keeping OSM data error free
From the data team at Mapbox