[Brazil] 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
Linting issues are errors in OpenStreetMap data, which is identified by data validators. The project was created to review errors with OSM data and fix it where there’s possibility for improving the road network. We’re concentrating on road mistakes to improve map condition. We get issues by an internal automated process made by our developers which is based on the open source tool [OSMLint](https://github.com/osmlab/osmlint).
The processing of features goes by this way: at first we find sources for fixes (it can be searched through aerial photos or street level photos). We use only sources that are allowed in OSM ID.Then we choose a source with the best quality of the picture and the newest one. On chosen sources should be seen features that we want to map. Also we can watch OSM history to understand what changes were done with the feature, compare dates of changing.
In cases of lack of up to date satellite or imagery the team doesn’t make any edits. And always taking care about local sources, which are the most relevant and unique for each country.
In Brazil we plan to upload data once a week to see and fix the latest mistakes in mapping after reviewing the 1st iteration.
[Link](https://wiki.openstreetmap.org/wiki/Mapbox_linters_types_description#Intro) to the page with more detailed info about types of issues, how do we get them and how they can be viewed. [Link](https://wiki.openstreetmap.org/wiki/How_Mapbox_Data_RAVE_team_work_on_receiving_feedback_from_OSM_users) to the page with info about how we deal with feedback.
### Examples of linters in OSM
As soon as we process issues, we'll update this ticket with [geojson](http://geojson.io/#map=2/20.0/-0.5) files, which will contain exact items we're going to review.

Now, we have a very small amount of fixes for turn restrictions, we discussed it with Andy (DWG) and Communities previously and decided not to fix it as it’s the most difficult type of investigation for not-locals, so we post the detections and ask the local community to carry out the fixes themselves.
### 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 Brazil. 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_Brazil) to the OSM Wiki page.
We use internal Mapbox data validation jobs that search OSM data for errors. The process is completely switched to automatic uploading and searching for data errors. Automation of the process was achieved with internal algorithm which detects mistakes on OSM and divides these issues by categories we have. Our plan is to review a subset of the detected issues manually, and fix any valid issues in OpenStreetMap.
Currently we are using the approach described below, the only difference is that we have an internal automated process by our developers.
Generally the process is:
First, we download fresh data from https://download.geofabrik.de/ .Then convert data from *.osm.pbf into geojson format for further packing into *.mbtiles. Use tippecanoe to make *.mbtiles. After that we use [osmlint](https://github.com/osmlab/osmlint) and [osmlint-osmium](https://github.com/osmlab/osmlint-osmium) which help us to spread linters by their types. Then received files come through our improvement algorithm, after which we get only needed linters for us. On this step we cut off footways, cycleways, golf carthpathes, aeroways, etc.
### Timeframe
1st iteration (June 2022): We plan to start reviewing detected issues in the June 2022, and editing OpenStreetMap data to fix valid issues.
### Tools
We will use existing OpenStreetMap editing tools, and using the hashtag **#mapbox_linters_brazil**
Editor: iD 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). Also you can leave a comment in a changesets.
### Linter Output for Brazil
As soon as we process issues, we'll update this page with json files, which will contain exact items we're going to review.
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 workflow pages and the OSMLint and osmlint-osmium documentation to understand the proposed Brazil review process. The issue mentions a future weekly review and GeoJSON or JSON outputs, but no output files or specific change are currently provided, so completion criteria are not defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100