Resource details

File name: Prochains passages des lignes sur le secteur d'Elbeuf du réseau Astuce exploitées par TAE
Format: gtfs-rt

Ce fichier au format GTFS-RT contient les prochains passages (trip updates) pour les lignes sur le secteur d’Elbeuf du réseau Astuce exploitées par TAE, à savoir les lignes régulières F9, A, B, C, E, F, G, D1 et D2 et les lignes scolaires 100, 101, 102, 103, 104, 106, 107 et 311.

Afin de pouvoir réutiliser ces données, il est nécessaire de faire le lien avec le GTFS spécifique à TAE (ressource disponible via ce même jeu de données) et non le GTFS global du réseau Astuce disponible par ailleurs.

This resource file is part of the dataset Réseau urbain Astuce - lignes du secteur d'Elbeuf (temps-réel).

Download availability

2024-10-09
100%
2024-10-10
100%
2024-10-11
100%
2024-10-12
100%
2024-10-13
100%
2024-10-14
99.4%
2024-10-15
100%
2024-10-16
100%
2024-10-17
100%
2024-10-18
100%
2024-10-19
100%
2024-10-20
100%
2024-10-21
100%
2024-10-22
100%
2024-10-23
100%
2024-10-24
100%
2024-10-25
100%
2024-10-26
100%
2024-10-27
100%
2024-10-28
100%
2024-10-29
100%
2024-10-30
100%
2024-10-31
100%
2024-11-01
100%
2024-11-02
100%
2024-11-03
100%
2024-11-04
100%
2024-11-05
100%
2024-11-06
100%
2024-11-07
100%
2024-11-08
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

⚠️124 warnings

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

Warnings

vehicle_id not populated W002 6 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 5002 does not have a vehicle_id
  • trip_id 3025 does not have a vehicle_id
  • trip_id 8006 does not have a vehicle_id
  • trip_id 8402 does not have a vehicle_id
  • trip_id 5015 does not have a vehicle_id

schedule_relationship not populated W009 118 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 3023 stop_id 4232 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 3023 does not have a schedule_relationship
  • trip_id 4012 stop_id 2105 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 4012 does not have a schedule_relationship
  • trip_id 3003 stop_id 1011 (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 83 24 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1 638 24 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.