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
❌49 errors, 12 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-05 at 09:03 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 6 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 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 54b46d6c-4783-4b61-8e99-12cf0dead1fa does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 159b0c79-d8f8-4298-8580-c46ba45060f4 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1000338-1000584 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1005038-1006880 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 6 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id M009-01 does not exist in the GTFS data routes.txt
- route_id C13 does not exist in the GTFS data routes.txt
- route_id C13 does not exist in the GTFS data routes.txt
- route_id 1000211 does not exist in the GTFS data routes.txt
- route_id 1000397 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 36 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac stop_id STP-GIRM9 does not exist in GTFS data stops.txt
- trip_id 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac stop_id STP-VIGM9 does not exist in GTFS data stops.txt
- trip_id 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac stop_id STP-STP-PORM9 does not exist in GTFS data stops.txt
- trip_id 54b46d6c-4783-4b61-8e99-12cf0dead1fa stop_id STP-FAUBOURGSA does not exist in GTFS data stops.txt
- trip_id 54b46d6c-4783-4b61-8e99-12cf0dead1fa stop_id STP-CHJARASGIOLU does not exist in GTFS data stops.txt
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 error
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 9 has stop_id STP-TR00009 but GTFS stop_sequence 9 has stop_id STP-TR00009-R - stop_ids should be the same
Warnings
timestamp not populated W001 12 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 5e18d9dd-1160-45a7-80e0-5ca093f87550 does not have a timestamp
- trip_id 1433719e-307e-4463-99dd-08199accca7a does not have a timestamp
- trip_id 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac does not have a timestamp
- trip_id 49802e9a-ba0c-487d-b927-70d99038fe06 does not have a timestamp
- trip_id 7b028b99-002f-4b40-b2c9-ec71905b709c 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 148 | 30 times (100 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 148 | 30 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 862 | 30 times (100 % of validations) |
| W001 | Timestamps should be populated for all elements | 312 | 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 | 21 | 21 times (70 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 26 | 10 times (33 % 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 | 7 | 7 times (23 % 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. | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-05 at 21:13 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-06-05 at 21:13 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "850603",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"delay": -366,
"time": "1749134154"
},
"stopId": "1001857",
"stopSequence": 1
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "1001946",
"stopSequence": 2
},
{
"arrival": {
"delay": -1012,
"time": "1749135908"
},
"departure": {
"delay": -1002,
"time": "1749135918"
},
"stopId": "1002650",
"stopSequence": 3
},
{
"arrival": {
"delay": -1112,
"time": "1749136108"
},
"departure": {
"delay": -1101,
"time": "1749136119"
},
"stopId": "1002599",
"stopSequence": 4
},
{
"arrival": {
"delay": -1254,
"time": "1749136566"
},
"departure": {
"delay": -1238,
"time": "1749136582"
},
"stopId": "1002649",
"stopSequence": 5
},
{
"arrival": {
"delay": -1414,
"time": "1749137006"
},
"departure": {
"delay": -1369,
"time": "1749137051"
},
"stopId": "1002598",
"stopSequence": 6
},
{
"arrival": {
"delay": -1261,
"time": "1749137219"
},
"departure": {
"delay": -1244,
"time": "1749137236"
},
"stopId": "1002597",
"stopSequence": 7
},
{
"arrival": {
"delay": -1465,
"time": "1749137555"
},
"departure": {
"delay": -1451,
"time": "1749137569"
},
"stopId": "1002648",
"stopSequence": 8
},
{
"arrival": {
"time": "1749139200"
},
"stopId": "1001962",
"stopSequence": 9
}
],
"trip": {
"directionId": 1,
"routeId": "1000187",
"scheduleRelationship": "SCHEDULED",
"startDate": "20250605",
"startTime": "16:42:00",
"tripId": "1000551-1000801"
},
"vehicle": {
"id": "406",
"label": "MEF-05",
"licensePlate": "BD-043-MM"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1749150782"
}
}