Resource details
This resource file is part of the dataset Réseau urbain Sylvia.
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
⚠️22 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-20 at 08:07 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 7 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-17825803 does not have a vehicle_id
- trip_id 1-17235981 does not have a vehicle_id
- trip_id 1-17235982 does not have a vehicle_id
- trip_id 1-17301516 does not have a vehicle_id
- trip_id 1-17825900 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 1019 min 19 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 14 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 1-17825803 stop_sequence 30 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1-17825803 does not have a schedule_relationship
- trip_id 1-17235981 stop_sequence 22 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1-17235981 does not have a schedule_relationship
- trip_id 1-17235982 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 | 633 | 25 times (83 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 266 | 25 times (83 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 15 | 15 times (50 % 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. | 55 | 13 times (43 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 138 | 5 times (17 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 76 | 5 times (17 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 603 | 5 times (17 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 14 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-21 at 07:09 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-12-21 at 07:09 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1766297394"
}
}