| Info | ||
|---|---|---|
| ||
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. |
NOTAM mapping to the AIXM Event Extension Objects
Event.notification.NOTAM
issued
number
series
year
affectedFIR
coordinates
effectiveEnd
effectiveStart
estimatedEnd
location
lowerLimit
maximumFL
minimumFL
permanent
purpose
radius
referredNumber
referredSeries
referredYear
schedule
scope
selectionCode
text
traffic
type
upperLimit
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 filling | issued | |
| Message Series | series | Expected to be managed automatically by the system |
| Message Number | number | |
| Message Year | year | |
| NOTAM N/R/C | type | |
| NOTAM to be replaced/cancelled - Series | referredNumber | |
| NOTAM to be replaced/cancelled - Number | referredSeries | |
| NOTAM to be replaced/cancelled - Year | referredYear | |
| Q) FIR | affectedFIR | |
| Q) NOTAM Code | selectionCode | |
| Q) Traffic | traffic | |
| Q) Purpose | purpose | |
| Q) Scope | scope | |
| Q) Lower Limit | minimumFL | |
| Q) Upper Limit | maximumFL | |
| Q) Coordinates | coordinates | |
| Q) Radius | radius | |
| A) | location | |
| B) | effectiveStart | |
| C) | effectiveEnd | |
| C) ... EST | estimatedEnd | |
| C) PERM | permanent | |
| D) | schedule | Convert to Upper Case |
| E) | text | Convert to Upper Case |
| F) | lowerLimit | Convert to Upper Case |
| G) | upperLimit | Convert 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.
