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-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%
2024-05-12
100%
2024-05-13
100%
2024-05-14
100%
2024-05-15
99.7%
2024-05-16
100%
2024-05-17
100%
2024-05-18
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

16 errors

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

Errors

stop_times_updates not strictly sorted E002 1 error

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors
  • trip_id 8-15454044162 stop_sequence [1, 2, 3, 3] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 12 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 8-15454044162 stop_sequence 3 arrival_time 09:14:00 (1716016440) is equal to previous stop arrival_time 09:14:00 (1716016440) - times must increase between two sequential stops
  • trip_id 8-15454044162 stop_sequence 3 arrival_time 09:14:00 (1716016440) is equal to previous stop departure_time 09:14:00 (1716016440) - times must increase between two sequential stops
  • trip_id 8-15454044162 stop_sequence 3 departure_time 09:14:00 (1716016440) is equal to previous stop departure_time 09:14:00 (1716016440) - times must increase between two sequential stops
  • trip_id 8-15454044162 stop_sequence 3 departure_time 09:14:00 (1716016440) is equal to previous stop arrival_time 09:14:00 (1716016440) - times must increase between two sequential stops
  • trip_id 8-15454044162 stop_sequence 4 arrival_time 09:26:00 (1716017160) is equal to previous stop arrival_time 09:26:00 (1716017160) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_sequence E036 1 error

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Sample errors
  • trip_id 8-15454044162 has repeating stop_sequence 3 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 1 error

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors
  • trip_id 8-15454044162 has repeating stop_id 4858 at stop_sequence 3 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 1 error

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Sample errors
  • GTFS-rt trip_id 8-15454044162 contains stop_sequence 3 that does not exist in GTFS stop_times.txt for this trip
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. 82 8 times (27 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 6 6 times (20 % of validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 6 6 times (20 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 6 6 times (20 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 6 6 times (20 % 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-18 at 22:06 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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-18 at 22:06 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "2.0", "timestamp": "1716062773" } }