The requirements of a document d' urban planning are defined in the code of urban planning. A prescription is in the form of a surfacing, linear or point information that appears on the graphic documents of the PLU or the POS. A prescription that superimposes on an area of the document d’#x27; urbanism generally exerts an additional constraint on the settlement of the zone. These objects have been digitised in accordance with the national requirements of the CNIG standard
In this dataset is l' assembling the surface requirements of local plans d' urban planning (PLU) and plans d' land use (POS) of the \#x27;Eure, This layer is for informational use, the paper zoning plan remains the opposable document.
__Origin__
This layer groups the requirements of the point type, of l' set of PLU or POS, digitised on the department of l'Eure.
__Partner organisations__
DDTM Eure
__Links annexes__
* [HTML view of metadata on the Internet](http://catalogue.geo-ide.developpement-durable.gouv.fr/catalogue/srv/fre/catalog.search#/metadata/fr-120066022-jdd-5fdf45e3-1df4-4ae6-a49f-64cb2d024e03)
* [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-5fdf45e3-1df4-4ae6-a49f-64cb2d024e03)
* [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_37992/23deff75-25ea-4612-be2d-6afbc5678a7a.internet.map)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/0bfc15c98d857e75f2ada3aa413d989244782326)
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.