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.
NOTAM mapping to the AIXM Event Extension Objects
| decoded NOTAM Item | Event.notification.NOTAM | Mapping guidance |
|---|---|---|
| series | To be created by system automatically with the creation of NOTAM and inserted | |
number | ||
issued | ||
year | ||
affectedFIR | ||
coordinates | ||
effectiveEnd | Insert here the structured contents of ...TimeSlice.validTime.TimePeriod.endPosition | |
effectiveStart | Insert here the structured contents of ...TimeSlice.validTime.TimePeriod.beginPosition | |
estimatedEnd | ||
| permanent | ||
| type | Insert here the value representing NOTAM type (NOTAMN, NOTAMR or NOTAMC) in accordance with the use of AIXM Event Extension | |
| Item Q | location | Insert here the calculated/designated coordinates representing the association of an event to a facility, service or area that corresponds with the event. |
| Item Q | radius | Insert here the calculated radius. |
| Item Q | maximumFL | |
| Item Q | minimumFL | |
| Item Q | purpose | |
| Item Q | scope | |
| Item Q | traffic | |
| Item Q | selectionCode | |
referredNumber | ||
referredSeries | ||
referredYear | ||
| Item D | schedule | Insert the decoded and structured contents of Item D |
| Item E | text | Insert the decoded and structured contents of Item E |
| Item F | lowerLimit | Insert the decoded and structured contents of Item F |
| Item G | upperLimit | Insert the decoded and structured contents of Item G |
