Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Definition

...

Data item

value

AIXM mapping

group

An indication whether the obstacle consists of a number of closely situated similar objects, for which a simple lat/long position (and eventually radius) is provided.

VerticalStructure.group with this list of values CodeYesNoType

mobile

An indication whether the obstacle is expected to move around its nominal location

VerticalStructure/VerticalStructurePart.mobile with this list of values CodeYesNoType

obstacle type

A type of vertical structure

VerticalStructure.type and VerticalStructure/VerticalStructurePart.type with this list of values CodeVerticalStructureType

description

A textual description of the obstacle, such as the number of similar items for a group, etc.

VerticalStructure.annotation with propertyName="type" and purpose="DESCRIPTION"

airport

Information such as designator or name used to identify the airport where the obstacle is located

VerticalStructure.annotation with purpose="WARNING"

location

A named geographical location where or close to which the obstacle is located (especially for Area 1 obstacles)

VerticalStructure.name

identifier

An alphanumerical designator by which the obstacle is identified in the national obstacle database

VerticalStructure/VerticalStructurePart.designator

point

The latitude, longitude and horizontal reference datum associated with the obstacle position.

VerticalStructure/VerticalStructurePart/ElevatedPoint according to the rules for encoding for encoding {{Geometrical and geographical data}}

line

Pairs of latitude/longitude values along a line, including the horizontal reference datum associated with the obstacle extent and location

VerticalStructure/VerticalStructurePart/ElevatedCurveaccording to the rules for encoding for encoding {{Geometrical and geographical data}}

polygon

Pairs of latitude/longitude values defining a polygon, including the horizontal reference datum associated with the obstacle extent and location

VerticalStructure/VerticalStructurePart/ElevatedSurfaceaccording to the rules for encoding for encoding {{Geometrical and geographical data}}

circle

A type of polygon in which all the points are located at constant geodesic distance from the centre of the circle.

VerticalStructure/VerticalStructurePart/ElevatedSurfaceaccording to the rules for encoding for encoding {{Geometrical and geographical data}}

elevation

The elevation (distance from Mean See Level) at the top of the obstacle.

VerticalStructure/VerticalStructurePart/ElevatedPoint or ElevatedSurface or ElevatedCurve/elevation including its unit of measure

height

The distance between the uppermost and the lowermost parts of the obstacle.

VerticalStructure/VerticalStructurePart.verticalExtent

relative position

A free text description of the obstacle position in relation to relevant airport elements, such as a runway threshold or the control tower.

VerticalStructure/VerticalStructurePart.annotation with propertyName="horizontalProjection_location" and purpose="REMARK"

Info
titleAIXM 5.1 work-around

 In AIXM 5.1, the _ character is not allowed in the pattern for propertyName, therefore, when using AIXM 5.1, the propertyName should be left empty.

lighting

An indication if the obstacle is lighted.

VerticalStructure.lightedwith the following list of valuesCodeYesNoType

marking description

Further details of the obstacle marking and lighting, such as times when lighting is available, compliance with the ICAO standards, etc. Also includes the description of visual markers (other than lights) that are installed on the obstacle, such as painting, flags, signs, etc.

VerticalStructure.annotation with propertyName="markingICAOStandard" and purpose="DESCRIPTION"

vicinity

The indication of AirportHeliport feature(s) in the vicinity of which the obstacle is located. 

Note: Because there are no strict operational rules for what 'vicinity' means, the NOTAM operator will have to explicitly select the AirportHeliport that need to be considered in the vicinity. But at least they can be coded in relation with the Event.

The Digital NOTAM data provider interface might offer suggestions with respect to the features affected by the new obstacle, but in any case, the operator shall be allowed to take the final decision by selecting the airports for which a NOTAM is really generated.

Event.associationEvent href

start time

The effective date & time when the obstacle starts to exist. This might be further detailed in a "schedule".

VerticalStructure/VerticalStructureTimeSlice.featureLifetime/beginPosition, VerticalStructure/VerticalStructureTimeSlice/validTime/timePosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the obstacle ceases to exist

VerticalStructure/VerticalStructureTimeSlice.featureLifetime/endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for {{Events with estimated end time}}

schedule

A schedule might be provided, in case the obstacle is only active according to a regular timetable, within the period between the start of life and the end of life.

VerticalStructure/VerticalStructurePart/Timesheet/...according to the rules for {{Schedules}}

note

A free text note that provides further details about the obstacle, such as the reason for which it exists, reduced height at certain times, etc.

VerticalStructure.annotation with purpose=”REMARK”

...

Assumptions for baseline data

...

No specific baseline data assumptions are made.

Remark (to be deleted later): Initially it has been assumed that an “area of interest for obstacles” exists in the form of ObstacleArea BASELINE TimeSlice(s) covering the complete period of validity of the event, coded as specified in the Coding Guidelines for the (ICAO) Obstacle Data Sets. This approach has been changed because not all AirportHeliports have ObstacleAreas coded and the new Event schema brings the possibility to code an "associationEvent". The NOTAM operator will have to explicitly select the AirportHeliport that need to be considered in the vicinity and they can be coded in relation with the Event. This would allow to explicitly code the 'vicinity' situation and can be used as 'decoding' criteria for deciding when several NOTAM are necessary - Ref. FG Decision on Webex 19 June, comment on Several NOTAM possible 

...