Simple download service (Atom) of the data package: Noise in the Environment — Strategic Noise Mapping in the Department of Puy-de-dome — 2018 — Data from Infrastructure Noise Areas (Fer and Roads) — 3 rd deadline
Open data API in a single place
Provided by BUREAU DE RECHERCHES GÉOLOGIQUES ET MINIÈRES
Get early access to Simple download service (Atom) of the data package: Noise in the Environment — Strategic Noise Mapping in the Department of Puy-de-dome — 2018 — Data from Infrastructure Noise Areas (Fer and Roads) — 3 rd deadline API!
Noise maps are defined by Article L.572-3 of the Environmental Code. The lot contains the geographical data of the noise zones, they are interoperable in accordance with Directive 2002/49/EC of 25 June 2002, transposed into French law by Articles L.572-1 to L.572-11 of the Environmental Code.
Noise level zones describe a noise exposure situation based on a noise indicator or area affected by noise. They are used primarily for the preparation of strategic noise maps pursuant to Article R.572-5 of the Environmental Code.
The published data relate to the Drôme’s land and rail infrastructure. The noise levels emitted by a given infrastructure over an average day are assessed using numerical models producing isophone curves translated into noise zones, according to the recommended index for all modes of transport at European level, i.e. the Lden index and the Ln index.
You will find in this lot for each of the infrastructures the data:
— of “type a”: areas exposed to noise according to the indicators Lden (full day) and Ln (night) in steps of 5 dB(A);
— of “type b”: noise-affected sectors defined in the Prefectural Sound Classification Orders.
— of “type c”: isophone curves for exceeding the limit values in Lden (full day) and Ln (night).
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.