gtfs-rt Transport open dataset - OFFRE DE TRANSPORTS RESEAU TAC - TEMPS REEL FLUX MISE A JOUR DES TRAJETS for Réseau urbain TAC Mobilité

Resource details

File name: OFFRE DE TRANSPORTS RESEAU TAC - TEMPS REEL FLUX MISE A JOUR DES TRAJETS

Format: gtfs-rt

ANNEMASSE AGGLO, EN TANT QU’AUTORITE ORGANISATRICE DE TRANSPORT URBAIN, A CONFIE A LA SOCIETE PRIVEE TP2A, FILIALE DE RATP DEV, LA GESTION DE L’EXPLOITATION DU RESEAU DE BUS TAC, DANS LE CADRE D’UNE DELEGATION DE SERVICE PUBLIC

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

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

❌84 errors, 25 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-20 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 1 error

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors

trip_id 21754915 stop_sequence for stop_ids [anniled1, vmomonn1, annlema2, annverd1, annduso1, annrcot1, annlivr1, anniled1, annimpo2, annsous2, annmerm2, annresi2, annmont1, vlgcoqu1, vlglang4, vlgvoir1, vlgabon1, vlgbich1, vlgarti1, vlgdeux1, craalte1] is not strictly sorted by increasing stop_sequence

GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 2 errors

If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence

Sample errors

trip_id 21755431 visits stop_id [cravict1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
trip_id 21755436 visits stop_id [cravict1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided

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

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

Sample errors

trip_id 21755677 stop_id ambedel1 does not exist in GTFS data stops.txt
trip_id 21755678 stop_id ambedel1 does not exist in GTFS data stops.txt
trip_id 21755189 stop_id ambedel1 does not exist in GTFS data stops.txt
trip_id 21755190 stop_id ambedel1 does not exist in GTFS data stops.txt
trip_id 21755191 stop_id ambedel1 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 76 errors

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors

trip_id 21755677 stop_id stjgare1 departure_time 08:09:00 (1766214540) is less than previous stop departure_time 09:05:29 (1766217929) - times must increase between two sequential stops
trip_id 21755677 stop_id stjgare1 departure_time 08:09:00 (1766214540) is less than previous stop arrival_time 09:05:29 (1766217929) - times must increase between two sequential stops
trip_id 21755677 stop_id stjaran2 arrival_time 08:11:04 (1766214664) is less than previous stop arrival_time 09:05:29 (1766217929) - times must increase between two sequential stops
trip_id 21755677 stop_id stjaran2 departure_time 08:11:04 (1766214664) is less than previous stop arrival_time 09:05:29 (1766217929) - times must increase between two sequential stops
trip_id 21755678 stop_id stjgare1 departure_time 07:09:32 (1766210972) is less than previous stop departure_time 08:03:42 (1766214222) - times must increase between two sequential stops

Warnings

vehicle_id not populated W002 25 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 21755677 does not have a vehicle_id
trip_id 21755436 does not have a vehicle_id
trip_id 21755423 does not have a vehicle_id
trip_id 21754929 does not have a vehicle_id
trip_id 21754915 does not have a vehicle_id

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	187	32 times (100 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	1 853	32 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	994	32 times (100 % of validations)
E009	If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence	100	28 times (88 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	46	26 times (81 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	9	2 times (6 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	9	2 times (6 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-21 at 02:56 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-12-21 at 02:56 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1766282168"
  }
}