140 likes | 439 Views
Open session. AIXM 5.1 XML Developers' Seminar #2 – Dec 2009. 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
E N D
Open session AIXM 5.1 XML Developers' Seminar #2 – Dec 2009
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
AIXM data base design • PULSAR: Design of the AIXM 5.1 database for the x-Snowtam trial Open session
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
Source code generation issues using XMLBeans • See AIXM Forum – many messages on this subject • Anyone here who has experience? Open session
Geoborders (Airspace border dependencies) Open session
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 GeoBorder Open session
Geoborders (Airspace border dependencies) • Significant Point reference from airspace vertex • <AirspaceVolume> <hasHorizontalBoundary> <Surface> <polygonPatches> <PolygonPatch> <exterior> <LinearRing> <gml:pointProperty xlink:href="#myPointID“ xlink:title=“236º/15NM from VOR/DME XYZ”/> • Where the Point with the gml:id “myPointID” is defined in the same file as position for a Navaid or DesignatedPoint <Navaid> …. <gml:pointProperty> <aixm:Point gml:id="myPointID"> <gml:pos>5.97166667 50.97611111</gml:pos> </aixm:Point> </gml:pointProperty> Open session
Derivation by restriction , why it is needed at all Open session
Implementation of AIXM 5.1 • EAD • Obstacle import/export in Q1 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 • eASM (Airspace activation and Route closures) • Intended for May 2010 • eRAD intended as well for 2010-2011 Open session
Loading and publishing Digital NOTAM Open session
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
ARINC424-A Model UML 2010: A424 v19 will become A424-A v1 Input for the definition of 424A content NDBX (former Arinc829)(Embedded format Requirements) ARINC424-19 “Bijection” between original A414-19 and Arinc424-A ASCII ARINC 424A ARINC424-A formats Script 1Visual Basic Script 2TBD ARINC 424A ASCII Full ARINC424A XML ARINC424A BXML(embedded XML) Adapted ARINC424 XML Open session
FMSSimulation Mapping AIXM / Arinc424A-XML • In 2011, EUROCONTROL will • Define a set of mapping rules for conversion of ground sources (AIPs published in AIXM 5.1 format) into Arinc424A-XML • 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 424A XML/BXML Open session