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
❌3 400 erreurs, 1 331 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 30/01/2026 à 08h02 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 198 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 chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 2-73203743-V426B-LMCJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 2-319160397-V627A-LMCJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 2-17236052-V17A-LMCJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:d57254af-7344-4416-aa6a-bc96e0191d5e:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 23 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id CAT56Scol60375 does not exist in the GTFS data routes.txt
- route_id AVBScol60833 does not exist in the GTFS data routes.txt
- route_id MorioLigne602 does not exist in the GTFS data routes.txt
- route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
- route_id MAURYLigne609 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 164 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id bre_vannes_2024_2025.14593 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id bre_vannes_2024_2025.14597 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id bre_vannes_2024_2025.25055 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id bre_vannes_2024_2025.14585 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id keoskol.11214710 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 2 896 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-319160397-V627A-LMCJV__ stop_sequence 17 arrival_time 07:32:59 (1769754779) is equal to previous stop departure_time 07:32:59 (1769754779) - times must increase between two sequential stops
- trip_id 2-319160397-V627A-LMCJV__ stop_sequence 46 arrival_time 07:09:29 (1769753369) is less than previous stop arrival_time 08:11:30 (1769757090) - times must increase between two sequential stops
- trip_id 2-319160397-V627A-LMCJV__ stop_sequence 46 arrival_time 07:09:29 (1769753369) is less than previous stop departure_time 08:11:30 (1769757090) - times must increase between two sequential stops
- trip_id 22-3172532229 stop_sequence 24 arrival_time 08:02:25 (1769756545) is equal to previous stop arrival_time 08:02:25 (1769756545) - times must increase between two sequential stops
- trip_id 22-3172532229 stop_sequence 24 arrival_time 08:02:25 (1769756545) is equal to previous stop departure_time 08:02:25 (1769756545) - times must increase between two sequential stops
trip start_time does not match first GTFS arrival_time E023 10 erreurs
For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip
Exemples d'erreurs
- GTFS-rt trip_id 2-5671092818 start_time is 13:15:00 and GTFS initial arrival_time is 13:20:00 - times do not match
- GTFS-rt trip_id 2-5671027272 start_time is 11:22:00 and GTFS initial arrival_time is 11:32:00 - times do not match
- GTFS-rt trip_id 2-5671092439 start_time is 11:50:00 and GTFS initial arrival_time is 12:00:00 - times do not match
- GTFS-rt trip_id 2-5671026900 start_time is 12:20:00 and GTFS initial arrival_time is 12:35:00 - times do not match
- GTFS-rt trip_id 2-5671092232 start_time is 17:30:00 and GTFS initial arrival_time is 17:25:00 - times do not match
stop_time_update departure time is before arrival time E025 5 erreurs
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.
Exemples d'erreurs
- trip_id 2-288161794 stop_sequence 8 departure_time 08:01:40 (1769756500) is less than the same stop arrival_time 08:02:01 (1769756521) - departure time must be equal to or greater than arrival time
- trip_id 22-2751528961 stop_sequence 9 departure_time 08:01:21 (1769756481) is less than the same stop arrival_time 08:01:32 (1769756492) - departure time must be equal to or greater than arrival time
- trip_id 22-2701328385 stop_sequence 6 departure_time 08:01:44 (1769756504) is less than the same stop arrival_time 08:02:01 (1769756521) - departure time must be equal to or greater than arrival time
- trip_id 2-218431494 stop_sequence 11 departure_time 08:02:01 (1769756521) is less than the same stop arrival_time 08:02:03 (1769756523) - departure time must be equal to or greater than arrival time
- trip_id 2-19202114 stop_sequence 9 departure_time 08:01:17 (1769756477) is less than the same stop arrival_time 08:01:36 (1769756496) - departure time must be equal to or greater than arrival time
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 104 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-5671092227 stop_sequence 7 has stop_id 4359 but GTFS stop_sequence 7 has stop_id 6816 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 8 has stop_id 4360 but GTFS stop_sequence 8 has stop_id 4359 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 9 has stop_id 4419 but GTFS stop_sequence 9 has stop_id 4360 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 10 has stop_id 4347 but GTFS stop_sequence 10 has stop_id 4419 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 11 has stop_id 4350 but GTFS stop_sequence 11 has stop_id 4347 - stop_ids should be the same
Avertissements
timestamp not populated W001 749 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC does not have a timestamp
- trip_id 2-73203743-V426B-LMCJV__ does not have a timestamp
- trip_id 2-319160397-V627A-LMCJV__ does not have a timestamp
- trip_id 2-17236052-V17A-LMCJV__ does not have a timestamp
- trip_id 2-19136573 does not have a timestamp
vehicle_id not populated W002 582 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 2-73138205-M574A-LMCJV__ does not have a vehicle_id
- trip_id 2-74055703-M574A-LMCJV__ does not have a vehicle_id
- trip_id 2-74121243-M574A-LMCJV__ does not have a vehicle_id
- trip_id 2-73203740-M574A-LMCJV__ does not have a vehicle_id
- trip_id 2-73138216-M5674A-LMCJV__ 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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 14 827 | 26 fois (90 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 11 702 | 26 fois (90 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 786 | 24 fois (83 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 438 | 24 fois (83 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 107 | 24 fois (83 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 64 318 | 24 fois (83 % 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. | 136 | 23 fois (79 % 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 | 1 358 | 14 fois (48 % des validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 130 | 13 fois (45 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 31/01/2026 à 04h27 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 31/01/2026 à 04h27 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1769830033"
}
}