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
❌2 273 erreurs, 490 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 12/08/2025 à 09h14 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 12 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 TP956013 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TP1018852 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TP893837 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TRIPID-12069 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 12 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id SAEIV.26 does not exist in the GTFS data routes.txt
- route_id SAEIVTEO.47 does not exist in the GTFS data routes.txt
- route_id SAEIVTEO.31 does not exist in the GTFS data routes.txt
- route_id MOBICEO does not exist in the GTFS data routes.txt
- route_id MOBICEO does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 51 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id TP956013 stop_id SAEIV.425 does not exist in GTFS data stops.txt
- trip_id TP956013 stop_id SAEIV.44 does not exist in GTFS data stops.txt
- trip_id TP956013 stop_id SP199031 does not exist in GTFS data stops.txt
- trip_id TP956013 stop_id SAEIV.46 does not exist in GTFS data stops.txt
- trip_id TP956013 stop_id SAEIV.52 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 2 187 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 4-319160521 stop_sequence 17 arrival_time 08:37:18 (1754980638) is equal to previous stop departure_time 08:37:18 (1754980638) - times must increase between two sequential stops
- trip_id 4-117702658 stop_sequence 27 arrival_time 09:24:54 (1754983494) is equal to previous stop arrival_time 09:24:54 (1754983494) - times must increase between two sequential stops
- trip_id 4-117702658 stop_sequence 27 arrival_time 09:24:54 (1754983494) is equal to previous stop departure_time 09:24:54 (1754983494) - times must increase between two sequential stops
- trip_id 4-117702658 stop_sequence 27 departure_time 09:24:54 (1754983494) is equal to previous stop departure_time 09:24:54 (1754983494) - times must increase between two sequential stops
- trip_id 4-117702658 stop_sequence 27 departure_time 09:24:54 (1754983494) is equal to previous stop arrival_time 09:24:54 (1754983494) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 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 4-134348804 stop_sequence 6 departure_time 09:12:29 (1754982749) is less than the same stop arrival_time 09:13:13 (1754982793) - departure time must be equal to or greater than arrival time
- trip_id 4-53411921 stop_sequence 3 departure_time 09:13:19 (1754982799) is less than the same stop arrival_time 09:13:31 (1754982811) - 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 9 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 4-302186501 stop_sequence 6 has stop_id 408 but GTFS stop_sequence 6 has stop_id 6710 - stop_ids should be the same
- GTFS-rt trip_id 4-302186497 stop_sequence 6 has stop_id 408 but GTFS stop_sequence 6 has stop_id 6710 - stop_ids should be the same
- GTFS-rt trip_id 4-302055513 stop_sequence 11 has stop_id 407 but GTFS stop_sequence 11 has stop_id 6709 - stop_ids should be the same
- GTFS-rt trip_id 4-302186498 stop_sequence 6 has stop_id 408 but GTFS stop_sequence 6 has stop_id 6710 - stop_ids should be the same
- GTFS-rt trip_id 4-302055502 stop_sequence 11 has stop_id 407 but GTFS stop_sequence 11 has stop_id 6709 - stop_ids should be the same
Avertissements
timestamp not populated W001 273 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 4-251854853 does not have a timestamp
- trip_id TP956013 does not have a timestamp
- trip_id 4-319160521 does not have a timestamp
- trip_id 4-121241602 does not have a timestamp
- trip_id TP1018852 does not have a timestamp
vehicle_id not populated W002 217 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 4-19136803 does not have a vehicle_id
- trip_id 4-17039669 does not have a vehicle_id
- trip_id 4-19136644 does not have a vehicle_id
- trip_id 4-17039538 does not have a vehicle_id
- trip_id 4-19136733 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. | 66 345 | 31 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 7 361 | 31 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 5 855 | 31 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 | 308 | 26 fois (84 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 308 | 26 fois (84 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 452 | 26 fois (84 % 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. | 65 | 23 fois (74 % 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 | 9 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 13/08/2025 à 03h28 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 13/08/2025 à 03h28 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1755048538"
}
}