Resource details

Format: gtfs-rt

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

Download availability

2024-04-15
99.5%
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%
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
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

150 errors, 18 warnings

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

Errors

GTFS-rt stop_id does not exist in GTFS data E011 75 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • trip_id 1-16908292 stop_id 163 does not exist in GTFS data stops.txt
  • trip_id 1-16908292 stop_id 165 does not exist in GTFS data stops.txt
  • trip_id 1-16908292 stop_id 167 does not exist in GTFS data stops.txt
  • trip_id 1-16908292 stop_id 169 does not exist in GTFS data stops.txt
  • trip_id 1-16908292 stop_id 172 does not exist in GTFS data stops.txt

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 75 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors
  • GTFS-rt trip_id 1-16908292 stop_sequence 10 has stop_id 163 but GTFS stop_sequence 10 has stop_id 4702290 - stop_ids should be the same
  • GTFS-rt trip_id 1-16908292 stop_sequence 11 has stop_id 165 but GTFS stop_sequence 11 has stop_id 4702292 - stop_ids should be the same
  • GTFS-rt trip_id 1-16908292 stop_sequence 12 has stop_id 167 but GTFS stop_sequence 12 has stop_id 4702294 - stop_ids should be the same
  • GTFS-rt trip_id 1-16908292 stop_sequence 13 has stop_id 169 but GTFS stop_sequence 13 has stop_id 4702296 - stop_ids should be the same
  • GTFS-rt trip_id 1-16908292 stop_sequence 14 has stop_id 172 but GTFS stop_sequence 14 has stop_id 4702299 - stop_ids should be the same

Warnings

vehicle_id not populated W002 6 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1-16908292 does not have a vehicle_id
  • trip_id 1-17235973 does not have a vehicle_id
  • trip_id 1-17301508 does not have a vehicle_id
  • trip_id 1-16842756 does not have a vehicle_id
  • trip_id 1-704774148 does not have a vehicle_id

schedule_relationship not populated W009 12 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 1-16908292 stop_sequence 10 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1-16908292 does not have a schedule_relationship
  • trip_id 1-17235973 stop_sequence 9 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 1-17235973 does not have a schedule_relationship
  • trip_id 1-17301508 stop_sequence 32 (and potentially more for this trip) does not have a schedule_relationship
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
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 2 186 30 times (100 % of validations)
E045 If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt 2 186 30 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 320 30 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 640 30 times (100 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 28 28 times (93 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-05-15 at 20:13 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 4 330 seconds. Try to update your feed at most every 30 seconds.

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-05-15 at 20:13 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:1-16908306", "trip_update": { "stop_time_update": [ { "arrival": { "delay": 1, "time": "1715796780" }, "departure": { "delay": 1, "time": "1715796780" }, "stop_id": "213", "stop_sequence": 32 } ], "timestamp": "1715796759", "trip": { "route_id": "1", "trip_id": "1-16908306" } } } ], "header": { "gtfs_realtime_version": "1.0", "timestamp": "1715796833" } }