Simple download service (Atom) of the dataset: Areas exposed to noise on the Charente-Maritime (areas of type A — index of type LN) Prefectural decree n°18-1536 of 24 July 2018
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 dataset: Areas exposed to noise on the Charente-Maritime (areas of type A — index of type LN) Prefectural decree n°18-1536 of 24 July 2018 API!
Type A noise zones — LN type index.
Layer produced by GIS workshop (April 2018) by compiling type A noise zones related to road infrastructure (CEEREMA report on "Strategic noise maps of the Charente-Maritime department (017) Major infrastructure not granted; Deadline 3: 2017-2022") and motorway ("Non-technical summary of the sound environment mapping of the ASF network on the Charente Maritime department (17) in 2016")
Noise zones are geometric elements of the strategic noise map.
These maps also referred to as “type a maps” represent for the reference year in the form of isophone curves, the areas exposed to more than 55 dB(A) according to the Lden indicator (case of this geographical layer) and to more than 50 dB(A) according to the Ln indicator, with a step of 5 in 5 dB(A).
The noise level on a noise map is represented on the basis of regulatory indicators: the “Ln” (Level night) and the “Lden” (Level day-evening-night) which are harmonised indicators at European level.
The Ln is the average sound level for the night period (22h-6h).
The Lden is the 24-hour weighted average sound level to account for the perceived discomfort with the same noise level, which is greater in the evening and at night compared to the day.
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.