Organised Editing/Activities/Resolve linting issues in Michigan
Contact
We welcome feedback, suggestions, and insights from local mappers. If you have questions about this work, or a specific edit by our team, please reach out to Vlada at vlada.boitsik@mapbox.com or post a comment in a changeset.
Background
As part of on-going work to improve the quality of OpenStreetMap data, we recently used osmlint-osmium and osmlint for detecting issues related to road network data in Michigan. In total, we are going to review issues in 10 categories. Our plan is to review a subset of the detected issues manually, and fix any valid issues in OpenStreetMap. Here’s a link to our Github ticket
We used the following linters:
| issue | total |
|---|---|
| crossinghighways | 2965 |
| crossinghighwaysbridges | 1 |
| impossibleangle | 32 |
| impossibleoneways | 129 |
| islandshighways | 597 |
| mixedlayer | 33 |
| tr-excessiverolestr | 9 |
| tr-invalidroletr | 3 |
| tr-missingroletr | 84 |
| tr-missingtyperestrictiontr | 5 |
Timeframe
We plan to start reviewing detected issues next week, and editing OpenStreetMap data to fix valid issues.
Tools and ground-truth sources
We will use existing OpenStreetMap editing tools, and using the #hashtag #mbx_linters_michigan
- Editor: iD or JOSM
- Satellite Imagery: Bing, Maxar, Esri
- Street Level Imagery: Mapillary, Other open sources if available
Examples of linters in OSM
Unconnected roads
- https://www.openstreetmap.org/edit#map=20/42.30780/-83.07404
- https://www.openstreetmap.org/edit#map=20/42.17764/-83.41519