Preparing for eTOD
Whilst the detail of the requirements for electronic terrain and obstacle (eTOD) datasets may be changing, there are some steps that states can take to prepare for their implementation.
Regardless of what approach is taken, it is clear that the advent of eTOD calls for better obstacle management by states. This needs to go hand in hand with aeronautical data quality legislation like the EUs ADQ. In one important area, there is something missing.
One of the key requirements for good data quality is minimising the manual transmission of data. This an area M-AIS have worked on with UK NATS and the tool we developed, ADEP, has a critical role to play in helping states improve their obstacle management in advance of eTOD. ADEP is an Aeronautical Data Exchange Processor, is a simple application designed for converting aeronautical data between formats. In particular, it has a full set of tools for checking electronic survey data and then converting it into an AIXM format. This includes obstacle surveys and the ADEP tool can make a significant improvement to state obstacle management.
The workflow starts when an electronic survey file (such as a csv file) arrives at the ADEP workstation by email or FTP. The first step is to check the CRC and digital signature of the file, to ensure that it is authentic and has not been amended, corrupted or intercepted during transit. If these checks are successful, ADEP is then used to check the content of the file. The checks carried out by ADEP are based on the most commonly ocurring survey errors and range from simple checks like line counts and highlighting duplicates to more sophisticated checks designed to make sure the data can complete its transition to AIXM smoothly.
A report folder is produced for every process that ADEP carries out, containing a summary of sub-processes, whether any problems were found and a reference copy of any temporary files produced during the process. This means that at any stage, the ADEP operator can send this report information back to the surveyor for clarification. Whats more, the report folder can be archived for future reference, improving the traceability of data.
One of the key requirements for good data quality is minimising the manual transmission of data. This an area M-AIS have worked on with UK NATS and the tool we developed, ADEP, has a critical role to play in helping states improve their obstacle management in advance of eTOD. ADEP is an Aeronautical Data Exchange Processor, is a simple application designed for converting aeronautical data between formats. In particular, it has a full set of tools for checking electronic survey data and then converting it into an AIXM format. This includes obstacle surveys and the ADEP tool can make a significant improvement to state obstacle management.
The workflow starts when an electronic survey file (such as a csv file) arrives at the ADEP workstation by email or FTP. The first step is to check the CRC and digital signature of the file, to ensure that it is authentic and has not been amended, corrupted or intercepted during transit. If these checks are successful, ADEP is then used to check the content of the file. The checks carried out by ADEP are based on the most commonly ocurring survey errors and range from simple checks like line counts and highlighting duplicates to more sophisticated checks designed to make sure the data can complete its transition to AIXM smoothly.
A report folder is produced for every process that ADEP carries out, containing a summary of sub-processes, whether any problems were found and a reference copy of any temporary files produced during the process. This means that at any stage, the ADEP operator can send this report information back to the surveyor for clarification. Whats more, the report folder can be archived for future reference, improving the traceability of data.
You can catch up with all the latest from Managed AIS by following the link below.
Issue 6 of Skyline, the Managed-AIS newsletter
Issue 6 of Skyline, the Managed-AIS newsletter
.png)
.jpg){kind=logo}
Comments
There are no comments yet for this item
Join the discussion