Transcript Slide 1

Changes in AIXM
5.1 from AIXM 5.0
Presented to: AIXM Developer’s Seminar
By: Navin Vembar
Date: January 14, 2010
Federal Aviation
Administration
The Change from 5.0 to 5.1
•
•
•
•
There were 46 accepted change proposals
All available on AIXM Wiki
Most were changes to existing features
Some were major conceptual changes,
however
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
2
New Features or Types
• AeronauticalGroundLight
– Aerodrome Beacons, etc.
• HotSpot
• RulesProcedures
• CodeMarkingConditionType
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
3
Removed Features, classes, types
• AirspaceAssociation removed
• TerrainPoint removed
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
4
Updates to Features
• Nose-In Guidance at Aircraft Stands
• GateStand->AircraftStand
• Add synchronized lighting attribute to
VerticalStructure
• Update to material attribute of
VerticalStructure
• Addition of certification date info to
AirportHeliport
• Runway Centerline Point designator
attribute
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
5
Updates to Features, cont’d
• Move attributes from VerticalStructure to
VerticalStructurePart
• Addition of Navaid purpose
• Addition of attributes to FAS Data Block
• Addition of offset attributes to FinalLeg
• Updates to SurfaceContamination feature to better
represent SNOWTAMs
• Add signalType to RadioFrequencyArea and
NavaidOperationalStatus
• Add Morse Code to MarkerBeacon feature
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
6
Updates to Relationships
• AirportHeliport isManagedBy relationship updated
to association class
• ApproachLightingSystem now inherits from
GroundLightSystem
• Multiplicity of relationship from PostalAddress, etc.
to ContactInformation
• Self-association for OrganizationAuthority
• Add relationship from Navaid to AirportHeliport
• Reversed association between Procedure and
SafeAltitudeArea
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
7
Updates to Relationships, cont’d
• New association between SafeAltitudeArea
and AirportHeliport
• New association between
MissedApproachLeg and
ApproachCondition
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
8
Updates to Types
•
•
•
•
•
•
•
•
•
•
Added new value in CodeProcedureDistanceType
Added new value in CodeAltitudeAdjustmentType
Remove Y, Z from CodeRouteDesignatorSuffixType
Separating RunwayElement and TaxiwayElement types
ILS Category changes to types
Add RNAV types to CodeDesignatedPointType
Use of ISO Language codes instead of custom
CodeFuelType is changed to codelist
Additional uom values
NOTAM updates to CodePurposeType, CodeFlightStatusType
and CodeOriginType
• Direction Finder added as a Navaid Type
• ALLOWED as FlightRestriction type
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
9
Changes to XSD
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
10
Changes in AIXM 5.1 XSD
schemas
•
•
The <<enumeration>> types no longer exist => replaced by
<<codelist>> with the OTHER value
Mapping of <<codelist>>
<simpleType name="CodeAircraftEngineBaseType">
<union>
<simpleType>
<restriction base="xsd:string">
<enumeration value="JET">
<annotation>
<documentation/>
</annotation>
</enumeration>
<enumeration value="PISTON"/>
<enumeration value=“TURBOPROP"/>
<enumeration value=“ALL"/>
</restriction>
</simpleType>
<simpleType>
<restriction base="string">
<pattern value="OTHER:\w{2,58}"/>
</restriction>
</simpleType>
</union>
</simpleType>
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
11
AIXM 5.1 Mapping Rules Datatypes
• Mapping
<<enumeration>>
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
<simpleType name="CodeAircraftEngineBaseType">
<union>
<simpleType>
<restriction base="xsd:string">
<enumeration value="JET">
<annotation>
<documentation/>
</annotation>
</enumeration>
<enumeration value="PISTON"/>
<enumeration value=“TURBOPROP"/>
<enumeration value=“ALL"/>
</restriction>
</simpleType>
<simpleType>
<restriction base="string">
<pattern value="OTHER:\w{2,58}"/>
</restriction>
</simpleType>
</union>
</simpleType>
Federal Aviation
Administration
12
AIXM 5.1 Mapping Rules Datatypes
• Mapping <<codelist>>
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
<simpleType name="CodeApproachLightingBaseType">
<union>
<simpleType>
<restriction base="xsd:string">
<enumeration value="ALSAF">
</enumeration>
<enumeration value="MALS">
</enumeration>
<enumeration value="MALSR">
</enumeration>
<enumeration value="SALS">
</enumeration>
......
</restriction>
</simpleType>
<simpleType>
<restriction base="string">
-- NO PATTERN -</restriction>
</simpleType>
</union>
</simpleType>
Federal Aviation
Administration
13
AIXM 5.1 Mapping Rules Datatypes
• Mapping <<datatype>> - default case
<simpleType name="DateBaseType">
<restriction base="xsd:date">
</restriction>
</simpleType>
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
14
AIXM 5.1 Mapping Rules NilReason
• Most of AIXM 5.1 Data Types define a
nilReason, used to indicate the reason for a
null value.
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
15
AIXM 5.1 Mapping Rules NilReason
• Mapping nilReason
<simpleType name="CodeAircraftEngineBaseType">
<union>
<simpleType>
<restriction base="xsd:string">
<enumeration value="JET">
……………………..
</restriction>
</simpleType>
<simpleType>
<restriction base="string">
<pattern value="OTHER:\w{2,58}"/>
</restriction>
</simpleType>
</union>
</simpleType>
<complexType name="CodeAircraftEngineType">
<simpleContent>
<extension base="aixm:CodeAircraftEngineBaseType">
<attribute name="nilReason“ type="aixm:NilReasonType"/>
</extension>
</simpleContent>
</complexType>
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
16
AIXM 5.1 Mapping Rules - UOM
• Mapping Units of Measurement
<simpleType name=“ValDepthBaseType">
<restriction base="xsd:decimal">
</restriction>
</simpleType>
<complexType name="ValDepthType">
<simpleContent>
<extension base="aixm:ValDepthBaseType">
<attribute name="nilReason" type="aixm:NilReasonType"/>
<attribute name="uom" type="aixm:UomDepthType" use="required"/>
</extension>
</simpleContent>
</complexType>
AIXM 5.1 Changes – AIXM Developer’s Seminar
Federal Aviation
17
January 2010
Administration
Conceptual Changes
• Replacement of all textual attributes with Notes
– To facilitate a truly digital, non-textual definitions
• In enumerations, allow for OTHER:<value>
– Allows for arbitrary enumeration values to be added by the user
• Greater harmonization of AIXM and AMDB
standards
– Focus on SurfaceCharacteristics
• Aircraft Characteristics Updates
– Updates across features and types to better represent the
capabilities of an aircraft
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
18
Conceptual Changes, cont’d
• Schedule
– Simplification of representation of schedule across
features (major change)
• Harmonzation of Usage Features
– Tied to the above
• Timesheet
– Significant updates to Timesheet
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
19
Base AIXM Feature/Object
Constructs
• AbstractAIXMObject:
Base type for AIXM complex types that are NOT features. For example,
City, ContactInformation, AirspaceVolume, etc. It derives from
AbstractGMLType so that AIXM objects are recognised as GML objects,
thus ensuring that GML-aware applications recognise them properly.
Retains only the mandatory gml:id attribute.
<complexType name="AbstractAIXMObjectType" abstract="true">
<complexContent>
<restriction base="gml:AbstractGMLType">
<sequence>
<sequence/>
</sequence>
<attribute ref="gml:id" use="required"/>
</restriction>
</complexContent>
</complexType>
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
20
Base AIXM Feature/Object
Constructs
• [Posted on the AIXM forum] The gml:id attribute
is now mandatory for AIXM "objects" also, such as
ContactInformation, VerticalStructurePart, etc. This is a
side effect of deriving all AIXM Objects from AbstractGML,
which was considered necessary in order to avoid the risk
that GML-aware applications do not see certain geometrical
<complexType name="CityType">
information, if hidden inside a non-GML object such as
<complexContent>
<extension base="aixm:AbstractAIXMObjectType">
VerticalStructurePart.
<sequence>
<group ref="aixm:CityPropertyGroup"/>
<element name="extension" minOccurs="0" maxOccurs="unbounded">
<complexType>
<sequence>
<element ref="aixm:AbstractCityExtension"/>
</sequence>
<attributeGroup ref="gml:OwnershipAttributeGroup"/>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
21
Base AIXM Feature/Object
Constructs
• AbstractAIXMPropertyType:
It provides a basis for deriving AIXM feature/object properties. It defines the
nilReason attribute and currently, it is only used for properties that are derived
from association with an AIM object.
<complexType name="AbstractAIXMPropertyType" abstract="true">
<attribute name="nilReason" type="gml:NilReasonEnumeration"/>
</complexType>
• The nilReason is now defined :
– In Datatypes.xsd for simple properties
– In AIXM_AbstractGML_ObjectTypes.xsd for
complex properties
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
22
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
23
Usage & Properties with Schedule
• In AIXM 5.0, the concept of “usage” was not
consistent
– Should be how a feature can be used, not its status
– Mixed status, flight restrictions and complex
schedules without consistency across features
• Simplify with PropertiesWithSchedule
– Replace Timesheet with PropertiesWithSchedule
– Represents status at different times
• No longer a separate feature
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
24
Example of PropertiesWithSchedule
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
25
Future Plans
• The next major update to AIXM (either 5.2 or
6.0) will come in 2012
• Minor updates in between, but they should
not include any conceptual changes
– Minimal impact to backward compatibility
• Developing a CM Plan
– Including formalization through ICAO, Eurocontrol
and the FAA
AIXM 5.1 Changes – AIXM Developer’s Seminar
January 2010
Federal Aviation
Administration
26