Voting Canton BoundariesContours des cantons de vote

Contours des cantons de voteVoting Canton Boundaries

APIExecutable4/7Query nowOpen workbench Subscribe🇫🇷France

This dataset provides the geographic boundaries of voting cantons, generated from polling station numbers. It is published as part of the Strasbourg open data portal and covers the local territorial area of Strasbourg, France. The dataset can be combined with the related dataset on constituencies, cantons and polling stations for the 2026 elections, making it useful for electoral mapping, administrative analysis and geospatial applications concerning voting districts.Ce jeu contient les délimitations des cantons générés à partir des numéros de bureaux de vote. Il peut être associé au jeu de données Plan des circonscriptions, cantons et bureaux de vote 2026 .

government

⬇ Export CSV List records Select & filter Run verified request Read the docs

Trust score

How is this computed?

fair

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

Data schema (4 fields)

Filterable via the API (2)

cod_cantonlibelle

Click a field to see example values.

Field	Type	Description
geo_point_2dGeo Point	geo_point_2d	Geographic coordinates of the canton's centroid.Geographic coordinates of the canton's centroid.
geo_shapeShape	geo_shape	Polygon geometry outlining the canton's boundary.Polygon geometry outlining the canton's boundary.
cod_cantonCod canton	text	Numeric code identifying the voting canton.Numeric code identifying the voting canton.
libelle	text	Name of the voting canton.Name of the voting canton.

Schema captured from opendatasoft 2 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 1libelle: Strasbourg 3 · geo_shape: [large value omitted]

{
  "libelle": "Strasbourg 3",
  "geo_shape": "[large value omitted]",
  "cod_canton": "3",
  "geo_point_2d": {
    "lat": 48.593179492016155,
    "lon": 7.712770657971183
  }
}

Record 2libelle: Strasbourg 1 · geo_shape: [large value omitted]

{
  "libelle": "Strasbourg 1",
  "geo_shape": "[large value omitted]",
  "cod_canton": "1",
  "geo_point_2d": {
    "lat": 48.57382775996963,
    "lon": 7.752063184109904
  }
}

Record 3libelle: Strasbourg 6 · geo_shape: [large value omitted]

{
  "libelle": "Strasbourg 6",
  "geo_shape": "[large value omitted]",
  "cod_canton": "6",
  "geo_point_2d": {
    "lat": 48.53517451229618,
    "lon": 7.774970353642284
  }
}

Record 4libelle: Strasbourg 4 · geo_shape: [large value omitted]

{
  "libelle": "Strasbourg 4",
  "geo_shape": "[large value omitted]",
  "cod_canton": "4",
  "geo_point_2d": {
    "lat": 48.61170722993398,
    "lon": 7.793121249261405
  }
}

Record 5libelle: Strasbourg 5 · geo_shape: [large value omitted]

{
  "libelle": "Strasbourg 5",
  "geo_shape": "[large value omitted]",
  "cod_canton": "5",
  "geo_point_2d": {
    "lat": 48.577768409666206,
    "lon": 7.784414994636775
  }
}

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

Verification Status

Using the API

Configuration

Base URL: https://data.strasbourg.eu/api/explore/v2.1/catalog/datasets/contours_des_cantons_de_vote

License

Licence Ouverte 2.0 (France / Etalab)Open

✓ Redistributable
✓ Attribution required

Query examples

curl -s 'https://data.strasbourg.eu/api/explore/v2.1/catalog/datasets/contours_des_cantons_de_vote/records?limit=20' -H 'Accept: application/json'

First 20 records of the dataset as JSON.

Uses the Opendatasoft Explore v2.1 syntax — supports select, where, group_by and order_by.

Full API documentation ↗

Rate limits

2 000 000 req/day

per ipmeasured

observed 2 days ago

Dataset

Volume & freshness

Records

Update cadence

Irregular

declared upstream

Last upstream update

9 months ago

2026-01-29

License

No license declared upstream.

○ Documentation○ Data dictionary○ Versioning

Source: opendatasoft

Machine-readable & source

JSON

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