Resource details
Version Fil Bleu des alertes de services au format GTFS-RT
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
❌3 080 errors, 304 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-18 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 69 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 stop_sequence [9, 18, 16, 11, 10, 15, 7, 12, 13, 8, 14, 17] is not strictly sorted by increasing stop_sequence
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698396 stop_sequence [28, 18, 23, 16, 20, 25, 27, 24, 17, 15, 21, 22, 14, 26, 19] is not strictly sorted by increasing stop_sequence
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698346 stop_sequence [33, 13] is not strictly sorted by increasing stop_sequence
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698341 stop_sequence [45, 26] is not strictly sorted by increasing stop_sequence
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698329 stop_sequence [32, 21] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 2 952 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:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 stop_sequence 16 arrival_time 09:17:09 (1752823029) is less than previous stop arrival_time 09:20:10 (1752823210) - times must increase between two sequential stops
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 stop_sequence 16 arrival_time 09:17:09 (1752823029) is less than previous stop departure_time 09:20:10 (1752823210) - times must increase between two sequential stops
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 stop_sequence 16 departure_time 09:17:09 (1752823029) is less than previous stop departure_time 09:20:10 (1752823210) - times must increase between two sequential stops
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 stop_sequence 16 departure_time 09:17:09 (1752823029) is less than previous stop arrival_time 09:20:10 (1752823210) - times must increase between two sequential stops
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 stop_sequence 11 arrival_time 09:12:10 (1752822730) is less than previous stop arrival_time 09:17:09 (1752823029) - times must increase between two sequential stops
GTFS-rt stop_sequence not found in GTFS data E051 59 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:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698346 contains stop_sequence 13 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698341 contains stop_sequence 26 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698329 contains stop_sequence 21 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698220 contains stop_sequence 52 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698090 contains stop_sequence 38 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 76 errors
Timestamps should be populated for all elements
Sample errors
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698495 does not have a timestamp
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 does not have a timestamp
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698396 does not have a timestamp
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698346 does not have a timestamp
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698341 does not have a timestamp
vehicle_id not populated W002 76 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698495 does not have a vehicle_id
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 does not have a vehicle_id
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698396 does not have a vehicle_id
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698346 does not have a vehicle_id
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698341 does not have a vehicle_id
schedule_relationship not populated W009 152 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698495 stop_sequence 15 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698495 does not have a schedule_relationship
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 stop_sequence 9 (and potentially more for this trip) does not have a schedule_relationship
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698453 does not have a schedule_relationship
- trip_id TTR:BUSTRAMETE_2025_V2:1637_PT2-PH3-VENDREDI:698396 stop_sequence 28 (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 | 1 942 | 26 times (90 % of validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 80 208 | 26 times (90 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 1 671 | 26 times (90 % of validations) |
W001 | Timestamps should be populated for all elements | 2 130 | 26 times (90 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 130 | 26 times (90 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 4 260 | 26 times (90 % 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 | 1 times (3 % 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-07-19 at 01:59 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-07-19 at 01:59 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1752883191"
}
}