Simple download service (Atom) of the data package: Plan for the prevention of technological risks of the Raffinerie du Midi in Côte-d’Or
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: Plan for the prevention of technological risks of the Raffinerie du Midi in Côte-d’Or API!
The COVADIS Data Standard on Technological Risk Prevention Plans (PPRTs) contains all the technical and organisational specifications for the digital storage of geographical data represented in the Risk Prevention Plans (RPPs). There are four technological risks: nuclear risk, industrial risk, risk of transport of hazardous materials and risk of dam failure. The Risk Prevention Plans (PPR) were established by the Act of 2 February 1995 on strengthening the protection of the environment. The PPRTs contain three categories of information: • Regulatory mapping translates into a geographical delimitation of the territory concerned by the risk. This delimitation defines areas in which specific regulations apply. These regulations are easement and impose requirements varying according to the hazard level to which the area is exposed. The areas are represented on a zoning plan that fully covers the study area. • The hazards at the origin of the risk are contained in hazard documents which may be inserted in the presentation report or annexed to the RPP.
These documents are used to map the different intensity levels of each hazard considered in the risk prevention plan.
• The issues identified during the preparation of the RPP can also be annexed to the approved document in the form of maps.
The PPRT of the Raffinerie du Midi was approved on 28 November 2016.
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.