Centralized traffic signal control postsPoste centralisé

Poste centraliséCentralized traffic signal control posts

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

This dataset from Bordeaux Métropole's open data portal lists the centralized control posts (postes centralisés) that manage the traffic-light-controlled intersections across the metropolitan area. The territory is divided into traffic zones, each overseen by one of these control posts, which coordinate signal operations for the junctions within it. The data is provided as point locations identifying where each control post is situated. It is published free of charge without authentication and is intended for use in traffic management, urban planning, and transport-related analysis within the Bordeaux Métropole area.Dictionnaire Public Bordeaux Métropole est propriétaire d'un réseau de carrefours à feux sur son territoire. Ce territoire est découpé en zones de circulation dont les carrefours à feux sont gérées par un poste centralisé. Ce jeu de données représente par un ponctuel la localisation de ces postes...

transport

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

Trust score

How is this computed?

poor

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

Data schema (7 fields)

Filterable via the API (5)

gidnomnaturecdatemdate

Click a field to see example values.

Field	Type	Description
geo_point_2dGeo Point	geo_point_2d	Geographic coordinates (latitude, longitude) of the control post.Geographic coordinates (latitude, longitude) of the control post.
geo_shapeShape	geo_shape	Geometric shape (GeoJSON point) representing the control post location.Geometric shape (GeoJSON point) representing the control post location.
gid	text	Primary key identifier of the record.Clé primaire
nom	text	Name of the traffic control post.Nom
nature	text	Type or category of the control post.Nature
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

Schema captured from opendatasoft 3 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 1gid: 2332 · nom: TALENCE

{
  "gid": "2332",
  "nom": "TALENCE",
  "cdate": "2014-11-12T09:20:12+00:00",
  "mdate": "2014-11-12T09:20:12+00:00",
  "nature": "POSTE DE COMMANDE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.591312,
        44.8077152
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.8077152,
    "lon": -0.591312
  }
}

Record 2gid: 2345 · nom: PESSAC

{
  "gid": "2345",
  "nom": "PESSAC",
  "cdate": "2014-11-12T09:20:12+00:00",
  "mdate": "2014-11-12T09:20:12+00:00",
  "nature": "POSTE DE COMMANDE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.6277194,
        44.8068902
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.8068902,
    "lon": -0.6277194
  }
}

Record 3gid: 2344 · nom: LE HAILLAN

{
  "gid": "2344",
  "nom": "LE HAILLAN",
  "cdate": "2014-11-12T09:20:12+00:00",
  "mdate": "2014-11-12T09:20:12+00:00",
  "nature": "POSTE DE COMMANDE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.6457688,
        44.8625526
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.8625526,
    "lon": -0.6457688
  }
}

Record 4gid: 2324 · nom: LORMONT

{
  "gid": "2324",
  "nom": "LORMONT",
  "cdate": "2014-11-12T09:20:12+00:00",
  "mdate": "2014-11-12T09:20:12+00:00",
  "nature": "POSTE DE COMMANDE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.5247862,
        44.864919
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.864919,
    "lon": -0.5247862
  }
}

Record 5gid: 2347 · nom: CAP FERRET

{
  "gid": "2347",
  "nom": "CAP FERRET",
  "cdate": "2014-11-12T09:20:12+00:00",
  "mdate": "2014-11-12T09:20:12+00:00",
  "nature": "POSTE DE COMMANDE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.6407423,
        44.8321271
      ]
    },
    "properties": {}
  },
  "geo_point_2d": {
    "lat": 44.8321271,
    "lon": -0.6407423
  }
}

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/pc_pczon_p

License

Licence Ouverte 2.0 (France / Etalab)Open

✓ Redistributable
✓ Attribution required

Query examples

curl -s 'https://opendata.bordeaux-metropole.fr/api/explore/v2.1/catalog/datasets/pc_pczon_p/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

50 000 req/day

per ipmeasured

observed 3 days ago

Dataset

Volume & freshness

Records

Last upstream update

3 days ago

2026-10-21

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.