Project Mapbox linters
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Documentación
- Claridad
- Necesita aclaración
- Estado de actividad
- Tranquilo
- Área
- documentation
Línea de trabajo
Comienza con la página wiki de OpenStreetMap enlazada y las issues de países referenciadas para entender las categorías del linter, el flujo de trabajo y las expectativas de los informes. La issue no especifica ningún archivo fuente, prueba ni cambio concreto en la documentación, por lo que sería necesario aclararlo antes de que el trabajo pueda considerarse completo.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Introduction
Mapbox Linters is a division inside Mapbox that reviews errors with OSM data and fixes it where there’s the possibility for improving the road network, concentrating on road mistakes to improve map conditions. We get issues by an internal automated process made by our developers which is based on the open source tool OSMLint.
Types of Activity
The goal of the Mapbox Linters team is to improve OSM data by using the following linters:
- crossing_highways - adding\removing points of intersection of roads.
- impossible_angle - removing and aligning dragged nodes.
- impossible_oneways - editing one-way road junction without end.
- islands_highways - extension of the road which isn't connected with other roads.
- mixed_layer - editing objects with intersection and different layers.
- tr_excessive_roles_str / tr_invalid_role_tr / tr_missing_role_tr / tr_missing_type_restriction_tr - correction, removal and addition of from/via/to roles.
- roundabout-common-node - fixing incorrect geometry.
- roundabout-missed-name - applying tag name=/ref= to exiting/entering oneways of the roundabout
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 an internal algorithm which detects mistakes on OSM and divides these issues by categories we have. Our plan is to review the detected issues manually, and fix all invalid cases in OSM.
Link to the page with more detailed info about types of issues, how do we get them and how they can be viewed.
Geographical Scope
The Mapbox Linters initiative conducted for the following countries: Italy, France, Belgium, Canada, Spain, Denmark, Greece, Hungary, Slovak Republic, Ireland, Switzerland, Croatia, Bulgaria, Brazil, USA, UK, Germany, Netherlands, Poland, Czech Republic, Sweden, Portugal, Norway, Finland, Austria, Singapore, Romania, Slovenia, Australia.
Hashtags
All edits made by our team in this project have the hashtag #mapbox_linters.
Editing Team
All members of the Linters team went through the onboarding process before starting editing on OpenStreetMap and are familiar with the principles of editing. All team members can be found here: link.
Sources
For OpenStreetMap edits we use sources that are integrated in the OpenStreetMap tool:
- Satellite Imagery: Bing, Maxar, Esri etc.
- Street Level Imagery: Mapillary, Bing, KartaView
- Tiger Roads
- Source with ODbL license
For some OSM map edits Mapbox will use proprietary sources for support. These will typically be in situations where there is not sufficient evidence using the available sources in OSM editors. The proprietary sources will be ground-level imagery and GPS traces, collected by our drivers during testing.
Workflow
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.
Timeframe
This project is ongoing and will be continuously active without any time constraints.
Results
The results of our review made by our team in OpenStreetMap will be displayed quarterly in the /mapping repository in this project ticket.
Contact
We welcome feedback from local mappers as local knowledge always prevails. If you have any questions about a specific edit done by the Mapbox team or want to suggest some improvements in the editing process you can contact osm-edit-escalations@mapbox.com or post a comment in a changeset.
More information about team : Wiki page
- Lenguaje dominante
- JavaScript
- Estrellas
- 254
- Forks
- 46
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de mapbox/mapping
-
Project Mapbox Trees Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
-
Project Missing Roads Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
Project Road attributes Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
-
Project MapData | Worldwide Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 15/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 15/100
Todos los issues de mapbox/mapping
Issues similares
-
Update HugeIcons library Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
antfu-collective/icones#398 ·
-
ECmail.com Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
wesbos/burner-email-providers#554 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
radiantearth/stac-browser#1023 ·
-
HMR stops working Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
components-web-app/docs#92 ·