Resource details

File name: Horaire temps réel (GTFS-RT PROTOBUF) - réseau Corolis (interurbain)
Format: gtfs-rt

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

2025-09-13
100%
2025-09-14
100%
2025-09-15
100%
2025-09-16
100%
2025-09-17
100%
2025-09-18
100%
2025-09-19
100%
2025-09-20
100%
2025-09-21
99.3%
2025-09-22
100%
2025-09-23
97.9%
2025-09-24
100%
2025-09-25
100%
2025-09-26
100%
2025-09-27
100%
2025-09-28
100%
2025-09-29
100%
2025-09-30
100%
2025-10-01
100%
2025-10-02
100%
2025-10-03
100%
2025-10-04
100%
2025-10-05
100%
2025-10-06
100%
2025-10-07
100%
2025-10-08
100%
2025-10-09
100%
2025-10-10
100%
2025-10-11
100%
2025-10-12
100%
2025-10-13
100%
Learn more
We test this resource download availability every hour by making an HTTP 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

⚠️35 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-10-13 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 12 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 53212 does not have a vehicle_id
  • trip_id 51105 does not have a vehicle_id
  • trip_id 51411 does not have a vehicle_id
  • trip_id 51501 does not have a vehicle_id
  • trip_id 51701 does not have a vehicle_id

schedule_relationship not populated W009 23 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 53212 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 53212 does not have a schedule_relationship
  • trip_id 51105 stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 51105 does not have a schedule_relationship
  • trip_id 51411 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
Validate this GTFS-RT now

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 276 30 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 542 30 times (100 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 4 4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-10-13 at 22:29 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-10-13 at 22:29 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1760387345" } }