Resource details
This resource file is part of the dataset Réseau urbain Transp’Or.
Download availability
Learn more
We test this resource download availability every hour by making an HTTPHEAD 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.
Validation details
❌92 errors, 7 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-09-16 at 09:03 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 92 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 191 stop_sequence 17 arrival_time 08:38:25 (1726468705) is less than previous stop departure_time 08:38:27 (1726468707) - times must increase between two sequential stops
- trip_id 191 stop_sequence 18 arrival_time 08:38:26 (1726468706) is less than previous stop departure_time 08:38:28 (1726468708) - times must increase between two sequential stops
- trip_id 191 stop_sequence 19 arrival_time 08:38:27 (1726468707) is less than previous stop departure_time 08:38:29 (1726468709) - times must increase between two sequential stops
- trip_id 191 stop_sequence 20 arrival_time 08:38:28 (1726468708) is less than previous stop departure_time 08:38:30 (1726468710) - times must increase between two sequential stops
- trip_id 191 stop_sequence 21 arrival_time 08:38:29 (1726468709) is less than previous stop departure_time 08:38:31 (1726468711) - times must increase between two sequential stops
Warnings
timestamp not populated W001 7 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 191 does not have a timestamp
- trip_id 191 does not have a timestamp
- trip_id 191 does not have a timestamp
- trip_id e8512a1a-da64-41d8-8e7c-978cb6e79b2c does not have a timestamp
- trip_id 346ae698-1a14-40c7-bf25-85b0f8b6927a does not have a timestamp
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 362 | 16 times (100 % of validations) |
| W001 | Timestamps should be populated for all elements | 130 | 16 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 | 1 times (6 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 2 | 1 times (6 % 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. | 1 | 1 times (6 % 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 | 138 | 1 times (6 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 1 | 1 times (6 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-09-16 at 21:19 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-09-16 at 21:19 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1726514377"
}
}