Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain TaM.
Ressources associées
Horaires de référence urbain (GTFS)
Disponibilité au téléchargement
En savoir plus
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
❌198 erreurs, 254 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 11/09/2026 à 09h02 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 6 erreurs
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Exemples d'erreurs
- trip_id 7-1-T102-1-080600-7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 7-1-T104-1-082901-7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 7-1-T112-1-081400-7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 7-1-T114-1-082200-7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 7-1-T129-1-082400-7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
stop_times_updates not strictly sorted E002 3 erreurs
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 1583586552-7 stop_sequence for stop_ids [1071, 1071, 1764, 1764, 1072, 1072, 1073, 1073, 1074, 1074, 1075, 1075, 1076, 1076, 1077, 1077, 1078, 1078, 1079, 1079, 1080, 1080, 1081, 1081, 1082, 1082, 1083, 1083, 1084, 1084, 1085, 1085, 1086, 1086, 1087, 1087, 1088, 1088, 1752, 1752, 1090, 1090, 1091, 1091, 1092, 1092, 1093, 1093, 1094, 1094, 1095, 1095, 1652, 1652, 1096, 1096, 1540, 1540, 1097, 1097, 2446, 2446] is not strictly sorted by increasing stop_sequence
- trip_id 1583586850-7 stop_sequence for stop_ids [1071, 1071, 1764, 1764, 1072, 1072, 1073, 1073, 1074, 1074, 1075, 1075, 1076, 1076, 1077, 1077, 1078, 1078, 1079, 1079, 1080, 1080, 1081, 1081, 1082, 1082, 1083, 1083, 1084, 1084, 1085, 1085, 1086, 1086, 1087, 1087, 1088, 1088, 1752, 1752, 1090, 1090, 1091, 1091, 1092, 1092, 1093, 1093, 1094, 1094, 1095, 1095, 1652, 1652, 1096, 1096, 1540, 1540, 1097, 1097, 2446, 2446] is not strictly sorted by increasing stop_sequence
- trip_id 1583463274-7 stop_sequence for stop_ids [1180, 1180, 1181, 1181, 1182, 1182, 1183, 1183, 1184, 1184, 1185, 1185, 1186, 1186, 1187, 1187, 1188, 1188, 1189, 1189, 1190, 1190, 1191, 1191, 1107, 1107, 1108, 1108, 1198, 1198, 1199, 1199, 1200, 1200, 1201, 1201, 1202, 1202, 1203, 1203, 1204, 1204, 1205, 1205, 1206, 1206, 1207, 1207] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 30 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 1583469585-7 stop_id 2603 arrival_time 09:24:13 (1789111453) is less than previous stop arrival_time 09:24:28 (1789111468) - times must increase between two sequential stops
- trip_id 1583469585-7 stop_id 2603 arrival_time 09:24:13 (1789111453) is less than previous stop departure_time 09:24:28 (1789111468) - times must increase between two sequential stops
- trip_id 1583469585-7 stop_id 2603 departure_time 09:24:13 (1789111453) is less than previous stop departure_time 09:24:28 (1789111468) - times must increase between two sequential stops
- trip_id 1583469585-7 stop_id 2603 departure_time 09:24:13 (1789111453) is less than previous stop arrival_time 09:24:28 (1789111468) - times must increase between two sequential stops
- trip_id 1583549126-7 stop_id 129 arrival_time 09:12:07 (1789110727) is less than previous stop arrival_time 09:12:14 (1789110734) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 159 erreurs
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id 7-1-T102-1-080600-7 has repeating stop_id 1071 - sequential stop_ids should be different
- trip_id 7-1-T102-1-080600-7 has repeating stop_id 1764 - sequential stop_ids should be different
- trip_id 7-1-T102-1-080600-7 has repeating stop_id 1072 - sequential stop_ids should be different
- trip_id 7-1-T102-1-080600-7 has repeating stop_id 1073 - sequential stop_ids should be different
- trip_id 7-1-T102-1-080600-7 has repeating stop_id 1074 - sequential stop_ids should be different
Avertissements
vehicle_id not populated W002 254 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 1583586550-7 does not have a vehicle_id
- trip_id 1583586552-7 does not have a vehicle_id
- trip_id 1583586553-7 does not have a vehicle_id
- trip_id 1583586556-7 does not have a vehicle_id
- trip_id 1583586559-7 does not have a vehicle_id
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 170 | 27 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 6 318 | 27 fois (100 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 20 | 6 fois (22 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 467 | 6 fois (22 % des validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 6 | 6 fois (22 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 8 | 4 fois (15 % des validations) |
| E041 | Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update | 1 | 1 fois (4 % 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.