Resource details
Offre théorique et temps-réel du réseau Diviamobilités, Dijon Métropole - Prochains passages aux arrêts
This resource file is part of the dataset Réseau urbain DiviaMobilités.
Download availability
Learn more
HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.For SIRI and SIRI Lite feeds, we perform a
GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.Validation details
❌1 error, 36 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-05 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 1 error
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 17-L9-2-B-083030 stop_id 4-1359 arrival_time 08:54:03 (1775372043) is equal to previous stop departure_time 08:54:03 (1775372043) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 36 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 17-L3-1-B-093600 does not have a vehicle_id
- trip_id 17-L3-2-B-095000 does not have a vehicle_id
- trip_id 17-L3-3-B-092000 does not have a vehicle_id
- trip_id 17-L4-1-B-090130 does not have a vehicle_id
- trip_id 17-L4-1-B-093700 does not have a vehicle_id
Previous validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 5,097 | 28 times (93 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 7,326 | 27 times (90 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 139 | 20 times (67 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 24 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-06 at 03:48 Europe/Paris.
trip_updates (3) vehicle_positions (0) service_alerts (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-04-06 at 03:48 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "17-PL-1-B-035000",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1775440200"
},
"stopId": "4-1605"
}
],
"timestamp": "1775440082",
"trip": {
"directionId": 0,
"routeId": "4-PL",
"scheduleRelationship": "SCHEDULED",
"tripId": "17-PL-1-B-035000"
},
"vehicle": {}
}
},
{
"id": "17-PL-1-B-041500",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1775441700"
},
"stopId": "4-274"
}
],
"timestamp": "1775437850",
"trip": {
"directionId": 1,
"routeId": "4-PL",
"scheduleRelationship": "SCHEDULED",
"tripId": "17-PL-1-B-041500"
},
"vehicle": {}
}
},
{
"id": "17-PL-1-B-044500",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1775443500"
},
"stopId": "4-1605"
}
],
"timestamp": "1775437850",
"trip": {
"directionId": 0,
"routeId": "4-PL",
"scheduleRelationship": "SCHEDULED",
"tripId": "17-PL-1-B-044500"
},
"vehicle": {}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775440110"
}
}