NOTAM mapping to Event extension objects

Why necessary

The NOTAM production rules indicate how to generate the content of the NOTAM/SNOWTAM fields. This small section needs to indicate how these fields are mapped onto the NOTAM, SNOWTAM, ASHTAM objects. This is most;y obvious, but for completeness sake it is better to be specified.

The "decoded NOTAM item" column used the terms from the ICAO DOC 8126, AIS Manual, 11th Edition, NOTAM Format, figure 6-A-1.

NOTAM message

NOTAM Format element 

NOTAM class properties

Remarks
Date and time of fillingissued
Message SeriesseriesExpected to be managed automatically by the system
Message Number

number

Message Year

year

NOTAM N/R/Ctype
NOTAM to be replaced/cancelled - SeriesreferredNumber
NOTAM to be replaced/cancelled - NumberreferredSeries
NOTAM to be replaced/cancelled - YearreferredYear
Q) FIR

affectedFIR


Q) NOTAM CodeselectionCode
Q) Traffictraffic
Q) Purposepurpose
Q) Scopescope
Q) Lower LimitminimumFL
Q) Upper LimitmaximumFL
Q) Coordinatescoordinates
Q) Radiusradius
A)

location


B)

effectiveStart


C)

effectiveEnd


C) ... EST

estimatedEnd


C) PERMpermanent
D) scheduleConvert to Upper Case
E)

text

Convert to Upper Case
F)

lowerLimit

Convert to Upper Case
G)upperLimitConvert to Upper Case

Note: As the guidelines above may not be exhaustive enough, the Common NOTAM Production rules and detailed guidelines in the NOTAM Production Scenarios should be used in order to structure the contents of Event.notification.NOTAM properly.