ArcMap

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 may 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, or triangulated irregular networks (TINs).

Usage

  • The Input Runway Features parameter must be z-enabled.

  • The selection you make in Runway Classification will automatically populate most of the surface parameters.

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

Syntax

arcpy.aviationois.ICAOAnnex14(in_features, runway_type, highend_clear_way_length, lowend_clear_way_length, airport_elevation, {runway_direction}, include_merged_surface, out_features)
ParameterExplanationData Type
in_features

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

Feature Layer
runway_type

The runway classification of the in_features.

  • NON_INSTRUMENT_CODE_NUMBER_1 —A 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_1 —An 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_2 —An 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_3 —An 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_4 —An 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_1 —An 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_2 —An 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_4 —An 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_4 —An 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

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

Double
lowend_clear_way_length

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

Double
airport_elevation

The highest point on any runway in an airport, in meters. 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)

Specifies at which end of the runway the approach surface will be created.

  • HIGH_END_TO_LOW_END —From runway high end to low end. The approach surface will be created at the high end of the runway.
  • LOW_END_TO_HIGH_END —From runway low end to high end. The approach surface will be created at the low end of the runway.
String
include_merged_surface

Indicates whether merged horizontal and conical surfaces are included in the OIS, in addition to the regular surfaces.

  • INCLUDE_MERGED_SURFACE —Include merged surfaces in the OIS output. This is the default.
  • NOT_INCLUDE_MERGED_SURFACE —Do not include merged surfaces in the OIS output.
Boolean
out_features

The output feature class or TIN that will contain the generated obstacle identification surfaces.

Feature Layer; Folder

Code sample

ICAOAnnex14 example (stand-alone Python 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_aviationois(inFeatures,runway,10,0,100,runwayDir,
                           "INCLUDE_MERGED_SURFACE",outFeatureClass)
arcpy.CheckInExtension("Aeronautical")

Environments

Licensing information

  • Basic: No
  • Standard: Requires Airports or Aviation Charting
  • Advanced: Requires Airports or Aviation Charting

Related topics