Resource details
This resource file is part of the dataset Réseau urbain CarSud.
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
❌266 errors, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-13 at 09:12 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 73 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 1061 stop_sequence 2 arrival_time 11:41:26 (1789285286) is less than previous stop departure_time 11:41:32 (1789285292) - times must increase between two sequential stops
- trip_id 1061 stop_sequence 3 arrival_time 11:42:01 (1789285321) is less than previous stop departure_time 11:42:18 (1789285338) - times must increase between two sequential stops
- trip_id 1061 stop_sequence 4 arrival_time 11:43:03 (1789285383) is less than previous stop departure_time 11:43:05 (1789285385) - times must increase between two sequential stops
- trip_id 1061 stop_sequence 5 arrival_time 11:43:57 (1789285437) is less than previous stop departure_time 11:44:06 (1789285446) - times must increase between two sequential stops
- trip_id 1061 stop_sequence 6 arrival_time 11:44:50 (1789285490) is less than previous stop departure_time 11:45:03 (1789285503) - times must increase between two sequential stops
trip start_time does not match first GTFS arrival_time E023 2 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 vehicle_id zenbus:Vehicle:364610008:LOC trip_id 1002 start_time is 10:50:00 and GTFS initial arrival_time is 16:35:00 - times do not match
- GTFS-rt trip_id 1002 start_time is 10:50:00 and GTFS initial arrival_time is 16:35:00 - times do 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 zenbus:Vehicle:364610008:LOC trip_id 1002 at (-21.375313,55.629055) 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 zenbus:Vehicle:4792280515870720:LOC trip_id 1128 at (-21.282091,55.528667) 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 zenbus:Vehicle:4900826771357696:LOC trip_id 1033 at (-21.239527,55.517326) 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 zenbus:Vehicle:5934103225434112:LOC trip_id 1129 at (-21.271624,55.519302) 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 zenbus:Vehicle:4858907118796800:LOC trip_id 1032 at (-21.196386,55.53895) 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 12 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 zenbus:Vehicle:364610008:LOC trip_id 1002 has route_id 81 but belongs to GTFS route_id 83 in GTFS trips.txt
- GTFS-rt entity ID 1172 trip_id 1002 has route_id 81 but belongs to GTFS route_id 83 in GTFS trips.txt
- GTFS-rt entity ID zenbus:Vehicle:4792280515870720:LOC trip_id 1128 has route_id T01 but belongs to GTFS route_id T06 in GTFS trips.txt
- GTFS-rt entity ID 1184 trip_id 1128 has route_id T01 but belongs to GTFS route_id T06 in GTFS trips.txt
- GTFS-rt entity ID zenbus:Vehicle:4900826771357696:LOC trip_id 1033 has route_id T03 but belongs to GTFS route_id T12 in GTFS trips.txt
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 172 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 1177 stop_sequence 46 has stop_id SJ00990C but GTFS stop_sequence 46 has stop_id SJ00980C - stop_ids should be the same
- GTFS-rt trip_id 1177 stop_sequence 47 has stop_id SJ01000C but GTFS stop_sequence 47 has stop_id SJ00990C - stop_ids should be the same
- GTFS-rt trip_id 1177 stop_sequence 48 has stop_id SJ01010C but GTFS stop_sequence 48 has stop_id SJ01000C - stop_ids should be the same
- GTFS-rt trip_id 1177 stop_sequence 49 has stop_id SJ01020C but GTFS stop_sequence 49 has stop_id SJ01010C - stop_ids should be the same
- GTFS-rt trip_id 1177 stop_sequence 50 has stop_id SJ01030C but GTFS stop_sequence 50 has stop_id SJ01020C - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 1 error
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 1061 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
Warnings
vehicle_id not populated W002 1 error
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1177 does not have a vehicle_id
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 1177 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 8,028 | 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 | 14,718 | 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 | 374 | 30 times (100 % 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. | 117 | 27 times (90 % of validations) |
| E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 349 | 25 times (83 % 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 | 64 | 23 times (77 % of validations) |
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 113 | 21 times (70 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 229 | 19 times (63 % 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 | 228 | 19 times (63 % of validations) |
| W006 | trip should include a trip_id | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-09-14 at 00:23 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-09-14 at 00:23 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1789338196"
}
}