Traffic light junctionsCarrefour à feux

Carrefour à feuxTraffic light junctions

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

Dataset published by Bordeaux Métropole, owner of a network of traffic-light-controlled junctions across its territory. Each record represents the point location of a junction, with attributes including the junction identifier and its control mode, whether managed locally, via TETRA radio, or centrally. The dataset supports mapping and analysis of traffic signal infrastructure within the Bordeaux metropolitan area.Dictionnaire Public Bordeaux Métropole est propriétaire d'un réseau de carrefours à feux sur son territoire. Ce jeu de données représente par un ponctuel la localisation de ces carrefours. Il fournit une information sur l'identifiant du carrefour, s'il est géré en local, par tétra ou s'il est cen...

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 (13 fields)

Filterable via the API (11)

gidgeom_erridentetatprocedurequipemenaturecdatemdatecommunecode_commune

Click a field to see example values.

Fill	Field	Type	Description
—	geo_point_2dGeo Point	geo_point_2d	Geographic coordinates (latitude, longitude) of the traffic light junction.Geographic coordinates (latitude, longitude) of the traffic light junction.
—	geo_shapeShape	geo_shape	Geometric shape representing the location of the traffic light junction.Geometric shape representing the location of the traffic light junction.
—	gid	int	Primary key identifier for the record.Clé primaire
—	geom_errGeom err	text	Error code indicating a geometry issue with the record.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	Identifier of the traffic light junction.Identifiant du carrefour
—	etat	text	Status of the junction: existing or removed.Etat : Liste des valeurs possibles : DEPOSE : Déposé EXISTANT : Existant
—	procedur	text	Administrative procedure type applied to the junction.Procédure : Liste des valeurs possibles : PROCEDURE : Procédure CONFORMITE : Conformité SANS_FI : Sans FI HORS_PROCEDURE : Hors procédure
—	equipeme	text	Type of equipment installed at the junction (traffic lights, tram, PMV, etc.).Equipement : Liste des valeurs possibles : TRAFIC : Trafic TRAFIC_TRAM_A : Trafic Tram A TRAFIC_TRAM_B : Trafic Tram B TRAFIC_TRAM_C : Trafic Tram C TRAFIC_TRAM_D : Trafic Tram D TRAFIC_SAEIV : Trafic SAEIV FEU_CLIGNOTANT : Feu clignotant PMV : PMV ALDYN : Jaldyn SIREDO : Siredo TRAFIC_TRAM_E : Trafic Tram E TRAFIC_TRAM_F : Trafic Tram F
—	nature	text	Management type of the junction: centralized, local, or Tetra.Nature : Liste des valeurs possibles : CENTRALISE : Centralisé LOCAL : Local TETRA : Tetra
—	cdate	datetime	Date the record was created.Date de création
100%	mdate	datetime	Date the record was last modified.Date de modification
100%	communeCommune	text	Name of the municipality where the junction is located.Name of the municipality where the junction is located.
100%	code_communeCommune code	text	INSEE code of the municipality where the junction is located.INSEE code of the municipality where the junction is located.

Schema captured from opendatasoft 1 day 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: 1828 · etat: DEPOSE

{
  "gid": 1828,
  "etat": "DEPOSE",
  "cdate": "2014-11-12T09:19:04+00:00",
  "ident": "Z28C15a",
  "mdate": "2026-10-20T13:20:48+00:00",
  "nature": "CENTRALISE",
  "commune": "Saint-Médard-en-Jalles",
  "equipeme": "TRAFIC",
  "geom_err": null,
  "procedur": "PROCEDURE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.7451086,
        44.9067602
      ]
    },
    "properties": {}
  },
  "code_commune": "33449",
  "geo_point_2d": {
    "lat": 44.9067602,
    "lon": -0.7451086
  }
}

Record 2gid: 1493 · etat: EXISTANT

{
  "gid": 1493,
  "etat": "EXISTANT",
  "cdate": "2014-11-12T09:18:04+00:00",
  "ident": "Z03C30",
  "mdate": "2015-09-18T11:13:00+00:00",
  "nature": "CENTRALISE",
  "commune": "Bordeaux",
  "equipeme": "TRAFIC_TRAM_B",
  "geom_err": null,
  "procedur": "PROCEDURE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.5744064,
        44.8284793
      ]
    },
    "properties": {}
  },
  "code_commune": "33063",
  "geo_point_2d": {
    "lat": 44.8284793,
    "lon": -0.5744064
  }
}

Record 3gid: 855 · etat: EXISTANT

{
  "gid": 855,
  "etat": "EXISTANT",
  "cdate": "2014-11-12T09:18:12+00:00",
  "ident": "Z06C13",
  "mdate": "2015-09-18T11:13:04+00:00",
  "nature": "CENTRALISE",
  "commune": "Bordeaux",
  "equipeme": "TRAFIC",
  "geom_err": null,
  "procedur": "CONFORMITE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.6068002,
        44.8369659
      ]
    },
    "properties": {}
  },
  "code_commune": "33063",
  "geo_point_2d": {
    "lat": 44.8369659,
    "lon": -0.6068002
  }
}

Record 4gid: 911 · etat: DEPOSE

{
  "gid": 911,
  "etat": "DEPOSE",
  "cdate": "2014-11-12T09:19:00+00:00",
  "ident": "Z28C04",
  "mdate": "2016-03-18T12:48:08+00:00",
  "nature": null,
  "commune": "Saint-Médard-en-Jalles",
  "equipeme": null,
  "geom_err": null,
  "procedur": null,
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.7073959,
        44.8905197
      ]
    },
    "properties": {}
  },
  "code_commune": "33449",
  "geo_point_2d": {
    "lat": 44.8905197,
    "lon": -0.7073959
  }
}

Record 5gid: 1002 · etat: EXISTANT

{
  "gid": 1002,
  "etat": "EXISTANT",
  "cdate": "2014-11-12T09:19:00+00:00",
  "ident": "Z33C19",
  "mdate": "2016-03-18T15:06:44+00:00",
  "nature": "LOCAL",
  "commune": "Blanquefort",
  "equipeme": "TRAFIC",
  "geom_err": null,
  "procedur": "PROCEDURE",
  "geo_shape": {
    "type": "Feature",
    "geometry": {
      "type": "Point",
      "coordinates": [
        -0.5935372,
        44.9109048
      ]
    },
    "properties": {}
  },
  "code_commune": "33056",
  "geo_point_2d": {
    "lat": 44.9109048,
    "lon": -0.5935372
  }
}

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_carf_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_carf_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 1 day ago

Dataset

Volume & freshness

Records

1.3k

1326

Last upstream update

2 days ago

2026-10-22

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.