[2.0] [OBS.NEW] Obstacle new (NOTAM)

Text NOTAM production rules

This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:

the abbreviation VST.BL indicates that the corresponding data item must be taken from the VerticalStructure BASELINE that has been created for the Event;
the abbreviation VSP.BL indicates that the corresponding data item must be taken from the VerticalStructurePart of the VerticalStructure BASELINE that has been created for the Event;

Several NOTAMs possible

Note that if an obstacle is located in the vicinity of one or more airports or affects more than one FIR, explicit associations between the Event and one or more AirportHeliport or Airspace may be coded. Then, there exist dedicated provision in the OPADD (v4.1, section 2.3.9.3) with regard to the NOTAM that need to be issued in order to ensure that the NOTAM appear correctly in the relevant en-route and airport Pre-Flight Information Bulletins (PIB). Further details are provided in the “several NOTAM possible” section.

The NOTAM production rules provided on this page, unless specified otherwise, are applicable to the “first NOTAM” and the NOTAM containing one or more FIR in Item A.

Event.concernedAirspace	Event.concernedAirportHeliport	NOTAM to be generated
1..*	None	produce a single NOTAM with scope E for all the FIR(s) identified
1..*	1..*	Produce a "first" NOTAM with scope E for all FIR and additional (scope A) NOTAM for each airport concerned.
1	1..*	Produce a "first" NOTAM with scope AE for the FIR and one of the aerodromes associated with the Event and additional (scope A) NOTAM for each additional airport.

Item A

The item A shall be generated according to the general production rules for item A using the concernedAirspace(s) or the concernedAirportHeliport, according to the rules specified in table above.

Item Q

Apply the common NOTAM production rules for item Q, complemented by the following specific rules for this particular scenario:

Q code

Always use: QOBCE

Scope

Identify as described in Several NOTAM possible section above.

Lower limit/Upper limit

For Scope E NOTAMs the VSP.BL.elevation, shall be used as Upper limit and '000' as Lower limit. This value shall be formatted according to the OPADD rules for 'LOWER/UPPER' qualifiers and rounded up to the nearest 100ft increment.

For Scope A or AE NOTAM, the default values "000/999" shall be inserted.

Geographical reference

According to OPADD 4.1, item 2.3.13.6:

for a single structure, the radius is 001 is used and the coordinates are derived from the VSP.BL.horizontalProjection position
for multiple structures (geometry of type Curve of Surface), calculate the center and the radius (in NM) of a circle that encompasses the whole obstacle.

Insert these values in the geographical reference item, formatted as follows:

- the set of coordinates comprises 11 characters rounded up or down to the nearest minute; i.e. Latitude (N/S) in 5 characters; Longitude (E/W) in 6 characters. The radius consists of 3 figures rounded up to the next higher whole Nautical Mile; e.g. 10.2NM shall be indicated as 011.

See also the Note with regard to the risk that the circle/radius does not encompass the whole area, as discussed in the Location and radius common rules for the NOTAM text generation.

Items B, C and D

Items B and C shall be decoded following the common production rules.

If at least one VSP.BL.timeInterval exists (the Event has an associated schedule), then the associated Timesheet(s) shall be decoded in item D according to the common NOTAM production rules for {{Item D, E - Schedules}}. Otherwise, item D shall be left empty.

Item E

The following pattern should be used for automatically generating the E field text from the AIXM data:

EBNF Code

template = ("Temporary(1)" | "Permanent(1)") ["VST.BL.group(2)"] ["VSP.BL.mobile(3)"] "VST.BL.type(4)" ["(" "VST.BL.annotation(5)" ")"] \n 
"erected" ["(7)" "(ID:" "VST.BL.name" ")"] ["located at" "VST.BL.annotation(6)"] "\n" \n
 "VSP.BL.horizontalProjection(8)" "\n" \n
"elevation" "VSP.BL.horizontalProjection.elevation(9)" ["(" "height" "VST.BL.verticalExtent(10)" ")"] "." "\n" \n
"VST.BL.lighted(11)" ["VST.BL.annotation(12)"] "." "\n" \n
{"VST.BL.annotation(13)" "."}.

Reference	Data item (from coding scenario)	Rule
(1)	end time	If VST.BL.featureLifetime/endPosition is NIL and VST.BL.featureLifetime/endPosition.indeterminatePosition has the value "unknown" (the obstacle is permanent), then insert the word "Permanent". Otherwise insert the word "Temporary".
(2)	group	If VST.BL.group='YES', then insert the words "group of". Otherwise leave empty.
(3)	mobile	If VSP.BL.mobile='YES', then insert the word "Mobile". Otherwise leave empty.
(4)	obstacle type	Insert here the obstacle type in lower case and, if needed, taking into account the rules described in Appendix A (new) - Abbreviations and acronyms If VST.BL.type='OTHER', then insert the word "Obstacle". If the VST.BL.type='OTHER:...', then insert the text that follows after 'OTHER:'. In all situations decode the VST.BL.type by replacing the "_" characters with blank.
(5)	description	If there exists a VerticalStructure.annotation with propertyName='type' and purpose='DESCRIPTION', then insert the text of that note according to the decoding rules for Notes. Otherwise leave empty.
(6)	location remarks	If there exists a VSP.BL.annotation with propertyName='horizontalProjection_location' and purpose='REMARK' then insert the text of that note according to the decoding rules for Notes. Otherwise leave empty the whole branch (including "located at"). Attention: the data provider interface shall help the operator to check if the information received from the originator is consistent with the real position of the obstacle on the airport surface. For example, this can be done by overlaying the obstacle (position and shape) on an airport map.
(7)	obstacle identification	Insert the content of VST.BL.VerticalStructure.name, if present
(8)	point, line, polygon	The GML encoding of the horizontalProjection (gml:Point, gml:Curve or gml:Surface) shall be translated into human readable text, following the rules for encoding and decoding GML geometries. Depending on the geometry type. the following text element shall be inserted before decoding the geometry: for gml:Point insert ":" for gml:Surface insert "within area:" for gml:Curve insert "along a line:"
(9)	elevation	Insert the value of the aixm:ElevatedPoint.elevation or aixm:ElevatedCurve.elevation or aixm:ElevatedSurface.elevation that is associated with the VSP.BL., followed by the value of the respective uom attribute.
(10)	height	Insert the content of VSP.BL.verticalExtent and of its uom attribute, if available. Otherwise leave empty the whole branch.
(11)	lighting	If VST.BL.lighted='YES', then insert "Lighted". If VST.BL.lighted='NO', then insert "Not lighted". Otherwise leave empty.
(12)	marking description	If there exists a VerticalStructure.annotation with propertyName='markingICAOStandard' and purpose='REMARK', then insert the text of that note according to the decoding rules for Notes. Otherwise leave empty.
(13)	note	Annotations shall be translated into free text according to the decoding rules for Notes.

Items F & G

Leave empty.

Event Update

The eventual update of this type of event shall be encoded following the general rules for [archived] Event update or cancellation, which provide instructions for all NOTAM fields, except for item E and the condition part of the Q code, in the case of a NOTAM C

If a NOTAM C is produced, then the 4th and 5th letters (the "condition") of the Q code shall be "CN", except for the situation of a “new NOTAM to follow", in which case “XX” shall be used.