Resource details
Le message TripUpdate au format GTFS-RT est disponibles dans ce flux.
This resource file is part of the dataset Réseau urbain Distribus.
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
❌177 errors, 30 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-10 at 10:54 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_updates have the same stop_id E037 22 errors
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id 1-257622037 has repeating stop_id 6248 at stop_sequence 10 - sequential stop_ids should be different
- trip_id 1-257622039 has repeating stop_id 6248 at stop_sequence 10 - sequential stop_ids should be different
- trip_id 1-258736168 has repeating stop_id 6248 at stop_sequence 10 - sequential stop_ids should be different
- trip_id 1-258277379 has repeating stop_id 6248 at stop_sequence 10 - sequential stop_ids should be different
- trip_id 1-258474011 has repeating stop_id 6248 at stop_sequence 10 - sequential stop_ids should be different
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 155 errors
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- GTFS-rt trip_id 1-257622037 stop_sequence 10 has stop_id 6248 but GTFS stop_sequence 10 has stop_id 11493 - stop_ids should be the same
- GTFS-rt trip_id 1-257622037 stop_sequence 11 has stop_id 11493 but GTFS stop_sequence 11 has stop_id 9624 - stop_ids should be the same
- GTFS-rt trip_id 1-257622037 stop_sequence 12 has stop_id 9624 but GTFS stop_sequence 12 has stop_id 6214 - stop_ids should be the same
- GTFS-rt trip_id 1-257622037 stop_sequence 13 has stop_id 6214 but GTFS stop_sequence 13 has stop_id 6226 - stop_ids should be the same
- GTFS-rt trip_id 1-257622037 stop_sequence 14 has stop_id 6226 but GTFS stop_sequence 14 has stop_id 19673 - stop_ids should be the same
Warnings
vehicle_id not populated W002 30 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-710672404 does not have a vehicle_id
- trip_id 1-711262212 does not have a vehicle_id
- trip_id 1-710475777 does not have a vehicle_id
- trip_id 1-711458817 does not have a vehicle_id
- trip_id 1-710672386 does not have a vehicle_id
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 |
|---|---|---|---|
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 424 | 24 times (96 % 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 | 2 914 | 24 times (96 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 582 | 24 times (96 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 3 | 1 times (4 % of validations) |
GTFS-RT feed content
Could not decode the GTFS-RT feed.
The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.