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
❌801 errors, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-04 at 08:07 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 4 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 430 stop_sequence 54 arrival_time 11:13:07 (1762240387) is less than previous stop departure_time 11:13:35 (1762240415) - times must increase between two sequential stops
- trip_id 707 stop_sequence 6 arrival_time 11:15:48 (1762240548) is less than previous stop departure_time 11:16:59 (1762240619) - times must increase between two sequential stops
- trip_id 707 stop_sequence 7 arrival_time 11:16:43 (1762240603) is less than previous stop departure_time 11:17:29 (1762240649) - times must increase between two sequential stops
- trip_id 707 stop_sequence 8 arrival_time 11:17:25 (1762240645) is less than previous stop departure_time 11:17:56 (1762240676) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 791 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 212 stop_sequence 6 has stop_id SJ0025P but GTFS stop_sequence 6 has stop_id SJ0030P - stop_ids should be the same
- GTFS-rt trip_id 212 stop_sequence 7 has stop_id SJ0020P but GTFS stop_sequence 7 has stop_id SJ0025P - stop_ids should be the same
- GTFS-rt trip_id 212 stop_sequence 8 has stop_id SJ0015P but GTFS stop_sequence 8 has stop_id SJ0020P - stop_ids should be the same
- GTFS-rt trip_id 212 stop_sequence 9 has stop_id SJ0010P but GTFS stop_sequence 9 has stop_id SJ0015P - stop_ids should be the same
- GTFS-rt trip_id 212 stop_sequence 10 has stop_id SJ0005P but GTFS stop_sequence 10 has stop_id SJ0010P - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 6 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 696 contains stop_sequence 75 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 708 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 917 contains stop_sequence 36 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 438 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 707 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 536 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 536 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 |
|---|---|---|---|
| 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 | 19 516 | 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 | 203 | 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. | 157 | 27 times (90 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 57 | 26 times (87 % 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 | 57 | 26 times (87 % 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. | 22 | 12 times (40 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-04 at 21:38 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 2025-11-04 at 21:38 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1762288719"
}
}