In 1 935 l' Article 2 of the Decree-Law of 30 October 1935 provides for SSPs (Plan de Surface Submersible) to manage the risk of #x27; flooding; These plans are considered to be servitude of public utility affecting the use of the soil and allow the administration of s' to oppose any action or work likely to hinder the free flow of water or the conservation of flood fields.
The flooded areas listed in the SSP come from the highest floods observed in the area of studies. The code of the environment specifies that the SSPs are considered to be a risk prevention plan for flooding (Article L 562-6 of the code of the environment).
The SSPs are being revised. Eventually, they will all be replaced by plans to prevent the risks of flooding (PPRi).
In Haute-Garonne, all SSPs were approved on 6 June 1951 by decree.
__Origin__
The zones have been digitised on plans of d' origins that lack precision and this complicates the setting on current repositories. For any application, reference should be made to the original approved documents.
__Partner organisations__
DDT Haute-Garonne
__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-948435bb-69e6-49ac-bf1e-abece733aaf1)
* [basic URL of wms/wfs services on the Internet](http://ogc.geo-ide.developpement-durable.gouv.fr/wxs?map=/opt/data/carto/geoide-catalogue/1.4/org_38004/b18f124e-9985-46f4-be32-48fa80ae4bd5.internet.map)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/5a1e6eed736de006f2c9b3494c70fa7a40f59479)
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.