[UK] Reviewing osmlint-osmium and osmlint data issues

Open
#387 24 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
data

Research direction

Start with the linked OSM Wiki page and one of the category ZIP files, then review the listed findings using iD or JOSM with the referenced imagery sources. Done means reviewing the UK findings across all nine categories and correcting valid OpenStreetMap issues or leaving them unchanged when the data is correct.

Written by the indexing model from the issue text.

Description

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 UK. In total, we are going to review issues in 9 categories.

Our plan is to review all detected issues and fix it in OpenStreetMap. There's a link to the OSM Wiki page.

Timeframe
We are going to start review on the end of August - September 2021.

Tools
We will use existing OpenStreetMap editing tools, we will use #hashtag for the project #mbx_linters_UK

Editor: iD or JOSM

Satellite Imagery: Bing, Maxar, Esri

Street Level Imagery: Mapillary, OpenStreetCam, 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 Natallia (natallia.zhouner@mapbox.com) or post a comment in a changeset.

Linter Output for UK
Issue Total Data
Crossing Highways 854 crossing_highways.zip
Island Highways 1157 island_highways.zip
Impossible Angle 350 impossible_angle.zip
Impossible Oneways 414 impossible_oneways.zip
Mixed layer 54 mixed_layer.zip
Missing Type Restriction 57 tr-missing_type.zip
Missing Role 1046 tr-missing_role.zip
Excessive Roles 261 tr-excessive_role.zip
Invalid Role 116 tr-invalid_role.zip

@Zetkun @abrohood @shvrm @lukasmartinelli @vladaboitsik

Dominant language
JavaScript
Stars
254
Forks
46
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/mapping

All issues in mapbox/mapping

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.