Resource details
Les mises à jour des trajets vous informent des fluctuations d’horaires. Elles sont délivrées au format GTFS-realtime, voir https://developers.google.com/transit/gtfs-realtime/guides/trip-updates?hl=fr.
This resource file is part of the dataset Réseau urbain Ametis.
Related resources
GTFS - pour être utilisé avec le GTFS-RT
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
❌104 errors, 4 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 104 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 18-5B-9-B-073000 stop_id 503 arrival_time 08:18:35 (1734679115) is equal to previous stop arrival_time 08:18:35 (1734679115) - times must increase between two sequential stops
- trip_id 18-5B-9-B-073000 stop_id 503 arrival_time 08:18:35 (1734679115) is equal to previous stop departure_time 08:18:35 (1734679115) - times must increase between two sequential stops
- trip_id 18-5B-9-B-073000 stop_id 503 departure_time 08:18:35 (1734679115) is equal to previous stop departure_time 08:18:35 (1734679115) - times must increase between two sequential stops
- trip_id 18-5B-9-B-073000 stop_id 503 departure_time 08:18:35 (1734679115) is equal to previous stop arrival_time 08:18:35 (1734679115) - times must increase between two sequential stops
- trip_id 18-10-10-B-074401 stop_id 31 arrival_time 08:28:25 (1734679705) is less than previous stop arrival_time 08:28:26 (1734679706) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 4 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 18-N2-11-B-034801 does not have a vehicle_id
- trip_id 18-7-3-B-074400 does not have a vehicle_id
- trip_id 18-N1-5-B-074100 does not have a vehicle_id
- trip_id 18-N3-8-B-080001 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. | 3 699 | 28 times (100 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 218 | 27 times (96 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 301 | 15 times (54 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-12-22 at 05:04 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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 2024-12-22 at 05:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1734840254"
}
}