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, The USA. In total, we are going to review issues in 10 categories. There were detected 3858 issues.
Our plan is to review all detected issues and fix it in OpenStreetMap. There's a link to our OSM Wiki page.
Timeframe
We plan to start reviewing detected issues next week, and editing OpenStreetMap data to fix valid issues.
Tools
We will use existing OpenStreetMap editing tools, and using the #mbx_linters_michigan
Editor: iD or JOSM
Satellite Imagery: Bing, Maxar, Esri
Street Level Imagery: Mapillary, Other open sources if available
Contact Person
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, The USA. In total, we are going to review issues in 10 categories. There were detected 3858 issues.
Our plan is to review all detected issues and fix it in OpenStreetMap. There's a link to our OSM Wiki page.
Timeframe
We plan to start reviewing detected issues next week, and editing OpenStreetMap data to fix valid issues.
Tools
We will use existing OpenStreetMap editing tools, and using the #mbx_linters_michigan
Editor: iD or JOSM
Satellite Imagery: Bing, Maxar, Esri
Street Level Imagery: Mapillary, Other open sources if available
Contact Person
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.
Linter Output
Examples
2.Dargged node (link1, link2
@legain @Andygol @abrohood @shvrm @lukasmartinelli @mikelmaron