Plu de CHATEAUNEUF SUR ISERE 26084 Updated on 09/08/2016 and Amendment No 2 13/07/2016 — FIN DE VALIDITE: 03/02/2017 enforceability of Amendment No. 3 approved on 19/12/2016
Open data API in a single place
Provided by etalab
Get early access to Plu de CHATEAUNEUF SUR ISERE 26084 Updated on 09/08/2016 and Amendment No 2 13/07/2016 — FIN DE VALIDITE: 03/02/2017 enforceability of Amendment No. 3 approved on 19/12/2016 API!
Set of GIS and PDF data of the Documents d'Urbanism of the Local Plan d'Urbanisme de CHATEAUNEUF SUR ISERE 26084 PLU approved on 16/12/2011 — Update of 09/08/2016 and Amendment No. 2 approved on 13/07/2016 Enforceability on 04/09/2016 — VALIDITE FIN: 03/02/2017 enforceability of Amendment No. 3 approved on 19/12/2016
__Origin__
DDTM30 data set in COVADIS format as part of the project led by DREAL LR in 2015
__Partner organisations__
DDT Drôme
__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-f26a0d26-1e26-4dcc-810f-3d36507767b5)
* [COVADIS data standard: Risk Prevention Plan PPRN PPRT](http://geostandards.developpement-durable.gouv.fr/afficherPageStandard.do?lot=Plan-de-prevention-des-risques-PPRN-PPRT)
* [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_38002/fr-120066022-orphan-4d0957a0-1fcb-493b-9f05-16e2c67f1e23.internet.map)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/62720cdd10f1b420acbac47e0fe2cdc317fcf9f5)
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.