AERO2K Flight Movement Inventory Project Report(68)

曝光台 注意防骗 网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者

Table 66: Trajectory assessment code system.
Departure  Cruise (En route)  Arrival  Trajectory 
C  F  C  Trajectory complete for departure and arrival and fine for en-route 
C  F  I  Trajectory complete for departure, incomplete for arrival and fine for en-route 
I  F  C  Trajectory incomplete for departure, complete for arrival and fine for en-route 
I  F  I  Trajectory incomplete for departure and arrival and fine for en-route 
C  D  C  Trajectory complete for departure and arrival and dubious for en-route 
C  D  I  Trajectory complete for departure, incomplete for arrival and dubious for en-route 
I  D  C  Trajectory incomplete for departure, complete for arrival and dubious for en-route 
I  D  I  Trajectory incomplete for departure and arrival and dubious for en-route 
Table 67: TrajectoryAssessment table.

The structure of the table is shown in Table 67 and the indexes in Table 68.
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’,...) 
Departure  Text  1  Qualifier for departure assessment 
EnRoute  Text  1  Qualifier for cruise assessment 
Arrival  Text  1  Qualifier for arrival assessment 

No.  NAME  FIELDS  PROPERTIES 
1  Fluid  Fluid  Ascending 
2  PrimaryKey  Fluid  Ascending 
Sources  Ascending 

Table 68: TrajectoryAssessment indexes.

 

 

 

3
.
M
e
r
g
i
n
g
s
t
e
p
s

Following the next steps, each flight independently of its source will be either deleted because of its inconsistency, either saved as it is, either merged with another flight in order to avoid duplicated flights in the final merged database.
These steps will be executed iteratively:

3.1. Prepare data for merging
3.1.1. Gain access to importing tools tables
Data that must be merged are saved in the importing tools tables. These tables must be linked to the current tool, in order to have access to imported flight data.

3.1.2. Merge AMOC and ETMS traffic tables
3.1.2.1. Clear MergedTraffic table for a new merging process
As a final state, data saved in traffic table will contain flights belonging only to one day. When a new set of flights for one day arrives, tables must be cleaned, not because not deleting will affect data in some unwanted way, but just for a faster data processing. The following code for clearing MergedTraffic table is used:
'--------------------------------------------------------------------------------
DoCmd.DeleteObject acTable, "MergedTraffic"
DoCmd.TransferDatabase acImport, "Microsoft Access", CurrentDb.Name, acTable, "MergedTraffic", "Model_MergedTraffic", True
DoCmd.DeleteObject acTable, "Inconsistent_MergedTraffic"
DoCmd.TransferDatabase acImport, "Microsoft Access", CurrentDb.Name, acTable, "Inconsistent_MergedTraffic", "ModelInconsistent_MergedTraffic", True
DoCmd.DeleteObject acTable, "TrajectoryAssessment"
DoCmd.TransferDatabase acImport, "Microsoft Access", CurrentDb.Name, acTable, "TrajectoryAssessment", "Model_TrajectoryAssessment", True
'--------------------------------------------------------------------------------
　
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：AERO2K Flight Movement Inventory Project Report(68)