gtfs-rt Transport open dataset - Horaires temps réel des lignes du réseau DISTRIBUS for Réseau urbain Distribus

Resource details

File name: Horaires temps réel des lignes du réseau DISTRIBUS

Format: gtfs-rt

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

Download availability

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

❌752 errors, 97 warnings

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

Errors

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

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

Sample errors

trip_id T3S-9-0906 stop_id Burgfelderhof_A does not exist in GTFS data stops.txt
trip_id T3S-9-0906 stop_id Saint-Exupéry_T3 does not exist in GTFS data stops.txt
trip_id T3S-9-0906 stop_id Place_Mermoz_T3 does not exist in GTFS data stops.txt
trip_id T3S-9-0906 stop_id Soleil_A does not exist in GTFS data stops.txt
trip_id T3S-10-0921 stop_id Waldenburgerstrasse_AR does not exist in GTFS data stops.txt

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 376 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 T3S-9-0906 stop_sequence 21 has stop_id Burgfelderhof_A but GTFS stop_sequence 21 has stop_id 311020 - stop_ids should be the same
GTFS-rt trip_id T3S-9-0906 stop_sequence 22 has stop_id Saint-Exupéry_T3 but GTFS stop_sequence 22 has stop_id 311248 - stop_ids should be the same
GTFS-rt trip_id T3S-9-0906 stop_sequence 23 has stop_id Place_Mermoz_T3 but GTFS stop_sequence 23 has stop_id 311002 - stop_ids should be the same
GTFS-rt trip_id T3S-9-0906 stop_sequence 24 has stop_id Soleil_A but GTFS stop_sequence 24 has stop_id 311016 - stop_ids should be the same
GTFS-rt trip_id T3S-10-0921 stop_sequence 6 has stop_id Waldenburgerstrasse_AR but GTFS stop_sequence 6 has stop_id 310998 - stop_ids should be the same

Warnings

vehicle_id not populated W002 32 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id T3S-9-0906 does not have a vehicle_id
trip_id T3S-10-0921 does not have a vehicle_id
trip_id T3S-2-0905 does not have a vehicle_id
trip_id T3S-2-0858 does not have a vehicle_id
trip_id T3S-2-0936 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 1 min 19 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 64 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id T3S-9-0906 stop_sequence 21 (and potentially more for this trip) does not have a schedule_relationship
trip_id T3S-9-0906 does not have a schedule_relationship
trip_id T3S-10-0921 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
trip_id T3S-10-0921 does not have a schedule_relationship
trip_id T3S-2-0905 stop_sequence 2 (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	9 422	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	9 422	30 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	912	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	1 819	30 times (100 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	12	12 times (40 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	2	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-09-08 at 00:58 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 785 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-09-08 at 00:58 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "SM:450-2430",
      "trip_update": {
        "stop_time_update": [
          {
            "arrival": {
              "delay": 30,
              "time": "1725749880"
            },
            "departure": {
              "delay": 30,
              "time": "1725749880"
            },
            "stop_id": "Rousserolles_R",
            "stop_sequence": 23
          },
          {
            "arrival": {
              "delay": 30,
              "time": "1725749910"
            },
            "stop_id": "Professeur_Coste_A",
            "stop_sequence": 24
          }
        ],
        "timestamp": "1725749536",
        "trip": {
          "direction_id": 1,
          "route_id": "604",
          "trip_id": "450-2430"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1725749885"
  }
}