Skip To Content

ICAO Annex 14

Summary

Creates obstruction identification surfaces based on the ICAO Annex 14 specification. These surfaces define areas of airspace around an aerodrome. Each area defines the limits to which an obstruction can project into an airspace. The type, function, and dimension of a surface differ by runway classification. This tool creates surfaces as polygon or multipatch features.

Usage

  • The Input Runway Features must be Z enabled.

  • This tool creates the OIS in an existing polygon or multipatch feature class. It can also be generated in an existing polygon shapefile. If a feature class is selected for Target, it must have a vertical spatial reference.

Syntax

ICAOAnnex14_aviation (in_features, target, runway_type, {highend_clear_way_length}, {lowend_clear_way_length}, {airport_elevation}, {runway_direction}, {include_merged_surface})
ParameterExplanationData Type
in_features

The input runway dataset. The feature class must be Z enabled and contain points, polylines, or polygons.

Feature Layer
target

The output feature class that will contain the generated obstruction identification surfaces.

Feature Layer
runway_type

The runway classification of the in_features.

  • NON_INSTRUMENT_CODE_NUMBER_1A runway intended for the operation of aircraft using visual approach procedures. Runway strip length is 30 meters.
  • NON_INSTRUMENT_CODE_NUMBER_2 A runway with a 60-meter strip length and 40-meter strip width that is intended for the operation of aircraft using visual approach procedures.
  • NON_INSTRUMENT_CODE_NUMBER_3 A runway with a 60-meter strip length and 75-meter strip width that is intended for the operation of aircraft using visual approach procedures.
  • NON_INSTRUMENT_CODE_NUMBER_4 A runway with a 60-meter strip length and 75-meter strip width that is intended for the operation of aircraft using visual approach procedures.
  • NON_PRECISION_APPROACH_CODE_NUMBER_1An instrument runway served by visual aids and a nonvisual aid providing at least directional guidance adequate for a straight-in approach. This runway type has a 60-meter strip length and a 75-meter strip width on either side of the runway centre line.
  • NON_PRECISION_APPROACH_CODE_NUMBER_2An instrument runway served by visual aids and a nonvisual aid providing at least directional guidance adequate for a straight-in approach. This runway type has a 60-meter strip length and a 75-meter strip width on either side of the runway centre line.
  • NON_PRECISION_APPROACH_CODE_NUMBER_3An instrument runway served by visual aids and a nonvisual aid providing at least directional guidance adequate for a straight-in approach. This runway type has a 60-meter strip length and a 150-meter strip width on either side of the runway centre line.
  • NON_PRECISION_APPROACH_CODE_NUMBER_4An instrument runway served by visual aids and a nonvisual aid providing at least directional guidance adequate for a straight-in approach. This runway type has a 60-meter strip length and a 150-meter strip width on either side of the runway centre line.
  • PRECISION_APPROACH_CATEGORY_I_CODE_NUMBER_1An instrument runway served by an Instrument Landing System (ILS) or a Microwave Landing System (MLS) and visual aids intended for operations with a decision height not lower than 60 meters (200 ft.) and either a visibility not less than 800 meters or a runway visual range not less than 550 meters. This runway type has a 60-meter strip length and a 75-meter strip width on either side of the runway centre line.
  • PRECISION_APPROACH_CATEGORY_I_CODE_NUMBER_2An instrument runway served by ILS and/or MLS and visual aids intended for operations with a decision height not lower than 60 meters (200 ft.) and either a visibility not less than 800 meters or a runway visual range not less than 550 meters. This runway type has a 60-meter strip length and a 75-meter strip width on either side of the runway centre line.
  • PRECISION_APPROACH_CATEGORY_I_CODE_NUMBER_3_4An instrument runway served by ILS and/or MLS and visual aids intended for operations with a decision height not lower than 60 meters (200 ft.) and either a visibility not less than 800 meters or a runway visual range not less than 550 meters. This runway type has a 60-meter strip length and a 150-meter strip width on either side of the runway centre line.
  • PRECISION_APPROACH_CATEGORY_II_III_CODE NUMBER_3_4An instrument runway served by ILS and/or MLS and visual aids intended for operations with a decision height lower than 60 meters (200 ft.) but not lower than 30 meters (100 ft.) and a runway visual range not less than 350 meters. This runway type has a 60-meter strip length and a 150-meter strip width on either side of the runway centre line.
String
highend_clear_way_length
(Optional)

The length, in meters, of the area at the high end of the runway. An aircraft can make a portion of its initial climb over this area.

Double
lowend_clear_way_length
(Optional)

The length, in meters, of the area at the low end of the runway. An aircraft can make a portion of its initial climb over this area.

Double
airport_elevation
(Optional)

The highest point, in meters, on any runway in an airport. The units for elevation are based on the specification. The tool will automatically populate this value from a z-value in your aeronautical database if you are using the AIS or Airports data model. Airport elevation is stored in the z-value of the ADHP point feature class in the AIS data model. In the Airports data model, elevation is stored in the z-value of the Airport Control Point feature class for records with the Point_Type field populated with AIRPORT_ELEVATION.

Double
runway_direction
(Optional)

The direction of the in_features.

  • HIGH_END_TO_LOW_ENDFrom runway high end to low end
  • LOW_END_TO_HIGH_ENDFrom runway low end to high end
String
include_merged_surface
(Optional)

Indicates whether merged surfaces are generated.

  • INCLUDE_MERGED_SURFACEAll the surfaces are generated for the merged surfaces, as well as merged conical and horizontal surfaces. This is the default.
  • NOT_INCLUDE_MERGED_SURFACESurfaces are not generated for the merged surfaces.
Boolean

Code sample

ICAOAnnex14 example (stand-alone script)

The following Python window script demonstrates how to use the ICAOAnnex14 tool.

import arcpy
# set gp environment
arcpy.env.workspace="c:/data/ois.gdb"
arcpy.CheckOutExtension("Aeronautical")
# Input Runway Feature Class
inFeatures = "RunwayCenterline"
# feature class that will contain the OIS surface
outFeatureClass="ObstructionIdSurface"
# runway variables
runway = "NON_INSTRUMENT_CODE_NUMBER_1"
runwayDir = "HIGH_END_TO_LOW_END"
#_Exec_ICAOAnnex14
arcpy.ICAOAnnex14_aviation(inFeatures,_outFeatureClass_,runway,10,0,100,runwayDir, "INCLUDE_MERGED_SURFACE")
arcpy.CheckInExtension("Aeronautical")

Environments

Licensing information

  • ArcGIS Desktop Basic: No
  • ArcGIS Desktop Standard: Yes
  • ArcGIS Desktop Advanced: Yes