Resource details
This resource file is part of the dataset Réseau interurbain de Corse du Sud.
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
❌107 errors, 12 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-03 at 09:00 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 9 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 49802e9a-ba0c-487d-b927-70d99038fe06 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1003299-1004673 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1000337-1000583 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1005271-1007129 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 8 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id VIGGIRM9 does not exist in the GTFS data routes.txt
- route_id 1000231 does not exist in the GTFS data routes.txt
- route_id 1000210 does not exist in the GTFS data routes.txt
- route_id 1000377 does not exist in the GTFS data routes.txt
- route_id 1000219 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 54 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 stop_id STP-GIRM9 does not exist in GTFS data stops.txt
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 stop_id STP-VIGM9 does not exist in GTFS data stops.txt
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 stop_id STP-GIRM9 does not exist in GTFS data stops.txt
- trip_id 1003299-1004673 stop_id 1002680 does not exist in GTFS data stops.txt
- trip_id 1003299-1004673 stop_id 1010960 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 3 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 1003299-1004673 stop_sequence 8 arrival_time 08:21:27 (1743661287) is less than previous stop arrival_time 08:39:59 (1743662399) - times must increase between two sequential stops
- trip_id 1003299-1004673 stop_sequence 8 arrival_time 08:21:27 (1743661287) is less than previous stop departure_time 08:40:22 (1743662422) - times must increase between two sequential stops
- trip_id 1005271-1007129 stop_sequence 8 arrival_time 08:49:00 (1743662940) is less than previous stop departure_time 08:53:41 (1743663221) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 33 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 1433719e-307e-4463-99dd-08199accca7a stop_sequence 5 has stop_id STP-TR00013-R but GTFS stop_sequence 5 has stop_id STP-TR00012-R - stop_ids should be the same
- GTFS-rt trip_id 1433719e-307e-4463-99dd-08199accca7a stop_sequence 6 has stop_id STP-TR00012-R but GTFS stop_sequence 6 has stop_id STP-TR00011-R - stop_ids should be the same
- GTFS-rt trip_id 1433719e-307e-4463-99dd-08199accca7a stop_sequence 7 has stop_id STP-TR00011-R but GTFS stop_sequence 7 has stop_id STP-TR00010-R - stop_ids should be the same
- GTFS-rt trip_id 1433719e-307e-4463-99dd-08199accca7a stop_sequence 8 has stop_id STP-TR00010-R but GTFS stop_sequence 8 has stop_id STP-TR00009-R - stop_ids should be the same
- GTFS-rt trip_id 1433719e-307e-4463-99dd-08199accca7a stop_sequence 9 has stop_id STP-TR00009-R but GTFS stop_sequence 9 has stop_id STP-TR00008 - stop_ids should be the same
Warnings
timestamp not populated W001 12 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1433719e-307e-4463-99dd-08199accca7a does not have a timestamp
- trip_id 8d5d5f4d-7644-46f0-aef6-c5bb00f11d28 does not have a timestamp
- trip_id 49802e9a-ba0c-487d-b927-70d99038fe06 does not have a timestamp
- trip_id 597c6cdb-9581-41d2-b234-632e7655c19a does not have a timestamp
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 does not have a timestamp
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 |
---|---|---|---|
W001 | Timestamps should be populated for all elements | 2 959 | 27 times (90 % 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 | 1 525 | 26 times (87 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 2 821 | 24 times (80 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 2 810 | 24 times (80 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 24 163 | 24 times (80 % of validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 666 | 21 times (70 % 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 | 21 | 18 times (60 % 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. | 163 | 17 times (57 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-03 at 13:21 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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 2025-04-03 at 13:21 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "825726",
"trip_update": {
"stop_time_update": [
{
"departure": {
"delay": 23075,
"time": "1743678575"
},
"stop_id": "1001868",
"stop_sequence": 1
},
{
"arrival": {
"delay": 23089,
"time": "1743678649"
},
"departure": {
"delay": 23099,
"time": "1743678659"
},
"stop_id": "1002030",
"stop_sequence": 2
},
{
"arrival": {
"delay": 22902,
"time": "1743678702"
},
"departure": {
"delay": 22914,
"time": "1743678714"
},
"stop_id": "1002031",
"stop_sequence": 3
},
{
"arrival": {
"time": "1743678703"
},
"departure": {
"time": "1743678715"
},
"stop_id": "1001787",
"stop_sequence": 4
},
{
"arrival": {
"time": "1743678704"
},
"departure": {
"time": "1743678716"
},
"stop_id": "1001785",
"stop_sequence": 5
},
{
"arrival": {
"time": "1743678705"
},
"departure": {
"time": "1743678717"
},
"stop_id": "1001788",
"stop_sequence": 6
},
{
"arrival": {
"time": "1743678706"
},
"stop_id": "1001786",
"stop_sequence": 7
}
],
"trip": {
"direction_id": 0,
"route_id": "1000054",
"schedule_relationship": "SCHEDULED",
"start_date": "20250403",
"start_time": "06:45:00",
"trip_id": "1000175-1000419"
},
"vehicle": {
"id": "186",
"label": "STIB-01",
"license_plate": "DA-979-NJ"
}
}
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743679314"
}
}