2.1. MergedTraffic table
The MergedTraffic table is used for keeping most important data about flights. Table 62 and Table 63 show the table structure and the indexes used.
Table 62: MergedTraffic table.
Key Field name Data type Size/Format Description
. Fluid Text 21 Flight unique identifier
. Sources Text 20 The name of the source application, this record was imported from ('AMOC', 'ETMS', ’BACK’,...)
TrafficID Number Autonumber Unique identifier for the flight
CallSign Text 15 Flight’s call sign
DepartureTime Date/Time yyyy-mm-dd hh:nn:ss Flight's date
DepartureAirport Text 5 Departure airport
ArrivalAirport Text 5 Arrival airport
AircraftType Text 10 Aircraft type
ArrivalTime Date/Time yyyy-mm-dd hh:nn:ss Last possible arrival time
AvgSpeed Number Single Flight's average speed
Table 63: MergedTraffic indexes.
No. NAME FIELDS PROPERTIES
1 TrafficID TrafficID Ascending
2 Fluid Fluid Ascending
3 PrimaryKey Fluid Ascending
Sources Ascending
2.2. MergedFlight table
The MergedFlight table is used to keep detailed information about flights. Table 64 and Table 65 show the table structure and the indexes used.
Table 64: MergedFlight table.
Key Field name Data type Size/Format Description
. UniqueID Number Autonumber Unique identifier
TrafficId Number Long This field links the flight table with the traffic table
CallSign Text 15 Flight’s call sign
EventTime Date/Time yyyy-mm-dd hh:nn:ss Flight’s event time
Latitude Number Single Latitude position (degrees)
Longitude Number Single Longitude position (degrees)
GroundSpeed Number Long Ground speed (knots)
FlightLevel Number Long Flight level
Source Text 5 The name of the source application this record was imported from ('AMOC', 'ETMS', 'BACK', ...)
AvgSpeed Number Single The average speed between two consecutive points
DeltaLevel Number Single Climb/descent rate
Table 65: FlightTable indexes
No. NAME FIELDS PROPERTIES
1 Traffic_id TrafficID Ascending
2 PrimaryKey UniqueID Ascending
2.3. Inconsistent_MergedTraffic
The Inconsistent_MergedTraffic table has the same structure as MergedTraffic, because all flights that are inconsistent and must be deleted will be moved from MergedTraffic table to Inconsistent_MergedTraffic table (See table's structure in Table 62).
2.4. TrajectoryAssessment table
The TrajectoryAssessment table has a special purpose. This purpose is to save important data about each flight's trajectory. A trajectory can be divided into three parts, the departure, the cruise and the arrival. Each part can be more or less completely reflected in saved flight data. The departure and arrival parts can be complete or incomplete. The cruise part can be fine or dubious. According to the characteristics of each flight's part, a flight's trajectory can be described as shown in Table 66.
中國航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：AERO2K Flight Movement Inventory Project Report(67)
