Territorial HubsPôle Territorial
Pôle TerritorialTerritorial Hubs
This dataset published on the Bordeaux Métropole open data portal maps the boundaries of the four territorial hubs (pôles territoriaux) created on 1 January 2016 to strengthen local governance within Bordeaux Métropole, as part of its metropolisation project under the MAPTAM law. These hubs act as single points of contact for residents and local stakeholders, coordinating public services at a sub-metropolitan level. The dataset is accessible without authentication and is intended for use in local administration, spatial analysis, and public information services across the Bordeaux metropolitan area.Dictionnaire Public Ce jeu de données représente les périmètres d'interventions des 4 pôles territoriaux (PT) qui ont été créés le 1er janvier 2016 pour renforcer la territorialisation de Bordeaux Métropole dans le cadre de son projet de Métropolisation (Loi MAPTAM). Guichets pour les usagers et...
Trust score
How is this computed?Weighted across five axes. Tap a ring for what it measures.
Data schema (8 fields)
Click a field to see example values.
| Field | Type | Description |
|---|---|---|
| geo_point_2dGeo Point | geo_point_2d | Geographic coordinates of the centroid of the territorial hub area.Geographic coordinates of the centroid of the territorial hub area. |
| geo_shapeShape | geo_shape | Geometric boundary shape of the territorial hub's area.Geometric boundary shape of the territorial hub's area. |
| gid | text | Primary key identifier for the record.Clé primaire |
| geom_errGeom err | text | Geometry error code indicating issues with the shape's validity.Code d'erreur géométrique : Liste des valeurs possibles : 9999 : Polygone compose et / ou à sections multiples 9998 : Linéaire compose et / ou à sections multiples 9996 : La géométrie contient des informations LRS 9995 : Nombre de dimensions différent de 2 ou 3 9994 : Présence d'un arc de cercle 9000 : Erreur autre 13343 : Polygone de moins de 4 points 13349 : Polygone papillon 13350 : Deux éléments d'un polygone archipel se touchent 13351 : Deux éléments d'un polygone archipel se touchent 13356 : Point double 13366 : Combinaison invalide d'intérieur / extérieur d'un polygone 13367 : Orientation invalide d'intérieur / extérieur d'un polygone |
| ident | text | Unique code identifying the territorial hub.Identifiant |
| cdate | datetime | Date and time the record was created.Date de création |
| mdate | datetime | Date and time the record was last modified.Date de modification |
| libelle | text | Display name of the territorial hub.Libellé graphique |
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.
Sample data (4 records)
Record 1gid: 2 · cdate: 2014-03-07T14:06:12+00:00
{
"gid": "2",
"cdate": "2014-03-07T14:06:12+00:00",
"ident": "PT_SUD",
"mdate": "2016-04-18T13:45:28+00:00",
"libelle": "Pôle territorial Sud",
"geom_err": null,
"geo_shape": "[large value omitted]",
"geo_point_2d": {
"lat": 44.786503119165765,
"lon": -0.6180271990585824
}
}Record 2gid: 4 · cdate: 2014-03-07T14:06:12+00:00
{
"gid": "4",
"cdate": "2014-03-07T14:06:12+00:00",
"ident": "PT_BORDEAUX",
"mdate": "2016-04-18T13:58:36+00:00",
"libelle": "Pôle territorial Bordeaux",
"geom_err": null,
"geo_shape": "[large value omitted]",
"geo_point_2d": {
"lat": 44.85753292858743,
"lon": -0.5734335853314744
}
}Record 3gid: 1 · cdate: 2014-03-07T14:06:12+00:00
{
"gid": "1",
"cdate": "2014-03-07T14:06:12+00:00",
"ident": "PT_OUEST",
"mdate": "2016-04-18T13:36:52+00:00",
"libelle": "Pôle territorial Ouest",
"geom_err": null,
"geo_shape": "[large value omitted]",
"geo_point_2d": {
"lat": 44.888002287272236,
"lon": -0.7064089107003687
}
}Record 4gid: 3 · cdate: 2014-03-07T14:06:12+00:00
{
"gid": "3",
"cdate": "2014-03-07T14:06:12+00:00",
"ident": "PT_RIVE_DROITE",
"mdate": "2016-04-18T13:36:40+00:00",
"libelle": "Pôle territorial Rive Droite",
"geom_err": null,
"geo_shape": "[large value omitted]",
"geo_point_2d": {
"lat": 44.92973826169885,
"lon": -0.5167244412897748
}
}Live sample captured at profiling time — values may have changed upstream.
Verification Status
Using the API
Configuration
- Base URL
- https://opendata.bordeaux-metropole.fr/api/explore/v2.1/catalog/datasets/se_pt_s
License
- ✓ Redistributable
- ✓ Attribution required
Query examples
curl -s 'https://opendata.bordeaux-metropole.fr/api/explore/v2.1/catalog/datasets/se_pt_s/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.
Rate limits
Dataset
Volume & freshness
License
No license declared upstream.
Source: opendatasoft
Machine-readable & source
Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.