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
❌1 error, 69 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-06 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_time_update departure time is before arrival time E025 1 error
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.
Sample errors
- trip_id 1-436274613 stop_sequence 2 departure_time 07:59:00 (1767682740) is less than the same stop arrival_time 07:59:25 (1767682765) - departure time must be equal to or greater than arrival time
Warnings
vehicle_id not populated W002 23 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-235470850 does not have a vehicle_id
- trip_id 1-17760352 does not have a vehicle_id
- trip_id 1-17760354 does not have a vehicle_id
- trip_id 1-251724987 does not have a vehicle_id
- trip_id 1-2835415041 does not have a vehicle_id
schedule_relationship not populated W009 46 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 1-235470850 stop_sequence 19 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1-235470850 does not have a schedule_relationship
- trip_id 1-17760352 stop_sequence 23 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1-17760352 does not have a schedule_relationship
- trip_id 1-17760354 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 | 431 | 23 times (77 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 862 | 23 times (77 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 12 | 12 times (40 % 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. | 21 | 8 times (27 % 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) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-07 at 03:35 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 2026-01-07 at 03:35 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1767753345"
}
}