Resource details
Flux temps réel (horaires) au format GTFS-RT du réseau Riv’Connect
This resource file is part of the dataset Réseau urbain Riv'Connect.
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
⚠️16 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-10-25 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 5 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 6946 does not have a vehicle_id
- trip_id 6719 does not have a vehicle_id
- trip_id 6748 does not have a vehicle_id
- trip_id 6750 does not have a vehicle_id
- trip_id 6873 does not have a vehicle_id
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 1293 min 38 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 10 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 6946 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6946 does not have a schedule_relationship
- trip_id 6719 stop_sequence 2 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6719 does not have a schedule_relationship
- trip_id 6748 stop_sequence 2 (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 | 9 | 2 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 18 | 2 times (100 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 1 | 1 times (50 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-10-25 at 20:29 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-10-25 at 20:29 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1761416975"
}
}