The plans for the prevention of technological risks (PPRT) were established by the Act of 2 February 1995 on strengthening the protection of the environment. They are the key instrument of the State in the field of risk prevention. Their objective is to control development in areas exposed to a major risk. PPRTs are approved by the prefects and generally carried out by the departmental directorates of the territories (DDT). These plans regulate land use or land use through construction prohibitions or requirements on existing or future buildings (constructive provisions, vulnerability reduction work, restrictions on use or agricultural practices, etc.).These plans may be under development (prescribed), implemented in advance or approved.The PPRT file contains a presentation note, a regulatory zoning plan and a regulation. Other graphic documents that are useful for understanding the approach (e.g. hazards, issues, etc.) can be attached. Each PPRT is identified by a polygon that corresponds to the set of affected municipalities within the scope of the prescription when it is in the prescribed state; and the envelope of restricted areas when it is in the approved state. This geographical table allows to map existing PPRTs on the department. Each PPRT document existing in this geographical table is linked with its GASPAR code of format “ddd[PREF|DDT|DDTM|DREAL]aaaannnn” (AAAA and NNNN correspond to the reference year and serial number of the associated PPRT procedure in GASPAR): 1. its administrative procedure for the preparation (or revision) managed in the GASPAR application, on the one hand, 2. its set of constituent spatial data as described in the metadata sheet N_PPRT_AAAANNNN, 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.