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, 45 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-10-27 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 5-705036289 stop_sequence 3 departure_time 06:47:00 (1761544020) is less than the same stop arrival_time 06:47:44 (1761544064) - departure time must be equal to or greater than arrival time
Warnings
vehicle_id not populated W002 15 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 5-705036289 does not have a vehicle_id
- trip_id 5-17235969 does not have a vehicle_id
- trip_id 5-17236049 does not have a vehicle_id
- trip_id 5-17236051 does not have a vehicle_id
- trip_id 5-17301505 does not have a vehicle_id
schedule_relationship not populated W009 30 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 5-705036289 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 5-705036289 does not have a schedule_relationship
- trip_id 5-17235969 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 5-17235969 does not have a schedule_relationship
- trip_id 5-17236049 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 | 358 | 26 times (87 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 716 | 26 times (87 % 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. | 67 | 14 times (47 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 11 | 11 times (37 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 32 | 3 times (10 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-10-28 at 00:30 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-28 at 00:30 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1761607845"
}
}