Resource details
Version Fil Bleu des mises à jour de trajets (retards, annulations, itinéraires modifiés) au format GTFS-RT (
filbleu-gtfsrt-tripupdates)
This resource file is part of the dataset Réseau urbain et périurbain Fil Bleu.
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
❌5 965 errors, 600 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-27 at 08:17 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 137 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence [25, 28, 29, 27, 24, 23, 22, 26] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740353 stop_sequence [14, 18, 22, 15] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740309 stop_sequence [25, 28, 16] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740289 stop_sequence [5, 2] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740276 stop_sequence [18, 22, 24, 26, 21] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 5 712 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 TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 27 arrival_time 08:25:17 (1764228317) is less than previous stop arrival_time 08:29:17 (1764228557) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 27 arrival_time 08:25:17 (1764228317) is less than previous stop departure_time 08:29:17 (1764228557) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 27 departure_time 08:25:17 (1764228317) is less than previous stop departure_time 08:29:17 (1764228557) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 27 departure_time 08:25:17 (1764228317) is less than previous stop arrival_time 08:29:17 (1764228557) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 24 arrival_time 08:21:17 (1764228077) is less than previous stop arrival_time 08:25:17 (1764228317) - times must increase between two sequential stops
GTFS-rt stop_sequence not found in GTFS data E051 116 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 TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740353 contains stop_sequence 15 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740309 contains stop_sequence 16 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740289 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740276 contains stop_sequence 21 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740267 contains stop_sequence 16 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 150 errors
Timestamps should be populated for all elements
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740353 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740338 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740309 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740289 does not have a timestamp
vehicle_id not populated W002 150 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740353 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740338 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740309 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740289 does not have a vehicle_id
schedule_relationship not populated W009 300 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 stop_sequence 25 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740366 does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740353 stop_sequence 14 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740353 does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11724_PT2-PH1-JEUDI:740338 stop_sequence 26 (and potentially more for this trip) 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 |
|---|---|---|---|
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 3 031 | 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. | 125 800 | 30 times (100 % of validations) |
| W001 | Timestamps should be populated for all elements | 3 268 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 3 268 | 30 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 6 536 | 30 times (100 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 795 | 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 160 | 13 times (43 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 3 | 3 times (10 % of validations) |
GTFS-RT feed content
Could not decode the GTFS-RT feed.
The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.