Resource details
Flux GTFS-RT service Trip Update
This resource file is part of the dataset Réseau urbain Alternéo.
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
❌45 errors, 195 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-11 at 08:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 5 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 1_41036430 stop_sequence [9, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48] is not strictly sorted by increasing stop_sequence
- trip_id 1_41036429 stop_sequence [9, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48] is not strictly sorted by increasing stop_sequence
- trip_id 1_41036464 stop_sequence [9, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48] is not strictly sorted by increasing stop_sequence
- trip_id 1_41035528 stop_sequence [14, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36] is not strictly sorted by increasing stop_sequence
- trip_id 1_41035527 stop_sequence [14, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 40 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_41036430 stop_sequence 1 departure_time 11:10:49 (1765437049) is less than previous stop departure_time 11:40:01 (1765438801) - times must increase between two sequential stops
- trip_id 1_41036430 stop_sequence 1 departure_time 11:10:49 (1765437049) is less than previous stop arrival_time 11:40:01 (1765438801) - times must increase between two sequential stops
- trip_id 1_41036430 stop_sequence 2 arrival_time 11:32:00 (1765438320) is less than previous stop arrival_time 11:40:01 (1765438801) - times must increase between two sequential stops
- trip_id 1_41036430 stop_sequence 2 departure_time 11:32:00 (1765438320) is less than previous stop arrival_time 11:40:01 (1765438801) - times must increase between two sequential stops
- trip_id 1_41036430 stop_sequence 15 arrival_time 11:40:37 (1765438837) is less than previous stop arrival_time 11:40:56 (1765438856) - times must increase between two sequential stops
Warnings
timestamp not populated W001 119 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1_41020352 does not have a timestamp
- trip_id 1_41020957 does not have a timestamp
- trip_id 1_41020880 does not have a timestamp
- trip_id 1_41020525 does not have a timestamp
- trip_id 1_41020501 does not have a timestamp
vehicle_id not populated W002 76 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1_41020352 does not have a vehicle_id
- trip_id 1_41020957 does not have a vehicle_id
- trip_id 1_41020525 does not have a vehicle_id
- trip_id 1_41020501 does not have a vehicle_id
- trip_id 1_41020513 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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 3 106 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 037 | 30 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. | 1 462 | 29 times (97 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 84 | 26 times (87 % of validations) |
| E009 | If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence | 62 | 20 times (67 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 20 | 6 times (20 % 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. | 1 | 1 times (3 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-11 at 23:22 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:22 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1765491749"
}
}