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 545 errors, 556 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-03 at 08:12 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 132 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:11734_PT2-PH3-MERCREDI:746903 stop_sequence [37, 43, 17] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746831 stop_sequence [17, 24, 22, 23, 20, 16, 21, 18, 19] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746763 stop_sequence [26, 29, 30, 28, 25, 24, 23, 27, 22] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746750 stop_sequence [5, 14, 18, 23, 15] is not strictly sorted by increasing stop_sequence
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746706 stop_sequence [26, 29, 17] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 5 302 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:11734_PT2-PH3-MERCREDI:746903 stop_sequence 17 arrival_time 08:14:20 (1764746060) is less than previous stop arrival_time 08:47:10 (1764748030) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746903 stop_sequence 17 arrival_time 08:14:20 (1764746060) is less than previous stop departure_time 08:47:10 (1764748030) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746903 stop_sequence 17 departure_time 08:14:20 (1764746060) is less than previous stop departure_time 08:47:10 (1764748030) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746903 stop_sequence 17 departure_time 08:14:20 (1764746060) is less than previous stop arrival_time 08:47:10 (1764748030) - times must increase between two sequential stops
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746903 stop_sequence 35 arrival_time 08:34:10 (1764747250) is less than previous stop arrival_time 08:53:10 (1764748390) - times must increase between two sequential stops
GTFS-rt stop_sequence not found in GTFS data E051 111 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:11734_PT2-PH3-MERCREDI:746903 contains stop_sequence 17 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746750 contains stop_sequence 15 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746706 contains stop_sequence 17 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746673 contains stop_sequence 21 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746664 contains stop_sequence 17 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 139 errors
Timestamps should be populated for all elements
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746903 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746831 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746763 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746750 does not have a timestamp
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746706 does not have a timestamp
vehicle_id not populated W002 139 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746903 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746831 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746763 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746750 does not have a vehicle_id
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746706 does not have a vehicle_id
schedule_relationship not populated W009 278 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746903 stop_sequence 37 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746903 does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746831 stop_sequence 17 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746831 does not have a schedule_relationship
- trip_id TTR:OFFRE_RENTREE25_V2:11734_PT2-PH3-MERCREDI:746763 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 152 | 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. | 130 606 | 30 times (100 % of validations) |
| W001 | Timestamps should be populated for all elements | 3 391 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 3 391 | 30 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 6 782 | 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 642 | 15 times (50 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 1 381 | 15 times (50 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 2 | 2 times (7 % 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.