Resource details
This resource file is part of the dataset Réseau urbain TIS.
Download availability
Learn more
We test this resource download availability every hour by making an HTTPHEAD 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.
Validation details
❌2 errors, 31 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-13 at 09:13 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 2 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 209-0913 stop_sequence 2 arrival_time 09:15:27 (1715584527) is less than previous stop arrival_time 09:15:28 (1715584528) - times must increase between two sequential stops
- trip_id 209-0913 stop_sequence 2 departure_time 09:15:27 (1715584527) is less than previous stop arrival_time 09:15:28 (1715584528) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 10 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 209-0913 does not have a vehicle_id
- trip_id 205-0937 does not have a vehicle_id
- trip_id 207-0907 does not have a vehicle_id
- trip_id 209-0837 does not have a vehicle_id
- trip_id 201-0920 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 13 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 20 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 209-0913 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 209-0913 does not have a schedule_relationship
- trip_id 205-0937 stop_sequence 4 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 205-0937 does not have a schedule_relationship
- trip_id 207-0907 stop_sequence 14 (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 | 314 | 30 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 627 | 30 times (100 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 27 | 27 times (90 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-05-13 at 19:31 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-05-13 at 19:31 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:202-1850",
"trip_update": {
"stop_time_update": [
{
"arrival": {
"delay": -45,
"time": "1715621475"
},
"stop_id": "EBERSHEIM-Gare",
"stop_sequence": 22
}
],
"timestamp": "1715621181",
"trip": {
"direction_id": 1,
"route_id": "A",
"trip_id": "202-1850"
}
}
}
],
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1715621514"
}
}