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
⚠️202 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-31 at 08:08 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 68 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC586223:LOC does not have a vehicle_id
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC586226:LOC does not have a vehicle_id
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC584656:LOC does not have a vehicle_id
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC584844:LOC does not have a vehicle_id
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC584245:LOC does not have a vehicle_id
schedule_relationship not populated W009 134 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC586223:LOC stop_sequence 12 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC586223:LOC does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC586226:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC586226:LOC does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:SemainexVSCOC584656: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,442 | 21 times (88 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2,876 | 21 times (88 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 2 | 2 times (8 % 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.