AERO2K Flight Movement Inventory Project Report(28)

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

8  FLIGHT_LEVEL  NUMBER(14)  Flight level in hundred of feet 
9  SOURCE  VARCHAR2(5)  The name of the sources this record was imported from (AMOC, ETMS, Back Aviation) 
10  AVG_SPEED  NUMBER(17,7)  Average speed between two chords in nm/hour 
11  DELTA_LEVEL  NUMBER(17,7)  Variation of flight level between two chords in feet/min 
12  ZONE_INDICATOR  VARCHAR2(1)  Identify in which zone of the 

 
 
 trajectory, the event is either “D” for departure or “E” for en route or “A” for arrival 
13  PROG_DIST  NUMBER(17)  Progressive distance in nm 

. Creation of statistics
In order to assess the quality of the data, reports were made at each important stage of making daily inventory in terms of flight number. The statistics results are grouped as shown in Table 32 and Table 33.

 

Table 32: Table IMPORT_LOG.

Col #  Column Name  Data Type  Data Description 
1  OID  NUMBER  Object Identifier 
2  FILENAME  VARCHAR2(35)  Name of the flie (e.g. 20020203_flight.txt) 
3  DATE_IMPORTED  DATE  Date of import of the file 
4  SOURCE  VARCHAR2(4)  The name of the source this file comes from (AMOC, ETMS, Back Aviation) 
5  STATUS  VARCHAR2(9)  Stage of the import of the file either started or completed or aborted 
6  IMPORT_TYPE  VARCHAR2(7)  Type of information imported either headers or legs 
7  TOTAL_NO_OF_RECORDS  NUMBER  Total number of records listed in the file 
8  NO_RECORDS_IMPORTED  NUMBER  Number of records imported from the file 
9  NO_INCONSISTENT_RECORDS  NUMBER  Number of records classified as inconsistent 
10  NO_MISSING_DATA_RECORDS  NUMBER  Number of records with missing data in the fields 

Table 33: Table MERGE_LOG.

Col #  Column Name  Data Type  Data Description 
1  OID  NUMBER  Object Identifier 
2  MERGE_DATE_RANGE  VARCHAR2(41)  Period of time 2002-02-02 08:53:00 - 2002-02-12 11:50:00 
3  STATUS  VARCHAR2(9)  Stage of the merge of the data e.g. started or completed or aborted 
4  LAST_COMPLETED_OPERATION  VARCHAR2(30)  Last operation completed e.g. ceanKinkyLegs or updateMergeLogTotals or deleteFltWOneLegOnly, etc… 
5  PRE_MERGE_AMOC  NUMBER  Number of AMOC 

 
 
 flights before merge 
6  PRE_MERGE_ETMS  NUMBER  Number of ETMS flights before merge 
7  PRE_MERGE_BA  NUMBER  Number of Back Aviation flights before merge 
8  MERGED_AMOC  NUMBER  Number of AMOC flights identified for merge 
9  MERGED_ETMS  NUMBER  Number of ETMS flights identified for merge 
10  MERGED_BA  NUMBER  Number of Back Aviation flights identified for merge 
11  TOTAL_MERGED  NUMBER  Total number of flights merged (all sources) 
12  POST_MERGE_AMOC  NUMBER  Number of flights not merged in AMOC 
13  POST_MERGE_ETMS  NUMBER  Number of flights not merged in ETMS 
14  POST_MERGE_BA  NUMBER  Number of flights not merged in Back Aviation 

7.2. Merge of schedule data with already merged AMOC and ETMS data
The same procedure used for AMOC and ETMS is applied to the merge of schedule data at the exception of the merge of the trajectory. Schedule data trajectory are derived from ETMS or AMOC trajectory or are artificially created, it would then be inconsistent to merge “real” trajectory with re-drawn trajectory. When a flight from AMOC, ETMS or merged is also identified as a duplicate in the schedule data, the scheduled flight is deleted.
　
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：AERO2K Flight Movement Inventory Project Report(28)