Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- TripUpdate
This resource file is part of the dataset Réseau urbain SURF.
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
❌122 errors, 103 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-07-26 at 09:12 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 122 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 2-755499009 stop_sequence 4 arrival_time 10:31:45 (1721982705) is equal to previous stop arrival_time 10:31:45 (1721982705) - times must increase between two sequential stops
- trip_id 2-755499009 stop_sequence 4 arrival_time 10:31:45 (1721982705) is equal to previous stop departure_time 10:31:45 (1721982705) - times must increase between two sequential stops
- trip_id 2-755499009 stop_sequence 4 departure_time 10:31:45 (1721982705) is equal to previous stop departure_time 10:31:45 (1721982705) - times must increase between two sequential stops
- trip_id 2-755499009 stop_sequence 4 departure_time 10:31:45 (1721982705) is equal to previous stop arrival_time 10:31:45 (1721982705) - times must increase between two sequential stops
- trip_id 2-691666968 stop_sequence 22 arrival_time 13:24:23 (1721993063) is equal to previous stop arrival_time 13:24:23 (1721993063) - times must increase between two sequential stops
Warnings
timestamp not populated W001 55 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 2-691666966 does not have a timestamp
- trip_id 2-758775809 does not have a timestamp
- trip_id 2-744882177 does not have a timestamp
- trip_id 2-708902939 does not have a timestamp
- trip_id 2-691470341 does not have a timestamp
vehicle_id not populated W002 48 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 2-744423425 does not have a vehicle_id
- trip_id 2-744161282 does not have a vehicle_id
- trip_id 2-744882178 does not have a vehicle_id
- trip_id 2-744030209 does not have a vehicle_id
- trip_id 2-744947713 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 977 | 27 times (87 % of validations) |
| W001 | Timestamps should be populated for all elements | 1 606 | 27 times (87 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 410 | 27 times (87 % 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. | 6 | 4 times (13 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 52 | 2 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 | 59 | 2 times (6 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-07-27 at 03:54 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-07-27 at 03:54 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1722045272"
}
}