gtfs-rt Transport open dataset - Prochains passages des lignes du réseau Astuce exploitées par Transdev Rouen for Réseau urbain Astuce

Resource details

File name: Prochains passages des lignes du réseau Astuce exploitées par Transdev Rouen

Format: gtfs-rt

Ce fichier au format GTFS-RT contient les prochains passages (trip updates) pour les lignes du réseau Astuce exploitées par Transdev Rouen, à savoir les lignes : Metro, T1, T2, T3, T4, F1, F2, F3, F4, F5, F7, F8, 11, 15, 20, 22, 27 et 41.

La fréquence de rafraîchissement de ce fichier est de 30 secondes.

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

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. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation details

⚠️4 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-21 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 33042 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 11346 min 29 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 33042 stop_sequence 32 (and potentially more for this trip) does not have a schedule_relationship
trip_id 33042 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
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	2 943	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	5 886	30 times (100 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	9	9 times (30 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-11-13 at 11:07 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 716 673 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-11-13 at 11:07 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "SM:33042",
      "trip_update": {
        "stop_time_update": [
          {
            "arrival": {
              "time": "1731492440"
            },
            "departure": {
              "time": "1731492440"
            },
            "stop_id": "12954",
            "stop_sequence": 32
          }
        ],
        "timestamp": "1731464271",
        "trip": {
          "direction_id": 1,
          "route_id": "06",
          "trip_id": "33042"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1731492474"
  }
}