A7_ASSIETTE/GENERATEUR_SUP_S.shp: table containing plates and surface generators related to easements of category A7 Attributes: • Idass: Identifier of l' plate • IdGen: Identifier of the generator of l' plate • nameAssess: Abbreviated name of l' plate, respecting the SUP naming rules • typeAss: Nature of the plate according to its main purpose and the category of SUP • modeGeoAss: Description of the method used to generate geometry of l' plate • paramCalc: Value of the parameter that made it possible to calculate l' plate when it corresponds to a buffer object • srcGeoAss: Type of map, geographical repository used as a source of georeferencing when digitising geometry • dateSrcAss: Date d’#x27; timeliness of the repository used during georeferencing of the <#x27; object. It is; it is about #x27; indicate the vintage of the source reference data. • attPart: Particular attribute to the class of servitude
__Origin__
Natural or technological risk prevention plans are one of the tools of the State’s risk prevention policy. The RPP is a regulatory prevention record that communicates risk areas to populations and planners and defines measures to reduce vulnerability. A PPR contains geographical data on a given territory that are very useful for crisis management, land or real estate management and urban planning. However, a PPR is not a crisis management operational document. Approved urban planning documents must include the zoning plan of the PPR as soon as it is approved. The Data Standard Risk Prevention Plan (RPP) should be used to exchange data between stakeholders in these different areas. The data standard should improve the availability of geographic data produced under PPRT or PPRN procedures. Some simple use cases have been identified: • define a scenario d' exchange of PPR data using shared structuring rules; • standardise service practices and improve the exchange of data between stakeholders in their different fields of application; • propose technical specifications to structure the spatial data produced at the time of the PPR; development of the PPR; • facilitate the mapping of major risk prevention plans prescribed or approved in a given territory; • disseminate to the public maps representing the regulatory areas of the RPPs and the areas subject to the hazard in a homogeneous manner; • keep track of hazards and issues that have been used to develop the zoning plan and regulations for the RPP. These data are interesting, especially in the event of a revision of the RPP. S' this data needs to be available in the department’s data infrastructure, another issue of this standard is to facilitate the return of PPR data to applications to raise-to-know about risks and to monitor risk prevention policy.
__Partner organisations__
DDT Lozère, DDTM Pyrénées-Atlantiques
__Links annexes__
* [XML metadata view](http://ogc.geo-ide.developpement-durable.gouv.fr/csw/all-dataset?REQUEST=GetRecordById&SERVICE=CSW&VERSION=2.0.2&RESULTTYPE=results&elementSetName=full&TYPENAMES=gmd:MD_Metadata&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ID=fr-120066022-ldd-6460299c-47bc-4a34-b217-5b69763ff5a0)
* [COVADIS data standard: Risk Prevention Plan PPRN PPRT](http://geostandards.developpement-durable.gouv.fr/afficherPageStandard.do?lot=Plan-de-prevention-des-risques-PPRN-PPRT)
* [ESCLANEDES PPRI — Link to enforceable documents](http://www.lozere.gouv.fr/Politiques-publiques/Environnement-Risques-naturels-et-technologiques/Risques-naturels/Les-plans-de-prevention-des-risques-en-Lozere-PPR/Esclanedes)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/300c59de8a31f57660643598b0761ffe7c63e35d)
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.