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
❌62 errors, 225 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-26 at 08:12 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 62 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 1583189817-16 stop_id 1764 arrival_time 07:31:35 (1766730695) is equal to previous stop arrival_time 07:31:35 (1766730695) - times must increase between two sequential stops
- trip_id 1583189817-16 stop_id 1764 arrival_time 07:31:35 (1766730695) is equal to previous stop departure_time 07:31:35 (1766730695) - times must increase between two sequential stops
- trip_id 1583189817-16 stop_id 1764 departure_time 07:31:35 (1766730695) is equal to previous stop departure_time 07:31:35 (1766730695) - times must increase between two sequential stops
- trip_id 1583189817-16 stop_id 1764 departure_time 07:31:35 (1766730695) is equal to previous stop arrival_time 07:31:35 (1766730695) - times must increase between two sequential stops
- trip_id 1583189817-16 stop_id 1072 arrival_time 07:31:35 (1766730695) is equal to previous stop arrival_time 07:31:35 (1766730695) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 225 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1583189779-16 does not have a vehicle_id
- trip_id 1583189785-16 does not have a vehicle_id
- trip_id 1583189778-16 does not have a vehicle_id
- trip_id 1583189777-16 does not have a vehicle_id
- trip_id 1583189770-16 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,715 | 29 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 7,011 | 29 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 | 429 | 24 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 318 | 16 times (55 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 849 | 15 times (52 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 20 | 10 times (34 % 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) |
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.