Digitizing exposure data for selected areas in Romania

Digitizing Exposure Data for Risk Modeling for selected areas in Romania is a component of the project “Technical Support for the Preparation Of Flood Risk Management Plans for Romania” supported by the World Bank, which has a secondary goal of improving the building and infrastructure features in the OSM database. The proposed import is currently (as of February 2021) at the planning stage. The area of interest (AOI) and specific datasets are defined below.

Goals

The objective of this import is to add datasets and attributes to OSM database of Romania for community use for various development activities.

Schedule

Outline of import plan with approximate time-frame

Import Data

Background

This import is a proposed component of the project assigned to RMSI by the World Bank, National Administration “Romanian Waters” (ANAR), and the Government of Romania (GoR) to develop exposure datasets adequate for risk modeling and mapping for selected Areas of Potential Significant Flood Risk (APSFR) in Romania as defined in first and second cycles of the EU Flood Directives. The data developed as part of this assignment aims to elaborate the existing Flood Hazard Risk Maps (FHRMs) and Flood Risk Management Plans (FRMPs) and, in turn, to enhance the country’s strategic approach to water management, ensuring measures balance competing priorities, are evidence-based, and take into account the interests of different stakeholders through appropriate mechanisms of engagement between public bodies, local stakeholders, and the wider public. The current assignment “Digitizing Exposure Data for Risk Modeling” will generate the necessary exposure data for risk modeling and mapping to be used in the current project. Data sources: The data has been captured using Ortho Photo images (vintage varies from 2015-2018) having 0.50 cm resolution provided by the Government of Romania which has been further updated by high-resolution images available in open source and field survey. Data license: The data imported to OSM will be released under ODbL license.

Area of Interest

Map showing AOIs to be updated in OSM

The AOIs, on which the import will focus, is highlighted in the figure above. In 6,660 km2 only building footprint would be produced, and in 4,231 km2 building footprints along with relevant attributes (Table below) would be produced. Specific attention will be given to existing OSM data, so as to not disturb any existing data.

OSM Data Files

The data files to be imported are in the form of shapefiles for the following exposure categories:

Detailed attributes information for data files to be imported to OSM

Layer Name	Attributes	OSM Tags
Building footprints	Type of Building (Residential, commercial, industrial, kindergartens, schools, high schools, universities, hospitals, police stations, fire stations, city halls, libraries, cultural heritage sites, train stations, ports, airports, bus stations)	building=*
Road Network	Category Width (meters) Number of Lanes	highway=* width=* lanes=*
Railway Network	Category Type Types of Gauge Line (single/ double)	railway=* railway=* tracks=*
Bridges/ Culverts	Width (meters) Number of Lanes	width=* lanes=*
Train Stations	Category Type	railway=*
Airports	Airport Type Airport name	aeroway=* ref=*/ name=*
Ports	Category Type Port name	harbour=yes and seamark:harbour:category=* name=*
Bus Stations	Types of Stations (e.g. Bus Stations/Terminals)	public_transport=*

Import Type

The import will be phased from February to April 2021. The initial imports will focus on areas where no OSM data exists, as a pilot. The response to the pilot will serve as learning for further imports. Once the changes are accepted, further imports adding to the AOIs will be commenced. For this, dedicated user accounts will be used by the team. The data in the form of shapefiles will be converted to GeoJSON format for upload through JOSM tool.

Data Preparation Plan

Data Reduction & Simplification

The import plan is designed so as to not damage or disturb any existing OSM data. To ensure this, the data importing team will download the latest OSM data in the AOIs represented above, and existing data will be filtered out. The cleaned data will then be converted into the requisite format and uploaded to OSM through JOSM tool.

Tagging Plans

All tags essential for each type of layer will be mapped into the layer prior to the upload.

Changeset Tags

We will ensure that any issue arising while the upload is resolved before creating new changesets.

Data Transformation

Detail description of the transformation conducted before the import will be provided under this category. Such as the process involved in converting the data prepared in the form of ESRI shapefiles into GeoJSON format using open-source software like QGIS.

Tools Used

QGIS for data transformation and to filter new data from the one already present in OSM. Java Open Street Map Editor – Validation of data, resolving errors and all conflicts which would then be uploaded to OSM.

Data Merge Workflow Plan

Team Approach

A dedicated team of editors using individual user accounts will work on the imports. All members of the team are well versed with the functionalities, requisite rules, and procedures of OSM platform as well as JOSM tool.

Workflow

1. Documentation of import plan on Wiki Page
2. Establishing contact with local mapping community and import mailing list
3. Follow import plan for cleaned data
4. Collate data in a packet of up to 10,000 features.
5. Check for data consistency (Projection system, etc.)
6. Filter duplicate data from existing OSM data
7. Convert data to GeoJSON format
8. Extract cleaned data to JOSM tool
9. Run validation checks for geolocation, overlaps, and other errors and warnings (as per OSM Guidelines)
10. Address any errors/ warnings identified
11. Once errors are eliminated, import data to OSM

Conflation

Conflation involves combining data from different sources to create data that is better than either of the sources on its own. Conflation will be handled with the utmost care and each and every conflict/ error/ warning reported in the data will be taken care of with high priority.

Team

For any queries, please reach out to osmromania@rmsi.com

Editing Team

(to be updated)

Reviewing Team

Data prepared for import will be suitably made available for review. No data will be uploaded until it has been reviewed. RMSI reviewing team will also be reviewing the data before it is imported into OSM.

Quality Assurance Framework

Quality assurance will help ensure the quality of data import to OSM. Quality assurance will comprise error detection, bug reporting, visualization and monitoring tool, and tag statistics.

Disclaimer

The World Bank does not necessarily own each component of the content contained within this work. Any input dataset or simulation outcome produced in this project does not represent the official position of the World Bank Group. The World Bank does not guarantee the accuracy of the data included in this work. The boundaries, colors, denominations, and other information shown on the outputs do not imply on the part of the World Bank any judgment, endorsement, or acceptance of such boundaries.