5
$\begingroup$

I just wonder what was the benefit of introducing AIXM (Aeronautical Information Exchange Model) version 5.1+?
What problems or demands does the new version (with its complex temporary model) actually solve? It allows some more complex scenarios, but I cannot imagine any real life use cases that were not possible in AIXM 4.5.
Might be that there are some more detailed Feature/Entity attributes. But that could be done with AIXM 4.5+?

Could anybody explain the need to me?

$\endgroup$
0

1 Answer 1

6
$\begingroup$

This version 5+ includes temporality at the feature level (in 4.5 it was at the message level). The model allows feature properties to change with time.

enter image description here

Source.

Version 5+ supports dynamic data. A value is associated with a validity period, and it can exist multiple values associated with different periods of validity for the same property.

From aixm.aero:

The purpose of the AIXM Temporality Concept is to enable the modelling and encoding of aeronautical data in relation with the time. As compared to the previous version 0.5, the version 1.0 (released with AIXM 5.1) includes some clarifications with regard to Schedules/Timesheets and some editorial corrections.

enter image description here

Typical temporary changes: Closed runway, inoperative aid, frequency change, obstacles... This example of a closure for one hour of an airport demonstrates dynamic data, and the part which was not available in 4.5:

enter image description here

Source.

As soon as the schedule of changes haves been entered in the database, it's easy to automatically prepare and schedule the corresponding NOTAMs. This is what is targeted by this upgrade of the model:

In order to satisfy the temporal requirements of aeronautical information systems, AIXM must include an exhaustive temporality model, which enables a precise representation of the states and events of aeronautical features. In particular, this shall enable the development and the implementation of digital NOTAM.

$\endgroup$
2
  • $\begingroup$ Yes, that's very generic and that is reflected in AIXM4.5 as well. More simple - less opportunities of different (miss)interpretations. I do not see the need for the extended model. What use case could not have been addressed before. $\endgroup$
    – m.weiloa
    Commented Mar 24 at 15:17
  • $\begingroup$ @m.weiloa. The point is temporality is now at the feature level, and dynamic data are available. I added an example in the answer. $\endgroup$
    – mins
    Commented Mar 24 at 17:10

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .