[Poland] Reviewing osmlint-osmium and osmlint data issues
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 Poland. 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 March 2022.
Tools
We will use existing OpenStreetMap editing tools, we will use #hashtag for the project #mapbox_linters_poland
Editor: iD or JOSM
Satellite Imagery: Geoportal 2: Orthophotomap, 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). Also you can leave a comment in a changesets.
Linter Output for Poland
As soon as we process issues, we'll update this page with json files, which will contain exact items we're going to review.
@Zetkun @abrohood @shvrm @lukasmartinelli @vladaboitsik
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.
Research direction
Start with the linked OpenStreetMap Wiki page and the eventual linter-output JSON files mentioned in the issue. Review the nine categories using iD or JOSM and the listed imagery sources; done means the detected Poland issues have been reviewed and corrected in OpenStreetMap.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100