Resource details
This resource file is part of the dataset Réseau urbain TUB.
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
❌4 errors, 15 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-14 at 09: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 3-275710002 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 3-275710002 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 3-275710002 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 3-275710002 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 3-304054560 does not have a vehicle_id
- trip_id 3-282329443 does not have a vehicle_id
- trip_id 3-303399199-03021-_____S_ does not have a vehicle_id
- trip_id 3-275710002 does not have a vehicle_id
- trip_id 3-292487219 does not have a vehicle_id
schedule_relationship not populated W009 10 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 3-304054560 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 3-304054560 does not have a schedule_relationship
- trip_id 3-282329443 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 3-282329443 does not have a schedule_relationship
- trip_id 3-303399199-03021-_____S_ stop_sequence 1 (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 |
---|---|---|---|
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 144 | 23 times (79 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 288 | 23 times (79 % of validations) |
E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 21 | 21 times (72 % of validations) |
E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 21 | 21 times (72 % of validations) |
E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 21 | 21 times (72 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 21 | 21 times (72 % of validations) |
W008 | The data in a GTFS-realtime feed should always be less than one minute old | 11 | 11 times (38 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-15 at 10:50 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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-06-15 at 10:50 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:3-282984457",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"delay": 44,
"time": "1749977324"
},
"stopId": "BDCTH3",
"stopSequence": 1
},
{
"departure": {
"delay": 640,
"time": "1749977920"
},
"stopId": "BDCTH3",
"stopSequence": 1
},
{
"arrival": {
"delay": 40,
"time": "1749978040"
},
"stopId": "BDBRD2",
"stopSequence": 7
}
],
"timestamp": "1749977341",
"trip": {
"directionId": 1,
"routeId": "16",
"tripId": "3-282984457"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1749977402"
}
}