Airport Schema Export AIXM

gizemBAYBAŞDAĞLI

Hi everyone,

I’m working with an Airports Database (AMDB). The database includes the expected AMDB feature layers which have vector data (e.g., RunwayElement, TaxiwayElement, Apron, MarkingLines, etc.), but many attribute fields are not fully populated.

When I export the database to AIXM using the Export AIXM 5.1 Message tool, not all features are exported. I selected AircraftGateStand, ApronElement, RunwayElement, RunwayEnd, TaxiwayElement, Marking, and RunwayBlastPad, but the export only included TaxiwayElement, Apron, and RunwayEnd. RunwayElement and AircraftGateStand were missing.

Has anyone experienced this? Do some features require specific relationships to be exported together, or are there mandatory attribute fields that must be filled before the export will include them?

Thanks in advance!

tschwartz

Hello Gizem,

Without looking at your data and current airports database version (which could be an issue as well), there are indeed extra features and feature attributes and relationship fields that are needed to be populated to export a an AIXM message. Sometimes a feature can have multiple relationships established as well. If you are using the esri_airports_scheme.xml that comes with our version 3.5 product files, this will include the first edition of scheme that supports AIXM and therefore the first required field of FEATTYPE defined by the DO272/ED99 FeatureTypeBaseType domain.

 

Next there will be field indicating the relationship filed that use the UUID (AIXM UUID format/concept) found in the required IDNUMBER of the related feature, which could be a parent or child feature depending on if you are mapping downwards or upwards from a feature. An example for AircraftGateStand where there is now a field added called APRONELEMENT_ID and has a more distinct alias set as Apron Element Feature Unique Identifier (UUID) to highlight that this needs the UUID from the related feature.

This typically continues upward to the  AirportControlPoint (AIXM ADHP) feature, or in our case up a level to the related ApronElement, then Apron, then AirportControlPoint and all set with the proper FEATTYPE and relationship UUID field populated with the correct UUID.

Hopefully this helps and allows you to export more complete messages with some further database population. Also, I believe Esri Turkey will be reaching out soon as well, so keep an eye out for an email from them on this topic related to your local situation.

Thanks!

Trevor Schwartz | Sr. GIS Consultant and Aviation Specialist | Professional Services