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
⚠️55 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 18 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1-2852192257 does not have a vehicle_id
- trip_id 1-33620979 does not have a vehicle_id
- trip_id 1-335611117 does not have a vehicle_id
- trip_id 1-436274613 does not have a vehicle_id
- trip_id 1-50790401 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 16 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 36 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 1-2852192257 stop_sequence 2 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1-2852192257 does not have a schedule_relationship
- trip_id 1-33620979 stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1-33620979 does not have a schedule_relationship
- trip_id 1-335611117 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 | 421 | 29 times (100 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 842 | 29 times (100 % of validations) |
W008 | The data in a GTFS-realtime feed should always be less than one minute old | 17 | 17 times (59 % of validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 9 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-12-21 at 20:11 Europe/Paris.
trip_updates (1) service_alerts (0) vehicle_positions (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 2024-12-21 at 20:11 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:1-16908306",
"trip_update": {
"stop_time_update": [
{
"arrival": {
"delay": 1,
"time": "1734808280"
},
"departure": {
"delay": 1,
"time": "1734808280"
},
"stop_id": "211",
"stop_sequence": 32
}
],
"timestamp": "1734808198",
"trip": {
"route_id": "1",
"trip_id": "1-16908306"
}
}
}
],
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1734808316"
}
}