Resource details
GTFS-RT (protobuff) des horaires aux arrêts.
This resource file is part of the dataset Réseau urbain Transurbain.
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
⚠️144 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-02-22 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 48 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id ATOUMOD004:ServiceJourney:490789:LOC does not have a vehicle_id
- trip_id ATOUMOD004:ServiceJourney:490799:LOC does not have a vehicle_id
- trip_id ATOUMOD004:ServiceJourney:394920:LOC does not have a vehicle_id
- trip_id ATOUMOD004:ServiceJourney:394931:LOC does not have a vehicle_id
- trip_id ATOUMOD004:ServiceJourney:394932:LOC does not have a vehicle_id
schedule_relationship not populated W009 96 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD004:ServiceJourney:490789:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:490789:LOC does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:490799:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:490799:LOC does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:394920:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 587 | 26 times (87 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 3 143 | 26 times (87 % 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. | 19 | 13 times (43 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 3 | 3 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-02-22 at 21:17 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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-02-22 at 21:17 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1740255462"
}
}