Upload
jordan-daniels
View
220
Download
3
Embed Size (px)
Citation preview
Presented to: AIXM Developer’s Seminar
By: Navin Vembar
Date: January 14, 2010
Federal AviationAdministrationChanges in AIXM
5.1 from AIXM 5.0
2Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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
3Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
New Features or Types
• AeronauticalGroundLight – Aerodrome Beacons, etc.
• HotSpot• RulesProcedures• CodeMarkingConditionType
4Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
Removed Features, classes, types
• AirspaceAssociation removed• TerrainPoint removed
5Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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
6Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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
7Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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
8Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
Updates to Relationships, cont’d
• New association between SafeAltitudeArea and AirportHeliport
• New association between MissedApproachLeg and ApproachCondition
9Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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
10Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
Changes to XSD
11Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
CodeAircraftEngineBaseType
JET : stringPISTON : stringTURBOPROP : stringALL : stringOTHER : string
<<codelist>>
string
<<XSDfacet>> whiteSpace : null = preserve
(from XMLSchemaDatatypes)
<<XSDsimpleType>>
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>
12Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
AIXM 5.1 Mapping Rules - Datatypes• Mapping
<<enumeration>>
<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>
string
<<XSDfacet>> whiteSpace : null = preserve
(from XMLSchemaDatatypes)
<<XSDsimpleType>>
CodeAircraftEngineBaseType
JET : stringPISTON : stringTURBOPROP : stringALL : stringOTHER : string
(from AIXM Data Types)
<<enumeration>>
13Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
AIXM 5.1 Mapping Rules - Datatypes• Mapping <<codelist>>
<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>
string
<<XSDfacet>> whiteSpace : null = preserve
(from XMLSchemaDatatypes)
<<XSDsimpleType>>
CodeApproachLightingBaseType
ALSAF : stringMALS : stringMALSR : stringSALS : stringSSALS : stringSSALR : stringLDIN : stringODALS : stringAFOVRN : stringMILOVRN : stringCALVERT : string
(from AIXM Data Types)
<<codelist>>
14Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
AIXM 5.1 Mapping Rules - Datatypes
• Mapping <<datatype>> - default case
<simpleType name="DateBaseType"> <restriction base="xsd:date"> </restriction></simpleType>
DateBaseType(from AIXM Data Types)
<<datatype>>
date
<<XSDfacet>> whiteSpace : string = collapse
(from XMLSchemaDatatypes)
<<XSDsimpleType>>
15Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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.
DateBaseType(from AIXM Data Types)
<<datatype>>
date
<<XSDfacet>> whiteSpace : string = collapse
(from XMLSchemaDatatypes)
<<XSDsimpleType>>
DateType
nilReason : CodeNilReasonType
(from AIXM Data Types)
<<datatype>>
string
<<XSDfacet>> whiteSpace : null = preserve
(from XMLSchemaDatatypes)
<<XSDsimpleType>>
CodeApproachLightingBaseType
ALSAF : stringMALS : stringMALSR : stringSALS : stringSSALS : stringSSALR : stringLDIN : stringODALS : stringAFOVRN : stringMILOVRN : stringCALVERT : string
(from AIXM Data Types)
<<codelist>>
CodeApproachLightingType
nilReason : CodeNilReasonType
(from AIXM Data Types)
<<datatype>>
string
<<XSDfacet>> whiteSpace : null = preserve
(from XMLSchemaDatatypes)
<<XSDsimpleType>>
CodeAircraftEngineBaseType
JET : stringPISTON : stringTURBOPROP : stringALL : stringOTHER : string
(from AIXM Data Types)
<<enumeration>>
CodeAircraftEngineType
nilReason : CodeNilReasonType
(from AIXM Data Types)
<<datatype>>
16Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
AIXM 5.1 Mapping Rules - NilReason
string
<<XSDfacet>> whiteSpace : null = preserve
(from XMLSchemaDatatypes)
<<XSDsimpleType>>
CodeAircraftEngineType
nilReason : NilReasonType
(from AIXM Data Types)
<<datatype>>
CodeAircraftEngineBaseType
JET : stringPISTON : stringTURBOPROP : stringALL : stringOTHER : string
(from AIXM Data Types)
<<enumeration>>
• 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>
17Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
AIXM 5.1 Mapping Rules - UOM
• Mapping Units of Measurement
<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>
<simpleType name=“ValDepthBaseType"> <restriction base="xsd:decimal"> </restriction></simpleType>
ValDepthType
uom : UomDepthTypenilReason : CodeNilReasonType
(from AIXM Data Types)
<<datatype>>
ValDepthBaseType(from AIXM Data Types)
<<datatype>>
decimal(from XMLSchemaDatatypes)
<<XSDsimpleType>>
18Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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
19Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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
20Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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>
21Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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 information, if hidden inside a non-GML object such as VerticalStructurePart.
<complexType name="CityType"> <complexContent>
<extension base="aixm:AbstractAIXMObjectType"> <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>
22Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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
23Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
24Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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
25Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
Example of PropertiesWithSchedule
26Federal AviationAdministration
AIXM 5.1 Changes – AIXM Developer’s SeminarJanuary 2010
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