Correction of INEGI roadnet

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Correction of INEGI roadnet
· Afrikaans · Alemannisch · aragonés · asturianu · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · Bân-lâm-gú · Basa Jawa · Baso Minangkabau · bosanski · brezhoneg · català · čeština · dansk · Deutsch · eesti · English · español · Esperanto · estremeñu · euskara · français · Frysk · Gaeilge · Gàidhlig · galego · Hausa · hrvatski · Igbo · interlingua · Interlingue · isiXhosa · isiZulu · íslenska · italiano · Kiswahili · Kreyòl ayisyen · kréyòl gwadloupéyen · Kurdî · latviešu · Lëtzebuergesch · lietuvių · magyar · Malagasy · Malti · Nederlands · Nedersaksies · norsk bokmål · norsk nynorsk · occitan · Oromoo · oʻzbekcha/ўзбекча · Plattdüütsch · polski · português · português do Brasil · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · Tiếng Việt · Türkçe · Vahcuengh · vèneto · Wolof · Yorùbá · Zazaki · српски / srpski · беларуская · български · қазақша · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · मराठी · हिन्दी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 吴语 · 粵語 · 中文(繁體)‎ · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް

1. An investigation was made about PostGIS or QGIS solutions to resolving road network DIS-connectivity. 2. A comparison of the RNC & OSM datasets was made to determine if any gaps exist between datasets.

Issue

Road network dis-connectivity issues were identified when examining the INEGI dataset "Información Vectorial de Localidades Amanzanadas y Números Exteriores" road network data. For the Mexican City Aguascalientes, 14,401 dangling ends/unconnected roads were identified:

Road Dis-connectivity in Aguascalientes
Image2015-2-4 16-36-41.png Image2015-2-4 16-37-18.png
Image2015-2-4 16-41-4.png Dangling ends were identified at all of the roadway intersections in the Aguascalientes dataset.


Issue Resolution (Proposed)

The proposed solution to resolve the dangling ends in the roadnet data is to leverage the PostGIS Topology extension. The thought is that by loading the data into a PostGIS Topology schema that the dangling end errors would be corrected.

PostGIS Topology Loading Methodology With Aguascalientes Data

The leveraging of PostGIS topology was started on a micro-level by only focusing on the Aguascalientes road edges. This work was done by:

  1. Enabling the postgis_topology and postgis Postgres extensions into a local machine's database (topology_test)
  2. Loading the 010010001v.shp into topology_test database as 'aguacalientes_roads'
  3. Correcting any st_issimple errors by running a query that creates new geometries using the st_unaryunion function.
  4. Loading the data to PostGIS Topology
a. Create topology schema (roads_topology)
b. Add topology column to 010010001v
c. Setting topology value to 010010001v topology column and creating topology nodes, edges, faces, etc.

The loading can be observed in the following SQL script: load_to_topology.sql

Result

The loading of the INEGI Rural/Urban data to a PostGIS topology schema will eliminate the the dangling edges that were observed with the raw INEGI dataset. Unfortunately, due to data integrity issues (intersecting ways, coincident edges, etc), there would be some edges that would not be populated. But the number of edges appears to be null

Aguascalientes After Loading to PostGIS Topology
Image2015-2-5 9-53-45.png Image2015-2-5 9-54-12.png Considerably fewer dangling edges identified in data.

Only 1,932 dangling edges found

Image2015-2-5 9-55-46.png Dangling edges identified are true dangles.
Image2015-2-5 9-58-46.png Image2015-2-5 9-59-26.png Errors in the loading edges has resulted in some edges not being populated


Contribution by: KristenK