Obstacle identification

Introduction

In AIXM 5.1(.1), two attributes can be used to provide obstacle "identification" data:

VerticalStructure.name - limited to 60 characters (upper case, alphanumeric and some special characters);
VerticalStructurePart.designator - limited to 16 characters (upper case, alphanumeric and some special characters).

AIXM 5.2 Change

A Change Proposal approved by the AIXM CCB for the next version will support the coding of additional obstacle identification properties, taking into consideration current practices for obstacle data in AIS publications. It will offer a significantly extended range of possibilities for obstacle identification:

name and designator both in the VerticalStructure and in the VerticalStructurePart, both with higher number of characters
an additional "geographicalLocation" attribute.

The coding guidelines for obstacle identification in AIXM 5.1(.1) are aligned with the backward mapping rules contained in that change proposal. See [replaced] [AIXM-399] Obstacle name, location and designator.

Single part obstacles

The obstacles must be collected and published with one unique identifier, generally coming from a national obstacle registry. Some examples, extracted from real AIP obstacle tables, are shown to the right. In AIXM 5.1, such identifier shall be coded using the VerticalStructure.name.

Multi-part obstacles

For obstacles that are coded with several parts, a separate coded designator can be coded in each VerticalStructurePart. The overall name of the obstacle should be coded using the VerticalStructure.name property.

Additional obstacle identification data

For some obstacles, a named geographical location of the obstacle is provided, such as the "Municipality" in the table copied to the right. With the current AIXM 5.1(.1) data model, this can be coded as annotation:

Add an annotation.Note associated with the VerticalStructure class having:
- purpose='REMARK'
- translatedNote.LinguisticNote.note="geographicalLocation: <geographicalLocation>"

Coding Examples

Single Part Obstacle

The Obstacle identifier/designation is coded using the VerticalStructure.name.

Example 1: OBS-0001

		<aixm:VerticalStructure gml:id="uuid.5f68d835-828c-4ccd-91b7-791058d9dd4d">
			<gml:identifier codeSpace="urn:uuid:">5f68d835-828c-4ccd-91b7-791058d9dd4d</gml:identifier>
			...
					<!-- To be used to code PANS-AIM Table A-6.2 "Obstacle Identifier"; ENR 5.4/AD 2.10 "obstacle identification or designation".-->
					<aixm:name>OBS-0001</aixm:name>
					<aixm:part>
						<aixm:VerticalStructurePart gml:id="V-af4ee6d6">
							...
							<!-- part designator is not required by PANS-AIM but may be used for multiple part obstacles. 
							nil & nilReason has not to be coded but is shown in the example for explanatory purposes. -->
							<aixm:designator xsi:nil="true" nilReason="inapplicable"/>
							...

Example 2: RODSAND II

		<aixm:VerticalStructure gml:id="uuid.47db48e9-d46a-4100-a266-25a3968b6a98">
			<gml:identifier codeSpace="urn:uuid:">47db48e9-d46a-4100-a266-25a3968b6a98</gml:identifier>
					...
					<aixm:name>RODSAND II</aixm:name>
					...
					<aixm:part>
						<aixm:VerticalStructurePart gml:id="vsp0002-1">
							...
							<aixm:designator xsi:nil="true" nilReason="inapplicable"/>
							...

Multi Part Obstacle

In case of a multipart obstacle in addition to the VerticalStructure.name each part has its own VerticalStructurePart.designator.

Example 3: Windpark

<aixm:VerticalStructure gml:id="uuid.6c7fac45-c24f-4e36-b196-687458d99070 ">
			<gml:identifier codeSpace="urn:uuid:">6c7fac45-c24f-4e36-b196-687458d99070</gml:identifier>
			...
					<aixm:name>WINDPARK DONLON IV</aixm:name>
					...
					<!-- Windturbine 1 of the Windpark-->
					<aixm:part>
						<aixm:VerticalStructurePart gml:id="vsp0003-1">
							....
							<aixm:designator>OBS-0003-1</aixm:designator>
							...
					</aixm:part>
					<!-- Windturbine 2 of the Windpark-->
					<aixm:part>
						<aixm:VerticalStructurePart gml:id="vsp0003-2">
							...
							<aixm:designator>OBS-0003-2</aixm:designator>
							...
					</aixm:part>
					...

The following coding examples can be found in the Obstacle Data Set - Specimen (DONLON):

No.	Description	XPath Expression
VST-EX-01		TBD
VST-EX-01		TBD