Colombia/Project-Road Names

From OpenStreetMap Wiki
Jump to navigation Jump to search



Colombia Road Name Project will use datasets which are shapefiles from the IGAC covering Colombia. Permission has be given to use this data.

About

Kaart will use data provided by Colombia's Instituto Geográfico Agustín Codazzi with OSM.
Kaart will continue efforts to ensure effective communication with Colombia's OSM community throughout the project process.

Project Outline

  1. Develop tools to efficiently and accurately convert .shp files to .osm.pbf and accurately map attributes
  2. Develop processes to edit and validate data using JOSM (including custom paint styles and validators)
  3. Create projects for each district using an instance of the OSM_Tasking_Manager

Goals

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

Schedule

  • Manual editing and validation using JOSM - April 2020 → August 2020

Progress

Project Completion Date
Bogota 11 June 2020
Valle del Cauca 13 May 2020
Atlantico 15 May 2020
Bolivar 22 May 2020
Norte de Santander 3 June 2020
Cundinamarca 6 July 2020
Santander 9 June 2020
Tolima 12 June 2020
Meta 17 June 2020
Magdalena 26 June 2020
Cesar 23 June 2020
Caldas 15 July 2020
Cordoba 30 June 2020
Risaralda 18 June 2020
Huila 15 July 2020
Narino 13 July 2020
Quindio 17 June 2020
Sucre 22 July 2020
Putumayo 20 July 2020
Cauca 4 August 2020
Guaviare 23 July 2020
Choco 27 July 2020
Casanare 30 July 2020
La Guajira 6 August 2020
Caqueta 4 August 2020
Boyaca 10 August 2020
Arauca 10 August 2020

Data

OSM Data Files

OSM data will be processed and delivered on a state by state basis.

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


Our team developed a tool to automate the process of converting the shapefile data.

Arguments

  • Shapefile
  • Translation file (compatible with ogr2osm)

Tools/Modules

Process

  1. Executes spatial analysis to extract Shapefile data within each department 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 data source.
Once we have converted the data into OSM_XML for a department, we can then create an OSM_Tasking_Manager project for the department 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.


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 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 Colombia 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 changes using Agregada geometría faltante utilizando datos de IGAC. #Kaart
  6. Source tag IGAC

Road Names

  1. Use the name layer to manually verify road names
  2. Run JOSM/Validator with the custom validator
  3. Upload changes using Actualicé nombres de vías utilizando datos de IGAC. #Kaart
  4. Source tag IGAC

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.