Traffic status in Vitoria-Gasteiz, in real timeGasteizko trafikoaren egoera, denbora errealean
Gasteizko trafikoaren egoera, denbora errealeanTraffic status in Vitoria-Gasteiz, in real time
Real-time data on traffic conditions in Vitoria-Gasteiz, Spain, covering measurement sensors and traffic density readings across the city's road network. The information is published through a REST API, allowing automated access to current traffic status for integration into other applications or monitoring systems. No authentication is required to access the service. The dataset is maintained by the municipal authority of Vitoria-Gasteiz as part of its open digital services related to urban mobility and transport management.Datos sobre el estado del tráfico en Vitoria-Gasteiz: sensores de medición y densidad. Los datos se proporcionan con una API REST.
Trust score
How is this computed?Weighted across five axes. Tap a ring for what it measures.
Data schema (9 fields)
Click a field to see example values.
| Field | Type | Description |
|---|---|---|
| volume | int | Number of vehicles detected in the measurement period.Number of vehicles detected in the measurement period. |
| load | mixed | Traffic load level measured by the sensor.Traffic load level measured by the sensor. |
| tipo_inventarioTipo inventario | text | Type of inventory or sensor category.Type of inventory or sensor category. |
| endDateEnd date | datetime | End date and time of the measurement period.End date and time of the measurement period. |
| occupancy | int | Percentage of time the sensor detected vehicle presence.Percentage of time the sensor detected vehicle presence. |
| proveedor | text | Name of the technology provider operating the sensor.Name of the technology provider operating the sensor. |
| type | text | Sensor or measurement point type code.Sensor or measurement point type code. |
| nombre | text | Identifier code of the traffic sensor.Identifier code of the traffic sensor. |
| startDateStart date | datetime | Start date and time of the measurement period.Start date and time of the measurement period. |
Schema inferred from the distribution file's first records 4 days ago. Column types are sampled estimates, not source-declared.
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 (5 records)
Record 1load: 50 · type: MS
{
"load": 50,
"type": "MS",
"nombre": "07010",
"volume": 0,
"endDate": "2026-10-09T02:45:00",
"occupancy": 100,
"proveedor": "OPTIMUS",
"startDate": "2026-10-09T02:30:00",
"tipo_inventario": "MS"
}Record 2load: 50 · type: MS
{
"load": 50,
"type": "MS",
"nombre": "07012",
"volume": 0,
"endDate": "2026-10-09T02:45:00",
"occupancy": 100,
"proveedor": "OPTIMUS",
"startDate": "2026-10-09T02:30:00",
"tipo_inventario": "MS"
}Record 3load: 14.667 · type: MS
{
"load": 14.667,
"type": "MS",
"nombre": "01059",
"volume": 2,
"endDate": "2026-10-09T02:45:00",
"occupancy": 11,
"proveedor": "OPTIMUS",
"startDate": "2026-10-09T02:30:00",
"tipo_inventario": "MS"
}Record 4load: 14.667 · type: MS
{
"load": 14.667,
"type": "MS",
"nombre": "01056",
"volume": 8,
"endDate": "2026-10-09T02:45:00",
"occupancy": 11,
"proveedor": "OPTIMUS",
"startDate": "2026-10-09T02:30:00",
"tipo_inventario": "MS"
}Record 5load: 0 · type: MS
{
"load": 0,
"type": "MS",
"nombre": "06191",
"volume": 0,
"endDate": "2026-10-09T02:45:00",
"occupancy": 0,
"proveedor": "OPTIMUS",
"startDate": "2026-10-09T02:30:00",
"tipo_inventario": "MS"
}Live sample captured at profiling time — values may have changed upstream.
Verification Status
Using the API
Query examples
curl -sL 'https://www.vitoria-gasteiz.org/c11-01w/traffic?action=data&format=GEOJSON' -o data.geojsonFull geojson file download — the schema shown was inferred from the file's first records.