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 Nosbus.
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
❌12 errors, 6 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-08 at 08:09 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 8 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 2-4833607681 stop_sequence 4 arrival_time 08:11:20 (1767856280) is equal to previous stop arrival_time 08:11:20 (1767856280) - times must increase between two sequential stops
- trip_id 2-4833607681 stop_sequence 4 arrival_time 08:11:20 (1767856280) is equal to previous stop departure_time 08:11:20 (1767856280) - times must increase between two sequential stops
- trip_id 2-4833607681 stop_sequence 4 departure_time 08:11:20 (1767856280) is equal to previous stop departure_time 08:11:20 (1767856280) - times must increase between two sequential stops
- trip_id 2-4833607681 stop_sequence 4 departure_time 08:11:20 (1767856280) is equal to previous stop arrival_time 08:11:20 (1767856280) - times must increase between two sequential stops
- trip_id 2-4833607681 stop_sequence 13 arrival_time 08:19:20 (1767856760) is equal to previous stop arrival_time 08:19:20 (1767856760) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 4 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id 2-4832624641 stop_sequence 12 doesn't have arrival or departure
- trip_id 2-4832624644 stop_sequence 12 doesn't have arrival or departure
- trip_id 2-4849074179 stop_sequence 1 doesn't have arrival or departure
- trip_id 2-4833542145 stop_sequence 14 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 6 errors
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id 2-4832624641 is in TripUpdates but not in VehiclePositions feed
- trip_id 2-4832624644 is in TripUpdates but not in VehiclePositions feed
- trip_id 2-4849336321 is in TripUpdates but not in VehiclePositions feed
- trip_id 2-4849074177 is in TripUpdates but not in VehiclePositions feed
- trip_id 2-4833542145 is in TripUpdates but not in VehiclePositions feed
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 |
|---|---|---|---|
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 52 | 17 times (59 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 77 | 17 times (59 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 108 | 13 times (45 % 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) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 23 | 1 times (3 % of validations) |
GTFS-RT feed content
Could not decode the GTFS-RT feed.
The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.