Resource details

Format: gtfs-rt

Les messages suivants du format GTFS-RT sont disponibles dans ce flux :

TripUpdate
VehiclePosition
Alert

This resource file is part of the dataset Réseau urbain Illygo.

Download availability

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
99.7%
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%
2024-05-04
100%
2024-05-05
100%
2024-05-06
100%
2024-05-07
100%
2024-05-08
100%
2024-05-09
100%
2024-05-10
100%
2024-05-11
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

No error detected

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

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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 70 7 times (23 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 5 5 times (17 % of validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 5 5 times (17 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 5 5 times (17 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 5 5 times (17 % 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-11 at 09:05 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-11 at 09:05 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "vehicle:643d0171e09c117cc7ffce24", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 2, "position": { "latitude": 47.903690338134766, "longitude": 0.3432539999485016 }, "stop_id": "7191", "timestamp": "1715411135", "trip": { "route_id": "921", "trip_id": "8-15454044162" }, "vehicle": { "id": "643d0171e09c117cc7ffce24", "label": "40000", "license_plate": "CX-449-FQ" } } }, { "id": "trip:8-15454044162", "trip_update": { "stop_time_update": [ { "arrival": { "time": "1715410361" }, "departure": { "time": "1715410839" }, "stop_id": "1573", "stop_sequence": 1 }, { "arrival": { "time": "1715411250" }, "departure": { "time": "1715411250" }, "stop_id": "7191", "stop_sequence": 2 }, { "arrival": { "time": "1715411610" }, "departure": { "time": "1715411610" }, "stop_id": "4858", "stop_sequence": 3 }, { "arrival": { "time": "1715412330" }, "departure": { "time": "1715412330" }, "stop_id": "855", "stop_sequence": 4 }, { "arrival": { "time": "1715412750" }, "departure": { "time": "1715412750" }, "stop_id": "7078", "stop_sequence": 5 } ], "timestamp": "1715411135", "trip": { "route_id": "921", "trip_id": "8-15454044162" }, "vehicle": { "id": "643d0171e09c117cc7ffce24", "label": "40000", "license_plate": "CX-449-FQ" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1715411141" } }