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
⚠️25 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-27 at 08:15 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 8 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 5-184614913 does not have a vehicle_id
- trip_id 5-17236051 does not have a vehicle_id
- trip_id 5-17301588 does not have a vehicle_id
- trip_id 5-637665281 does not have a vehicle_id
- trip_id 5-705101826 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 1 min 26 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 16 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 5-184614913 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 5-184614913 does not have a schedule_relationship
- trip_id 5-17236051 stop_sequence 22 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 5-17236051 does not have a schedule_relationship
- trip_id 5-17301588 stop_sequence 8 (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 | 578 | 24 times (80 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1,156 | 24 times (80 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 16 | 16 times (53 % 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. | 52 | 11 times (37 % 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-27 at 21:31 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-27 at 21:31 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1766867480"
}
}