AndyTol
commented
1 month ago | We would like to share some changesets that we noticed during our data quality check of OpenStreetMaps. In the course of our work since the beginning of May, we have reverted 28 changesetss with various types of vandalism: Screenshot | Description & Links |
|---|---|
| Graffiti (OSMCha) | |
| Graffiti (OSMCha) | |
| Dragged node (OSMCha) | |
| Profanity (OSMCha) | |
| Wrong tagging (OSMCha) | |
| Fictional mapping (OSMCha) |
Introduction
Mapdata Improvements Initiative focuses on conducting worldwide editing activities across all layers and feature types in OSM. Our primary goal is to address issues such as vandalism, offensive data, broken roads, snapped points, outdated information, missing service roads, incorrect heights, and other inaccuracies that compromise the quality of OSM data.
Types of Activity
Our primary goals include:
Detected Vandalism: We actively identify and address instances of vandalism in the OSM database, ensuring that inaccurate or malicious edits are corrected in a timely manner.
Combating offensive data: We strive to maintain a welcoming and inclusive environment in OSM by removing offensive or inappropriate data points.
Improving osm data: We work to address gaps in OSM coverage by adding missing roads, poi, and other important features, thereby enriching the overall dataset.
Data accuracy: We verify and correct data inconsistencies such as incorrect elevations\heights, mistake tagging objects, and other inaccuracies that warning the reliability of OSM data.
Geographical scope
Data improvements will be made worldwide
How to find Mapdata edits
All edits made by our team in this project have the hashtag #mapbox_editing
Editing Team
All members of team went through the onboarding process before starting editing on OpenStreetMap and are familiar with the principles of editing. New editors are guided to OSM training resources like the OSM Wiki and iD editor's Help panel. All team members can be found here: link
Tools
Team will use OSM ID and JOSM for completing the task. JOSM has validation warnings for buildings and other possible issues that are important to prevent improper changes. We also actively use OsmCha.
Sources
For some OSM map edits Mapbox will use proprietary sources for support. These will typically be in situations where there is not sufficient evidence using the available sources in OSM editors. The proprietary sources will be ground-level imagery and GPS traces, collected by our drivers during testing.
Timeframe
This project has constant edits on an ongoing basis. Contact We welcome feedback from local mappers as local knowledge always prevails. If you have any questions about a specific edit done by the Mapbox Feedback team or want to suggest some improvements in the editing process you can contact osm-edit-escalations@mapbox.com or post a comment in a changeset.
More information about team : Wiki page