Resource details

Format: gtfs-rt

This resource file is part of the dataset Réseau scolaire Sankéo.

Download availability

2024-04-03
100%
2024-04-04
100%
2024-04-05
100%
2024-04-06
100%
2024-04-07
100%
2024-04-08
100%
2024-04-09
100%
2024-04-10
100%
2024-04-11
100%
2024-04-12
100%
2024-04-13
100%
2024-04-14
100%
2024-04-15
100%
2024-04-16
100%
2024-04-17
100%
2024-04-18
100%
2024-04-19
100%
2024-04-20
100%
2024-04-21
100%
2024-04-22
100%
2024-04-23
100%
2024-04-24
100%
2024-04-25
100%
2024-04-26
100%
2024-04-27
100%
2024-04-28
100%
2024-04-29
100%
2024-04-30
100%
2024-05-01
100%
2024-05-02
100%
2024-05-03
100%
Learn more We test this resource download availability every hour by making an HTTP 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.

Validation details

⚠️2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-03 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 4876347597914112:0 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 11 min 30 sec old which is greater than the recommended age of 65 seconds
Validate this GTFS-RT now

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
W008 The data in a GTFS-realtime feed should always be less than one minute old 27 27 times (90 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 9 8 times (27 % of validations)
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 4 4 times (13 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-05-03 at 23:54 Europe/Paris.

trip_updates (1) vehicle_positions (1) service_alerts (0)

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-05-03 at 23:54 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "zenbus:Vehicle:797790001:LOC", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 18, "position": { "latitude": 42.77934265136719, "longitude": 2.962023973464966 }, "stop_id": "zenbus:StopPoint:SP:816960030:LOC", "timestamp": "1714753252", "trip": { "route_id": "zenbus:Line:802340020:LOC", "start_date": "20240503", "start_time": "17:55:00", "trip_id": "5147878483820544:2" }, "vehicle": { "id": "zenbus:Vehicle:797790001:LOC" } } }, { "id": "20240503:5123780586242048:2", "trip_update": { "stop_time_update": [ { "arrival": { "time": "1714773294" }, "departure": { "time": "1714773304" }, "stop_id": "zenbus:StopPoint:SP:816960030:LOC", "stop_sequence": 18 } ], "timestamp": "1714773255", "trip": { "route_id": "zenbus:Line:802340020:LOC", "start_date": "20240503", "start_time": "17:55:00", "trip_id": "5147878483820544:2" }, "vehicle": { "id": "zenbus:Vehicle:797790001:LOC" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1714773255" } }