KIU SNAPSHOTS (Schedule)

Introduction

Kiu Snapshots Schedule is a file delivery service that allows to have an updated replica of the schedule. This service enables an initial synchronization of the schedule, and with each modification, it will send differential files.

File Structure

The name of the CSV file has the prefix SKD_ and the UTC timestamp of its generation, resulting in the following pattern: SKD_YYYYMMDDTHHMMSSFFFZ.csv.

Internally, the file contains a header with the name of each column, followed by records of the legs/segments affected by the file.

Kiu may add new columns in future developments without prior notice. In this case, existing columns will not be modified.

NAME	DESCRIPTION/FORMAT	EXAMPLE

NAME	DESCRIPTION/FORMAT	EXAMPLE
action	Indicates the action to be taken on the flight, with possible values RCP, NEW, RPL, CNL: RCP → The recap action will be sent to synchronize the entire database or a specific flight. If the flight_number is empty, the entire destination database should be deleted and the flights reported as NEW should be reinserted. If a specific flight is indicated (flight_number <> ''), only that flight should be deleted. NEW → This action is received for new flights or after a RECAP. RPL → Any modification to a flight is notified with this replace action. To process it, records with the key flight_carrier + flight_number + flight_date should be deleted from the destination first, and then the records specified in the file should be inserted. CNL → Indicates a cancellation, so records with the key flight_carrier + flight_number + flight_date should be deleted from the destination.	SKD
timestamp	Date and time of the flight modification	2023-09-21T19:50:32.970
flight_carrier	Airline code. Format: 4 alphanumeric characters.	00XX
flight_number	Flight number	1199
flight_number_suffix	Reserved space for future development. Empty.
flight_date	Commercial flight date	2023-04-01
departure_date	Departure date of leg/segment. Format: YYYY-MM-DD	2023-04-01
arrival_date	Arrival date of leg/segment. Format: YYYY-MM-DD	2023-04-01
origin	Departure Airport Code. Format: 3 alphabetical characters	EZE
destination	Arrival airport code. Format: 3 alphabetical characters	GIG
airport_number_from	Numerical identification of the origin airport, 0 to N. For example, if the flight goes AEP-COR-BRC-FTE, the segments will be formed as follows: AEP (0) - COR (1) AEP (0) - BRC (2) AEP (0) - FTE (3) COR (1) - BRC (2) COR (1) - FTE (3) BRC (2)- FTE (3)	0
airport_number_to	Numerical identification of the origin airport, 1 to N	1
city_origin	Departure city code. Format: 3 alphabetical characters	BUE
city_destination	Arrival city code. Format: 3 alphabetical characters	RIO
equipment	IATA aircraft code. Format: 3 alphanumeric characters	737
equipment_configuration_id	KIU aircraft code (KASAT Table). Format: 4 numeric characters	0006
flight_service_type	Flight type based on IATA publications, so new types may be added in future publications. Some examples of this field: J: Scheduled - Passenger M: Scheduled - Cargo Q: Scheduled - Passenger/Cargo C: Charter - Passenger H: Charter - Cargo Formato: 1 caracter	J
flight_type	Flight Type I: International D: Domestic	D
departure_time_local_time	Departure Time (Local Time) Format: HHMM	1640
arrival_time_local_time	Arrival Time (Local Time) Format: HHMM	1910
departure_terminal	Departure terminal Format: 1-2 alphanumeric characters	1
arrival_terminal	Arrival Terminal Format: 1-2 alphanumeric characters	T4

KIU Online Documentation

KIU SNAPSHOTS (Schedule)

Introduction

File Structure

Related pages