Resource details
This resource file is part of the dataset Réseau urbain Izilo.
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
❌4 061 errors, 151 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-11 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 278 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 4525507 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4525508 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4595384 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4525509 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4595379 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 1 error
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 113 does not exist in the GTFS data routes.txt
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 4525862 stop_id PTUDY does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 3 780 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 4525508 stop_sequence 2 arrival_time 08:01:22 (1765436482) is equal to previous stop departure_time 08:01:22 (1765436482) - times must increase between two sequential stops
- trip_id 4525508 stop_sequence 2 departure_time 08:01:22 (1765436482) is equal to previous stop departure_time 08:01:22 (1765436482) - times must increase between two sequential stops
- trip_id 4525508 stop_sequence 3 arrival_time 08:01:22 (1765436482) is equal to previous stop arrival_time 08:01:22 (1765436482) - times must increase between two sequential stops
- trip_id 4525508 stop_sequence 3 arrival_time 08:01:22 (1765436482) is equal to previous stop departure_time 08:01:22 (1765436482) - times must increase between two sequential stops
- trip_id 4525508 stop_sequence 3 departure_time 08:01:22 (1765436482) is equal to previous stop departure_time 08:01:22 (1765436482) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 1 error
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id 4595382 has repeating stop_id CRF at stop_sequence 62 - sequential stop_ids should be different
Warnings
vehicle_id not populated W002 151 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 4525508 does not have a vehicle_id
- trip_id 4595384 does not have a vehicle_id
- trip_id 4525509 does not have a vehicle_id
- trip_id 4525362 does not have a vehicle_id
- trip_id 4525363 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 732 | 8 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 959 | 8 times (100 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 8 | 7 times (88 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 10 | 7 times (88 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 27 643 | 7 times (88 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 4 | 3 times (38 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-11 at 23:32 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (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 2025-12-11 at 23:32 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1765492345"
}
}