Resource details

File name: Horaires temps réel des lignes du réseau Pass'O
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Pass'O.

Download availability

2025-01-18
100%
2025-01-19
100%
2025-01-20
100%
2025-01-21
100%
2025-01-22
99.3%
2025-01-23
100%
2025-01-24
100%
2025-01-25
100%
2025-01-26
100%
2025-01-27
100%
2025-01-28
100%
2025-01-29
100%
2025-01-30
45.8%
2025-01-31
0%
2025-02-01
0%
2025-02-02
0%
2025-02-03
0%
2025-02-04
0%
2025-02-05
0%
2025-02-06
0%
2025-02-07
0%
2025-02-08
0%
2025-02-09
0%
2025-02-10
0%
2025-02-11
0%
2025-02-12
0%
2025-02-13
0%
2025-02-14
0%
2025-02-15
0%
2025-02-16
0%
2025-02-17
0%
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. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation details

1 error, 4 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-01-30 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • trip_id 14330 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 14330 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 233164 min 54 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 2 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 14330 stop_sequence 12 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 14330 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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 12 12 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 12 12 times (100 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 12 12 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 24 12 times (100 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.