Resource details
Mises à jour des trajets
This resource file is part of the dataset Réseau urbain TaM.
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
❌57 errors, 274 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-20 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 13-1-T127-1-071000-13 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 38 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 1582780835-13 stop_id 93 arrival_time 07:55:44 (1763621744) is equal to previous stop arrival_time 07:55:44 (1763621744) - times must increase between two sequential stops
- trip_id 1582780835-13 stop_id 93 arrival_time 07:55:44 (1763621744) is equal to previous stop departure_time 07:55:44 (1763621744) - times must increase between two sequential stops
- trip_id 1582780835-13 stop_id 93 departure_time 07:55:44 (1763621744) is equal to previous stop departure_time 07:55:44 (1763621744) - times must increase between two sequential stops
- trip_id 1582780835-13 stop_id 93 departure_time 07:55:44 (1763621744) is equal to previous stop arrival_time 07:55:44 (1763621744) - times must increase between two sequential stops
- trip_id 1582780835-13 stop_id 159 arrival_time 07:55:44 (1763621744) is equal to previous stop arrival_time 07:55:44 (1763621744) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 error
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.
Sample errors
- trip_id 13-1-T131-0-073300 stop_id 1074 departure_time 07:32:52 (1763620372) is less than the same stop arrival_time 07:33:00 (1763620380) - departure time must be equal to or greater than arrival time
Sequential stop_time_updates have the same stop_id E037 17 errors
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id 13-1-T127-1-071000-13 has repeating stop_id 1071 - sequential stop_ids should be different
- trip_id 13-1-T127-1-071000-13 has repeating stop_id 1764 - sequential stop_ids should be different
- trip_id 13-1-T127-1-071000-13 has repeating stop_id 1072 - sequential stop_ids should be different
- trip_id 13-1-T127-1-071000-13 has repeating stop_id 1073 - sequential stop_ids should be different
- trip_id 13-1-T127-1-071000-13 has repeating stop_id 1074 - sequential stop_ids should be different
Warnings
vehicle_id not populated W002 274 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1582926369-13 does not have a vehicle_id
- trip_id 1582926221-13 does not have a vehicle_id
- trip_id 1582926399-13 does not have a vehicle_id
- trip_id 1582926429-13 does not have a vehicle_id
- trip_id 1582926430-13 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 367 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 6 841 | 30 times (100 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 174 | 21 times (70 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 130 | 13 times (43 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 1 108 | 11 times (37 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 24 | 9 times (30 % of validations) |
| E041 | Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update | 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. | 3 | 3 times (10 % of validations) |
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 1 | 1 times (3 % 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.