Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Kicéo.
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
❌213 erreurs
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 16/05/2026 à 09h00 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
stop_times_updates not strictly sorted E002 10 erreurs
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 2-33619988 stop_sequence [1, 2, 3, 4, 5, 6, 8, 8] is not strictly sorted by increasing stop_sequence
- trip_id 2-74121221 stop_sequence [10, 11, 13, 13] is not strictly sorted by increasing stop_sequence
- trip_id 2-33619980 stop_sequence [8, 8] is not strictly sorted by increasing stop_sequence
- trip_id 2-33620020 stop_sequence [1, 2, 3, 4, 5, 6, 8, 8] is not strictly sorted by increasing stop_sequence
- trip_id 2-33620010 stop_sequence [1, 2, 3, 4, 5, 6, 8, 8] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 8 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 2-185663492 stop_sequence 27 arrival_time 10:30:03 (1778920203) is less than previous stop arrival_time 10:33:03 (1778920383) - times must increase between two sequential stops
- trip_id 2-185663492 stop_sequence 27 arrival_time 10:30:03 (1778920203) is less than previous stop departure_time 10:33:03 (1778920383) - times must increase between two sequential stops
- trip_id 2-185663492 stop_sequence 27 departure_time 10:30:03 (1778920203) is less than previous stop departure_time 10:33:03 (1778920383) - times must increase between two sequential stops
- trip_id 2-185663492 stop_sequence 27 departure_time 10:30:03 (1778920203) is less than previous stop arrival_time 10:33:03 (1778920383) - times must increase between two sequential stops
- trip_id 2-185663492 stop_sequence 29 arrival_time 10:32:03 (1778920323) is less than previous stop arrival_time 10:37:03 (1778920623) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_sequence E036 10 erreurs
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Exemples d'erreurs
- trip_id 2-33619988 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
- trip_id 2-74121221 has repeating stop_sequence 13 - stop_sequence must increase for each stop_time_update
- trip_id 2-33619980 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
- trip_id 2-33620020 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
- trip_id 2-33620010 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 175 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 2-251854852 stop_sequence 5 has stop_id 4009 but GTFS stop_sequence 5 has stop_id 6464 - stop_ids should be the same
- GTFS-rt trip_id 2-251854852 stop_sequence 7 has stop_id 4234 but GTFS stop_sequence 7 has stop_id 4012 - stop_ids should be the same
- GTFS-rt trip_id 2-319160326 stop_sequence 36 has stop_id 378 but GTFS stop_sequence 36 has stop_id 638 - stop_ids should be the same
- GTFS-rt trip_id 2-319160326 stop_sequence 37 has stop_id 497 but GTFS stop_sequence 37 has stop_id 631 - stop_ids should be the same
- GTFS-rt trip_id 2-319160326 stop_sequence 38 has stop_id 548 but GTFS stop_sequence 38 has stop_id 359 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 10 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 2-33619988 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-74121221 contains stop_sequence 13 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-33619980 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-33620020 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 2-33620010 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
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 |
|---|---|---|---|
| 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 | 4 709 | 28 fois (97 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 170 | 26 fois (90 % des validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 170 | 26 fois (90 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 170 | 26 fois (90 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 336 | 25 fois (86 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 16/05/2026 à 23h40 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 16/05/2026 à 23h40 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1778967616"
}
}