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
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
❌196 errors, 32 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-28 at 08:13 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 4 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 1-857866252 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-1006698497 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-594739201-A50_2-__C____ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-186384385-TDV_7-__C____ 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 51 does not exist in the GTFS data routes.txt
- route_id 60 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 186 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 1-694419459 stop_sequence 19 arrival_time 08:17:12 (1769584632) is equal to previous stop arrival_time 08:17:12 (1769584632) - times must increase between two sequential stops
- trip_id 1-694419459 stop_sequence 19 arrival_time 08:17:12 (1769584632) is equal to previous stop departure_time 08:17:12 (1769584632) - times must increase between two sequential stops
- trip_id 1-694419459 stop_sequence 19 departure_time 08:17:12 (1769584632) is equal to previous stop departure_time 08:17:12 (1769584632) - times must increase between two sequential stops
- trip_id 1-694419459 stop_sequence 19 departure_time 08:17:12 (1769584632) is equal to previous stop arrival_time 08:17:12 (1769584632) - times must increase between two sequential stops
- trip_id 1-589496321 stop_sequence 22 arrival_time 08:30:23 (1769585423) is equal to previous stop arrival_time 08:30:23 (1769585423) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 errors
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 1-522387457 stop_sequence 11 departure_time 08:12:46 (1769584366) is less than the same stop arrival_time 08:13:21 (1769584401) - departure time must be equal to or greater than arrival time
- trip_id 1-186777601 stop_sequence 11 departure_time 08:10:21 (1769584221) is less than the same stop arrival_time 08:11:26 (1769584286) - 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 1-857866252 has repeating stop_id 812 at stop_sequence 2 - sequential stop_ids should be different
- trip_id 1-1006698497 has repeating stop_id 421 at stop_sequence 2 - sequential stop_ids should be different
Warnings
timestamp not populated W001 32 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1-857866252 does not have a timestamp
- trip_id 1-1006698497 does not have a timestamp
- trip_id 1-594739201-A50_2-__C____ does not have a timestamp
- trip_id 1-1275199491 does not have a timestamp
- trip_id 1-570687489 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. | 4,638 | 29 times (97 % of validations) |
| W001 | Timestamps should be populated for all elements | 706 | 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 | 78 | 23 times (77 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 40 | 22 times (73 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 40 | 22 times (73 % 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. | 42 | 20 times (67 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-29 at 02:28 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 2026-01-29 at 02:28 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1769650115"
}
}