Mexico Road Name Project

From OpenStreetMap Wiki
Jump to navigation Jump to search



Mexico Road Name Project will use Marco_Geoestadístico_Nacional_(MGN) datasets which are shapefiles from the INEGI datasets covering Mexico.

About

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.

Project Outline

  1. Determine which INEGI data set is most effective → MGN (June 2018)
  2. Develop tools to efficiently and accurately convert .shp files to .osm.pbf and accurately map attributes
  3. Develop processes to edit and validate data using JOSM (including custom paint styles and validators)
  4. Create projects for each state using an instance of the OSM_Tasking_Manager

Goals

To contribute up-to-date data for the road networks of Mexico by updating missing geometry and road names.

Schedule

  • 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)

Progress

Mexico City

Tasking Manager

  • Started Mapping: December 12, 2018
  • Finished Mapping: January 8, 2019

Oaxaca

Tasking Manager

  • Started Mapping: December 4, 2018
  • Finished Mapping: February 18, 2019

Yucatán

Tasking Manager

  • Started Mapping: March 19, 2019
  • Finished Mapping: April 30, 2019

Quintana Roo

Tasking Manager

  • Started Mapping: March 25, 2019
  • Finished Mapping: April 30, 2019

Querétaro

Tasking Manager

  • Started Mapping: July 10, 2019
  • Finished Mapping: September 10, 2019

Colima

Tasking Manager

  • Started Mapping: July 10, 2019
  • Finished Mapping: August 9, 2019

Michoacán

Tasking Manager

  • Started Mapping: August 14, 2019
  • Finished Mapping: On Going

Guanajuato

Tasking Manager

  • Started Mapping: October 10, 2019
  • Finished Mapping: On Going


Data

Background

States and their id's

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:

Directory Contents
catalogos PDF and .txt files describing the data sets
conjunto de datos "Data Sets" .shp files
metadatos Metadata information

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).

Data source site: MGN data set
Data license: Terms of Use
Type of license (if applicable): LIBRE_USO_MX
OSM attribution (if required): INEGI
ODbL Compliance verified: yes

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).

Methods

  • 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 Preparation

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:

Arguments

  • Shapefile
  • Translation file (compatible with ogr2osm)

Tools/Modules

Process

  1. Executes spatial analysis to extract Shapefile data within each state into individual Shapefiles
  2. Converts Shapefile to .osm and translates attributes to OSM tags
  3. 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.

Tagging Plans

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

Changeset Tags

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

Prior to using the tool described above, we make sure the data is encoded using ISO-8859-1 and is projected to WGS84 using QGIS.

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

Team Approach

The development of the tools and the actual project will be handled by the Kaart Team with constant collaboration with the local Mexico community.

References

Workflow

Once the user selects a task, they will follow the following workflows:

Missing Geometry

  1. Download task from tasking manager.
  2. Correct geometry
  3. Add missing geometry
  4. Run JOSM/Validator with the custom validator
  5. Upload changeset using the comment: Agregada geometría faltante utilizando datos de INEGI. #Kaart

Road Names

  1. Use the name layer to manually verify road names
  2. Run JOSM/Validator with the custom validator
  3. Upload changeset using the comment: Actualicé nombres de vías utilizando datos de INEGI. #Kaart

QA

QA will be incorporated into the OSM_Tasking_Manager's validation. We will be using custom validators as well.

You can view changesets using OSMCha.

See also

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 [1].

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 [2].