Overcoming the Complexities of AIXM with Model Based Data Integration

Overcoming AIXM Complexity with FME

Agenda ● AIXM Intro & Challenges
● Safe & FME
● FME approach to AIXM challenges
● Visualizing
○ Extract, process and build / interpret AIXM objects
and geometry
● AIXM to GIS (Reading AIXM)
● GIS to AIXM (Writing AIXM)
● AIXM Validation
● Integrating AIXM with Enterprise Systems and Web
Services
● Versions, Extensions and Related Formats
● Migrate from AIXM 4.5 to 5.1
● Summary

AIXM = Aeronautical Information Exchange Model - See: aixm.aero
Purpose: Provide a digital format for Aeronautical Information Services (AIS)
Requirements:
● AIS information/data flows are increasingly complex and made up of
interconnected systems with multiple suppliers and consumers.
● Air Traﬀic Management (ATM) system needs high data quality, cost eﬀiciency and
automation.
● AIS is moving from paper products and messages to provision of digital data.
● AIXM supports this transition by enabling the collection, verification, distribution
and transformation of digital aeronautical data
https://www.aixm.aero/
What is AIXM?

AIXM Scope
● Aerodrome/Heliport including taxi ways, services,
facilities, etc.
● Airspace structures
● Organisations and units, including services
● Points and Navaids
● Procedures
● Routes
● Flight restrictions
AIXM takes advantages of established information
engineering standards and supports current and future
aeronautical information system requirements.

AIXM Functional Groups
• ADHP (Aerodrome/Heliport)
• Airspace
• Designated Points
• MSA (Minimum Sector Altitude)
• Navigation Aids
• Obstacles
• Organizational Authorities
• Runways
• Special Navigation Aid Systems
• Procedure Legs

Chicago O’Hare: Airport Chart
● Runways
● Taxiways
● Aprons
● Runway Lighting Systems
● Vertical Structures

Chicago O’Hare: AIXM 5.1 GML

Chicago O’Hare: AIXM5 to OGC KML

Seattle: Minimum Vector Altitude Airspaces

AIXM 4.5 Challenges
● Non geometric
● Highly normalized
● Object oriented – XML based
● Rules based – many conditions and
restrictions between related
elements
● Application schema validation
● Limited available sample data,
incomplete datasets

AIXM 5 Challenges
● Geometry modelled according to GML
standard. Inherently complex –
geometry properties and traits
● Complex relationships between
features / feature types
● Namespace challenges
● Object oriented – XML based. Requires
complex transforms to/from relational
● Rules based – many conditions and
restrictions between related tables
● Application schema validation
● Limited available sample data,
incomplete datasets

XML Data Structures: Object vs Relational
attribute1 attribute2 Active
Date_From
Active
Date_To
Coordinates
John Vancouver 11-22-99 12-11-09 -123.1,49.25
-122.9,49.15
June Surrey 02-25-05 9-15-10 -122.8,49.12
-122.5,49.0

Years of solving data challenges
25+
10,000+
Organizations trusting us worldwide
Partners supporting our network
150+
128
Countries with FME customers
Safe Software
Company Profile
www.safe.com

Industry
Customers that
Rely on FME

Our Mission
To help you maximize the value of data.

Connect
to Data Sources
Transform
the Data
Automate
the Workflows

FME®
Integration Platform
Connect. Transform. Automate.
FME Desktop FME Server FME Cloud
Build & Run Data Workflows Automate Data Workflows
(on-premises)
Automate Data Workflows
(hosted FME Server)
Mobile Apps
Access the Power of FME
Wherever You Are
Get a free trial of FME Desktop and FME Server at safe.com

AIXM Opportunities and
Approaches with FME

Common AIXM Challenges Addressed with FME
Improve your
operational eﬀiciency
Obstacle avoidance/
Restrictions on
operations aﬀecting air
safety
Manage your facilities
and infrastructure
Enterprise Automation
Restrictions /
Obstacles / UAV
Management
Airport Management
Convert to/from AIXM
and analyze airspaces
Airspace Management

AIXM 5 GML Benefits with FME
● Geometry processing handled by GML schema & FME’s
GML infrastructure: Readily consume & generate datasets
Unlike AIXM 4.5, geometry complexity often hidden from
the user. Focus on features not XML.
● Extensions are easy – just a matter of employing the
extension schema
● Namespace handling – namespace prefix helps keep
them straight
● Object oriented data model. FME’s tools for object to
relational transforms have evolved considerably
● Rules based – automate data transformation. Map once
then automate.
● Automate XML and business rule validation

EU INSPIRE Airports to AIXM 5 GML
● Standard to Standard translations are easier
● Write: AIXMBasicMessage, AirportHeliport, AirportHeliportTimeSlice
● Hierarchy with gml_parent_id, gml_id
● GeometryPropertySetter (xml_geometry), Aggregator

Demos
● Read Chicago -> Inspector, writing KML
● INSPIRE to AIXM5
● Visualization (Central America)
● AIXM to GIS
● GIS to AIXM
● AIXM 4.5 to 5.1 Runways
● Alternative Encodings: OGC Features
API / GeoJSON
● Other dataset examples from Europe

FME and 3D Visualization...
● From simple to complex workflows
● From small to huge dataset
● The Magic of FME handles it all
● From 2D to 3D display
● Scale: from kilobytes to gigabytes
● Google Earth performs seamlessly
Google Earth Logo is a registered trademark of Google Inc.
... a Perfect Combination!

AIXM - Vancouver Area Airspace Zones
UAV flight planning

Example: Visualizing YVR in 3D (PDF, KML)

Overcoming the Complexities of AIXM with Model Based Data Integration

Austrian Obstacles: AIXM to Geodatabase

GIS to AIXM: Geodatabase to AIXM5

Obstacle
Avoidance
and Planning

Obstacle Limitation Surface
Showcase:
3D Civil Aviation Tool
Obstacle Limitation Surface / Airport Zoning
Regulation
With minimum parameters, FME handles all
the magic of complex calculations for
constructing 3D models and generate
contours, eliminating the need to acquire
expensive third-party software (e.g. Obstacle
Surface Planner from Simtra) for generating
Obstacle Limitation Surfaces, enabling
inspectors to regulate structure’s height within
AZR.
Vancouver International Airport OLS/AZR
Obstacle Limitation
Surface

Flight Obstacles
● Flight obstacles from Excel
● FME Server reads source data and provides an HTML report, and if the data
is valid, it’s written to an Oracle db
● The HTML report contains a map + feature info
HTML
Report
Oracle DB
Excel

High place recognition using LAS
● National Land Survey provides LAS datasets from whole Finland through an API
● FME reads selected LAS mapsheets from the API
● FME analyzes, which LAS points are over a certain threshold (diﬀerent for every
airport)
● FME produces maps and lists of the areas, and map sheets, which have these
high places

High place recognition using LAS

Analysis done 45 km from
airports

Data Quality and
Validation
I can’t think of a single solution with
FME where data quality and validation
were not part of the “Data Preparation”
or day to day activity.
Data Health is something every
organization battles.

XMLValidator: Assess AIXM Validity and Generate Diagnostics
Possible Values:
● None
● Syntax
● Syntax and Namespace
● Syntax and Schema
New:
● Multiple XSD support
Use XMLValidator pointing to
FMExmlschemasaixm5.1mes
sageAIXM_BasicMessage.xsd

Integrating AIXM with
Enterprise Systems
& Web Services

Data Integration
The Opportunity
● Bring data sources together
● Share information automatically
● Build redundant database for
mission critical functions
● Format data and streamline for
stakeholders

FME as Data Integration Platform at Schiphol
GIS
Core-database
with Assets
and Infrastructure
information
Edit Platform
Schiphol Internal
Schiphol
Optimized
Viewing
data
Viewing Platform
Schiphol Internal
Viewing Platform
Schiphol Internal&External
Optimized
Geo Data
Realtime External
Sources
API Platform
Public
Geo
API
Wayfinding
POI’s
Maps
Routing
FME is the “Glue” between systems to keep data up to date and in Sync.

Service Notices HTML to CSV and PDF Download

Nav Canada Service Notices: HTML to CSV, PDF

AIXM Version and
Extension Support
AIXM Versions Supported:
● 4.5
● 5.0, 5.1, 5.1.1
● Extensions: FAA, EUROCONTROL
Related Formats:
● FIXM, WXXM, ARINC424*
*SpatialDNA

AIXM Related Formats
WXXM - covering weather data
FIXM - dedicated to flight telemetry data
AMXM - specified for airport mapping databases (AMDB)
SWIM - System Wide Information Management: moving SWIM into operational domains
in a global and harmonised manner.

FME Support for XML/GML: Overview
● Support for XML family of formats
● XML reading and writing (Feature Path Mode)
● XML writing with XMLTemplater, Text File Writer
● XML Reading and Writing with new XSD-Driven XML Reader/Writer
● GML reading and writing (application schema, ignore schema)
● XML processing including XQuery, XSLT, validation and formatting
● OGC Web Service Clients (WxS, OGC API Features)
● Web Services hosted by FME Server

XML Processing
● Use flattening to resolve objects into features and fields
● Use schema mapping transformers to relate flattened fields to
desired destination data model
● OR preserve XML data model and update in place using XQuery
and XSLT transformers
● Use XMLTemplater to merge FME attributes into an XML
template or structure you define. Supports sub-templates to
nest feature types.
● Validate XML for syntax or against application schema
● Format XML to serialize or pretty print

Key points on FME GML Writer
● GML writing uses application schema (.xsd’s) - destination
model captured from the XML schema
● Map schema directly to destination feature type fields
● Multiple, complex geometry support
● Geometry names and traits
● Voidable attributes in output GML / null support in FME
● XMLTemplater no longer needed for most GML writing, but
useful for other XML generation like metadata, xml_xml &
xml_geometry object fields

Spatial DNA: AIXM & ARINC424
ARINC424:
● Commercial text standard for aviation
data developed in the 1970’s
● Used by flight management systems
and ATC (by Honeywell in 757s,767s)
Spatial DNA:
● Use FME to supports conversion
between ARINC424, AIXM 4.5 & 5.1
● Safe partner and maker of ARINC424
FME plug-in
● Frequentis implementation story

Weather
Information
Exchange Model
Interoperable
meteorological
information
exchange covering
the needs of the
aviation industry
eurocontrol.int
faa.gov
Power of Generic GML: WXXM

AIXM 4.5: Reading – Key Tasks
● Feature Merging
● Building Geometries
○ All geometries built using points (generated by reader) and information from
attributes
○ E.g. Runways, Holding Procedures, Minimum Sector Altitude
(Width, length, bearing) Turn direction, speed, course angle From/to angles, radius

AIXM 4.5 to AIXM 5.1 Migration Tasks
● Read AIXM 4.5 and perform joins (FeatureMerger)
● Interpret parameters & build geometries (LineBuilder, Buﬀerer)
● Perform schema mapping & define feature properties
(AttributeCopier, AttributeCreator)
● Transform geometry to match destination schema
(GeometryPropertySetter, Aggregator)
● Generate ids & parent / child relationships (AttributeCreator)
● Map to parent, child and container feature types to write to AIXM5

Migration - AIXM 4.5 Input: YVR Runways*
*Source AIXM4.5 data here derived from publicly available open street map data. As with any data in this webinar, it is for demo purposes only and not to be used for navigation.

AIXM 4.5 to AIXM 5.1: Runways
● Read AIXM4.5 and perform joins
● Interpret parameters & build geometries
● Perform schema mapping & define feature properties
● Transform geometry to match destination schema
● Generate ids & parent / child relationships
● Write parent, child and container elements to AIXM5

Migration - AIXM 5.1 Output: YVR Runways

AIXM Next:
Future Proofing Your AIS

AIXM Next / AIS Future Proofing
● AIXM 5.2
● Digital NOTAMs
● Other encodings: GeoJSON
● Related Standards: OGC Features API, REST,
INSPIRE
● Emerging applications: UAS
● Bug fixes
● Resources

Digital NOTAMs: Special Activity Airspace

Digital NOTAMs: Runway Closure

Alternative Encodings:
OGC API Features: HTML, JSON, GeoJSON via REST

Chicago O’Hare via OGC API Features / GeoJSON

AIXM and UAVs: UK Airspace Restrictions

● FME has comprehensive support for aviation data including AIXM & AIS
● Standards support is central to our goal of promoting data sharing, integration &
automation
● Ongoing support and refinements for AIXM 4.5 and 5.1 and beyond
● Core improvements to GML / XML infrastructure supports AIXM
● Airports have seen significant development in regards to system integration
● Leverage FME Server to automate repeatable workflows, updates, enterprise
integration and cloud for overall Aeronautical Information Systems support.
● FME supports your workflows: airspace management, obstacle avoidance, uav
restrictions, enterprise solutions architecture, alternative encodings
Summary

AIXM Resources
AIXM Home / Github: aixm.aero github.com/aixm
Eurocontrol
AIXM Confluence Page: ext.eurocontrol.int/aixm_confluence
AIXM Forum: eurocontrol.int/agor/HomeLoggedOn.do
AIXM Data: ext.eurocontrol.int/aixm_confluence/display/AIX/Inventory
FAA AIXM:
faa.gov/about/oﬀice_org/headquarters_oﬀices/ato/service_units/mission_support/aixm/
NATS nats-uk.ead-it.com/public/index.ph
ICAO Data: https://gis.icao.int/icaoetod/
AIXM Wikipedia: en.wikipedia.org/wiki/AIXM
OGC Aviation: https://www.ogc.org/domain/aviation

EU INSPIRE TN WFS: Austrian Air Transport Network

Austria AIS WFS: Navaid:DME, Airspaces

Austria - AIXM Obstacles: Wind Farms

Spain AIXM: Navaids, Designated Points, Lights

FME Community
+10,000 Global Users
● Ask how-to questions
● Engage with Safers
● Submit ideas for FME
Knowledge & Training
Learn FME
Technical Support
Report a Problem
● Articles & tutorials
● Live online training
● On-demand resources
● Support cases
● Live chat
● When in doubt… ask us!
We’re All About Free Resources
"FME sets the standard for support and is the leader by far". - Brad
“Very helpful and went above and beyond to help find a solution to my request! A+" - Justin
FME Hub
Discover More
● Access transformers,
templates, connectors,
and more

FME Resources: Aviation
Knowledge.safe.com safe.com/presentations/
Partners: https://www.safe.com/partners/
Grafton: safe.com/presentations/new-era-of-aviation-fme-cloud-safer-skies/
FME customer stories
Nav Canada: safe.com/presentations/data-driven-aeronautical-chart/:
fme.ly/yvrjfme.ly/yyj fme.ly/ams fme.ly/lax fme.ly/drones
safe.com/airports
search.safe.com/#q=aixm&sort=relevancy&f:@commontype=[Questions]

FME AIXM Updates
● AIXM 5.x Reader/Writer: Added v5.1.1 support
● AIXM: Added warning messages for AIXM reading wrong version
● AIXM 4.5 Writer: Added dataset validation
● AIXM 5.x reader: Map embedded objects as Multi Geometries, not
Null
● AIXM5 reader: Snap defined geometries when constructing paths
● AIXM 5 writer: GML uom fixes for curves
● AIXM 4.5 reader: Read created and eﬀective into
aixm_update_created and aixm_update_eﬀective format attributes
for snapshot files – 2019.2
● New XSD Driven XML Reader and Writer (for metadata etc) – 2020.0
● Numerous enhancements based on improvements to core GML R/W

Bonus Content
Connect with us for more FME

Thank You!
Any questions we can answer?
Connect with us for more FME

Question: “Feature Type RunwayTimeSlice has an Attribute annotation{}. But it
doesn't find its way into my XML File. What am I doing wrong?”
Answer: Write an xml_xml field with the AIXM5 GML writer, the value needs to be
a valid XML fragment. Given annotation{} is a series object, use a list element.
Create annotation{0} with the value:
<aixm:annotation xmlns:aixm="http://www.aixm.aero/schema/5.1"
xmlns:gml="http://www.opengis.net/gml/3.2">
<aixm:Note gml:id="anno_@Value(_uuid)">
<aixm:purpose>REMARK</aixm:purpose></aixm:Note>
</aixm:annotation>
FME Community QnA: AIXM Annotations

Question:
“From VerticalStructure feature I have to go to VerticalStructurePart Object,
then through VerticalStructurePartGeometry and then Geometry:
ElevatedPoint object. Does anybody know how to solve these complex
relationships to correctly write VerticalStructureDataSlice geometry in FME?”
FME Community QnA: AIXM Complex Geometry

Answer:
● Use the AttributeCreator, GeometryPropertySetter, Aggregator method. This
requires the above transformers for each level of nesting. This can be tricky –
possible to overwrite the Child with Parent geometry.
(note: don’t forget to use GQuery)
● Alternatively, try XMLTemplater with a template of the desired output geometry.
Feed the required field values or GML geometries into the template
(GeometryExtractor). The AIXM Writer allows XML fragments for any
xml_geometry field, xml_xml fields or any parent of a nested field (parent.child).

vs.
Normal feature geometry writing, vs option for xml_xml,
xml_geometry XML fragment template geometry writing

Overcoming the Complexities of AIXM with Model Based Data Integration

More Related Content

Similar to Overcoming the Complexities of AIXM with Model Based Data Integration (20)

More from Safe Software (20)

Recently uploaded (20)

Overcoming the Complexities of AIXM with Model Based Data Integration