Information or annexes of the POS (Plan d’Occupation des Sols) and the PLUs (Local Urbanisation Plan) of the 25 municipalities of Lorient Agglomeration.
This is annexed information in accordance with Articles R123-13 and R123-14 of the Urbanism Code which may interfere with the right to construct and contextual information reported for information purposes on graphic documents without mentioning in the regulation.
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.
The information, as opposed to the requirements of the PLU itself, originates from an external source.
**Collection method**
Miscellaneous sources
**Attributes**
| Champ | Alias | Type |
| — | — | | — |
| ‘urlfic’ | File Link | ‘varchar’ | ‘urlfic’ |
| ‘datappro’ | Date of approval of the latest procedure | ‘varchar’ |
| ‘typeinf’ | Type of information | ‘varchar’ |
| ‘datvalid’ | Date of last procedure that impacted the object | ‘varchar’ |
| ‘txt’ | Information Label | ‘varchar’ | ‘txt’ |
| ‘id’ | Unique ID of each object | ‘int4,PrimaryKey’ |
| ‘nomfic’ | File name | ‘varchar’ |
| ‘insee’ | INSEE code of the municipality | ‘varchar’ |
| ‘libelle’ | Information name | ‘varchar’ |
| ‘code’ | 4-digit information code (typeinf + stypeinf) — 5 digits si standard 2014 | ‘varchar’ |
| ‘stypeinf’ | subtype detailing the type (2 digits) | ‘varchar’ |
| ‘lib_attr1’ | additional field that changes depending on the type of information | ‘varchar’ |
| ‘lib_val1’ | value that corresponds to the lib_attr1 field | ‘varchar’ |
| ‘lib_attr2’ | additional field that changes depending on the type of information | ‘varchar’ |
| ‘lib_val2’ | value that corresponds to the lib_attr2 field | ‘varchar’ |
| ‘lib_attr3’ | additional field that changes depending on the type of information | ‘varchar’ |
| ‘lib_val3’ | value that corresponds to the lib_attr3 field | ‘varchar’ |
| ‘lib_attr4’ | additional field that changes depending on the type of information | ‘varchar’ |
| ‘lib_val4’ | value that corresponds to the lib_attr4 field | ‘varchar’ |
| ‘commentaries’ | ‘varchar’ |
| ‘lib_attr5’ | additional field that changes depending on the type of information: daytime ref sound level in dB(A) (6h-22h) | ‘varchar’ |
| ‘lib_val5’ | value that corresponds to the lib_attr5 field | ‘varchar’ |
| ‘lib_attr6’ | additional field that changes depending on the type of information: Nocturnal ref sound level in dB(A) (22h-6h) | ‘varchar’ |
| ‘lib_val6’ | value that corresponds to the lib_attr6 field | ‘varchar’ |
For more information, see [the metadata on the Isogeo catalog](https://open.isogeo.com/s/0bd17a2a330842c68ec4a412d1df6824/AiCyPK6W8fg012l-vHV0s5tPry5b0/r/8f98138e66cc4affb1c8587692cd8b5a).
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.