POS 2009 again effective since 18/01/2017 (PLU cancelled by the Administrative Court of Toulouse).
The surface requirements of the land use plan (POS) are digitised in accordance with the national requirements of the CNIG. The requirements of a POS are defined in the \#x27; article R123-11 of the code of l' urban planning and are in the form of \#x27; information that appears on the graphical documents of the POS. A requirement superimposed on an area of the document d' urbanism generally exerts an additional constraint on the settlement of the area.
In this dataset are the surface requirements of TYPE 01 (classified wooded areas) and 05 (reserved locations) if they appear on the POS graphical documents.
__Origin__
The perimeter of a prescribed PPR is usually provided in the prefect’s prescription order. The perimeter d' exposure to risks — or regulated perimeter — corresponds to the \#x27; geometric aggregation of l' all the restricted zones listed in the same PPR. The perimeter of the study corresponds to the envelope in which the hazards were studied.
__Partner organisations__
DDT Ariège
__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-jdd-525390b4-19d0-4a19-90f3-074df61d80c8)
* [COVADIS data standard: Scope of PPRN](http://geostandards.developpement-durable.gouv.fr/afficherPageStandard.do?jeu=N_PERIMETRE_PPRN_AAAANNNN_S)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/22dcb6488e020f46684b45dc94c95d8a909d0d03)
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.