Mexico Road Name Project
- 1 About
- 2 Project Outline
- 3 Goals
- 4 Schedule
- 5 Progress
- 6 Data
- 7 Data Preparation
- 8 Data Merge Workflow
- 9 See also
Kaart will use data provided by Mexico’s National Institute of Statistics and Geography (INEGI) with OSM.
Kaart will continue efforts to ensure effective communication with Mexico’s OSM community throughout the project process.
- Determine which INEGI data set is most effective → MGN (June 2018)
- Develop tools to efficiently and accurately convert .shp files to .osm.pbf and accurately map attributes
- Develop processes to edit and validate data using JOSM (including custom paint styles and validators)
- Create projects for each state using an instance of the OSM_Tasking_Manager
To contribute up-to-date data for the road networks of Mexico by updating missing geometry and road names.
- Discussion with Mexico's OSM community - September 2018
- Announcement to Imports mailing list - September 2018
- Develop data processing tools - September 2018
- Manual editing and validation using JOSM - October 2018 → Completion(TBD)
|1||Tabasco||3 December 2018|
|2||Mexico City||8 January 2019|
|3||Oaxaca||18 February 2019|
|4||Yucatán||30 April 2019|
|5||Quintana Roo||30 April 2019|
|6||Querétaro||10 September 2019|
|7||Colima||9 August 2019|
|8||Michoacán||5 November 2019|
|9||Guanajuato||13 December 2019|
|10||Jalisco||20 July 2019|
|11||Nuevo León||13 December 2019|
|12||Baja California||8 January 2020|
|13||Chihuahua||10 January 2020|
|14||Puebla||26 February 2020|
|15||Coahuila||7 February 2020|
|16||Mexico||27 April 2020|
|17||Morelos||September 3, 2020|
|18||Tlaxcala||September 18, 2020|
The data is delivered as a .zip (~2.6GB) of the entire country of Mexico which contains a .zip for each state. Each state has a corresponding number(id) prefixing the name of the state (ex. 01_aguascalientes) as shown in the PDF on the right.
The state .zip contains 3 directories:
|catalogos||PDF and .txt files describing the data sets|
|conjunto de datos||"Data Sets" .shp files|
There are 13 different data sets within conjunto de datos for each state (information describing them can be found in contenido.pdf in catalogos).
The data set containing road data is Ejes de vialidad which will be identified by the id prefixing the letter "e" (ex. 01e.shp).
OSM Data Files
OSM data will be processed and delivered on a state by state basis. If there are any questions or concerns regarding the OSM data, please contact User:Zlavergne (examples of data may be made available).
- Automated tool to prepare data for conflation
- Automated tool to conflate data and output OSM_XML files
- Progress tracking will be done using an instance of the OSM_Tasking_Manager
- Manual processes for editing and validating data in JOSM
Data Reduction & Simplification
This project focuses on road names and missing road geometries. As described in the Data #Background section, we will be using the Ejes de vialidad data set.
Our team developed a tool to automate the process of converting the shapefile data. Simply explained below:
- Translation file (compatible with ogr2osm)
- Executes spatial analysis to extract Shapefile data within each state into individual Shapefiles
- Converts Shapefile to .osm and translates attributes to OSM tags
- Converts .osm file to .osm.pbf
Each task will have one OSM_XML file to compare names in OSM with names from INEGI:MGN.
Once we have converted the data into OSM_XML for a state, we can then create an OSM_Tasking_Manager project for the state and use the task bounds to take the appropriate Bounding_box of the converted files as a separate layer into JOSM.
All of these processes have been extensively tested and their outputs will be closely monitored throughout the project process.
|MNG Field||OSM Tag||Description (Sp)||Description (En)|
|NOMVIAL||name||NOMBRE DE VIALIDAD||Name of Road|
|TIPOVIAL||highway||TIPO DE VIALIDAD||Type of Road|
|SENTIDO||oneway||SENTIDO DE LA VIALIDAD||Sense of the Road|
|CVE_SEG||CLAVE DEL SEGMENTO DE VIALIDAD CONFORME A LAS MANZANAS||Key of road segment according to blocks|
|CVE_VIAL||inegi:road_key||CLAVE DE LA VIALIDAD||Road Key|
|CVE_LOC||CLAVE DE LOCALIDAD||Locality Key|
|CVE_MUN||CLAVE DE MUNICIPIO||Municipality Key|
|CVE_ENT||CLAVE DE ENTIDAD FEDERATIVA||Federal Entity Key|
We will use the following changeset comments: Agregada geometría faltante utilizando datos de INEGI. #Kaart for the missing geometry and Actualicé nombres de vías utilizando datos de INEGI. #Kaart for the road name validation. We will use the changeset source: source=INEGI:MGN:06-2018
Data Transformation Results
OSM XML files will be created on a state by state basis to keep the data as accurate as possible.
Data Merge Workflow
The development of the tools and the actual project will be handled by the Kaart Team with constant collaboration with the local Mexico community.
Once the user selects a task, they will follow the following workflows:
- Download task from tasking manager.
- Correct geometry
- Add missing geometry
- Run JOSM/Validator with the custom validator
- Upload changeset using the comment: Agregada geometría faltante utilizando datos de INEGI. #Kaart
- Use the name layer to manually verify road names
- Run JOSM/Validator with the custom validator
- Upload changeset using the comment: Actualicé nombres de vías utilizando datos de INEGI. #Kaart
You can view changesets using OSMCha.
The email to the Imports mailing list was sent on 2018-09-18 and can be found in the archives of the mailing list at .
The email to the Talk-mx mailing list was sent on 2018-10-2 and can be found in the archives of the mailing list at .