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
❌267 errors, 238 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-11-16 at 08:18 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 6 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 18-40-1-1-085500 stop_sequence for stop_ids [4-1078, 4-1390, 4-318, 4-315, 4-310, 4-300, 4-287, 4-238, 4-215, 4-205, 4-573, 4-593, 4-580, 4-340, 4-330, 4-343, 4-10075, 4-10079, 4-10080, 4-10081, 4-337, 4-339, 4-1708, 4-484, 4-547, 4-1401, 4-1402, 4-1403, 4-1676, 4-1606] is not strictly sorted by increasing stop_sequence
- trip_id 18-40-2-1-082000 stop_sequence for stop_ids [4-1078, 4-1390, 4-318, 4-315, 4-310, 4-300, 4-287, 4-238, 4-215, 4-205, 4-573, 4-593, 4-580, 4-340, 4-330, 4-343, 4-10075, 4-10079, 4-10080, 4-10081, 4-337, 4-339, 4-1708, 4-484, 4-547, 4-1401, 4-1402, 4-1403, 4-1676, 4-1606] is not strictly sorted by increasing stop_sequence
- trip_id 18-40-3-1-080200 stop_sequence for stop_ids [4-1078, 4-1390, 4-318, 4-315, 4-310, 4-300, 4-287, 4-238, 4-215, 4-205, 4-573, 4-593, 4-580, 4-340, 4-330, 4-343, 4-10075, 4-10079, 4-10080, 4-10081, 4-337, 4-339, 4-1708, 4-484, 4-547, 4-1401, 4-1402, 4-1403, 4-1676, 4-1606] is not strictly sorted by increasing stop_sequence
- trip_id 18-40-4-1-075600 stop_sequence for stop_ids [4-1606, 4-1675, 4-1398, 4-1399, 4-1400, 4-1342, 4-548, 4-549, 4-1700, 4-159, 4-337, 4-10078, 4-10077, 4-10076, 4-343, 4-340, 4-10074, 4-162, 4-586, 4-573, 4-166, 4-165, 4-164, 4-593, 4-202, 4-194, 4-193, 4-191, 4-167, 4-336, 4-1078] is not strictly sorted by increasing stop_sequence
- trip_id 18-40-4-1-083800 stop_sequence for stop_ids [4-1078, 4-1390, 4-318, 4-315, 4-310, 4-300, 4-287, 4-238, 4-215, 4-205, 4-573, 4-593, 4-580, 4-340, 4-330, 4-343, 4-10075, 4-10079, 4-10080, 4-10081, 4-337, 4-339, 4-1708, 4-484, 4-547, 4-1401, 4-1402, 4-1403, 4-1676, 4-1606] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 261 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 18-L3-3-1-073800 stop_id 4-89 arrival_time 08:11:29 (1794813089) is equal to previous stop departure_time 08:11:29 (1794813089) - times must increase between two sequential stops
- trip_id 18-L5-1-1-080400 stop_id 4-71 arrival_time 08:14:33 (1794813273) is equal to previous stop departure_time 08:14:33 (1794813273) - times must increase between two sequential stops
- trip_id 18-L5-3-1-074100 stop_id 4-35 arrival_time 08:11:50 (1794813110) is equal to previous stop departure_time 08:11:50 (1794813110) - times must increase between two sequential stops
- trip_id 18-L5-4-1-074400 stop_id 4-71 arrival_time 07:53:19 (1794811999) is equal to previous stop departure_time 07:53:19 (1794811999) - times must increase between two sequential stops
- trip_id 18-L5-10-1-073200 stop_id 4-1625 arrival_time 07:38:11 (1794811091) is equal to previous stop arrival_time 07:38:11 (1794811091) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 238 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 18-L3-1-1-085900 does not have a vehicle_id
- trip_id 18-L3-2-1-091600 does not have a vehicle_id
- trip_id 18-L3-3-1-083700 does not have a vehicle_id
- trip_id 18-L3-4-1-091700 does not have a vehicle_id
- trip_id 18-L3-5-1-084100 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,128 | 29 times (97 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 6,496 | 28 times (93 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 142 | 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 | 47 | 4 times (13 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 33 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-11-17 at 03:14 Europe/Paris.
trip_updates (2) 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-11-17 at 03:14 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "9-93-1-1-035800",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1794884280"
},
"stopId": "4-1077"
}
],
"timestamp": "1794881501",
"trip": {
"directionId": 0,
"routeId": "4-93",
"scheduleRelationship": "SCHEDULED",
"tripId": "9-93-1-1-035800"
},
"vehicle": {}
}
},
{
"id": "9-93-2-1-035500",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"time": "1794884100"
},
"stopId": "4-421"
}
],
"timestamp": "1794881501",
"trip": {
"directionId": 0,
"routeId": "4-93",
"scheduleRelationship": "SCHEDULED",
"tripId": "9-93-2-1-035500"
},
"vehicle": {}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1794881691"
}
}