mapbox / mapbox/mapping

[Italy] Reviewing osmlint-osmium and osmlint data issues

Open
#378 5 comments 0 reactions 1 assignee View on GitHub

@vladaboitsik is already working on this.

Since May 21, 2021.

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

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 Italy. 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 in the 1st of June.

Tools

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

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 Natallia (natallia.zhouner@mapbox.com) or post a comment in a changeset.

Example
  1. Dragged node and duplicate
    link
Screenshot 2021-05-21 at 14 56 02
  1. Crossing highways in the same layer (need to add a tunnel)
    link
Screenshot 2021-05-21 at 14 57 17
Linter Output for Italy
Issue Texas Italy Data
Crossing Highways 1221 crossings1.json, crossings2.json,crossings3.json,crossings4.json, crossings5.json
Island Highways 802 islandshighways.json.zip
Impossible Angle 277 impossibleangle.json.zip
Impossible Oneways 843 impossibleoneways.json.zip
Mixed layer 109 mixedlayer.json.zip
Missing Type Restriction 28 tr-missingtyperestrictiontr.json.zip
Missing Role 775 tr-missingroletr.json.zip
Excessive Roles 74 tr-excessiverolestr.json.zip
Invalid Roles 80 tr-invalidroletr.json.zip

@Zetkun @Andygol @abrohood @shvrm @lukasmartinelli @mikelmaron

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.