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
❌254 errors, 214 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-22 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 7 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 14-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 14-40-2-1-085000 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 14-40-3-1-091900 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 14-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
- trip_id 14-40-4-1-094800 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 247 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 14-L3-2-1-081300 stop_id 4-88 arrival_time 08:49:34 (1790059774) is equal to previous stop departure_time 08:49:34 (1790059774) - times must increase between two sequential stops
- trip_id 14-L3-12-1-082200 stop_id 4-88 arrival_time 08:58:49 (1790060329) is equal to previous stop departure_time 08:58:49 (1790060329) - times must increase between two sequential stops
- trip_id 14-L5-5-1-084200 stop_id 4-71 arrival_time 08:53:01 (1790059981) is equal to previous stop departure_time 08:53:01 (1790059981) - times must increase between two sequential stops
- trip_id 14-L5-8-1-082200 stop_id 4-71 arrival_time 08:32:26 (1790058746) is equal to previous stop departure_time 08:32:26 (1790058746) - times must increase between two sequential stops
- trip_id 14-L5-8-1-082200 stop_id 4-78 arrival_time 08:43:36 (1790059416) is equal to previous stop departure_time 08:43:36 (1790059416) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 214 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 14-L3-1-1-100100 does not have a vehicle_id
- trip_id 14-L3-2-1-091600 does not have a vehicle_id
- trip_id 14-L3-2-1-100200 does not have a vehicle_id
- trip_id 14-L3-3-1-092600 does not have a vehicle_id
- trip_id 14-L3-4-1-091700 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 9,070 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 5,517 | 30 times (100 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 180 | 23 times (77 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 61 | 7 times (23 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 109 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-09-23 at 02:32 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (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-09-23 at 02:32 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1790123557"
}
}