Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

A basic knowledge of the AIXM key concepts, in particular of the Temporality model, is necessary in order to understand the Digital NOTAM coding examples discussed here. The XML sources are attached, together with the Visio file that contains the source of the diagrams used on the page.

A Digital NOTAM is a small data set, which provides in a coded format (AIXM 5.1 or later versions) information about operationally significant aeronautical information changes. Most of the time, these changes are of short duration and affect only a few of the properties of a feature (the operational status of a runway, the activation status of an airspace, the position of a runway threshold, etc.). It may also happen that the change is of longer duration or even permanent and it is also possible that the event in fact consists in the creation of a complete new feature (such as a temporary new obstacle).

Relation with the baseline data

In

most

situations,

the

Digital

NOTAM

is

in

the

form

of

a

"temporary

delta"

which

contains

only

the

properties

actually

changed

during

the

event.

For

example,

if

an

Airspace

is

activated,

the

Digital

NOTAM

is

encoded

as

a

TEMPDELTA

TimeSlice

for

the

Airspace

that

contains

an

(activation.AirspaceActivation.)status='ACTIVE'.

Image Removed

Image Added

The

TEMPDELTA

and

the

BASELINE

records

are

closely

related,

they

are

facets

of

the

same

feature.

When

there

is

no

baseline

feature,

the

Digital

NOTAM

itself

is

in

the

form

of

a

new

baseline.


It

contains

all

the

properties

that

are

necessary

to

be

know

for

that

feature

during

its

duration

of

validity.

Image Modified


The role of the Event feature


Warning
titleToDo

take the previous diagram and add the Event as another box, related to the TEMPDELTA. Add a second TEMPDELTA for a related feature (a route closure)




Warning
titleToDo

take the previous diagram and add the Event as another box, related to the BASELINE. Add a second TEMPDELTA for a related feature (a runway closure because of a temporary crane at its end.



Basic elements of the XML coding

explain here the basic elements of the XML coding (collapsed elements), for the two threads

  • the Event
  • the TEMPDELTA timeslice with its type and its meaningful attributes.
  • the association with the event

More advanced elements of the XML encoding

For both threads

  • duration of validity
  • gml:identifier as the principal means to connect the TEMPDELTA with the BASELINE. Mention that the BASELINE is not part of the digital NOTAM encoding, but that it can be provided as a complement. More details in the next section.

Option - complementary baseline data

Except for the new obstacle, show here how additional baseline data could be provided in order to:

  • generate NOTAM text or text for pre-flight briefing
  • graphicaly represent the event
  • identify the feature affected in a system that does no use the UUID values as feature identifier


Table of Contents