Table 52: The flight 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', 'AEM3', 'BACK', 'OAG'...) 
AvgSpeed  Number  Single  The average speed between two consecutive points 
 DeltaLevel  Number  Single  Climb/descent rate 
Table 53: Flight table indexes.

No.  NAME  FIELDS  PROPERTIES 
1  PrimaryKey  UniqueID  Ascending 
2  traffic_id  TrafficId  Ascending 
3  tfTime  TrafficId  Ascending 
EventTime  Ascending 

3.2. The importing procedure

This paragraph describes the steps that must be followed in order to correctly import the AMOC provided text files.
3.2.1. Import AMOC tool task
Figure 51 shows in a simplified manner the tool task.
Figure 51: Import AMOC tool task.
AMOC provided text
ImportAmoc.mdb

Flight_yyyymmdd.txt

3.2.2. Importing steps
The steps to follow in order to import the AMOC text files are:

Delete AMOC flight heads from the traffic table (empty the traffic table)
Delete AMOC flight legs from the flight table (empty the flight table)
Import AMOC traffic file (flight heads)
Import AMOC flight file (flight legs)
Link the two imported tables (link flight heads with their legs)
Change airport codes to a preferred code (IATA)
Consistency check (delete or correct inconsistent flight heads and legs)
Change all Date/Time field values to GMT time
Calculate the fluid (flight unique identifier)
Split the flights that pass the midnight, inserting a new leg that has the EventTime hour

00:00:00 Prepare data for merging

3.2.3. Describing the importing steps
In order to have a single day list of flights, the importing procedure must start with the deletion of all other flights that were imported previously. So in the first two steps the flight heads and legs will be deleted.
Step 1 - Delete AMOC flight heads from the traffic table
To delete the flight heads, three tables must be emptied. These tables are:

AmocTraffic.
Amoc_ImportedTraffic.
Amoc_InconsistentTraffic.

AmocTraffic is the table that will store at the end of the importing procedure, the flight
heads.
Amoc_ImportedTraffic is a temporary table that helps the process of importing the flight
heads.
Amoc_InconsistentTraffic is the table that will store at the end of the importing procedure
all inconsistent flight heads that must be deleted.

Each of the previous tables has a corresponding model table: AmocTraffic – ModelTraffic  Amoc_ImportedTraffic – ModelAmoc_ImportedTraffic  Amoc_InconsistentTraffic – ModelTraffic

These 2 tables are always empty, but they store the structure of the 3 tables described
before.
To empty the tables, the following code is used:

'--------------------------------------------------------------------------------
DoCmd.DeleteObject acTable, "AmocTraffic"
　
中國航空網 m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：AERO2K Flight Movement Inventory Project Report(47)