National Road Network
|This is very much a work in progress. Feel free to contact Martijn van Exel (talk) to discuss.|
- 1 About
- 2 Import Plan Outline
- 3 Goals
- 4 Schedule
- 5 Import Data
- 6 Data Preparation
- 7 Data Merge Workflow
- 8 QA
This page proposes a partial, strictly community guided import of road network data recently released by INEGI.
Import Plan Outline
The first step is to take inventory of the available data. Initial investigation suggests that there is a separate dataset for the main road network and the local roads. The inventory will be published here.
After that, we will assess the quality of the data, looking at attributes, topology and geometric accuracy. This will be a combination of spot checking and systematic analysis. The results will be published here.
The third step will be to work on the way conflation with existing OSM data will be achieved. The community will discuss options to reach a decision. Options may include algorithmic pre-processing of the data, a full manual conflation, or an approach driven by the relative quality of existing vs INEGI data per geographic area.
- To enhance the current OSM road network for the country of Mexico with open data made available
- To strengthen the Mexican community
- Data catalog and analysis - Q1, 2015
- Attribute Translation - Q1, 2015
- Pre-conflation discussion and tool development - Q2, 2015
- Release changesets to community for processing - end of Q2, 2015
- Community validation and import - Q3-4, 2015
We hope to be finished by the end of 2015.
Type of license: ADD Link to permission (if required): ADD IF RELEVANT OSM attribution (if required): ADD IF RELEVANT ODbL Compliance verified: ADD
OSM Data Files
The OSM data files will be delivered on a per-area bases in the form of JOSM XML files.
This will be a one-time import using a combination of methods and tools:
- An automated process for converting and pre-processing the data.
- An automated process for conflating the data with the existing OSM data and outputting OSM change files.
- Manual checking, uploading and validation of the resulting OSM change files using the OSM Tasking Manager, via JOSM
Data Reduction & Simplification
Conversion and translation
The source data is in Shapefile format and contains attributes that either need to be translated to OSM tags, or discarded if they are redundant. The attribute mapping is described in detail in the next section. These are the attributes present in the INEGI source data:
Describe the transformations you'll need to conduct, the tools you're using, and any specific configurations or code that will be used in the transformation.
Data Transformation Results
The JOSM XML files will be made available through an instance of the OSM Tasking Manager.
Data Merge Workflow
- The development and testing of the custom tools for conflation will be done by the Telenav OSM team. Intermediary results will be made available to the community to assess. Important decisions regarding attribute mapping and conflation will be evaluated with the community.
- Martijn van Exel (talk) 04:35, 24 March 2015 (UTC) Will arrange for an instance of the Tasking Manager to be made available, and the job defined and created.
- The actual import will be a MX and global community effort, with help and guidance from Telenav where needed. The Telenav Map Analyst team will participate in the import.
Detail the steps you'll take during the actual import.
Information to include:
- Step by step instructions
- Changeset size policy
- Revert plans
Identify your approach to conflation here.
Add your QA plan here.