Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Lignes d'Azur.
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
❌1 110 erreurs, 3 270 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 09/01/2026 à 08h06 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 666 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 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 12 arrival_time 09:11:00 (1767946260) is less than previous stop arrival_time 09:11:28 (1767946288) - times must increase between two sequential stops
- trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 12 arrival_time 09:11:00 (1767946260) is less than previous stop departure_time 09:11:28 (1767946288) - times must increase between two sequential stops
- trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 12 departure_time 09:11:00 (1767946260) is less than previous stop departure_time 09:11:28 (1767946288) - times must increase between two sequential stops
- trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 12 departure_time 09:11:00 (1767946260) is less than previous stop arrival_time 09:11:28 (1767946288) - times must increase between two sequential stops
- trip_id 6683351-57_A_50_5706_07:20-JANV2026-57-Semaine-08 stop_sequence 32 arrival_time 08:11:54 (1767942714) is less than previous stop arrival_time 08:12:10 (1767942730) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 7 erreurs
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id 6719761-76_R_19_7602_08:05-PROJET2026-76-Semaine-92-1110100 has repeating stop_id 1205 at stop_sequence 29 - sequential stop_ids should be different
- trip_id 6719761-76_R_19_7602_08:05-PROJET2026-76-Semaine-92-1110100 has repeating stop_id 1205 at stop_sequence 30 - sequential stop_ids should be different
- trip_id 6719767-76_R_20_7601_08:42-PROJET2026-76-Semaine-92-1110100 has repeating stop_id 1205 at stop_sequence 42 - sequential stop_ids should be different
- trip_id 6719767-76_R_20_7601_08:42-PROJET2026-76-Semaine-92-1110100 has repeating stop_id 1205 at stop_sequence 43 - sequential stop_ids should be different
- trip_id 6719776-76_A_21_7602_08:50-PROJET2026-76-Semaine-92-1110100 has repeating stop_id 710 at stop_sequence 1 - sequential stop_ids should be different
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 436 erreurs
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Exemples d'erreurs
- GTFS-rt trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 9 has stop_id 5227 but GTFS stop_sequence 9 has stop_id 5259 - stop_ids should be the same
- GTFS-rt trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 10 has stop_id 5043 but GTFS stop_sequence 10 has stop_id 5069 - stop_ids should be the same
- GTFS-rt trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 12 has stop_id 5259 but GTFS stop_sequence 12 has stop_id 5115 - stop_ids should be the same
- GTFS-rt trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 13 has stop_id 5069 but GTFS stop_sequence 13 has stop_id 5245 - stop_ids should be the same
- GTFS-rt trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 14 has stop_id 5150 but GTFS stop_sequence 14 has stop_id 5130 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 1 erreur
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 6621574-54_R_98_5404_09:09-PROJET2025-54-Semaine-21 contains stop_sequence 39 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 819 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 6673227-58_R_98_5802_08:08-PROJET2025-58-Semaine-08 does not have a timestamp
- trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 does not have a timestamp
- trip_id 6687131-14_R_99_1404_09:39-JANV2026-14-L-Ma-J-V-38 does not have a timestamp
- trip_id 6694007-05_A_99_05S1_07:57-JANV2026-05-L-Ma-J-V-39 does not have a timestamp
- trip_id 6647492-62_R_98_6204_07:38-PROJET2025-62-Semaine-17 does not have a timestamp
vehicle_id not populated W002 819 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 6673227-58_R_98_5802_08:08-PROJET2025-58-Semaine-08 does not have a vehicle_id
- trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 does not have a vehicle_id
- trip_id 6687131-14_R_99_1404_09:39-JANV2026-14-L-Ma-J-V-38 does not have a vehicle_id
- trip_id 6694007-05_A_99_05S1_07:57-JANV2026-05-L-Ma-J-V-39 does not have a vehicle_id
- trip_id 6647492-62_R_98_6204_07:38-PROJET2025-62-Semaine-17 does not have a vehicle_id
schedule_relationship not populated W009 1 632 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 6673227-58_R_98_5802_08:08-PROJET2025-58-Semaine-08 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6673227-58_R_98_5802_08:08-PROJET2025-58-Semaine-08 does not have a schedule_relationship
- trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6682876-20_A_49_2002_08:47-JANV2026-20-Semaine-44 does not have a schedule_relationship
- trip_id 6687131-14_R_99_1404_09:39-JANV2026-14-L-Ma-J-V-38 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
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. | 25 478 | 30 fois (100 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 249 | 30 fois (100 % des validations) |
| E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 10 116 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 20 027 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 20 027 | 30 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 39 974 | 30 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 | 69 | 25 fois (83 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 116 | 8 fois (27 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 7 | 2 fois (7 % des validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 7 | 2 fois (7 % des validations) |
| E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 12 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 10/01/2026 à 01h57 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updatesFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 10/01/2026 à 01h57 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1768006622"
}
}