Resource details
Horaires temps-réel du réseau Envia
This resource file is part of the dataset Réseau urbain Envia.
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
❌140 errors, 21 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-17 at 09:02 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 2 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 8-1006698507 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 8-857866245 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 2 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 60 does not exist in the GTFS data routes.txt
- route_id 51 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 133 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 8-718471183 stop_sequence 33 arrival_time 09:10:37 (1715929837) is equal to previous stop arrival_time 09:10:37 (1715929837) - times must increase between two sequential stops
- trip_id 8-718471183 stop_sequence 33 arrival_time 09:10:37 (1715929837) is equal to previous stop departure_time 09:10:37 (1715929837) - times must increase between two sequential stops
- trip_id 8-718471183 stop_sequence 33 departure_time 09:10:37 (1715929837) is equal to previous stop departure_time 09:10:37 (1715929837) - times must increase between two sequential stops
- trip_id 8-718471183 stop_sequence 33 departure_time 09:10:37 (1715929837) is equal to previous stop arrival_time 09:10:37 (1715929837) - times must increase between two sequential stops
- trip_id 8-644087869 stop_sequence 20 arrival_time 09:04:08 (1715929448) is equal to previous stop arrival_time 09:04:08 (1715929448) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 error
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.
Sample errors
- trip_id 8-570359810 stop_sequence 2 departure_time 09:01:53 (1715929313) is less than the same stop arrival_time 09:02:06 (1715929326) - departure time must be equal to or greater than arrival time
Sequential stop_time_updates have the same stop_id E037 2 errors
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id 8-1006698507 has repeating stop_id 421 at stop_sequence 2 - sequential stop_ids should be different
- trip_id 8-857866245 has repeating stop_id 812 at stop_sequence 2 - sequential stop_ids should be different
Warnings
timestamp not populated W001 21 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 8-1006698507 does not have a timestamp
- trip_id 8-857866245 does not have a timestamp
- trip_id 8-671285258 does not have a timestamp
- trip_id 8-718340111 does not have a timestamp
- trip_id 8-718471183 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. | 3 316 | 29 times (97 % of validations) |
| W001 | Timestamps should be populated for all elements | 447 | 29 times (97 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 44 | 22 times (73 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 39 | 21 times (70 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 39 | 21 times (70 % 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. | 10 | 8 times (27 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-05-18 at 01:04 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-05-18 at 01:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1715987041"
}
}