GeoZones

Open data API in a single place

Provided by etalab

Get early access to GeoZones API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2019.05.13 14:09
Created
2015.04.30
Available languages
French
Keywords
geojson, arrondissements, communes, epci, pays, iris, contours, cantons, regions
Quality scoring
175

Dataset description

Simple geospatial and administrative reference. The purpose of this dataset is to provide a common geospatial and administrative repository based on opendata datasets. The goal is to be easily embedded in applications for self-completion, for example. There is no universality objective (levels are not comparable across countries) or absolute accuracy (most source datasets have an accuracy of 100 m). Nor is there any desire to reproduce the complexity of the graph of the territories. The data is produced in GeoJSON/WGS84. ## Model There are two types of objects: — levels — the zones ### Levels/Levels They allow the various known levels of the reference framework to be modelled and their theoretical relationships. Their name is transducible. ### Zones An area is the association of a unique identifier with geographical polygon, a level and a name. It has less a single code for the level. It may have several known identifiers, which are not necessarily unique. The name is optionally transducible (*ex:* European Union, World) The following attributes are exported to the GeoJSON: — **ID**: A unique identifier according to the specification [GeoID](https://github.com/etalab/geoids) — **code**: The unique identifier for a given date of the zone for its level — **Level**: The Identifier of the connecting level — **name**: The display name of the area in English *(maybe translated)* — **population**: Approximate/estimated population *(optional)* — **Area**: Estimated/approximative area in km<sup>2</sup> *(optional)* — **Wikidata**: Associated Wikidata node *(optional)* — **Wikipedia**: A reference to Wikipedia *(optional)* — **DBpedia**: A reference to DBPedia *(optional)* — **Flag**: A reference to the DBPedia flag *(optional)* — **blazon**: A reference to the DBPedia blazon *(optional)* — **Keys**: a dictionary of the different codes known for this area — **parents**: an unordered list of identifiers of the different known parents — **Ancestors**: list of possible ancestors — **Successors**: list of possible successors — **validity**: a validity period (object with ‘start’/‘end’ attributes) *(optional)* # # construction This dataset is built with the [GeoZones] tool(https://www.data.gouv.fr/fr/reuses/geozones/) whose code is [published on Github](https://github.com/etalab/geozones). You can find the [detail of French specificities](https://github.com/etalab/geozones/blob/master/LISEZMOI.md) on the repository. ## Possible future improvements ### Fields — Overall weight = f(population, area, level) ### Deliverables — Different details — Localised JSON — Translations into JSON (as an alternative hard format PO/MO current) — Level statistics (number of zones, coverage of attributes...) Historical ## — **30/04/2015**: first version — **15/04/2016**: adding the URLs of the coats/flags and an export using [msgpack](http://msgpack.org/) to reduce the size of the generated archive — **19/04/2016**: correction version providing a finer cutting of common shapes — **09/06/2016**: correction version adding parents for the municipalities of Corsica/DROM-COM and calculating the population for the districts — **15/06/2017**: version including data from [GeoHisto](https://github.com/etalab/geohisto) and using [GeoIDs](https://github.com/etalab/geoids), integrates 2017 data (COG, OSM). — **28/08/2017**: Addition of EPCIS history from [GeoHisto](https://github.com/etalab/geohisto). — **08/05/2019**: Switch to COG 2019, fix bugs, add the key ‘geonames’, switch to Wikidata, cantons and iris are no longer exported
Build on reliable and scalable technology
Revolgy LogoAmazon Web Services LogoGoogle Cloud Logo
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.

Didn't find the API you need?

Let us know and we will figure it out for you.

API Store provides access to European Open Data via scalable and reliable REST API interface.
Copyright © 2024. Made with ♥ by Apitalks