PDToolKit eTOD DataStore - CAD
This is the main application where all the required effort is needed to build the
eTOD Database that ICAO has mandated. Here the user is able to view the data, add
new data, import data and then decide which data should be added to the eTOD database.
Options to easily add data into the eTOD Database are available along with tools
to identify and reconcile differences in the obstacles between the CAD software
and eTOD database.
One of the key improvements with the ICAO eTOD specification is the evolution of
2 new types of obstacles (as well as Point), these are:
- Point
- Line (new)
- Polygon (new)
These are all supported in the PDToolKit suite of applications including PDToolKit
Procedure Design and the generic Obstacle Analysis engine.
Synchronisation: CAD and eTOD Database
The eTOD Database will be the primary storage of the obstacle data. The screen shot
to the right shows the CAD Synchronisation dialog that enables the Procedure Designer
to easily and effectively see the status of the obstacles in the CAD drawing. Options
and information for the user are:
- Which obstacles are in the CAD drawing but not in the eTOD Database
- Which obstacles are in the eTOD Database but added to CAD Polygon (new)
- Quickly add Obstacles from eTOD to the CAD drawing
- Define a geometric query to obtain obstacles from the eTOD Database in the surround
geographical area
The dialog shows two columns of obstacle id’s, the first column are the obstacles
in the “Drawing” and the second column the obstacles in the eTOD Database.
The row in the column where there is a gap easily shows where the obstacle data
is missing from the CAD drawing or the eTOD Database.
On the right side of the screen capture, two further PDToolKit dialogs are docked
within the CAD main environment; these are:
- Obstacle Analysis Dialog - Used to allow the user to access if
the obstacles penetrate through the 3D surfaces constructed by the user or through
the PDToolKit tools.
- Obstacle Properties Dialog - This dialog will show the properties
(Name and Values) of the information about the obstacle that has been obtained by
the Procedure Designer and/or the eTOD Database. In this image the eTOD Database
information is in grey as this is only for show and the user is not allowed to edit
this information whilst in CAD.
eTOD Area 2: 3D Surface Construction
As defined in ICAO Annex 15, PDToolKit eTOD CAD allows the construction of the 3D
surfaces around the ARP and runways; this option is available through a simple dialogue
which also allows the user to adjust the standard parameters to specific local requirements.
The second screen shot to the right shows the dialogue box where the user has control
over the convex boundary that is drawn based on the ARP and any influences by subsidiary
runways (which alter the overall shape and dimension). A boundary for the TMA can
also be selected allowing the default circular boundary of Area 2 to be cut and
follow the shape of the TMA boundary.
The next screen shot shows the PDToolKit eTOD CAD tool in a typical working environment
with the screen split into two view ports showing different 3D views of the geographical
area. Part of the terrain is shown as a background image with 3D contours added.
Obstacles are drawn in red and the Properties dialog on the right hand side shows
the PDToolKit Obstacle ID used for a unique link to the eTOD database.
Procedure Design
If your obstacles are stored in the eTOD database then they can easily be displayed
and added into the Procedure Design drawing. A dialogue will appear showing the
current obstacles in the procedure CAD drawing on the left hand side list and the
obstacles stored in the eTOD database on the right hand side. The user can easily
compare which obstacles are in both by the green colour, otherwise red identifies
that the obstacles are not in the other environment.
Import and Survey Data
A key feature is the ability to import data from different sources, the PDToolKit
eTOD CAD allows data to be imported in the following key methods:
- PDTScript Language - A scripting language that allows bulk data
to be added to the CAD software using the obstacle, NAVAIDS and surface construction
tools in PDToolKit. This is a simple script language and can easily be created from
existing products. I.e. Microsoft Access / Microsoft Excel.
- CAP232 - This is a UK specification defining a common standard
format for the data of the airport survey.
- AIXM 4.5 - AIXM Snapshot message files(XML) for point obstacles,
NavAids, etc.
- AIXM 5.x - Support for this version of AIXM Snapshot message files(XML)
for point obstacles, NavAids, etc. will be added when needed.
- eTOD XML - This is planned to be supported when other survey companies
can supply the customer the survey data in this format.
Note:
Not all formats above address and handle the complete range of eTOD specifications.
Reviewing the eTOD data (Obstacles and Terrain)
One way to review and view the obstacle data is to use Google Earth, which is shown
in the final screen shot to the right of this page. A Google Earth file is created
and this can easily be emailed or passed to colleagues in the office for assessment.
In the example shown, this is a aerodrome overlaid by obstacles drawn from the eTOD
database together with 3D surfaces (eTOD point obstacle are seen as cylinders (coloured
white). In this type of display it is easy for the designer to orientate and show
to others, by presentation, the relative locations and meaning of aerodrome facilities,
obstacles, terrain and surface.
The Obstacle Identification is also passed to Google Earth and this is listed on
the left hand side in gray as pdtObsId.
Note:
PDToolKit eTOD DataStore does not include the CAD software; one of the following
CAD applications is required: AutoCAD MAP 3D 2008, AutoCAD MAP 3D 2009, Bentley
MicroStation MAP, for other CAD software please contact ASD.
|