Umbria/Import/Edificato

Import edificato dell'Umbria (DRAFT)

This is an import of buildings extracted from the DataBase di Sintesi Nazionale (DBSN) issued by the Istituto Geografico Militare (IGM) and containing the most significant information of the entire Italian territory. The import will only concern the territory of the Umbria region and is currently at the planning stage.

Goals

The goal of the import is to import the buildings of the Umbria region, starting with the areas where the lack of mapping by volunteers is greatest and continuing to the municipalities where a concrete contribution to the map will be made.

Schedule

The import will presumably start in October 2023 and continue until the target is reached, expected within six months.

Import Data

The database, in GeoDatabase format, is subdivided according to provincial administrations, so only zip files relating to the Umbrian provinces, Perugia and Terni, will be downloaded.

Background

Data source site: https://www.igmi.org/it/dbsn-database-di-sintesi-nazionale
Data license:Open Data Commons Open Database License (ODbL) ver. 1.0 [1]
ODbL Compliance verified: yes (Import/ODbL_Compatibility)

OSM Data Files

Data files prepared for the import are available in: https://github.com/arcanma/Umbria_buildings_import/tree/main/Umbria_buildings

Import Type

Buildings object of import will be splitted according to the municipal administrative limits, each municipality will be imported individually using JOSM.

Data Preparation

Data Reduction & Simplification

The data relating to the built environment (layer "edifc") will be extracted from the files relating to the provinces of Perugia and Terni using QGIS , the geometries that have OSM as source (attribute meta_ist=03) will be eliminated, then they will be saved in GeoPackage format splitting them according to the municipal administrative limits (layer "comune"), thus obtaining 92 files.

Tagging Plans

The transformation was prepared according to the specifications of the DB (https://www.igmi.org/dbsn_supporto/dbsn/dbsn_specs.pdf) and also according to the actual correspondence in the elements object of the import, the DB is a collector of data provided by different institutions and not all of them used the attributes in the same way.

Changeset Tags

Fill in the values your changesets will use.

Key	Value
comment	Import Fabbricati Comune di <nome comune>
type	import
source	DataBase di Sintesi Nazionale-Istituto Geografico Militare
source:url	https://www.igmi.org/it/dbsn-database-di-sintesi-nazionale
source:date	age of dataset at time of import, if known.
import:page	link to this wiki page
source:license	Open Data Commons Open Database License v1.0 (https://spdx.org/licenses/ODbL-1.0.html)

Data Transformation

Using the ogr2osm tool, each file will be converted to osm format and at the same time the labels of each object will be converted according to the scheme shown in the table below:

Original Tag	Imported	Description	OSM Tag	Note
fid	No	Primary key
OBJECTID	No	Object ID
edifc_uso	Yes	Building use	building / amenity / man_made / tourism / etc.	1
edifc_ty	Yes	Building type	building
edifc_sot	Yes	Underground building	location=underground + building:levels	2
classid	No	ClassId
edifc_nome	Yes	Building name	name
edifc_stat	Yes	Building status	Building + construction / ruins	3
edifc_at	No	Building height
scril	No	Scale Level
meta_ist	No	Data source
edifc_mon	no	Monumental building
shape_Leng	No	Perimeter
shape_Area	No	Area
check_geom	Yes	To be checked on regional border	building + fixme:geometry
comune_ist	No	Municipality code
comune_nom	No	Municipality name

1. The label will be assigned according to the type of use detected, possibly even combining several labels. See the conversion file for more details.
2. If the building is classified as underground it will be set location=underground + building:levels=0, the label fixme:building is also added to indicate a necessary check.
3. If the edifc_stat attribute has value 01 (Under construction) the labels will be: building=construction + fixme:building="resurvey construction type and status", if it is intended for a specific use this will be assigned to the construction label. If instead the edifc_stat attribute has value 02 (Ruins) the labels ruins=yes and fixme:building="resurvey status" will be added.

Data Transformation Results

The transformation rules files is available here: edificato.py, the resulting files are available here: Umbria_buildings.

Data Merge Workflow

Team Approach

The import process will be performed by the user Arcanma, using the account arcanma-import

References

When importing, buildings already present in OSM will be taken into account, in case of matches priority will be given to what is already present. During the transformation for buildings with attributes that may have generated mismatched tags, fixme tags have been added to resolve any inaccuracies before import. The target area of the import will be downloaded into JOSM to do an offline validation prior to import to avoid interference between the imported objects and what is already present in OSM.

Workflow

For each municipality the following steps will be taken, starting with those with less than 100 buildings mapped on OSM per 1000 inhabitants (detectable by Umbria/Statistica_Elementi), so that conflicts can be checked fairly quickly and a consistent contribution to the map can be made.

1. Open with JOSM the file obtained in the previous step, then download the buildings already included in OSM for the corresponding municipality using the Overpass API, through the plugin Conflation and JOSM Validator check which objects are already present, keeping the one already present, in case of evident wrong or not correctly aligned geometry only the geometry correction will be done, keeping the labels.
2. For buildings not included in OSM, the presence of fixme, fixme:classify, fixme:building or fixme:geometry tags will be checked, in which case the warning will be resolved by comparison with aerial photos and other information sources if necessary, then the relevant fixme tag will be removed. If the existence and status of the building cannot be determined with sufficient certainty, it will not be imported.
3. The remaining buildings will be those subject to the import process, before proceeding the area will be downloaded to JOSM to check with the integrated Validator for possible conflicts with other elements already in OSM and will be resolved before import.
4. Once prepared the data will be loaded considering a limit of 5000 buildings per changeset, so normally it will be one changeset per municipality except for larger municipalities where there will be more changesets.

All changeset ids will be recorded, in case any anomaly is found during import or afterwards it is possible to revert by changeset id, checking buildings with version>1 to exclude from revert those which have been changed later.

Conflation

See step 1 paragraph above

QA

See steps 2 and 3 paragraph above

See also

The post to the community forum was sent on YYYY-MM-DD and can be found here

(Category:Import)