Hello!
I encountered a bug in the AIXM 4.5 writer. The feature type "AIRSPACE_DERIVED_GEOMETRY" is mixing up the order of the elements in the resulting AIXM file. Therefor the output file is not valid against the AIXM 4.5 schema.
The XML fragment which looks like this in the source file (AseUid and codeOpr are alternating):
<Adg>
<AdgUid mid="1">
<AseUid mid="1">
<codeType>RAS</codeType>
<codeId>ABCD</codeId>
</AseUid>
</AdgUid>
<AseUidBase mid="2">
<codeType>PART</codeType>
<codeId>ABCD_1</codeId>
</AseUidBase>
<codeOpr>UNION</codeOpr>
<AseUidComponent mid="3">
<codeType>PART</codeType>
<codeId>ABCD_2</codeId>
</AseUidComponent>
<codeOpr>UNION</codeOpr>
<AseUidComponent mid="4">
<codeType>PART</codeType>
<codeId>ABCD_3</codeId>
</AseUidComponent>
<codeOpr>UNION</codeOpr>
<AseUidComponent mid="5">
<codeType>PART</codeType>
<codeId>ABCD_4</codeId>
</AseUidComponent>
</Adg>Are written like this into the destination file (AseUid and codeOpr are grouped together):
<Adg>
<AdgUid mid="1">
<AseUid mid="1">
<codeType>RAS</codeType>
<codeId>ABCD</codeId>
</AseUid>
</AdgUid>
<AseUidBase mid="2">
<codeType>PART</codeType>
<codeId>ABCD_1</codeId>
</AseUidBase>
<codeOpr>UNION</codeOpr>
<codeOpr>UNION</codeOpr>
<codeOpr>UNION</codeOpr>
<AseUidComponent mid="3">
<codeType>PART</codeType>
<codeId>ABCD_2</codeId>
</AseUidComponent>
<AseUidComponent mid="4">
<codeType>PART</codeType>
<codeId>ABCD_3</codeId>
</AseUidComponent>
<AseUidComponent mid="5">
<codeType>PART</codeType>
<codeId>ABCD_4</codeId>
</AseUidComponent>
</Adg>Please address and resolve this bug as AIXM 4.5 is still wide spread in the aviation community.