1.3. Relationships between AERO2K flight movement tool and other tables
The importation of air traffic data from various sources required the harmonisation of the information. For this, databases linking the data between sources had to be developed. Two databases on airports and airlines and an application for converting local time to GMT were created. The airport and airline databases allow matching airport and airline codes between sources. The relationship between the different applications required for the import procedure is shown in Figure 1. The applications are fully described in the following paragraphs.
1.4. Flight movement tool prototype overview
Based on the overall observations, a prototype flight movement tool was developed and to facilitate the use and understanding of AERO2K flight movement tool in Access, a graphical user interface (GUI) was created. An overview of the tool is shown in Figure 2. The tool should allow the import/conversion of the flight movement data i.e. AMOC and ETMS into a standard format. Flight movement data from the different sources would then be merged into a single table. This table of flights would be completed with schedule data from other part of the world and obtained from a commercial database Back Aviation. Schedule data would require their time conversion into GMT and the generation of a Great Circle trajectory. Once all data are merged, an inventory for the selected day where data were collected (representative day) would be created. The inventory made out of the representative data would be used as the basis for creating inventories for the days for which no data were collected i.e. virtual days. This last part was developed duringthe development of the prototype tool but not inplemented into the prototype tool. The tool would be supported with an airport, an airline and a fleet table and assisted with a Geographical Information System (GIS) for visualizing and analyzing flight trajectories. Finally either the virtual or representative inventories would be exported as text files.
Figure 1: Relationships between the different applications required for importing data to AERO2K flight movement tool.
Generate unique keys for traffic flights Convert all event times to standard time (GMT) Compute FLUID field Split flights as midnight …
2
.
T
h
e
i
m
p
o
r
t
i
n
g
p
r
o
c
e
d
u
r
e
f
o
r
A
M
O
C
f
i
l
e
s
2.1. AMOC source
AMOC data were derived from flight plan data files produced daily by the CFMU (Central Flow Management Unit). These flight plan data files were processed through AMOC, an ATFM (Air traffic flow management) simulator, to generate a traffic file and a flight file in respect with the route structure and ATFM environment prevailing. AMOC data cover most flights entering the ECAC (European Civil Aviation Conference) area. The country members of the ECAC area are listed in Table 70 (Appendix).
2.2. AMOC file importing procedure
The importing procedure for AMOC files as developed in the Access prototype tool for the sample data set is described in “AERO2K Import AMOC tool” written by Nicu Stancioi (2002), (Appendix).
3
.
T
h
e
i
m
p
o
r
t
i
n
g
p
r
o
c
e
d
u
r
e
f
o
r
E
T
M
S
f
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：AERO2K Flight Movement Inventory Project Report(11)
