Zoning composed of all territorial coherence scheme (SCOT) perimeters
The Law on Solidarity and Urban Renewal (SRU Law) of 13/12/2000 provides for the establishment, as of 1 January 2002, of territorial coherence schemes, which replace the master plans. Drawn up by the elected representatives, at the level of the basin of life, housing or employment, they will be designed to express the overall strategy of the agglomeration and to set out the main choices in terms of housing, balance between natural and urban areas, infrastructure and commercial urban planning. In peri-urban areas, in the event that SCOT does not exist, any urbanisation area will be blocked, unless the prefect agrees, within a radius of 15 km around the municipalities of the agglomeration if it has more than 15,000 inhabitants.
These data correspond to a definition of a macroscopic SCOT: the content of the SCOT which includes a presentation report, a development and sustainable development project (DDAP), regulation and guidance document is not covered in this data.
SCOTs that are no longer enforceable are to be archived with a ‘cancelled’ state by adding an end-of-validity date.
This national sheet corresponds to a part of the metadata contained in the COVADIS standard. This standard has been developed in a generic and non-milled manner (its name and definitions do not mention any dates) to apply to different versions of the data. The local GeoBase layers must be suffixed _aaaa, ayya corresponding to the vintage of the data.
This sheet is likely to evolve as a result of the second Law on the Grenelle of the Environment.
This data is replicated internally on Postgres in the schema: c_amgt_urb_zon_plan/n_scot_zsup_034
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.