mapbox / mapbox/mapping

[Hungary] Reviewing osmlint-osmium and osmlint data issues

Open
#401 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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 use internal Mapbox data validation jobs that search OSM data for errors for detecting issues related to road network data in Hungary. 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](https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/resolve_linting_issues_in_Hungary) to the OSM Wiki page.

### Timeframe

We are going to start review on the end of March 2022.

### Tools

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

Editor: iD
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). Also you can leave a comment in a changesets.

### Linter Output for Hungary
As soon as we process issues, we'll update this page with json files, which will contain exact items we're going to review.

@abrohood @shvrm @lukasmartinelli @vladaboitsik

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.

Research direction

Read the linked OSM Wiki page for the Hungary activity and review the issue's planned scope across nine categories. Check the forthcoming linter JSON outputs and use iD with the listed imagery sources; done means reviewing the detected issues and fixing them in OpenStreetMap.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.