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
❌113 errors, 18 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-18 at 09:16 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 1 error
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 14-857866254 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 51 does not exist in the GTFS data routes.txt
Sequential stop_time_update times are not increasing E022 108 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 14-589168643 stop_sequence 24 arrival_time 09:16:38 (1744960598) is equal to previous stop arrival_time 09:16:38 (1744960598) - times must increase between two sequential stops
- trip_id 14-589168643 stop_sequence 24 arrival_time 09:16:38 (1744960598) is equal to previous stop departure_time 09:16:38 (1744960598) - times must increase between two sequential stops
- trip_id 14-589168643 stop_sequence 24 departure_time 09:16:38 (1744960598) is equal to previous stop departure_time 09:16:38 (1744960598) - times must increase between two sequential stops
- trip_id 14-589168643 stop_sequence 24 departure_time 09:16:38 (1744960598) is equal to previous stop arrival_time 09:16:38 (1744960598) - times must increase between two sequential stops
- trip_id 14-589496322 stop_sequence 28 arrival_time 09:42:13 (1744962133) is equal to previous stop arrival_time 09:42:13 (1744962133) - 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 14-637599824 stop_sequence 16 departure_time 09:15:20 (1744960520) is less than the same stop arrival_time 09:15:38 (1744960538) - departure time must be equal to or greater than arrival time
- trip_id 14-695074850 stop_sequence 15 departure_time 09:15:26 (1744960526) is less than the same stop arrival_time 09:15:56 (1744960556) - departure time must be equal to or greater than arrival time
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 14-857866254 has repeating stop_id 812 at stop_sequence 2 - sequential stop_ids should be different
Warnings
timestamp not populated W001 18 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 14-589168643 does not have a timestamp
- trip_id 14-637730871 does not have a timestamp
- trip_id 14-671285304 does not have a timestamp
- trip_id 14-694419483 does not have a timestamp
- trip_id 14-589496322 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 749 | 33 times (100 % of validations) |
| W001 | Timestamps should be populated for all elements | 645 | 33 times (100 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 60 | 29 times (88 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 42 | 28 times (85 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 42 | 28 times (85 % 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. | 45 | 24 times (73 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-19 at 00:40 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-04-19 at 00:40 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1745016033"
}
}