gtfs-rt Transport open dataset - filbleu-gtfsrt-tripupdates for Réseau urbain et périurbain Fil Bleu

Resource details

File name: filbleu-gtfsrt-tripupdates

Format: gtfs-rt

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

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

❌4 717 errors, 464 warnings

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

Errors

stop_times_updates not strictly sorted E002 106 errors

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors

trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 stop_sequence [17, 15] is not strictly sorted by increasing stop_sequence
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659153 stop_sequence [18, 19, 20, 21, 23, 24, 17] is not strictly sorted by increasing stop_sequence
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654108 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:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654076 stop_sequence [18, 17] is not strictly sorted by increasing stop_sequence
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654017 stop_sequence [30, 20, 25, 18, 22, 27, 29, 26, 19, 23, 24, 28, 21] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 4 516 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:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 stop_sequence 15 arrival_time 09:11:36 (1743664296) is less than previous stop arrival_time 09:14:36 (1743664476) - times must increase between two sequential stops
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 stop_sequence 15 arrival_time 09:11:36 (1743664296) is less than previous stop departure_time 09:14:36 (1743664476) - times must increase between two sequential stops
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 stop_sequence 15 departure_time 09:11:36 (1743664296) is less than previous stop departure_time 09:14:36 (1743664476) - times must increase between two sequential stops
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 stop_sequence 15 departure_time 09:11:36 (1743664296) is less than previous stop arrival_time 09:14:36 (1743664476) - times must increase between two sequential stops
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 stop_sequence 22 arrival_time 09:21:32 (1743664892) is less than previous stop arrival_time 09:24:36 (1743665076) - times must increase between two sequential stops

GTFS-rt stop_sequence not found in GTFS data E051 95 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:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 contains stop_sequence 15 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659153 contains stop_sequence 17 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:653960 contains stop_sequence 13 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:653943 contains stop_sequence 26 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:653926 contains stop_sequence 21 that does not exist in GTFS stop_times.txt for this trip

Warnings

timestamp not populated W001 116 errors

Timestamps should be populated for all elements

Sample errors

trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 does not have a timestamp
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659153 does not have a timestamp
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654108 does not have a timestamp
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654076 does not have a timestamp
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654017 does not have a timestamp

vehicle_id not populated W002 116 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 does not have a vehicle_id
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659153 does not have a vehicle_id
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654108 does not have a vehicle_id
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654076 does not have a vehicle_id
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654017 does not have a vehicle_id

schedule_relationship not populated W009 232 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 stop_sequence 17 (and potentially more for this trip) does not have a schedule_relationship
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659185 does not have a schedule_relationship
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659153 stop_sequence 18 (and potentially more for this trip) does not have a schedule_relationship
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:659153 does not have a schedule_relationship
trip_id TTR:BUSTRAM2024-2025_V2:1571_PT2-PH1-JEUDI:654108 stop_sequence 9 (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
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	3 115	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.	129 938	30 times (100 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	2 668	30 times (100 % of validations)
W001	Timestamps should be populated for all elements	3 344	30 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	3 344	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	6 688	30 times (100 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-04 at 01:59 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 5 749 seconds. Try to update your feed at most every 30 seconds.

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-04-04 at 01:59 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1743724791"
  }
}