An Open Street Maps INSPIRE databases story a

An Open. Street. Maps & INSPIRE databases story a technical experience with transport network

Introduction of the story • Spanish INSPIRE TN database ▫ Sources: Cadastre (streets), Statistical Office (street names), National Mapping Agency (roads). ▫ Auxiliary sources: Regional and Local Mapping Agencies. ▫ Features: �INSPIRE oriented (with some extensions) �WMS & WFS implemented base on this database � 3 D �Network topology �Postgre. SQL ▫ We have invested a lot of human and economic resources.

But we have to face a problem • The complex updating processes: ▫ Many organizations with competences in TN. ▫ Distributed task. ▫ No software tools available for a very complex data model.

What if we use Open. Street. Maps? • They have an open software environment for editing and updating geometries. • It’s a very success and well known project (easy to sell the idea). • It’s very well supported project -including the EEA : ( -.

And even more… • • It could be a key source of VGI. It could be a source for data quality evaluation. It could be a source for detecting changes. It could be a source for data we don’t have (as road directions). • It could be a way to disseminate official data. ▫ So the system should work in both directions.

So we started to work • First attempt: ▫ Contacting with the Spanish OSM association. ▫ But it is a group of geeks �They don’t have an organizational structure. �We couldn’t hire them.

So we started to work • Second attempt: ▫ A Spanish company had worked for Eurostat in a project to compare OSM vs Euro. Regional. Maps railways data. So, at least, they knew the OSM data model. ▫ Then we decided to contract them.

The project • “Defining a transformation protocol and a gateway from Spanish INSPIRE TN and OSM databases”. • Budget: 60 k € • Subcontractor: Guadaltel

The architecture GATEWAY TN - OSM INSPIRE TN DB OSM TN DB EDITOR SW

The software • Kettle tool for initial migration ETL processes (Pentaho configuration). • Tile. Calculator library for inclusion in the bulk load process for OSM data model. • Application to execute migration and synchronization processes from INS TN to OSM and from OSM to INS TN. • i. D OSM editor.

The outcomes of the project • Feasibility of the use of OSM environment as a collaborative platform for the maintenance of INS TN database. • Migration protocols allow the communication and track changes between INS TN and OSM databases. • Performance improvements have been needed due to the big amount of data to be migrated. • OSM data model implements a completely denormalized structure, so errors in the insertion can be reverted to INS TN database. ▫ OSM open data model allows a free insertion and edition of tags and values non standardized for TN.

Next steps • Improving INS TN geometries to facilitate OSM migration process. • Enhancing massive loads process. • Reusing of existing tags in OSM to improve the INS TN mapping. • Developing a plugin for OSM i. D editor to manage TN specific data and logic. • Communications, dissemination, training.

OSM, a threat or an opportunity? • A threat ▫ They are taking the place of the NMCAs

OSM, a threat or an opportunity? • An opportunity ▫ Spreading official data

OSM, a threat or an opportunity? • An opportunity ▫ Using OSM data �Only if the contributor declares their data as “public domain”. �If not, the OSM licenses is more restrictive than IGN one. �You can use OSM for commercial porpouses.

“if you can’t beat them, join them”