Open session AIXM 5 1 XML Developers Seminar

Open session AIXM 5. 1 XML Developers' Seminar #2 – Dec 2009 The European Organisation for the Safety of Air Navigation

Content • • • AIXM data base design AIXM and open source software Source code generation issues using XMLBeans Geoborders Derivation by restriction, why it is needed at all Implementation of AIXM 5. 1 Loading and publishing Digital NOTAM Flight Procedure Coding Mapping with ARINC 424 (A) Open session 2

AIXM data base design • PULSAR: Design of the AIXM 5. 1 database for the x-Snowtam trial Open session 3

AIXM and open source software • • • Open source modeling tools that work with AIXM • UML – XMI exported by Rational Rose • The scripts only work in Rational Rose… • In 2010, we will move to EA from Sparx • XML schema – we try to make it work with xerces • Weak link – the GML and especially the metadata schema, which are outside our control Open source software developed based on AIXM • See www. sourceforge. net • Probably not finalised • Digital SNOWTAM Trial software of Eurocontrol – available for evaluation, not approved to be released as open source What else? Open session 4

Source code generation issues using XMLBeans • See AIXM Forum – many messages on this subject • Anyone here who has experience? Open session 5

Geoborders (Airspace border dependencies) Open session 6

Geoborders (Airspace border dependencies) • geo-border reference from airspace vertex • FAA solution mentioned yesterday By reference to a local copy of the exact extraction from the Geo. Border Open session 7

Geoborders (Airspace border dependencies) • • Significant Point reference from airspace vertex <Airspace. Volume> <has. Horizontal. Boundary> <Surface> <polygon. Patches> <Polygon. Patch> <exterior> <Linear. Ring> <gml: point. Property xlink: href="#my. Point. ID“ xlink: title=“ 236º/15 NM from VOR/DME XYZ ”/> • Where the Point with the gml: id “my. Point. ID” is defined in the same file as position for a Navaid or Designated. Point <Navaid> …. <gml: point. Property> <aixm: Point gml: id="my. Point. ID"> <gml: pos>5. 97166667 50. 97611111</gml: pos> </aixm: Point> </gml: point. Property> Open session 8

Derivation by restriction , why it is needed at all Open session 9

Implementation of AIXM 5. 1 • EAD • Obstacle import/export in Q 1 2010 • Upload only via IFS (not ESI yet) • Minimum data set export • Progressively, during 2010 -2011 • Digital NOTAM increment 1 – end 2011 • Full import/export in AIXM 5. 1 (probably) • CFMU / ADR • e. ASM (Airspace activation and Route closures) • Intended for May 2010 • e. RAD intended as well for 2010 -2011 Open session 10

Loading and publishing Digital NOTAM Open session 11

Flight Procedure Coding • FAA • Digital charting and procedure design system based on AIXM 5. 0 • Limited experience in Eurocontrol • We are interested to cooperate with those who are interested by this side of the model in order to validate and improve the model from a PANS-OPS perspective • Intended for AIXM 5. 2 Open session 12

2010: A 424 v 19 will become A 424 -A v 1 Input for the definition of 424 A content NDBX (former Arinc 829) ARINC 424 -19 ARINC 424 -A Model UML “Bijection” between original A 414 -19 and Arinc 424 -A ASCII ARINC 424 A ARINC 424 -A formats ARINC 424 A ASCII Open session (Embedded format Requirements) Script 1 Visual Basic Script 2 TBD Full ARINC 424 A XML Adapted ARINC 424 XML ARINC 424 A BXML (embedded XML) 13

Mapping AIXM / Arinc 424 A-XML • In 2011, EUROCONTROL will • Define a set of mapping rules for conversion of ground sources (AIPs published in AIXM 5. 1 format) into Arinc 424 AXML • Develop, as a proof of concept, some code that implements these rules • Primary focus will be on data used by the FMS (former NDBX scope) • Objective: validate the concept of a full digital data chain from AIPs up to the embedded system ARINC 424 A XML/BXML Open session FMS Simulation 14