Definition
...
The following diagram identifies the information items that are usually provided by a data originator for the temporary outage of obstacle lighting.
| Code Block | ||||
|---|---|---|---|---|
| ||||
input = "obstacle type" [description] [group] [mobile] \n ["location remarks"] ["obstacle identification"] \n [position] "lighting status = UNSERVICEABLE" \n "start time" "end time" [schedule] \n {note} {"affected aerodrome"} {"affected FIR"}. |
...
Data item | value | AIXM mapping | |||||||
obstacle type | A type of vertical structure. The item is used alone or in combination with other attributes in order to identify the obstacle concerned. | VerticalStructure.type and VerticalStructure/VerticalStructurePart.type | |||||||
| description | A textual description of the obstacle, such as the number of similar items for a group, etc. The item is used alone or in combination with other attributes in order to identify the obstacle concerned. | VerticalStructure.annotation with propertyName="type" and purpose="DESCRIPTION" | |||||||
group | An indication whether Digital NOTAM refers to a group of obstacles with similar height located in close proximity to one another, coded as a single VerticalStructure | VerticalStructure.group | |||||||
mobile | An indication whether the obstacle has no fixed position. | VerticalStructure/VerticalStructurePart.mobile with this list of values CodeYesNoType | |||||||
| location remarks | A named geographical location where or close to which the obstacle is located (especially for Area 1 obstacles). The item is used alone or in combination with other attributes in order to identify the obstacle concerned. | VerticalStructure/VerticalStructurePart.annotation with propertyName='horizontalProjection_location' and purpose="REMARK"
| |||||||
| obstacle identification | An alphanumerical designator by which the obstacle is identified in the national obstacle database. | VerticalStructure.name | |||||||
position | The latitude, longitude and possibly the horizontal reference datum associated with the obstacle position. The item is used alone or in combination with other attributes in order to identify the obstacle concerned. | VerticalStructure/VerticalStructurePart/ElevatedPoint or ElevatedSurface or ElevatedCurve | |||||||
lighting status | The status of the obstacle warning lights. | VerticalStructure/VerticalStructureLightingStatus.status .status Only the value 'UNSERVICEABLE' is supported in this scenario. | |||||||
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/VerticalStructureLightingStatus/Timesheet/... according to the rules for {{Schedules}} | |||||||
start time | The effective date & time when the temporary change of an obstacle's light status starts. This might be further detailed in a "schedule". | VerticalStructure/VerticalStructureTimeSlice.featureLifetime/beginPosition, VerticalStructure/VerticalStructureTimeSlice/validTime/beginPosition, Event/EventTimeSlice.validTime/beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition | |||||||
end time | The effective date & time when the temporary change of an obstacle's light status ends. | VerticalStructure/VerticalStructureTimeSlice.featureLifetime/endPosition, VerticalStructure/VerticalStructureTimeSlice/validTime/endPosition, Event/EventTimeSlice.validTime/endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for {{Events with estimated end time}} | |||||||
note | A free text note that provides further details about the obstacle lighting status. | VerticalStructure/VerticalStructureLightingStatus.annotation with purpose='”REMARK' | |||||||
| affected aerodrome | A reference (name, designator) to one or more airports/heliports that for which the establishment of the obstacle light outage has an operational relevance and needs to be notified to the users thereof. Note: Attention: the data provider interface shall warn the operator to check if the information received from the originator is consistent with the airport(s) for which the obstacle is situated in the area of interest for obstacles, as automatically calculated by the application using the obstacle positional data (lat/long). | Event.concernedAirportHeliport | |||||||
| affected FIR | A reference (type, designator) to one or more airspace of type FIR, for which the obstacle light outage has an operational relevance and needs to be notified. Note: the FIR within which the obstacle is physically situated does not need to be provided by the data originator. It will be automatically identified by the application that enables the coding of the Event. If an additional FIR is specified by the originator, the application should check the plausibility of this data based on the FIR boundary. | Event.concernedAirspace |
...
Identifier | Data encoding rule | |
ER-01 | The temporary outage of the obstacle/obstruction lighting shall be encoded as:
| |
ER-02If baseline data has one or more light elements, then set their operational status to u/s; otherwise create an ad-hoc light element, no position, put on 'unserviceable'. | ER-03 | If the obstacle lighting system is limited to a discrete schedule within the overall time period between the “start time” and the “end time”, then it shall be encoded using as many as necessary timeInterval/Timesheet properties for the VerticalStructureLightingStatus of the VerticalStructure TEMPDELTA Timeslice. See the rules for Event Schedules. |
ER-04 | According to the AIXM Temporality Concept, the VerticalStructureLightingStatus elements included in TEMPDELTA completely replace all BASELINE VerticalStructureLightingStatus information, during the time of applicability of TEMPDELTA. Therefore, if the modified operational status only concerns certain times, the other times when the obstacle lighting system remains in the same status as in the BASELINE data shall be explicitly included in the TEMPDELTA. All VerticalStructureLightingStatus elements that are copied from the BASELINE data for completeness sake shall get an associated Note with purpose='REMARK' and the text='Baseline data copy. Not included in the NOTAM text generation'. This is based on the current NOTAM practice which consists of including in the NOTAM only the changed information and not explicitly including the static data that remains valid during the NOTAM applicability. It is recommended that the input interface provides a "calendar/level" view of the lighting status, enabling the operator to graphically check the status at different times |