Municipalities making up the Grand Poitiers Urban Community before 1 January 2017Communes composant la Communauté Urbaine GP avant le 1e janvier 2017

Name: Municipalities making up the Grand Poitiers Urban Community before 1 January 2017
Creator: datafair

Communes composant la Communauté Urbaine GP avant le 1e janvier 2017Municipalities making up the Grand Poitiers Urban Community before 1 January 2017

APIDiscovered1/7blocked by verifiedQuery nowOpen workbench Subscribe🇫🇷France

Website Docs

This dataset provides the municipal boundaries of the 42 municipalities that made up the Communauté Urbaine Grand Poitiers (Grand Poitiers Urban Community) up to 31 December 2016, published by Grand Poitiers. It reflects the territorial configuration prior to two mergers that took effect on 1 January 2017: Jaunay-Clan with Marigny-Brizay, and Beaumont with Saint-Cyr. The dataset is useful for tracking historical administrative boundary changes within the Grand Poitiers area and for comparing pre- and post-merger municipal geographies.Ce jeu de données présente les limites communales des 42 communes formant la Communauté Urbaine Grand Poitiers jusqu'au 31 décembre 2016. Le 1er janvier 2017, les communes de Jaunay Clan et Marigny Brizay ont fusionné. De même pour les communes de Beaumont et Saint-Cyr.

health

⬇ Export CSV List records Run verified request Schema OpenAPI spec Read the docs

Trust score

How is this computed?

fair

Weighted across five axes. Tap a ring for what it measures.

Data schema (20 fields)

Filterable via the API (20)

geometrygeo_point_2dgml_idobjectididprec_planinom_communecode_inseestatutcantonarrondisstdepartregionpopulmulticanxyepcishape_areashape_len

Click a field to see example values.

Field	Type	Description
geometryGeometry	string	Commune boundary geometry in GeoJSON format.Commune boundary geometry in GeoJSON format.
geo_point_2dCoordinates	string	Geographic coordinates of the commune's centroid.Geographic coordinates of the commune's centroid.
gml_idGml id	string	GML identifier of the boundary feature.GML identifier of the boundary feature.
objectid	integer	Internal object identifier of the record.Internal object identifier of the record.
id	string	Unique identifier of the commune surface record.Unique identifier of the commune surface record.
prec_planiPrec plani	integer	Planimetric precision of the boundary geometry, in meters.Planimetric precision of the boundary geometry, in meters.
nom_communeCommune name	string	Name of the commune.Name of the commune.
code_inseeINSEE commune code	string	INSEE code identifying the commune.INSEE code identifying the commune.
statut	string	Administrative status of the commune.Administrative status of the commune.
canton	string	Canton to which the commune belongs.Canton to which the commune belongs.
arrondisst	string	Arrondissement to which the commune belongs.Arrondissement to which the commune belongs.
depart	string	Department to which the commune belongs.Department to which the commune belongs.
region	string	Region to which the commune belongs.Region to which the commune belongs.
popul	integer	Population count of the commune.Population count of the commune.
multican	boolean	Indicates whether the commune spans multiple cantons.Indicates whether the commune spans multiple cantons.
x	boolean	Boolean flag related to the commune's spatial position.Boolean flag related to the commune's spatial position.
y	boolean	Boolean flag related to the commune's spatial position.Boolean flag related to the commune's spatial position.
epci	boolean	Indicates whether the commune belongs to an intercommunal grouping (EPCI).Indicates whether the commune belongs to an intercommunal grouping (EPCI).
shape_areaShape area	number	Area of the commune's boundary polygon.Area of the commune's boundary polygon.
shape_lenShape len	number	Perimeter length of the commune's boundary polygon.Perimeter length of the commune's boundary polygon.

Schema captured from datafair 27 days ago.

Query the data

Pick columns and a sort, then fetch a live preview straight from the source. Choose an API-filterable column (marked ▾) under “Where” to pick from its list of values.

Where=

Sort by

Sample data (5 records)

Record 1id: SURFCOMM0000000054728786 · popul: 6987

{
  "id": "SURFCOMM0000000054728786",
  "popul": 6987,
  "_score": null,
  "canton": "POITIERS 4E CANTON",
  "depart": "VIENNE",
  "gml_id": "Limites_communales_CU42.26",
  "region": "POITOU-CHARENTES",
  "statut": "Commune simple",
  "geometry": "{\"coordinates\":[[[[0.342121134492211,46.53943423696158],[0.342148689402846,46.53953848654145],[0.34213150634697,46.53964980593353],[0.342091932715771,46.53976510889783],[0.341998852342038,46.54004044031737],[0.34186190829031,46.540224655877246],[0.341683712071499,46.54039800330018],[0.341550060517516,46.54051472370785],[0.341398587972099,46.54062202133688],[0.341249079484849,46.54071584896042],[0.341095055151372,46.5407951564103],[0.340938568306911,46.54084467563344],[0.340859790240081,46.540853…",
  "multican": false,
  "objectid": 946,
  "shape_len": 21377.5246692031,
  "arrondisst": "POITIERS",
  "code_insee": "86214",
  "prec_plani": 30,
  "shape_area": 13599709.5663297,
  "nom_commune": "Saint-Benoît"
}

Record 2id: SURFCOMM0000000054728721 · popul: 1344

{
  "id": "SURFCOMM0000000054728721",
  "popul": 1344,
  "_score": null,
  "canton": "LUSIGNAN",
  "depart": "VIENNE",
  "gml_id": "Limites_communales_CU42.27",
  "region": "POITOU-CHARENTES",
  "statut": "Commune simple",
  "geometry": "{\"coordinates\":[[[[0.126003112415074,46.398952053593966],[0.126052866190962,46.399318236460076],[0.126176060655218,46.3999223470161],[0.126178866831293,46.400042258805335],[0.125953501339323,46.400191563951],[0.125954475165031,46.400470016306805],[0.125961915200911,46.40060085771419],[0.125953732259583,46.40092953806683],[0.1259302575802,46.40112808148838],[0.125915275261241,46.4012889933686],[0.125931371940322,46.401403833982606],[0.125945053411588,46.401564567148796],[0.125983121576683,46.4016…",
  "multican": false,
  "objectid": 973,
  "shape_len": 36637.4897078862,
  "arrondisst": "POITIERS",
  "code_insee": "86045",
  "prec_plani": 30,
  "shape_area": 42828350.3865885,
  "nom_commune": "Celle-Levescault"
}

Record 3id: SURFCOMM0000000054728787 · popul: 87906

{
  "id": "SURFCOMM0000000054728787",
  "popul": 87906,
  "_score": null,
  "canton": "POITIERS",
  "depart": "VIENNE",
  "gml_id": "Limites_communales_CU42.36",
  "region": "POITOU-CHARENTES",
  "statut": "Pr1fecture de r0gion",
  "geometry": "{\"coordinates\":[[[[0.302367843914609,46.54310216108669],[0.302724755805015,46.543620525824856],[0.303161038162683,46.543907408917704],[0.303735057332985,46.54433989018106],[0.304218362149127,46.54446840568018],[0.305068142296051,46.54455329752339],[0.305353995005926,46.54437082870726],[0.305596299779187,46.544250400217],[0.30591854830889,46.54409761752529],[0.306028596021455,46.54409029820468],[0.305878999412154,46.54494990208348],[0.305921058697183,46.5457626638195],[0.30351027246151,46.5474294…",
  "multican": true,
  "objectid": 1005,
  "shape_len": 55623.0373303102,
  "arrondisst": "POITIERS",
  "code_insee": "86194",
  "prec_plani": 30,
  "shape_area": 42551432.9775329,
  "nom_commune": "Poitiers"
}

Record 4id: SURFCOMM0000000054728809 · popul: 1947

{
  "id": "SURFCOMM0000000054728809",
  "popul": 1947,
  "_score": null,
  "canton": "SAINT-JULIEN-L'ARS",
  "depart": "VIENNE",
  "gml_id": "Limites_communales_CU42.4",
  "region": "POITOU-CHARENTES",
  "statut": "Commune simple",
  "geometry": "{\"coordinates\":[[[[0.415915132887899,46.57808990912919],[0.416459580341299,46.57908870499271],[0.416224255156225,46.58057801878255],[0.416151972403847,46.581054774514506],[0.416114216648286,46.58146474155203],[0.416125988548356,46.58179474400595],[0.416296448503898,46.5819472423745],[0.416324686795004,46.58215058654928],[0.416250640122465,46.58225161983151],[0.416305034600516,46.58256456593514],[0.416349923974046,46.58280252061338],[0.416378111426176,46.58289685219238],[0.416395473548697,46.5829…",
  "multican": false,
  "objectid": 880,
  "shape_len": 21610.4458505695,
  "arrondisst": "POITIERS",
  "code_insee": "86261",
  "prec_plani": 30,
  "shape_area": 15685647.4686413,
  "nom_commune": "Sévres-Anxaumont"
}

Record 5id: SURFCOMM0000000054728789 · popul: 2433

{
  "id": "SURFCOMM0000000054728789",
  "popul": 2433,
  "_score": null,
  "canton": "SAINT-JULIEN-L'ARS",
  "depart": "VIENNE",
  "gml_id": "Limites_communales_CU42.10",
  "region": "POITOU-CHARENTES",
  "statut": "Chef-lieu de canton",
  "geometry": "{\"coordinates\":[[[[0.454033612327427,46.555948384638434],[0.453928611768857,46.5559874897938],[0.453830177203497,46.55602584111042],[0.453620301267606,46.55610135163664],[0.453418043784945,46.556181535946884],[0.453225967937918,46.556267351696285],[0.45308965566225,46.556333687729165],[0.452909153177776,46.55642336486272],[0.452731385664766,46.55651039915355],[0.45254599981653,46.55659275986422],[0.452389021796036,46.55665412989534],[0.452214284597796,46.55670429440782],[0.452000575007311,46.556…",
  "multican": false,
  "objectid": 872,
  "shape_len": 27443.3879976408,
  "arrondisst": "POITIERS",
  "code_insee": "86226",
  "prec_plani": 30,
  "shape_area": 18666833.9919467,
  "nom_commune": "Saint-Julien-l'Ars"
}

Live sample captured at profiling time — values may have changed upstream.

Verification Status

Using the API

Configuration

Base URL: https://data.grandpoitiers.fr/data-fair/api/v1/datasets/decoupages-administratifs-communaute-urbaine-42-communes/
Format: openapi

License

Licence Ouverte 2.0 (France / Etalab)Open

✓ Redistributable
✓ Attribution required

Query examples

curl -s 'https://data.grandpoitiers.fr/data-fair/api/v1/datasets/decoupages-administratifs-communaute-urbaine-42-communes/lines?size=20' -H 'Accept: application/json'

First 20 records of the dataset as JSON.

Full API documentation ↗

Dataset

Volume & freshness

Records

Update cadence

Irregular

declared upstream

Last upstream update

3 years ago

2023-08-24

License

No license declared upstream.

○ Documentation○ Data dictionary○ Versioning

Source: datafair

Machine-readable & source

OpenAPI spec JSON

Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.