Jeu de données ouvert gtfs-rt - OFFRE DE TRANSPORTS RESEAU TAC - TEMPS REEL FLUX MISE A JOUR DES TRAJETS pour Réseau urbain TAC

Détails de la ressource

Nom du fichier : 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

Cette ressource fait partie du jeu de données Réseau urbain TAC.

Disponibilité au téléchargement

Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type HEAD dont le temps de réponse doit être inférieur à 5 secondes. Si nous détectons une indisponibilité, nous effectuons un nouveau test toutes les 10 minutes, jusqu'à ce que la ressource soit à nouveau disponible.

Pour les flux SIRI et SIRI Lite, nous effectuons une requête HTTP de type GET : nous considérons une réponse avec un code 401 ou 405 comme étant disponible. En cas d'erreur 500, nous considèrerons que le flux est indisponible, sauf si il semble contenir du SOAP.

Rapport de validation

❌189 erreurs, 91 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 27/06/2025 à 09h10 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 14 erreurs

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

Exemples d'erreurs

trip_id 21251991 stop_sequence [13, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25] is not strictly sorted by increasing stop_sequence
trip_id 21252483 stop_sequence [11, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16] is not strictly sorted by increasing stop_sequence
trip_id 21252475 stop_sequence [11, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16] is not strictly sorted by increasing stop_sequence
trip_id 21251988 stop_sequence [13, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25] is not strictly sorted by increasing stop_sequence
trip_id 21251992 stop_sequence [13, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25] is not strictly sorted by increasing stop_sequence

GTFS-rt stop_id does not exist in GTFS data E011 26 erreurs

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

Exemples d'erreurs

trip_id 21252113 stop_id annmobl1 does not exist in GTFS data stops.txt
trip_id 21252483 stop_id ambecof2 does not exist in GTFS data stops.txt
trip_id 21252483 stop_id vlgroto3 does not exist in GTFS data stops.txt
trip_id 21252483 stop_id vlgroto3 does not exist in GTFS data stops.txt
trip_id 21252092 stop_id annchab2 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 134 erreurs

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

Exemples d'erreurs

trip_id 21251991 stop_sequence 1 departure_time 09:35:00 (1751009700) is less than previous stop departure_time 09:54:11 (1751010851) - times must increase between two sequential stops
trip_id 21251991 stop_sequence 1 departure_time 09:35:00 (1751009700) is less than previous stop arrival_time 09:54:11 (1751010851) - times must increase between two sequential stops
trip_id 21251991 stop_sequence 2 arrival_time 09:36:06 (1751009766) is less than previous stop arrival_time 09:54:11 (1751010851) - times must increase between two sequential stops
trip_id 21251991 stop_sequence 2 departure_time 09:36:06 (1751009766) is less than previous stop arrival_time 09:54:11 (1751010851) - times must increase between two sequential stops
trip_id 21252483 stop_sequence 1 departure_time 09:56:00 (1751010960) is less than previous stop departure_time 10:14:52 (1751012092) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 10 erreurs

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Exemples d'erreurs

trip_id 21251991 has repeating stop_id annandr2 - sequential stop_ids should be different
trip_id 21252483 has repeating stop_id vlgroto3 - sequential stop_ids should be different
trip_id 21252475 has repeating stop_id vlgroto3 - sequential stop_ids should be different
trip_id 21251988 has repeating stop_id annandr2 - sequential stop_ids should be different
trip_id 21251992 has repeating stop_id annandr2 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 5 erreurs

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Exemples d'erreurs

GTFS-rt trip_id 21252113 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 21252122 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 21252126 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 21252109 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 21252112 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 57 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id 21251991 does not have a timestamp
trip_id 21252385 does not have a timestamp
trip_id 21252222 does not have a timestamp
trip_id 21252211 does not have a timestamp
trip_id 21252113 does not have a timestamp

vehicle_id not populated W002 34 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 21251991 does not have a vehicle_id
trip_id 21252385 does not have a vehicle_id
trip_id 21252222 does not have a vehicle_id
trip_id 21252113 does not have a vehicle_id
trip_id 21252483 does not have a vehicle_id

Valider ce GTFS-RT maintenant

Validations précédentes

Voici un récapitulatif des différents types d'erreurs constatés au cours des 30 derniers jours.

Identifiant d'erreur	Description	Nombre d'erreurs	Nombre d'occurences
W001	Timestamps should be populated for all elements	1 310	29 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	821	29 fois (100 % des validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	1 473	28 fois (97 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	194	27 fois (93 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	587	27 fois (93 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	93	24 fois (83 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	93	22 fois (76 % des validations)
E025	Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.	1	1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 28/06/2025 à 03h45 Europe/Paris.

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

Entités présentes dans ce flux lors des 7 derniers jours.

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 28/06/2025 à 03h45 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


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