Resource details
Les 2 types de données sont mises à disposition dans ce flux de données temps réel.
Pour l’instant les données sont diffusées en GTFS-RT et en Siri lorsque le flux sera disponible.
This resource file is part of the dataset Réseau urbain Citibus.
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
❌193 errors, 1 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-23 at 08:14 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 17 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 300000007 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 300000149 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 300000219 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 300000509 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 300000917 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip start_time does not match first GTFS arrival_time E023 13 errors
For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip
Sample errors
- GTFS-rt trip_id 300000205 start_time is 07:25:00 and GTFS initial arrival_time is 12:05:00 - times do not match
- GTFS-rt trip_id 300000088 start_time is 07:27:00 and GTFS initial arrival_time is 08:46:00 - times do not match
- GTFS-rt trip_id 300000358 start_time is 07:35:00 and GTFS initial arrival_time is 17:57:00 - times do not match
- GTFS-rt trip_id 300000124 start_time is 07:50:00 and GTFS initial arrival_time is 12:50:00 - times do not match
- GTFS-rt trip_id 300000796 start_time is 07:52:00 and GTFS initial arrival_time is 08:54:00 - times do not match
trip direction_id does not match GTFS data E024 14 errors
GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt
Sample errors
- GTFS-rt trip_id 300000205 trip.direction_id is 0 but GTFS trip.direction_id is 1 - direction_id does not match
- GTFS-rt trip_id 300000088 trip.direction_id is 0 but GTFS trip.direction_id is 1 - direction_id does not match
- GTFS-rt trip_id 300000124 trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt trip_id 300000796 trip.direction_id is 0 but GTFS trip.direction_id is 1 - direction_id does not match
- GTFS-rt trip_id 300000085 trip.direction_id is 0 but GTFS trip.direction_id is 1 - direction_id does not match
Vehicle position far from trip shape E029 6 errors
The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.
Sample errors
- vehicle.id narbonne-712 trip_id 300000205 at (43.18588,3.0204415) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id narbonne-603 trip_id 300000358 at (43.18479,3.0001726) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id narbonne-713 trip_id 300000085 at (43.18766,2.9966717) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id narbonne-714 trip_id 300000104 at (43.165073,2.9881632) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id narbonne-707 trip_id 300000435 at (43.191814,3.0150628) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
GTFS-rt trip.trip_id does not belong to GTFS-rt trip.route_id in GTFS trips.txt E035 26 errors
The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt
Sample errors
- GTFS-rt entity ID trip-300000205 trip_id 300000205 has route_id D but belongs to GTFS route_id 15 in GTFS trips.txt
- GTFS-rt entity ID trip-300000088 trip_id 300000088 has route_id E but belongs to GTFS route_id 6 in GTFS trips.txt
- GTFS-rt entity ID trip-300000358 trip_id 300000358 has route_id C but belongs to GTFS route_id CIT2 in GTFS trips.txt
- GTFS-rt entity ID trip-300000124 trip_id 300000124 has route_id D but belongs to GTFS route_id 20 in GTFS trips.txt
- GTFS-rt entity ID trip-300000796 trip_id 300000796 has route_id A but belongs to GTFS route_id CIT2 in GTFS trips.txt
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 113 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 300000205 stop_sequence 29 has stop_id _2572 but GTFS stop_sequence 29 has stop_id _2731 - stop_ids should be the same
- GTFS-rt trip_id 300000205 stop_sequence 30 has stop_id _2444 but GTFS stop_sequence 30 has stop_id _2615 - stop_ids should be the same
- GTFS-rt trip_id 300000205 stop_sequence 31 has stop_id _2442 but GTFS stop_sequence 31 has stop_id _2543 - stop_ids should be the same
- GTFS-rt trip_id 300000205 stop_sequence 32 has stop_id _2580 but GTFS stop_sequence 32 has stop_id _2733 - stop_ids should be the same
- GTFS-rt trip_id 300000205 stop_sequence 33 has stop_id _2506 but GTFS stop_sequence 33 has stop_id _2449 - stop_ids should be the same
VehiclePosition and TripUpdate ID pairing mismatch E047 1 error
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- trip_id 300000124 and vehicle_id narbonne-605 pairing in VehiclePositions does not match trip_id 300000127 and vehicle_id narbonne-605 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
GTFS-rt stop_sequence not found in GTFS data E051 3 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 300000358 contains stop_sequence 27 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 300000124 contains stop_sequence 26 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 300000796 contains stop_sequence 17 that does not exist in GTFS stop_times.txt for this trip
Warnings
ID in one feed missing from the other W003 1 error
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id 300000127 is in TripUpdates but not in VehiclePositions feed
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 | 386 | 24 times (80 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 304 | 24 times (80 % of validations) |
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 262 | 24 times (80 % of validations) |
| E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 554 | 24 times (80 % 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 | 2,799 | 24 times (80 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 170 | 22 times (73 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 48 | 21 times (70 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 89 | 19 times (63 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 73 | 13 times (43 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-24 at 04:29 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-01-24 at 04:29 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1769225394"
}
}