Resource details
Données horaires temps réel, au format GTFS-RT PROTOBUF, du réseau Corolis (interurbain)
This resource file is part of the dataset Réseau interurbain Corolis.
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
❌1 error, 168 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-01 at 08:13 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_updates have the same stop_id E037 1 error
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id 51701 has repeating stop_id BEBAU2 at stop_sequence 9 - sequential stop_ids should be different
Warnings
vehicle_id not populated W002 57 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 50101 does not have a vehicle_id
- trip_id 53601 does not have a vehicle_id
- trip_id 53701 does not have a vehicle_id
- trip_id 53801 does not have a vehicle_id
- trip_id 50123 does not have a vehicle_id
schedule_relationship not populated W009 111 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 50101 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 50101 does not have a schedule_relationship
- trip_id 53601 stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 53601 does not have a schedule_relationship
- trip_id 53701 does not have a schedule_relationship
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 |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 020 | 23 times (79 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 997 | 23 times (79 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 4 | 3 times (10 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-02 at 04:34 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (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-12-02 at 04:34 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1764646445"
}
}