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

❌6 028 errors, 592 warnings

Shapes present in the GTFS have been ignored, some rules are not enforced.

Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-17 at 08:12 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 141 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:1569_PT2-PH1-MARDI:654153 stop_sequence [14, 5] is not strictly sorted by increasing stop_sequence
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654075 stop_sequence [9, 18, 16, 11, 10, 15, 7, 12, 6, 13, 8, 14, 17] is not strictly sorted by increasing stop_sequence
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654061 stop_sequence [16, 14] is not strictly sorted by increasing stop_sequence
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654058 stop_sequence [12, 11, 8, 10, 9] is not strictly sorted by increasing stop_sequence
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654050 stop_sequence [40, 9] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 5 768 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:1569_PT2-PH1-MARDI:654153 stop_sequence 5 arrival_time 08:11:36 (1734419496) is less than previous stop arrival_time 08:21:33 (1734420093) - times must increase between two sequential stops
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654153 stop_sequence 5 arrival_time 08:11:36 (1734419496) is less than previous stop departure_time 08:21:33 (1734420093) - times must increase between two sequential stops
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654153 stop_sequence 5 departure_time 08:11:36 (1734419496) is less than previous stop departure_time 08:21:33 (1734420093) - times must increase between two sequential stops
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654153 stop_sequence 5 departure_time 08:11:36 (1734419496) is less than previous stop arrival_time 08:21:33 (1734420093) - times must increase between two sequential stops
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654153 stop_sequence 7 arrival_time 08:12:44 (1734419564) is less than previous stop arrival_time 08:17:44 (1734419864) - times must increase between two sequential stops

GTFS-rt stop_sequence not found in GTFS data E051 119 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:1569_PT2-PH1-MARDI:654153 contains stop_sequence 5 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654061 contains stop_sequence 14 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654050 contains stop_sequence 9 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654018 contains stop_sequence 18 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654008 contains stop_sequence 28 that does not exist in GTFS stop_times.txt for this trip

Warnings

timestamp not populated W001 148 errors

Timestamps should be populated for all elements

Sample errors

trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654153 does not have a timestamp
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654075 does not have a timestamp
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654061 does not have a timestamp
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654058 does not have a timestamp
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654050 does not have a timestamp

vehicle_id not populated W002 148 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654153 does not have a vehicle_id
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654075 does not have a vehicle_id
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654061 does not have a vehicle_id
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654058 does not have a vehicle_id
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654050 does not have a vehicle_id

schedule_relationship not populated W009 296 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654153 stop_sequence 14 (and potentially more for this trip) does not have a schedule_relationship
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654153 does not have a schedule_relationship
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654075 stop_sequence 9 (and potentially more for this trip) does not have a schedule_relationship
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654075 does not have a schedule_relationship
trip_id TTR:BUSTRAM2024-2025_V2:1569_PT2-PH1-MARDI:654061 stop_sequence 16 (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 060	27 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.	126 920	27 times (90 % of validations)
W001	Timestamps should be populated for all elements	3 259	27 times (90 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	3 259	27 times (90 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	6 518	27 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 955	22 times (73 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	752	5 times (17 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	28	5 times (17 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-12-18 at 01:59 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 3 068 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 2024-12-18 at 01:59 Europe/Paris. You can look at the GTFS-RT documentation.


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