The Risk Prevention Plans (RPPs) were established by the Law of 2 February 1995 on the strengthening of environmental protection. They are the essential tool of the State in the field of risk prevention. Their objective is to control development in areas at major risk.
PPRs are approved by the prefects and generally carried out by the Departmental Directorates of Territories (DDT). These plans regulate land use or land use through construction bans or requirements on existing or future buildings (constructive provisions, vulnerability reduction work, restrictions on agricultural use or practices, etc.).
These plans may be under development (prescribed), applied in advance or approved.
The PPR file contains a submission note, a regulatory zoning plan and a regulation. Other graphical documents that are useful for understanding the approach (alases, challenges, etc.) can be attached. Each PPR is spotted by a polygon that corresponds to the set of municipalities
concerned with the scope of prescription when it is in the prescribed state; and the envelope of restricted zones when it is in the approved state.
This geographical table makes it possible to map existing PPRTs on the department.
Each PPRT document existing in the geographic table N_DOCUMENT_PPRT is linked using its GASPAR code in the format “ddd[PREF|DDT|DDTM|DREAL]aaaannnn” (AAAA and NNNN correspond to the reference year and serial number of the associated PPR procedure in GASPAR):
1. its administrative procedure for preparing (or revising) managed in the GASPAR application, on the one hand,
2. to its series of numerical constituent geographical data described by the metadata sheet N_PPRT_AAAANNNN (#0001496) on the other hand.
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.