Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- TripUpdate
- VehiclePosition
- Alert
This resource file is part of the dataset Réseau urbain Brévibus.
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
❌76 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-07 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 2 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 8-1583087665 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 9] is not strictly sorted by increasing stop_sequence
- trip_id 8-1616642275 stop_sequence [1, 2, 3, 4, 4] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 68 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-1583087665 stop_sequence 9 arrival_time 09:10:50 (1715065850) is equal to previous stop arrival_time 09:10:50 (1715065850) - times must increase between two sequential stops
- trip_id 8-1583087665 stop_sequence 9 arrival_time 09:10:50 (1715065850) is equal to previous stop departure_time 09:10:50 (1715065850) - times must increase between two sequential stops
- trip_id 8-1583087665 stop_sequence 9 departure_time 09:10:50 (1715065850) is equal to previous stop departure_time 09:10:50 (1715065850) - times must increase between two sequential stops
- trip_id 8-1583087665 stop_sequence 9 departure_time 09:10:50 (1715065850) is equal to previous stop arrival_time 09:10:50 (1715065850) - times must increase between two sequential stops
- trip_id 8-1583087665 stop_sequence 10 arrival_time 09:11:50 (1715065910) is equal to previous stop arrival_time 09:11:50 (1715065910) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_sequence E036 2 errors
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Sample errors
- trip_id 8-1583087665 has repeating stop_sequence 9 - stop_sequence must increase for each stop_time_update
- trip_id 8-1616642275 has repeating stop_sequence 4 - stop_sequence must increase for each stop_time_update
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-1583087665 has repeating stop_id 6082 at stop_sequence 9 - sequential stop_ids should be different
- trip_id 8-1616642275 has repeating stop_id 6167 at stop_sequence 4 - sequential stop_ids should be different
GTFS-rt stop_sequence not found in GTFS data E051 2 errors
All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip
Sample errors
- GTFS-rt trip_id 8-1583087665 contains stop_sequence 9 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 8-1616642275 contains stop_sequence 4 that does not exist in GTFS stop_times.txt for this trip
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. | 868 | 15 times (50 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 27 | 13 times (43 % of validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 27 | 13 times (43 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 27 | 13 times (43 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 23 | 13 times (43 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-05-08 at 05:07 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2024-05-08 at 05:07 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1715137678"
}
}