gtfs-rt Transport open dataset - Horaires temps réel des lignes du réseau TUB for Réseau urbain TUB - CA de Bar-le-Duc

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

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, 24 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-03-12 at 08:01 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 3-275775489 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 22] 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 3-275775489 has repeating stop_sequence 22 - 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 3-275775489 has repeating stop_id BDROC1 at stop_sequence 22 - 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 3-275775489 contains stop_sequence 22 that does not exist in GTFS stop_times.txt for this trip

Warnings

vehicle_id not populated W002 8 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 3-304054558 does not have a vehicle_id
trip_id 3-855703554 does not have a vehicle_id
trip_id 3-282263554 does not have a vehicle_id
trip_id 3-299040821 does not have a vehicle_id
trip_id 3-303399197 does not have a vehicle_id

schedule_relationship not populated W009 16 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 3-304054558 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 3-304054558 does not have a schedule_relationship
trip_id 3-855703554 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 3-855703554 does not have a schedule_relationship
trip_id 3-282263554 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	169	27 times (90 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	338	27 times (90 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	37	26 times (87 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	37	26 times (87 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	37	26 times (87 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	37	26 times (87 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	8	8 times (27 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	14	2 times (7 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	7	2 times (7 % 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-03-12 at 22:39 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 19 142 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-03-12 at 22:39 Europe/Paris. You can look at the GTFS-RT documentation.


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