Resource details
Données temps réel du réseau urbain Agglobus de BOURGES - Mises à jour des trajets
This resource file is part of the dataset Réseau urbain AggloBus.
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
❌16 errors, 127 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-31 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 8 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 21834039 stop_sequence for stop_ids [boucre3, boujuin5, bouesch2, boucorn2, bouroll2, boulin, boucoth4, bousent2, boufran2, bouampe2, bougcha, bousncf2, boupfic, boupoul, bouplan, bounatiC, boujura, bouauro, boueuro3, bourauc, boujoff, boufoch, boujacq, bouparc, bouzéro, bouleol, boureno, boubour, boulabo, boualle, bouvald, boulac, bouboye, bourott] is not strictly sorted by increasing stop_sequence
- trip_id 21834084 stop_sequence for stop_ids [bourott, bouboye2, boulac2, bouvald2, boualle2, boulabo2, boubour2, boureno2, bouleol2, bouzéro2, bouparc2, boujacq2, boufoch3, boujoff2, bourauc2, boueuro4, bouauro2, boujura2, bounatiD, bouplan2, boupoul2, boupfic2, bousncf, bougcha2, bouampe, boufran, bousent, boucoth3, boulin2, bouroll, boucorn, bouesch, boujuin4, boucre3] is not strictly sorted by increasing stop_sequence
- trip_id 21834040 stop_sequence for stop_ids [boucre3, boujuin5, bouesch2, boucorn2, bouroll2, boulin, boucoth4, bousent2, boufran2, bouampe2, bougcha, bousncf2, boupfic, boupoul, bouplan, bounatiC, boujura, bouauro, boueuro3, bourauc, boujoff, boufoch, boujacq, bouparc, bouzéro, bouleol, boureno, boubour, boulabo, boualle, bouvald, boulac, bouboye, bourott] is not strictly sorted by increasing stop_sequence
- trip_id 21834085 stop_sequence for stop_ids [bourott, bouboye2, boulac2, bouvald2, boualle2, boulabo2, boubour2, boureno2, bouleol2, bouzéro2, bouparc2, boujacq2, boufoch3, boujoff2, bourauc2, boueuro4, bouauro2, boujura2, bounatiD, bouplan2, boupoul2, boupfic2, bousncf, bougcha2, bouampe, boufran, bousent, boucoth3, boulin2, bouroll, boucorn, bouesch, boujuin4, boucre3] is not strictly sorted by increasing stop_sequence
- trip_id 21834041 stop_sequence for stop_ids [boucre3, boujuin5, bouesch2, boucorn2, bouroll2, boulin, boucoth4, bousent2, boufran2, bouampe2, bougcha, bousncf2, boupfic, boupoul, bouplan, bounatiC, boujura, bouauro, boueuro3, bourauc, boujoff, boufoch, boujacq, bouparc, bouzéro, bouleol, boureno, boubour, boulabo, boualle, bouvald, boulac, bouboye, bourott] is not strictly sorted by increasing stop_sequence
GTFS-rt stop_id does not exist in GTFS data E011 8 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 21834039 stop_id bouzéro does not exist in GTFS data stops.txt
- trip_id 21834084 stop_id bouzéro2 does not exist in GTFS data stops.txt
- trip_id 21834040 stop_id bouzéro does not exist in GTFS data stops.txt
- trip_id 21834085 stop_id bouzéro2 does not exist in GTFS data stops.txt
- trip_id 21834041 stop_id bouzéro does not exist in GTFS data stops.txt
Warnings
vehicle_id not populated W002 5 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 21833543 does not have a vehicle_id
- trip_id 21833630 does not have a vehicle_id
- trip_id 21833473 does not have a vehicle_id
- trip_id 21833550 does not have a vehicle_id
- trip_id 21833393 does not have a vehicle_id
schedule_relationship not populated W009 122 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 21833702 stop_id bouday (and potentially more for this trip) does not have a schedule_relationship
- trip_id 21833702 does not have a schedule_relationship
- trip_id 21833758 stop_id doubri (and potentially more for this trip) does not have a schedule_relationship
- trip_id 21833758 does not have a schedule_relationship
- trip_id 21834039 stop_id boucre3 (and potentially more for this trip) does not have a schedule_relationship
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 | 159 | 28 times (93 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 3,144 | 28 times (93 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 250 | 25 times (83 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 250 | 25 times (83 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-01 at 04:59 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-01-01 at 04:59 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1767239951"
}
}