Resource details
This resource file is part of the dataset Réseau urbain Rezo.
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
❌2 errors, 4 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-19 at 09:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 1 error
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 5164981467217920:12 stop_id zenbus:StopPoint:SP:399950008:LOC does not exist in GTFS data stops.txt
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 error
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- GTFS-rt trip_id 5164981467217920:12 stop_sequence 49 has stop_id zenbus:StopPoint:SP:399950008:LOC but GTFS stop_sequence 49 has stop_id 151588 - stop_ids should be the same
Warnings
vehicle_id not populated W002 1 error
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 5164981467217920:12 does not have a vehicle_id
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 302 min 27 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 2 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 5164981467217920:12 stop_sequence 49 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 5164981467217920:12 does not have a schedule_relationship
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 |
---|---|---|---|
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2 000 | 30 times (100 % 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 | 2 000 | 30 times (100 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 118 | 30 times (100 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 236 | 30 times (100 % of validations) |
W008 | The data in a GTFS-realtime feed should always be less than one minute old | 11 | 11 times (37 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-05-19 at 03:59 Europe/Paris.
trip_updates (1) service_alerts (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-05-19 at 03:59 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:5164981467217920:12",
"trip_update": {
"stop_time_update": [
{
"arrival": {
"delay": 1,
"time": "1716083952"
},
"departure": {
"delay": 1,
"time": "1716083962"
},
"stop_id": "zenbus:StopPoint:SP:399950008:LOC",
"stop_sequence": 49
}
],
"timestamp": "1716083941",
"trip": {
"route_id": "zenbus:Line:507050001:LOC",
"trip_id": "5164981467217920:12"
}
}
}
],
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1716083981"
}
}