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

Resource details

File name: Prochains passages des lignes 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 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.

La fréquence de rafraîchissement de ces données 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

❌1 266 errors, 126 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-23 at 09:11 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 42 errors

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 4087 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 4088 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 4089 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 4090 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 4091 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 42 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

route_id 118 does not exist in the GTFS data routes.txt
route_id 118 does not exist in the GTFS data routes.txt
route_id 118 does not exist in the GTFS data routes.txt
route_id 118 does not exist in the GTFS data routes.txt
route_id 118 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 1 182 errors

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

Sample errors

trip_id 4087 stop_id 9106 does not exist in GTFS data stops.txt
trip_id 4087 stop_id 9104 does not exist in GTFS data stops.txt
trip_id 4087 stop_id 9180 does not exist in GTFS data stops.txt
trip_id 4087 stop_id 9102 does not exist in GTFS data stops.txt
trip_id 4087 stop_id 9044 does not exist in GTFS data stops.txt

Warnings

vehicle_id not populated W002 42 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 4087 does not have a vehicle_id
trip_id 4088 does not have a vehicle_id
trip_id 4089 does not have a vehicle_id
trip_id 4090 does not have a vehicle_id
trip_id 4091 does not have a vehicle_id

schedule_relationship not populated W009 84 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 4087 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 4087 does not have a schedule_relationship
trip_id 4088 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 4088 does not have a schedule_relationship
trip_id 4089 stop_sequence 1 (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
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	173	5 times (100 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	173	5 times (100 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	4 591	5 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	173	5 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	346	5 times (100 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-09-24 at 02:18 Europe/Paris.

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

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-09-24 at 02:18 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1758673085"
  }
}