gtfs-rt Transport open dataset - Mises à jour des trajets en temps réel GTFS-RT for Réseau urbain Bibus

Resource details

File name: Mises à jour des trajets en temps réel GTFS-RT

Format: gtfs-rt

Les mises à jour des trajets vous informent des fluctuations d’horaires.
Elles sont délivrées au format GTFS-realtime, voir https://developers.google.com/transit/gtfs-realtime/guides/trip-updates?hl=fr.

This resource file is part of the dataset Réseau urbain Bibus.

Download availability

Learn more

We test this resource download availability every hour by making an HTTP 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

❌3 536 errors, 6 652 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-03 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 29 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors

trip_id 16957525 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 16957535 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 16958640 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 16957546 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 16957539 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 29 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

route_id NAV does not exist in the GTFS data routes.txt
route_id NAV does not exist in the GTFS data routes.txt
route_id NAV does not exist in the GTFS data routes.txt
route_id NAV does not exist in the GTFS data routes.txt
route_id NAV does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 161 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

trip_id 16549706 stop_id ROBERV_3 does not exist in GTFS data stops.txt
trip_id 16957525 stop_id DEP_KER2 does not exist in GTFS data stops.txt
trip_id 16550007 stop_id P GROA_2 does not exist in GTFS data stops.txt
trip_id 16550007 stop_id P AMIS_1 does not exist in GTFS data stops.txt
trip_id 16957535 stop_id DEP_KER2 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 376 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 16550595 stop_sequence 28 arrival_time 09:41:09 (1743666069) is less than previous stop arrival_time 09:41:26 (1743666086) - times must increase between two sequential stops
trip_id 16550595 stop_sequence 28 arrival_time 09:41:09 (1743666069) is less than previous stop departure_time 09:41:26 (1743666086) - times must increase between two sequential stops
trip_id 16550595 stop_sequence 28 departure_time 09:41:09 (1743666069) is less than previous stop departure_time 09:41:26 (1743666086) - times must increase between two sequential stops
trip_id 16550595 stop_sequence 28 departure_time 09:41:09 (1743666069) is less than previous stop arrival_time 09:41:26 (1743666086) - times must increase between two sequential stops
trip_id 17021100 stop_sequence 3 arrival_time 18:20:00 (1743697200) is less than previous stop arrival_time 18:37:05 (1743698225) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 398 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors

GTFS-rt trip_id 16550595 stop_sequence 1 has stop_id STMICH_2 but GTFS stop_sequence 1 has stop_id BRANDA_1 - stop_ids should be the same
GTFS-rt trip_id 16550595 stop_sequence 2 has stop_id VHUGO_2 but GTFS stop_sequence 2 has stop_id STMICH_2 - stop_ids should be the same
GTFS-rt trip_id 16550595 stop_sequence 3 has stop_id REPUBL_2 but GTFS stop_sequence 3 has stop_id VHUGO_2 - stop_ids should be the same
GTFS-rt trip_id 16550595 stop_sequence 4 has stop_id GAMBET_2 but GTFS stop_sequence 4 has stop_id REPUBL_2 - stop_ids should be the same
GTFS-rt trip_id 16550595 stop_sequence 5 has stop_id KENNED_3 but GTFS stop_sequence 5 has stop_id GAMBET_2 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 1 543 errors

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Sample errors

GTFS-rt trip_id 16550308 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 17020994 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 16561155 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 17020987 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 16550497 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip

Warnings

timestamp not populated W001 1 663 errors

Timestamps should be populated for all elements

Sample errors

trip_id 16550308 does not have a timestamp
trip_id 17020994 does not have a timestamp
trip_id 16561155 does not have a timestamp
trip_id 16550595 does not have a timestamp
trip_id 17020987 does not have a timestamp

vehicle_id not populated W002 1 663 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 16550308 does not have a vehicle_id
trip_id 17020994 does not have a vehicle_id
trip_id 16561155 does not have a vehicle_id
trip_id 16550595 does not have a vehicle_id
trip_id 17020987 does not have a vehicle_id

schedule_relationship not populated W009 3 326 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 16550308 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
trip_id 16550308 does not have a schedule_relationship
trip_id 17020994 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
trip_id 17020994 does not have a schedule_relationship
trip_id 16561155 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship

Validate this GTFS-RT now

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
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	2 212	30 times (100 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	735	30 times (100 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	4 539	30 times (100 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	5 085	30 times (100 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	42 571	30 times (100 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	42 538	30 times (100 % of validations)
W001	Timestamps should be populated for all elements	47 341	30 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	47 341	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	94 682	30 times (100 % of validations)
E025	Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-04 at 01:59 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-04-04 at 01:59 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1743724758"
  }
}