Most airspaces may be encoded with just one AirspaceVolume, i.e. a set of vertical limits and one horizontalProjection without referencing or coping other airspace geometries.
Note
In case the airspace consists of just one airspace volume the attributes of the association classes AirspaceComponentGeometry will not be coded. The AirspaceVolumeDependency will not be used.
Coding Example
The figure below show a simple example of such an airspace, a Prohibited Area with designator EAP2.
The geometry of EAP2 is defined by vertical limits from ground to unlimited and a circle of 15Nm as lateral limit:
:
The figure below shows the encoding of an AirspaceVolume mapped form the AIXM UML to the AIXM XML:
Note that in the coding of the upper limit is not conform with the guidelines. It should be 'FT ' 'UNL' insated of 'FL' '999'.
