[Slovak Republic] Reviewing osmlint-osmium and osmlint data issues
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- data
Research direction
Start with the linked OpenStreetMap Wiki activity page and the planned linter-output JSON files; the issue says these files will contain the exact items to review. Use the listed iD editor and imagery sources to review all nine categories, with completion defined as resolving the detected OpenStreetMap data issues and updating the outputs.
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 use internal Mapbox data validation jobs that search OSM data for errors for detecting issues related to road network data in Slovak Republic. 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 March 2022.
Tools
We will use existing OpenStreetMap editing tools, we will use #hashtag for the project #mapbox_linters_slovak
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 Slovak Republic
As soon as we process issues, we'll update this page with json files, which will contain exact items we're going to review.
cc @abrohood @shvrm @lukasmartinelli @vladaboitsik
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mapbox/mapping
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
Similar issues
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·
-
bug p1 tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 84/100