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

⚠️504 warnings

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

Warnings

vehicle_id not populated W002 168 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 1044 does not have a vehicle_id
trip_id 1055 does not have a vehicle_id
trip_id 1074 does not have a vehicle_id
trip_id 1130 does not have a vehicle_id
trip_id 1149 does not have a vehicle_id

schedule_relationship not populated W009 336 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 1044 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
trip_id 1044 does not have a schedule_relationship
trip_id 1055 stop_sequence 10 (and potentially more for this trip) does not have a schedule_relationship
trip_id 1055 does not have a schedule_relationship
trip_id 1074 stop_sequence 17 (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
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	5 245	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	10 490	30 times (100 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	81	16 times (53 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	81	16 times (53 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	81	16 times (53 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	78	16 times (53 % 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)
W008	The data in a GTFS-realtime feed should always be less than one minute old	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-15 at 14:59 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 632 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 2025-04-15 at 14:59 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "SM:29378",
      "trip_update": {
        "stop_time_update": [
          {
            "arrival": {
              "time": "1744721970"
            },
            "departure": {
              "time": "1744721970"
            },
            "stop_id": "13255",
            "stop_sequence": 36
          }
        ],
        "timestamp": "1744717792",
        "trip": {
          "route_id": "10",
          "trip_id": "29378"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1744721976"
  }
}