The migration of the prototype tool to an Oracle 9i database toolset conducted to changes. It led to a review of the import and merge procedures. The sample data set size was increased to a week of data i.e. 4/02/02 to 10/02/02. New functions were also added to the tool migrated to Oracle 9i. Back Aviation import was reviewed and trajectory was added to the schedule data. A method called virtual day inventory generator was also developed for creating movement inventory for days where no data had been collected. These modified and new functions are described in the paragraphs below. The architecture used in Access was kept; a modelling step overview is shown in Figure 12.
2
.
T
h
e
i
m
p
o
r
t
i
n
g
p
r
o
c
e
d
u
r
e
The first step in the importing procedures consists of importing the headers (information on the flight and aircraft) into a temporary Flight table (Table 18). It is followed by the update of the maximum stop time in all sources. Then the import of AMOC and ETMS flight legs (information on the trajectory) to a temporary Flight_Leg table (Table 19) can start. The import of the schedule data is described in this paragraph but occurs later in the inventory process.
Table 18: Table FLIGHT_TEMP.
Col # Column Name Data Type Data Description
1 OID NUMBER(15) Object Identifier
2 CALLSIGN VARCHAR2(15) Flight’s callsign
3 DEP_TIME DATE Time and date of departure
4 DEP_AIRPORT VARCHAR2(5) Airport of departure
5 ARR_AIRPORT VARCHAR2(5) Airport of arrival
6 SOURCES VARCHAR2(20) The name of the sources this record was imported from (AMOC, ETMS, Back Aviation)
7 FLUID VARCHAR2(21) Flight unique identifier
8 AIRCRAFT_TYPE VARCHAR2(15) Aircraft type
9 ARR_TIME DATE Time and date of arrival
10 ASSESSMENT NUMBER Number (0 to 7) attributed to the trajectory for assessing the quality
11 IMPORT_LOG_OID NUMBER Object Identifier for the import_log table (foreign key)
12 MOVE_TO_INCONSISTENT VARCHAR2(50) Reason for moving data to the inconsistent table
Table 19: Table FLIGHT_LEG_TEMP.
Col # Column Name Data Type Data Description
1 OID NUMBER(15) Object Identifier for the flight
2 FLIGHT_OID NUMBER(15) Object Identifier for each leg of the flight
3 CALLSIGN VARCHAR2(15) Flight’s callsign
4 EVENT_TIME DATE Time and date of the event
5 LATITUDE NUMBER(17,7) Latitude of the event in decimal degree
6 LONGITUDE NUMBER(17,7) Longitude of the event in in decimal degree
7 GROUND_SPEED NUMBER(17,7) Ground speed in knots
8 FLIGHT_LEVEL NUMBER(14) Flight level in hundred of feet
9 SOURCE VARCHAR2(5) The name of the sources this record was imported from (AMOC, ETMS, Back Aviation)
10 AVG_SPEED NUMBER(17,7) Empty at the stage of the import
11 DELTA_LEVEL NUMBER(17,7)
12 ZONE_INDICATOR VARCHAR2(1)
13 PROG_DIST NUMBER(17)
14 IMPORT_LOG_OID NUMBER
2.1. Header importing procedure
Import of AMOC headers
The import of AMOC headers consists of extracting data from the AMOC Traffic.txt file and to load them into FLIGHT_TEMP table (Table 18). The operations to run on the data are: 中国航空网 www.aero.cn 航空翻译 www.aviation.cn 本文链接地址：AERO2K Flight Movement Inventory Project Report(20)
