PROCEEDINGS of the23rd International Congress on Acoustics
9 to 13 September 2019 in Aachen, Germany

Acoustic noise maps exchange / integration of data within various database systems problems, needs, new possibilities, interoperability
Tomasz MALEC11KFB Acoustics Sp. z o.o., PolandABSTRACT
When creating acoustic maps, it is necessary to use many data sources such as Numeric Model of Terrain(NMT), Building Data Base (BDT), Environmental Data Base (cover, bridge, etc.) and others. For thesedata it is necessary to apply a layer of acoustic data such as traffic parameters and type of pavement forroads/rails, sound power level for industrial source, noise barriers, etc. The sources of these data may vary,including those based on open licenses(OpenStreetMap, Inspire), paid government data (NMT, BDT, etc.).
Each of the above data can be presented in several generally used data formats. All data was integrating in
the noise map calculation programs. This approach blurs the transparency of data. It becomes legitimate toask if it can be standardized so that it is possible to pass data between programs to calculate noise maps or
generally available GIS tools. The work presents an overview of data, tools for their usage, methods oftheir storage. Based on the review, the directions of changes necessary to increase the transparency of thesedata and their interoperability were proposed.
Keywords: noise maps, noise modeling, GIS

1. INTRODUCTION
In accordance with the European Union Directive 2002/49 / EC [1], each member country isobliged to develop acoustic maps. By 2019, the calculation methods are set out in Annex II toDirective 2002/49 / EC [1]. From 2019, the new CNOSSOS-EU calculation method described in
Directive 2015/996 applies [2]. A detailed description of individual methodologies and methods ofcreating acoustic maps can be studied in the CIRCABC platform managed by the EU [3]. All data
developed as part of acoustic mapping should be reported in accordance with the defined mechanism[4]. All of the above issues have been codified. However, there are no clear standards for obtaining,processing and exporting data. One of the few good examples are the guidelines developed at thebeginning of the process of developing acoustic maps [5]. When developing an acoustic map, there
are three data areas to be processed, as shown in Figure 1.
The following chapters describe data sources, problems and needs related to their processing,new possibilities of data acquisition and processing, and directions for further work.

1t.malec@kfb-acoustics.com

7022

Figure 1 – Areas of data processed
2. DATA SOURCETo prepare noise map we need to process a lot of data from different sources of origin. Most data
sources are not adapted to the needs of acoustic mapping and require several stages of processing.
This processing is not standardized and each map maker does it according to his experience andgeneral knowledge. In addition, each noise calculation program has different ways of proc essing andstoring data, which further complicates the situation.
2.1 Exchange / Integration with acoustic data
When creating acoustic maps, it is necessary to use many data sources such as Numeric Model ofTerrain (NMT), Building Data Base (BDT), Environmental Data Base (cover, bridge, etc.) andothers. For these data it is necessary to apply a layer of acoustic da ta such as traffic parameters andtype of pavement for roads/rails, sound power level for industrial source, noise barriers, etc. The
sources of these data may vary, including those based on open licenses(OpenStreetMap, Inspire),
paid government data (NMT, BDT, etc.). Each of the above data can be presented in several
generally used data formats. All data was integrating in the noise map calculation programs. Thisapproach blurs the transparency of data.
A summary of the input data, their formats and sources are presented in Table 1.

Table 1 – Input data, their formats and sourceL.p.

123Objects
Numeric Model of
Terrain (NMT)
Building Data Base(BDT)Road data

Data

Data formats
ASCII; SHP; GeoTiff;

XYZ; contour line; Raster

LAS; ADF; TTN;
DGN; DXF

Surface; Height

Track; Grade line; Surface Typ;
Traffic; Speed; Bridge

SourceGovernment; LIDAR; Dron
Mapping; INSPIRESHP; OSM; GML;

Government;

ASCII; WKT; GeoTiff

OpenStreetMap; INSPIRESHP; CSV; XLS;

Roads administrator; Road

DWG; DGN; DXF;

project; National inspection

WKTservices7023

L.p.

456Objects

Rail data

Industry data

Data

Data formats

SourceTrack; Grade line; Type of Track;

SHP; CSV; XLS;Rail administrator; RailRailhead Roughness; Number of

DWG; DGN; DXF;

project; National inspection

Trains; Speed; Bridge; Rail Joints

WKTservices

Building Surface; Heights; Road; Rail;

SHP; CSV; XLS;

Source: point, line, area; Sound power

DWG; DGN; DXF;

level and spectrum; Work time;

DOC; WKT

Ground Absorption; Foliage; Area

Land-use data

Usage

7Population data

8

Measurements

number of residents
LpA; Spectrum; coordinates; nonacoustic data (meteo; traffic, etc.)

Factory administrator;
National inspection services

SHP; CSV; XLS;

Government; LIDAR; Dron

DWG; DGN; DXF;

Mapping; INSPIRE; Zoning

DOC; WKT; GeoTiff

plan

XLS; CSV; SHP

Government

XLS; SHP; DOC

Reports; Own Measurement

2.2 Problems and needs
The multitude of data, their sources and formats as well as methods and processing tools lead tomany problems. The main need is to develop clear procedures, standardize data and ensure theirinteroperability. The goal is to develop methods that allow the largest possible automation of dataprocessing and validation. Table 2 summarizes the most important problems and needs.

Table 2 – Problems and needs
Problems

Needs

the same data in different formats

standardizationdifferent data formattinginteroperability

different structures of the same dataclear procedures

different attribute names of the same data
no data connections
no data validation methods
different id of the same datano possibility of transition with the model
between noise modeling programs
undefined data export structures
unfiltered data7024

3. NEW POSSIBILITIES
Looking at all processes related to the development of acoustic maps and other areas ofmanagement of a large number of spatial data, methods should be developed that will interact withexisting ones. It seems natural to use good experiences, methods, tools and data structuresdeveloped in OpenStreetMap [6], CityGML [7] and OGC [8] type projects, which could be easily
supplemented with acoustic data and used in the development of acoustic maps.
Another place of new possibilities is the common publication a nd the use of data developed onacoustic maps in other acoustic projects. Currently only final results are available in the form ofmaps and tables. However, there is no access to data accepted for calculations and processed foracoustic needs. This often results in the re-generation of the same data with other acoustic
assessments of the same noise sources and prevents data validation in the process of their self improvement (eg improvement of geometry at each next noise counting process).
Dissemination of drones as a tool for collecting spatial data can significantly accelerate theprocess of creating maps and refreshing geometry data.
When looking at the number of data processed, one should also consider using Big Data
processing algorithms that would allow to automate data validation processes.
Another field for creating new tools is creating a matrix of source rankings, which can enable
quick estimation of the direction of changes without the need to perform repeated time -consuming
calculations.
The last field of new opportunities is the attempt to automate the mapping process based oncontinuous measurements and constant access to databases.
Table 4 summarizes the most important new possibilities related to the development of acoustic
maps.

Table 4 – New possibilities
New possibilities
the use of LOD, OSM, WKT, etc. data structures for data storage
scanning of key places with difficult geometry using a drone
addition of subsequent data layers to existing ones
data processing based on Big Data algorithms
data validation by users based on methods developed in opensource environments
widespread use of data already validated for other acoustic projects
database integration
creating a matrix of source rankings for control points
estimating directions of changes based on calculations on the source ranking matrices (without additional calculations inacoustic software)
Automation of mapping based on continuous measurements and constant access to databases

4. INTEROPERABILITY
Definition: “Interoperability is a characteristic of a product or system, whose interfaces arecompletely understood, to work with other products or systems, at present or in the future, in either
implementation or access, without any restrictions” [9]When creating the data structure associated with the acoustic map, it is necessary to maintain thedata interoperability. Currently, we all process data without a well-developed homogeneous
structure and processing methods. At the moment, even the usual transfer of d ata from one program
to the other noise calculation program becomes a problem.

7025

A good starting point would be the transition to open data formats and open environments fortheir processing. An example of this is the recent work of French researchers who have successfully
attempted to create an acoustic map in an open source environment [10]5. ACTION PLAN
Based on the above review, the following steps are proposed:x Step 1: overview of used data,x Step 2: review of data structures,x Step 3: definition of needs (what data are necessary, in what format, in what detail, etc.) ,x Step 4: review of open data structures (OSM, CITYGML, WKT, etc.)
x Step 5: creation of basic data structures,x Step 6: standardization of data processing,x Step 7: creation of data validation methods,
x Step 8: development of final standards, guidelines and methods of data processing
The development of uniform standards, guidelines and methods will allow for a correct
assessment of the scale of the noise problem and will enable a reliable assessment of the results
between individual countries. Currently, the work is focused on the creation of new assessment
methods, forgetting that the result of acoustic mapping is strictly dependent on the input data andmethods of their processing. Without standardization in this area, each map will be the original
project of its creator and it will not be possible to reliably compare results in the next edition of themaps.

REFERENCES
1. Directive 2002/49/EC of the European Parliament and of the Council of 25 June 2002 relating to
the assessment and management of environmental noise - Declaration by the Commission in theConciliation Committee on the Directive relating to the assessment and management ofenvironmental noise http://data.europa.eu/eli/dir/2002/49/oj
2. Commission Directive (EU) 2015/996 of 19 May 2015 establishing common noise assessment
methods according to Directive 2002/49/EC of the European Parliament and of the Council (Textwith EEA relevance) http://data.europa.eu/eli/dir/2015/996/oj
3. Plattform CIRCABC - Environmental Noise Directive (2002/49/EC)
https://circabc.europa.eu/w/browse/7ee2560e-7a0d-4e16-8c61-f3a05ee2dd6f
4. Technical report No 9/2012- Electronic Noise Data Reporting Mechanism - handbook fordelivery of data in accordance with Directive 2002/49/EC, EEA
https://www.eea.europa.eu/publications/noise-handbook/#additional-files
5. Good Practice Guide for Strategic Noise Mapping and the Production of Associated Data on NoiseExposure, European Commission Working Group Assessment of Exposure to Noise (WG-AEN),
WG-AEN 004.2007.doc, Version 2 13th August 2007
6. https://wiki.openstreetmap.org/wiki/Main_Page
7. https://www.opengeospatial.org/standards/citygml
8. http://www.opengeospatial.org/
9. https://en.wikipedia.org/wiki/Interoperability
10. E. Bocher, G. Guillaume, J. Picaut, G. Petit, N. Fortin, NoiseModelling: An Open Source GISBased Tool to Produce Environmental Noise Maps, ISPRS Int. J. Geo-Inf. 2019, 8(3), 1307026