[Ready to review] Obstacle operator/owner

Introduction

Table A6-2 Obstacle attributes of PANS-AIM has ‘Data originator identifier’ as a mandatory attribute for Obstacle, whereas in PANS-AIM Data Catalogue Table 1-6 Obstacle data, this attribute is missing and a new property ‘Obstacle | Operator / Owner’ appears. This property requires  the name and contact information of obstacle operator or owner.

Description of obstacle DATA ORIGINATOR IDENTIFIER (source EUROCONTROL TOD Manual)

• An indication of who the originating authority for obstacle data is. The data originator is considered to be the entity which performs measurements and represents it in the form of set of obstacles. Typically, this metadata should be collected for each obstacle represented.
  The originator identifier is usually maintained by the entity storing obstacle data within the State but is not provided to the next intended user in the obstacle data set.

Description of obstacle DATA ORIGINATION as potential functions/responsibility in national TOD policy (source EUROCONTROL TOD Manual)

The organisation responsible for or owning objects in accordance with the national obstacle permission process and organisation responsible for the survey of obstacles and provision of quality-assured data

• The data origination entity in the data process is considered to be the organisation responsible for the obstacle in the national obstacle permission process. Different organisations may be responsible for obstacle data, for example:
  • Area 1: obstacle owner;
  • Area 2: aerodrome operator, obstacle owner, ANSP;
  • Area 3, 4: aerodrome operator.
• The actual origination of the obstacle is done by surveying the obstacles and providing quality-assured data to the responsible organisation.

Data originator and obstacle owner are not necessarily the same entity e.g. data originator could be an entity providing an obstacle survey, but not being an obstacle owner. In any case, this information is useful for States in their obstacle management process and the data catalogue is a description of the data that can be collected by an AIS and not included the data products. 

The analysis of these requirements in the Basic properties for obstacles section indicate that the data originator identifier of each individual obstacle is not published as part of the Obstacle data sets. In most cases the information about the obstacle operator/owner and data originators is used internally at the entity playing the role of obstacle registrar in the State and will not be part of the obstacle data set.

However, in some particular cases (e.g. mobile or temporary obstacle) it might be necessary to provide the information about the obstacle owner within the data set, in order to enable the airspace users to contact the owner and find out if the obstacle is present at a certain moment in time. For that purpose, the contact details of the obstacle owner can be mapped to a Note associated with the VerticalStructure  VerticalStructure.annotation.Note

Example : Operator/Owner

The example below shows the encoding of the operator/owner.

		<aixm:VerticalStructure gml:id="uuid.5f68d835-828c-4ccd-91b7-791058d9dd4d">
			<gml:identifier codeSpace="urn:uuid:">5f68d835-828c-4ccd-91b7-791058d9dd4d</gml:identifier>
			...
					<aixm:type>ANTENNA</aixm:type>
					...
					<!-- Operator/Owner not required by PANS-AIM but contained in Appendix 1 "Aeronautical Data Catalogue".
					In AIXM 5.1(1) it may only be coded as Note for an Obsatcle data set.
					Note: For data provided by the data originator this information will be rather coded as metadata.-->
					<aixm:annotation>
						<aixm:Note gml:id="n0001">
							<aixm:purpose>REMARK</aixm:purpose>
							<aixm:translatedNote>
								<aixm:LinguisticNote gml:id="ln0001">
									<aixm:note>Obstacle Owner: DONLON TELECOM, Donlon Street 100, 2020 DOLNLON, Phone: +00123456789, email: info@donlontele.com</aixm:note>
								</aixm:LinguisticNote>
							</aixm:translatedNote>
						</aixm:Note>
					</aixm:annotation>
					...