... a type of
AIRSPACE_VERTEX
|
|
Attributes
... see as well the attributes of the super-type entity
|
|
CODE_TYPE
Type
|
|
|
Relationships
... see as well the relationships of the super-type entity
|
|
|
must be
composing
one and only one
AIRSPACE_CORRIDOR
Airspace Corridor
|
|
|
|
Attributes
|
|
VAL_WIDTH
Width
|
|
UOM_WIDTH
Unit of measurement [width]
|
|
TXT_RMK
Remark
|
|
|
Relationships
|
|
|
must be
describing the horizontal shape of
one and only one
AIRSPACE
Airspace
|
|
must be
made of
one or more
AIRSPACE_CLINE_VERTEX
Airspace centreline vertex
|
|
|
|
Attributes
|
|
TXT_RMK
Remark
|
|
|
Relationships
|
|
|
must be
for
one and only one
AIRSPACE
Airspace
|
|
|
|
either must be
based on the same horizontal extent as
one and only one
AIRSPACE
Airspace
|
|
... or must be
the aggregation of
one or more
AIRSPACE_AGGREG_COMP
Airspace Aggregation Component
|
|
Rule:
- There must exist exactly one related AIRSPACE_AGGREG_COMP having CODE_OPR = 'BASE'.
|
|
|
|
Attributes
|
|
NO_SEQ
Sequence number
|
|
GEO_LAT
Latitude
|
|
GEO_LONG
Longitude
|
|
CODE_DATUM
Datum
|
|
VAL_GEO_ACCURACY
Geographical accuracy
|
|
UOM_GEO_ACCURACY
Unit of measurement [geographical accuracy]
|
|
GEO_LAT_ARC
Latitude for arc
|
|
GEO_LONG_ARC
Longitude for arc
|
|
VAL_RADIUS_ARC
Radius of arc
|
|
UOM_RADIUS_ARC
Unit of measurement [arc, circle radius]
|
|
VAL_CRC
Cyclic redundancy check
|
|
TXT_RMK
Remark
|
|
|
Relationships
|
|
|
may be
located at
one and only one
SIGNIFICANT_POINT
Significant point
|
|
Rule:
- The position of the related SIGNIFICANT_POINT must be identical to the position of the AIRSPACE_VERTEX..
|
|
may be
using as arc
one and only one
SIGNIFICANT_POINT
Significant point
|
|
Rule:
- This relationship can only occur for instances of AIRSPACE_VERTEX that have CODE_TYPE = 'CWA', 'CCA' or 'ABE'..
- The position of the related SIGNIFICANT_POINT must be identical to the position given by the GEO_LAT_ARC, GEO_LONG_ARC attributes of the AIRSPACE_VERTEX..
|
|
|
|
Attributes
|
|
VAL_ANGLE_BRG
Bearing indication
|
|
TXT_RMK
Remark
|
|
|
Relationships
|
|
|
either must be
referring to
one and only one
SIGNIFICANT_POINT
Significant point
|
|
The point at which the indication occurs.
|
|
... or must be
referring to
one and only one
NAV_SYS_CHECKPOINT
Checkpoint
|
|
either must be
using
one and only one
NDB
Non-directional radio beacon [NDB]
|
|
... or must be
using
one and only one
VOR
VHF omnidirectional radio range beacon [VOR]
|
|
... or must be
using
one and only one
TACAN
Tactical air navigation beacon [TACAN]
|
|
|
|
Attributes
|
|
TXT_NAME
Name
|
|
[CODE_COMPOSITION]
DEPRECATED-4.5
Surface composition
|
|
[CODE_COND_SFC]
DEPRECATED-4.5
Surface condition
|
|
[CODE_STRENGTH]
DEPRECATED-4.5
Surface strength method
|
|
[TXT_DESCR_STRENGTH]
DEPRECATED-4.5
Surface strength
|
|
CODE_STS
Operational status
|
|
TXT_MARKING
Marking system description
|
|
[TXT_LGT]
DEPRECATED-4.5
Lighting system description
|
|
TXT_RMK
Remark
|
|
|
Relationships
|
|
|
may be
having the geometry described by
one and only one
AD_HP_SURFACE_BORDER
Aerodrome / Heliport Surface border
|
|
must be
located at
one and only one
AD_HP
Aerodrome / Heliport
|
|
may be
having
one or more
GATE_STAND
Parking position stand or gate
|
|
must be
having
one and only one
SURFACE_CHARACTERISTICS
Surface characteristics
|
|
may be
having
one or more
APRON_LGT_SYS
Apron lighting system
|
|
... a type of
SURFACE_LGT_SYS
|
|
Attributes
... see as well the attributes of the super-type entity
|
|
CODE_PSN
Position
|
|
|
Relationships
... see as well the relationships of the super-type entity
|
|
|
must be
owned by
one and only one
APRON
Apron
|
|
|
|
Attributes
|
|
CODE_TYPE
Type
|
|
TXT_RMK
Remark
|
|
|
Relationships
|
|
|
must be
responsible for
one and only one
AIRSPACE
Airspace
|
|
must be
also
one and only one
ORG_AUTH
Organisation or authority
|
|
|
|
Attributes
|
|
TXT_CALL_SIGN
Call sign
|
|
CODE_LANG
Language
|
|
TXT_RMK
Remark
|
|
|
Relationships
|
|
|
must be
provided on
one and only one
FREQUENCY
Frequency
|
|
In aeronautical radio communication the Unit providing a Service is identified by its CALL_SIGN. Depending on the type of Service, a Unit may have more than one CALL_SIGN, and with each an associated frequency.
|
|
Note:
|
|
In State AIPs, each service has two associated lists, one with frequencies and another with CALLSIGNs and languages. This situation may be interpreted in two ways: 1) each service has some associated CALL_SIGNs, each of which has one or several related frequencies or 2) each service has some associated frequencies, each of which has one or several related CALL_SIGNs. The second case has been considered for this model, based on the fact that the 'default' situation is a service provided on one frequency, but with different call signs, depending on the language used.
|
|
|
|
Attributes
|
|
CODE_ID
Identification
|
|
GEO_LAT
Latitude
|
|
GEO_LONG
Longitude
|
|
CODE_DATUM
Datum
|
|
VAL_GEO_ACCURACY
Geographical accuracy
|
|
UOM_GEO_ACCURACY
Unit of measurement [geographical accuracy]
|
|
VAL_CRC
Cyclic redundancy check
|
|
CODE_TYPE
Type
|
|
TXT_NAME
Name
|
|
TXT_RMK
Remark
|
|
|
Relationships
|
|
|
may be
used as
one and only one
SIGNIFICANT_POINT
Significant point
|
|
|
|
either may be
at the centre of
one and only one
TLOF
Touch down and lift off area [TLOF]
|
|
Rule:
- Over the same time period, the values of the GEO_LAT, GEO_LONG, CODE_DATUM, VAL_GEO_ACCURACY and UOM_GEO_ACCURACY attributes must be equal with those of the similarly named attributes in the related TLOF.
|
|
... or may be
the reference point of
one and only one
AD_HP
Aerodrome / Heliport
|
|
Rule:
- Over the same time period, the values of the GEO_LAT, GEO_LONG, CODE_DATUM, VAL_GEO_ACCURACY and UOM_GEO_ACCURACY attributes must be equal with those of the similarly named attributes in the related AD_HP.
|
|
... or may be
located at
one and only one
RWY_CLINE_POINT
Position on the centre line of a RWY
|
|
Rule:
- Over the same time period, the values of the GEO_LAT, GEO_LONG, CODE_DATUM, VAL_GEO_ACCURACY and UOM_GEO_ACCURACY attributes must be equal with those of the similarly named attributes in the related RWY_CLINE_POINT.
|
|
... or may be
located at
one and only one
FATO_CLINE_POINT
FATO - centre line position
|
|
Rule:
- Over the same time period, the values of the GEO_LAT, GEO_LONG, CODE_DATUM, VAL_GEO_ACCURACY and UOM_GEO_ACCURACY attributes must be equal with those of the similarly named attributes in the related FATO_CLINE_POINT.
|
|
... or may be
associated with
one and only one
AD_HP
Aerodrome / Heliport
|
|