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
❌2 errors, 148 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-09 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_time_update departure time is before arrival time E025 2 errors
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-671154177 stop_sequence 4 departure_time 07:13:27 (1765260807) is less than the same stop arrival_time 07:13:49 (1765260829) - departure time must be equal to or greater than arrival time
- trip_id 1-17301586 stop_sequence 3 departure_time 07:22:00 (1765261320) is less than the same stop arrival_time 07:22:32 (1765261352) - departure time must be equal to or greater than arrival time
Warnings
vehicle_id not populated W002 49 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-17760257 does not have a vehicle_id
- trip_id 1-235470850 does not have a vehicle_id
- trip_id 1-235536385 does not have a vehicle_id
- trip_id 1-17760352 does not have a vehicle_id
- trip_id 1-235601921 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 49 min 25 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 98 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 1-17760257 stop_sequence 30 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1-17760257 does not have a schedule_relationship
- trip_id 1-235470850 stop_sequence 4 (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-235536385 stop_sequence 6 (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 | 723 | 26 times (87 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 446 | 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. | 121 | 17 times (57 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 15 | 15 times (50 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 28 | 6 times (20 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-10 at 04:21 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-10 at 04:21 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1765336913"
}
}