Zoning of the planning documents of Lorient Agglomeration

Open data API in a single place

Provided by etalab

Get early access to Zoning of the planning documents of Lorient Agglomeration API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2021.12.27 09:48
Created
2021.12.27
Available languages
French
Keywords
dpds, amenagement-urbanisme-zonages-planification, plans-locaux-durbanisme, zonages, geoportail-de-lurbanisme, urbanisme, donnees-ouvertes, plu, documents-durbanisme, urbanisme-et-foncier-planification-et-documents-durbanisme
Quality scoring
195

Dataset description

Zoning of the POS (Plan d’Occupation des Sols) and the PLUs (Local Urbanisation Plan) of the 25 member municipalities of Lorient Agglomeration. Zoning covers the entire communal territory with the exception of areas covered by a Backup and Development Plan. The Urban Planning Code defines 4 main types of areas (R.123-5 to 8): urban areas (U), to be urbanised (AU), agricultural (A) or natural and forestry (N). Each zoning is attached to a written regulation setting different rules according to the intended purpose of the construction (R.123-9). This database aggregates municipal data that comply with the National Prescriptions of the CNIG (National Geographical Information Council). **Collection context** The GIS (Geographic Information System) mission works the data of the municipalities so that they can comply with national and European standards and aggregate them throughout the agglomeration. Zoning is sectors to which a special regulation applies which corresponds to the objectives set out in the urban planning document resulting from the various studies carried out in the territory by the municipalities, the departments of Lorient Agglomeration and/or the design offices. Sources: Lorient Agglomeration, DDTM, member municipalities, design offices. **Collection method** Scanning from the cadastre repository (PCI Vector). Zoning is usually an aggregate of cadastral plots. **Attributes** | Champ | Alias | Type | | — | — | | — | | ‘datvalid’ | Date of last procedure that impacted the object | ‘varchar’ | | ‘typezone’ | Type of zone | ‘varchar’ | | ‘nomfic’ | File name | ‘varchar’ | | ‘urlfic’ | File Link | ‘varchar’ | ‘urlfic’ | | ‘libelong’ | Full Area Name | ‘varchar’ | | ‘insee’ | INSEE code of the municipality | ‘varchar’ | | ‘libelle’ | Short name of the zone | ‘varchar’ | | ‘datappro’ | Date of approval of the last administrative procedure | ‘varchar’ | | ‘id’ | Unique Object ID | ‘int4,PrimaryKey’ | | ‘lib_attr1’ | default value “destdomi” | ‘varchar’ | | ‘lib_val1’ | destdomi codes | ‘varchar’ | | ‘lib_attr2’ | default value “destdomi2” | ‘varchar’ | | ‘lib_val2’ | destdomi2 subcodes | ‘varchar’ | | ‘commentaries’ | ‘varchar’ | For more information, see [the metadata on the Isogeo catalog](https://open.isogeo.com/s/0bd17a2a330842c68ec4a412d1df6824/AiCyPK6W8fg012l-vHV0s5tPry5b0/r/7da141b63eaa42f18776f7b2963e5c3e).
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
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.

Didn't find the API you need?

Let us know and we will figure it out for you.

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks