Vector scanning of the municipal map of Chis (65146), in April 2010.
This digitisation complies with the CNIG’s national specifications — dematerialisation of municipal maps.
Potential uses: ADS instruction.
Generalised zoning.
Any operation of ' fitting-out.
__Origin__
Internal input to DDT 65 from the signed document available in the POS (Sufl Documentation) library.
Seizure on BD-Parcellaire 2007; BD Topo road axis.
Production objectives: Provision of the CC in the ADS GIS (DDT instructors).
DATA QUALITY: Working scale (to ensure a degree of precision of the EMR; order of the EMR):
— Urban area: 1/500° recommended, 1/750° mandatory
— Low-density area: 1/1500° compulsory
Verification according to the method laid down in the tender specifications (regions, precision checks of points by sample, etc.).
Particularities:
* Classified wooded areas: the classified wooded spaces n' have not been digitised. The communal map cannot delineate wooded areas.
* On the approved paper graphic document, there is no area affected by noise in the area intended for urbanisation. In the representation on the ADS SIG, the area affected by noise was digitised on the whole of the RN21, including the area mentioned above.
August 2019: integration of the update (SUP PM1) of 04/04/2019
__Partner organisations__
DDT Indre, DDT Hautes-Pyrénées
__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-485d3471-7c62-4212-8ab1-d2283ef0f5ca)
[See this page on geo.data.gouv.fr](https://geo.data.gouv.fr/fr/datasets/a0450c06a9a24a83426e4715500aba98594db080)
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.