Resource details
Heures de passage en temps réel aux points d’arrêts des lignes du réseaux de transport ZOU! Express, au format GTFS-RT (Real Time)
This resource file is part of the dataset Réseau interurbain Express ZOU !.
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.Validation details
❌5 errors, 48 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-07 at 08:05 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 5 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 6927|20230901|8 stop_sequence 1 arrival_time 06:50:13 (1730958613) is equal to previous stop departure_time 06:50:13 (1730958613) - times must increase between two sequential stops
- trip_id 80A5|20240406|36 stop_sequence 18 arrival_time 09:47:00 (1730969220) is equal to previous stop arrival_time 09:47:00 (1730969220) - times must increase between two sequential stops
- trip_id 80A5|20240406|36 stop_sequence 18 arrival_time 09:47:00 (1730969220) is equal to previous stop departure_time 09:47:00 (1730969220) - times must increase between two sequential stops
- trip_id 80A5|20240406|36 stop_sequence 18 departure_time 09:47:00 (1730969220) is equal to previous stop departure_time 09:47:00 (1730969220) - times must increase between two sequential stops
- trip_id 80A5|20240406|36 stop_sequence 18 departure_time 09:47:00 (1730969220) is equal to previous stop arrival_time 09:47:00 (1730969220) - times must increase between two sequential stops
Warnings
timestamp not populated W001 48 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 6928|20230901|1 does not have a timestamp
- trip_id 6026|20240901|1 does not have a timestamp
- trip_id 94R2|20231023|1 does not have a timestamp
- trip_id 6914|20190715|1 does not have a timestamp
- trip_id 94A1|20231023|1 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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 1 246 | 29 times (100 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 332 | 28 times (97 % 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. | 12 | 8 times (28 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-11-08 at 04:28 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-11-08 at 04:28 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1731036526"
}
}