3.5. Function
In summary, the function of the virtual day inventory generator (Figure 31) is to:
.
Retrieve the number of flights for a region for each day of the year from Back Aviation database.
.
Calculate the daily traffic trend for each region over the whole year and the number of flights occurring on representative days (per region).
.
Per region, calculate the ratio (ratio rdiregion) between the number of flights inventoried for a representative day (rdi AERO2K) and the number of flights as given by Back Aviation trend database (rdi BA). For each of the seven regions, ratios will be calculated for each day of the six representative weeks of data collection i.e. 294 ratios in total.
.
Apply one of the previous ratio (function of the closeness of the virtual day and representative day) to the number of flights given by the trend (vdi BA) and estimate how many flights should be in operation on the chosen virtual day (vdi recAERO2K).
.
Select the inventory matching the ratio chosen.
.
Compare the number of flights obtained in this inventory (rdi AERO2K) with the number of flights (vdi recAERO2K) estimated from the ratio and the Back Aviation trend database.
.
Look at the flight distribution in a region in the representative AERO2K inventory (rdi AERO2K). Flights will have been sorted chronologically.
.
Adjust and apply the distribution to the number of flights calculated for the virtual day (vdi recAERO2K) and select the required number of flights for each region.
Create a new world inventory (vdi recAERO2K) for the virtual day chosen by compiling the inventories obtained for each region.
P
H
A
S
E
4
Flight movement inventory delivery
1
.
I
n
t
r
o
d
u
c
t
i
o
n
The objective of WP2.1 was to deliver a world civil flight movement inventory. This was done by generating six inventories corresponding to the weeks of data collection and by having the option of extending these data to the corresponding months using the virtual day function. The generation of these inventories was a long process that requested a permanent testing of the tool coding.
2
.
D
e
l
i
v
e
r
y
Figure 32 shows a representation in GIS of all flights in the world departing on the 8/02/2002.
3
.
T
e
s
t
i
n
g
During the migration of the prototype tool from Access to Oracle 9i, the opportunity was taken for modeling the system using Rational Rose. This new step slightly delayed the migration of the tool but produced complete system documentation through UML diagrams.
Figure 33 shows the overall design scheme for AERO2K flight movement tool; it specifies how the user or actor interacts with the scenarios. Scenarios are represented by colored ovals and are detailed further in activity diagrams. Unbroken lines describe the association between the tool user and the main scenarios while broken lines show dependencies between scenarios. For example, the import of AMOC cannot start before static data are done. Activities diagrams are represented from Figure 34 to Figure 50. An activity is symbolized by a rounded rectangle. Unbroken lines describe a state transition between activities and colored rectangles represent the state. A thick line is a synchronization line; a one to many activities has to be synchronized before the activity can begin.
Figure 37: Create airport static data activity diagram.
中国航空网 www.aero.cn 航空翻译 www.aviation.cn 本文链接地址：AERO2K Flight Movement Inventory Project Report(40)
