Import/Catalogue/Address import for Torino
- 1 About
- 2 Import Plan Outline
- 3 Goals
- 4 Schedule
- 5 Import Data
- 6 Data Preparation
- 7 Data Merge Workflow
- 8 QA
This page talks about importing addresses using the data provided by the Municipality of Torino (Italy).
Import Plan Outline
This import goal is to use the high-quality dataset provided by the Municipality of Torino in order to steadily improve the addresses available in OSM. It will not be a blind import, data will be checked.
The import took place from 13 to 15 March 2017.
Address format in Torino
House numbering in Torino follows the European scheme.
An address in Torino is determined by its streetname and housenumber.
A housenumber is also unique per street.
Housenumbers can include a subordinate. These are noted with suffix letters (e.g. in "7a", "a" is the subordinate). Subordinates usually arise when a new house is build between existing houses with subsequent housenumbers. E.g. when a house is build between numbers 7 and 9, the new house will most likely get number 7a (since even numbers are reserved for the other side).
Data source site (as at March 2017): http://aperto.comune.torino.it/?q=node/504
Data license: http://www.dati.gov.it/iodl/2.0/
Type of license: IODL v2.0
OSM attribution: http://wiki.openstreetmap.org/wiki/Contributors#Torino
ODbL Compliance verified: yes
From the IODL 2.0 license (in Italian): "indicare la fonte delle Informazioni e il nome del Licenziante, includendo, se possibile, una copia di questa licenza o un collegamento (link) ad essa."
Translation: "state the data source and the licensor name, including, if possible, a copy of this License or a connection (link) to it."
It should be enough to add the attribution in the Contributors page, like already done for Venice.
The dataset will be normalized and data already existing will be put aside.
The existing OpenStreetMap data are not present in the dataset and will be analyzed and merged later.
The data is presented as a csv file. This csv file consists in a collection of punctual elements, one for each housenumber.
Each row has the keys:
- COD_CIVICO: incremental number for internal reference
- COMUNE: city name
- VIA: street name
- CIVICO: house number
- CIRCOSCRIZIONE: district
- CAP: zip code
- COORDINATA_X: longitude
- COORDINATA_Y: latitude
The tags that will be used in the final upload are addr:housenumber, addr:street, addr:postcode.
The tags will be as follows:
- addr:housenumber will contain the housenumber.
- addr:street will contain the street name normalized to follow Italian conventions.
- addr:postcode will contain CAP.
Dedicated upload account
The account used for the import is Ale_Zena_IT-import
The original csv file was imported in a Postgis database table. The projection is EPSG:4326 (WGS84 latitude-longitude).
The table was joined with the italian copy of the OSM database (updated several times a day), searching for duplicates.
The points already in OSM (normalized street name and number) where marked and not considered for ther import phase.
Data Merge Workflow
Addresses already in OSM can be extracted using the following Overpass query:
<code> <osm-script> <query into="comune" type="area"> <has-kv k="admin_level" v="8"/> <has-kv k="name" v="Torino"/> </query> <union> <query type="node"> <area-query from="comune"/> <has-kv k="addr:housenumber"/> </query> <query type="way"> <area-query from="comune" /> <has-kv k="addr:housenumber"/> </query> <item/> <recurse type="down"/> </union> <print mode="meta" /> </osm-script> </code>
In order to have manageable data, it will be uploaded a changeset for each CAP (zipcode) zone (there are 36 zones in total).
Before of each upload, points outside the city boundary will be deleted (coordinate error).
In case of import problem the changeset will be reverted using the JOSM Reverter Plugin
A project has been set up at OSM tasking Manager to manage further adjustments raising from names inconsistency.
After the import, addr:street names could be slightly different than street names.
These differences should be catched using OSM Inspector (map already centered on Torino).
The result can be used to locate areas where streets are missing.
Missing roads will be created in JOSM using PCN 2012 areal images.
The result can be used to derive street names for unnamed streets when all the nodes along the street has the same addr:street value.
Missing road names will be identified using the OpenStreetMap NoName Map Overlay:
OSM Inspector can also be used to find these streets.