Jeu de données ouvert gtfs-rt - Tisseo_GTFSRT.pb pour Réseau urbain Tisséo - CA Le Muretain Agglo, CA du Sicoval, CC Le Grand Ouest Toulousain, CC des Coteaux Bellevue, Toulouse Métropole

Détails de la ressource

Nom du fichier : Tisseo_GTFSRT.pb

Format : gtfs-rt

Fichier GTFS-RT

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

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

❌208 erreurs, 3 228 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 12/02/2026 à 08h04 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 51 erreurs

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

Exemples d'erreurs

trip_id 2216775 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence
trip_id 2216767 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence
trip_id 2216302 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence
trip_id 2216893 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence
trip_id 2191982 stop_sequence [1, 2, 2] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 4 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 2216766 stop_sequence 5 arrival_time 08:14:39 (1770880479) is less than previous stop arrival_time 08:15:08 (1770880508) - times must increase between two sequential stops
trip_id 2216766 stop_sequence 5 arrival_time 08:14:39 (1770880479) is less than previous stop departure_time 08:15:08 (1770880508) - times must increase between two sequential stops
trip_id 2216766 stop_sequence 5 departure_time 08:14:39 (1770880479) is less than previous stop departure_time 08:15:08 (1770880508) - times must increase between two sequential stops
trip_id 2216766 stop_sequence 5 departure_time 08:14:39 (1770880479) is less than previous stop arrival_time 08:15:08 (1770880508) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_sequence E036 51 erreurs

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Exemples d'erreurs

trip_id 2216775 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update
trip_id 2216767 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update
trip_id 2216302 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update
trip_id 2216893 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update
trip_id 2191982 has repeating stop_sequence 2 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 51 erreurs

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

Exemples d'erreurs

trip_id 2216775 has repeating stop_id stop_point:SP_4437 at stop_sequence 2 - sequential stop_ids should be different
trip_id 2216767 has repeating stop_id stop_point:SP_4437 at stop_sequence 2 - sequential stop_ids should be different
trip_id 2216302 has repeating stop_id stop_point:SP_3112 at stop_sequence 2 - sequential stop_ids should be different
trip_id 2216893 has repeating stop_id stop_point:SP_1679 at stop_sequence 2 - sequential stop_ids should be different
trip_id 2191982 has repeating stop_id stop_point:SP_1820 at stop_sequence 2 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 51 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 2216775 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 2216767 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 2216302 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 2216893 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 2191982 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 41 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id new_8530 does not have a vehicle_id
trip_id new_8529 does not have a vehicle_id
trip_id new_8524 does not have a vehicle_id
trip_id new_8532 does not have a vehicle_id
trip_id new_6347 does not have a vehicle_id

schedule_relationship not populated W009 3 187 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id 2151952 does not have a schedule_relationship
trip_id 2151953 does not have a schedule_relationship
trip_id 2151941 does not have a schedule_relationship
trip_id 2151920 does not have a schedule_relationship
trip_id 2151921 does not have a schedule_relationship

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
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	696	29 fois (100 % des validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	745	29 fois (100 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	690	29 fois (100 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	689	29 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	4 362	29 fois (100 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	77 684	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.	148	7 fois (24 % des validations)

Contenu du flux GTFS-RT

Impossible de décoder le flux GTFS-RT

Le flux GTFS-RT doit être accessible en HTTP, sans authentification et utiliser le format Protobuf.