Resource details

File name: Horaires temps réel des lignes du réseau TUB
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain TUB.

Download availability

2025-01-17
100%
2025-01-18
100%
2025-01-19
100%
2025-01-20
100%
2025-01-21
100%
2025-01-22
99.3%
2025-01-23
100%
2025-01-24
100%
2025-01-25
100%
2025-01-26
100%
2025-01-27
100%
2025-01-28
100%
2025-01-29
100%
2025-01-30
100%
2025-01-31
100%
2025-02-01
100%
2025-02-02
100%
2025-02-03
100%
2025-02-04
100%
2025-02-05
100%
2025-02-06
100%
2025-02-07
100%
2025-02-08
100%
2025-02-09
100%
2025-02-10
100%
2025-02-11
100%
2025-02-12
99.3%
2025-02-13
97.9%
2025-02-14
100%
2025-02-15
100%
2025-02-16
100%
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 errors, 16 warnings

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

Errors

stop_times_updates not strictly sorted E002 1 error

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

Sample errors
  • trip_id 2-275709965 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 20] is not strictly sorted by increasing stop_sequence

Sequential stop_time_updates have the same stop_sequence E036 1 error

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Sample errors
  • trip_id 2-275709965 has repeating stop_sequence 20 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 1 error

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors
  • trip_id 2-275709965 has repeating stop_id BDSEB1 at stop_sequence 20 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 1 error

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 2-275709965 contains stop_sequence 20 that does not exist in GTFS stop_times.txt for this trip

Warnings

vehicle_id not populated W002 5 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 2-304054525 does not have a vehicle_id
  • trip_id 2-282329104 does not have a vehicle_id
  • trip_id 2-275709965 does not have a vehicle_id
  • trip_id 2-303399166 does not have a vehicle_id
  • trip_id 2-292487187 does not have a vehicle_id

Header timestamp is older than 65 seconds W008 1 error

The data in a GTFS-realtime feed should always be less than one minute old

Sample errors
  • header.timestamp is 1206 min 32 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 10 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 2-304054525 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 2-304054525 does not have a schedule_relationship
  • trip_id 2-282329104 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 2-282329104 does not have a schedule_relationship
  • trip_id 2-275709965 stop_sequence 1 (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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 161 28 times (93 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 322 28 times (93 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 22 14 times (47 % of validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 22 14 times (47 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 22 14 times (47 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 22 14 times (47 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 9 9 times (30 % of validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-02-16 at 13:33 Europe/Paris.

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

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-02-16 at 13:33 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "1.0", "timestamp": "1739709225" } }