Jeu de données ouvert gtfs-rt - om-mobilite-tao-gtfs-rt.csv pour Réseau urbain TAO

Détails de la ressource

Nom du fichier : om-mobilite-tao-gtfs-rt.csv

Format : gtfs-rt

GTFS et GTFS-RT - Réseau TAO - Orléans Métropole (csv)

Cette ressource fait partie du jeu de données Réseau urbain TAO.

Disponibilité au téléchargement

Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type 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.

Rapport de validation

❌348 erreurs, 5 792 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 26/07/2024 à 09h07 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

GTFS-rt stop_id does not exist in GTFS data E011 41 erreurs

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Exemples d'erreurs

trip_id ORLEANS:VehicleJourney:11_R_101_8_1103_5_191100 stop_id ORLEANS:StopArea:00030601 does not exist in GTFS data stops.txt
trip_id ORLEANS:VehicleJourney:11_R_101_8_1101_5_162200 stop_id ORLEANS:StopArea:00030601 does not exist in GTFS data stops.txt
trip_id ORLEANS:VehicleJourney:11_R_101_8_1102_5_101200 stop_id ORLEANS:StopArea:00030601 does not exist in GTFS data stops.txt
trip_id ORLEANS:VehicleJourney:11_R_101_8_1103_5_153200 stop_id ORLEANS:StopArea:00030601 does not exist in GTFS data stops.txt
trip_id ORLEANS:VehicleJourney:12_A_84_8_1241_5_174800 stop_id ORLEANS:StopArea:00030601 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 266 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 ORLEANS:VehicleJourney:2_R_342_8_204_5_095300 stop_sequence 18 arrival_time 10:15:00 (1721981700) is less than previous stop arrival_time 10:15:36 (1721981736) - times must increase between two sequential stops
trip_id ORLEANS:VehicleJourney:2_R_342_8_204_5_095300 stop_sequence 18 arrival_time 10:15:00 (1721981700) is less than previous stop departure_time 10:15:36 (1721981736) - times must increase between two sequential stops
trip_id ORLEANS:VehicleJourney:40_R_85_8_4002_5_095500 stop_sequence 15 arrival_time 10:25:00 (1721982300) is less than previous stop arrival_time 10:27:31 (1721982451) - times must increase between two sequential stops
trip_id ORLEANS:VehicleJourney:40_R_85_8_4002_5_095500 stop_sequence 15 arrival_time 10:25:00 (1721982300) is less than previous stop departure_time 10:27:31 (1721982451) - times must increase between two sequential stops
trip_id ORLEANS:VehicleJourney:40_R_85_8_4002_5_095500 stop_sequence 15 departure_time 10:25:00 (1721982300) is less than previous stop departure_time 10:27:31 (1721982451) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 41 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 ORLEANS:VehicleJourney:11_R_101_8_1103_5_191100 stop_sequence 24 has stop_id ORLEANS:StopArea:00030601 but GTFS stop_sequence 24 has stop_id ORLEANS:StopArea:00030602 - stop_ids should be the same
GTFS-rt trip_id ORLEANS:VehicleJourney:11_R_101_8_1101_5_162200 stop_sequence 24 has stop_id ORLEANS:StopArea:00030601 but GTFS stop_sequence 24 has stop_id ORLEANS:StopArea:00030602 - stop_ids should be the same
GTFS-rt trip_id ORLEANS:VehicleJourney:11_R_101_8_1102_5_101200 stop_sequence 24 has stop_id ORLEANS:StopArea:00030601 but GTFS stop_sequence 24 has stop_id ORLEANS:StopArea:00030602 - stop_ids should be the same
GTFS-rt trip_id ORLEANS:VehicleJourney:11_R_101_8_1103_5_153200 stop_sequence 24 has stop_id ORLEANS:StopArea:00030601 but GTFS stop_sequence 24 has stop_id ORLEANS:StopArea:00030602 - stop_ids should be the same
GTFS-rt trip_id ORLEANS:VehicleJourney:12_A_84_8_1241_5_174800 stop_sequence 1 has stop_id ORLEANS:StopArea:00030601 but GTFS stop_sequence 1 has stop_id ORLEANS:StopArea:00030602 - stop_ids should be the same

Avertissements

timestamp not populated W001 1 448 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id ORLEANS:VehicleJourney:15_A_246_8_1540_5_191000 does not have a timestamp
trip_id ORLEANS:VehicleJourney:1_A_542_8_110_5_150500 does not have a timestamp
trip_id ORLEANS:VehicleJourney:3_A_331_8_302_5_124100 does not have a timestamp
trip_id ORLEANS:VehicleJourney:8_R_321_8_802_5_142800 does not have a timestamp
trip_id ORLEANS:VehicleJourney:LB_A_100_8_LB02_5_181600 does not have a timestamp

vehicle_id not populated W002 1 448 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id ORLEANS:VehicleJourney:15_A_246_8_1540_5_191000 does not have a vehicle_id
trip_id ORLEANS:VehicleJourney:1_A_542_8_110_5_150500 does not have a vehicle_id
trip_id ORLEANS:VehicleJourney:3_A_331_8_302_5_124100 does not have a vehicle_id
trip_id ORLEANS:VehicleJourney:8_R_321_8_802_5_142800 does not have a vehicle_id
trip_id ORLEANS:VehicleJourney:LB_A_100_8_LB02_5_181600 does not have a vehicle_id

schedule_relationship not populated W009 2 896 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id ORLEANS:VehicleJourney:15_A_246_8_1540_5_191000 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
trip_id ORLEANS:VehicleJourney:15_A_246_8_1540_5_191000 does not have a schedule_relationship
trip_id ORLEANS:VehicleJourney:1_A_542_8_110_5_150500 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
trip_id ORLEANS:VehicleJourney:1_A_542_8_110_5_150500 does not have a schedule_relationship
trip_id ORLEANS:VehicleJourney:3_A_331_8_302_5_124100 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship

Valider ce GTFS-RT maintenant

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
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	882	25 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.	6 788	25 fois (83 % 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	882	25 fois (83 % des validations)
W001	Timestamps should be populated for all elements	34 581	25 fois (83 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	34 581	25 fois (83 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	69 162	25 fois (83 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 27/07/2024 à 03h53 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (0)

Entités présentes dans ce flux lors des 7 derniers jours.

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 27/07/2024 à 03h53 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1722045204"
  }
}