This COVADIS data standard concerns Local Plan Documents d' Urban Planning (PLU) and Plans d' Land Use (POS that are equivalent to PLU). This data standard offers a technical framework describing in detail how to dematerialise these documents from #x27; urbanism into a geographical database that is exploitable by a GIS tool and interoperable. This data standard concerns both graphic zoning plans, the requirements s'y superimposed and the regulations s' applying to each type of zone.This COVADIS data standard was drawn up from the specifications for the dematerialisation of documents d' urban planning updated in 2012 by the CNIG, itself based on the consolidated version of the code of l' urban planning dated 16 March 2012. The recommendations of these two documents are consistent even if their object is not the same. The COVADIS data standard offers definitions and a structure to organise and store existing PLU/POS geographical data in an infrastructure in digital form, while the CNIG specifications serve to frame the digitisation of this data. The ' Data Structure part; presented in this COVADIS standard provides additional recommendations for data file storage (see Part C). These are specific choices for the MAA and MEDDE data infrastructure that do not apply outside their context.The communal maps are the subject of another COVADIS data standard.
__Origin__
The boundaries of a zone are represented on the graphical documents of the PLU or POS. They generally correspond to the boundaries of n°#x27; an aggregate of cadastral plots.
A prescription is shown on the graphical documents of the PLU or POS. Its geometry is obtained by scanning the figures drawn on the regulatory zoning plane. The resulting geographical table must contain all the requirements identified as such in the urban planning document.
Surface, linear or point information is shown on the graphical document of the PLU or POS. Its geometry is usually obtained by scanning the overdrawn figures of the regulatory zoning plane. The resulting geographic table must contain all geographical objects of an informative nature in the urban planning document.
The geometry of cadastral plots is a data derived from the cadastral geographical reference chosen at the time of the; elaboration of the document d' urbanism. This cadastral geographical repository can be either the Parcellar BD provided by the Ø;IGN, or the computerised cadastral plan (CCP) provided by the DGI.
__Partner organisations__
DDTM Somme
__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-ldd-6ad4afe6-835b-4b03-9780-941b42e5699a)
* [direct download of lot and associated documents](http://atom.geo-ide.developpement-durable.gouv.fr/atomArchive/GetResource?id=fr-120066022-ldd-cab63273-b3ae-4e8a-ae1c-6192e45faa94&datasetAggregate=true)
* [COVADIS data standard: Local plan d' urban planning v2.0](http://geostandards.developpement-durable.gouv.fr/afficherPageStandard.do?lot=Plan-local-d-urbanisme-v2.0)
* [associated download service](http://atom.geo-ide.developpement-durable.gouv.fr/atomMetadata/GetResourceDescription?id=fr-120066022-orphan-residentifier-f05dc5c6-3a6f-4169-9980-40e6e31d0557&scope=INTERNET)
* [direct download of lot and associated documents](http://atom.geo-ide.developpement-durable.gouv.fr/atomArchive/GetResource?id=fr-120066022-ldd-9acf7f5f-edfa-4fc7-82a7-85aabb9650e7&datasetAggregate=true)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/8d87f5cbb2da8178ac714e3e6d4e4eaed3a54c79)
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.