FAA 13A (Aviation)

Disponible avec une licence Aviation Airports.

Disponible avec une licence Aviation Charting.

Synthèse

Creates obstruction identification surfaces (OIS) based on the FAA Advisory Circular 150/5300-13A specification. These approach and departure surfaces are designed to protect the use of the runway in both visual and instrument meteorological conditions near the airport and are used to support planning and design activities. The type, function, and dimension of a surface differ by its runway classification. This tool creates surfaces as a polygon or multipatch features.

Héritage :

This tool is deprecated. This functionality is replaced by the FAA 13A Surfaces tool.

Utilisation

  • Le paramètre Input Runway Features (Entités de piste en entrée) doit prendre en charge les valeurs z.

  • 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 specified for the Target OIS Features parameter, it must have a vertical spatial reference.

  • To create a .json file for the Custom JSON File parameter, use the CustomizeOIS.exe utility included in the Aviation Airports Product Data download available from My Esri.

  • OIS tools are flexible and accept a variety of input and output feature class types. For more information, see the OIS Input and Output schemas.

  • A departure runway classification can include a clearway surface. Clearway length, slope, width, and negative offset distance must be provided in the Custom JSON File parameter.

  • The Input Airport Control Point Feature parameter can be used to supply x-, y-, and z-geometry for displaced threshold features. If displaced thresholds are included, surfaces will be constructed based on their x-, y-, and z-geometry instead of their corresponding runway feature endpoint.

  • The Length of High Runway End parameter refers to runway direction identifiers 19 through 36. The Length of Low Runway End parameter refers to runway direction identifiers 01 through 18.

Paramètres

ÉtiquetteExplicationType de données
Input Runway Features

The input runway dataset. The feature class must be z-enabled and contain polylines.

Feature Layer
Target OIS Features

The target feature class that will contain the generated OIS.

Feature Layer
Runway Classification

Specifies the classification of the runway.

  • Small airplanes approach speeds less than 50 knotsApproach end of runways are expected to serve small airplanes with approach speeds less than 50 knots. This applies to visual runways only, day or night.
  • Small airplanes approach speeds 50 knots or moreApproach end of runways are expected to serve small airplanes with approach speeds of 50 knots or more. This applies to visual runways only, day or night.
  • Large airplanes for visual runways only, day or nightApproach end of runway are expected to serve large airplanes. This applies to visual runways only, day or night.
  • Instrument approach visibility greater than or equal to 3/4 mile Approach end of runways are expected to accommodate instrument approaches having visibility greater than or equal to 3/4 statute mile.
  • Instrument approach less than 3/4 mile visibilityApproach end of runways are expected to accommodate instrument approaches having visibility minimums less than 3/4 statute mile.
  • Vertical guidance approachApproach end of runways are expected to accommodate instrument approaches with vertical guidance.
  • Departure Departure runway ends are used for any instrument operations.
String
Length of High Runway End Clearway
(Facultatif)
Héritage :

This parameter is no longer supported. It is still included in the tool's syntax for compatibility in scripts and models but is hidden on the tool dialog box.

Double
Length of Low Runway End Clearway
(Facultatif)
Héritage :

This parameter is no longer supported. It is still included in the tool's syntax for compatibility in scripts and models but is hidden on the tool dialog box.

Double
Custom JSON File
(Facultatif)

The import configuration, in JSON format, that will be used to create the custom OIS.

File
Generate Clearway
(Facultatif)

Specifies whether a clearway surface will be generated for departure runways.

  • Checked—A clearway surface will be generated.
  • Unchecked—A clearway surface will not be generated. This is the default.
Boolean
Input Airport Control Point Feature
(Facultatif)

Supplies x-, y-, and z-geometry for displaced threshold features. If displaced thresholds are included, surfaces will be constructed based on their x-, y-, and z-geometry instead of their corresponding runway feature endpoint.

Feature Layer

Sortie obtenue

ÉtiquetteExplicationType de données
Output OIS Features

The updated feature class containing the generated OIS.

Feature Layer

arcpy.aviation.FAA13A(in_features, target, runway_type, {highend_clear_way_length}, {lowend_clear_way_length}, {custom_json_file}, {generate_clearway_surface}, {airport_control_point_feature_class})
NomExplicationType de données
in_features

The input runway dataset. The feature class must be z-enabled and contain polylines.

Feature Layer
target

The target feature class that will contain the generated OIS.

Feature Layer
runway_type

Specifies the classification of the runway.

  • SMALL_AIRPLANE_APPROACH_SPEEDS_LT_50Approach end of runways are expected to serve small airplanes with approach speeds less than 50 knots. This applies to visual runways only, day or night.
  • SMALL_AIRPLANE_APPROACH_SPEEDS_GT_50Approach end of runways are expected to serve small airplanes with approach speeds of 50 knots or more. This applies to visual runways only, day or night.
  • LARGE_AIRPLANE_VISUAL_RUNWAY_DAY_NIGHTApproach end of runway are expected to serve large airplanes. This applies to visual runways only, day or night.
  • INSTRUMENT_GT_EQ_3/4_MILE Approach end of runways are expected to accommodate instrument approaches having visibility greater than or equal to 3/4 statute mile.
  • INSTRUMENT_LT_3/4_MILE_VISIBILITYApproach end of runways are expected to accommodate instrument approaches having visibility minimums less than 3/4 statute mile.
  • VERTICAL_GUIDANCE_APPROACHApproach end of runways are expected to accommodate instrument approaches with vertical guidance.
  • DEPARTURE Departure runway ends are used for any instrument operations.
String
highend_clear_way_length
(Facultatif)
Héritage :

This parameter is no longer supported. It is still included in the tool's syntax for compatibility in scripts and models but is hidden on the tool dialog box.

Double
lowend_clear_way_length
(Facultatif)
Héritage :

This parameter is no longer supported. It is still included in the tool's syntax for compatibility in scripts and models but is hidden on the tool dialog box.

Double
custom_json_file
(Facultatif)

The import configuration, in JSON format, that will be used to create the custom OIS.

File
generate_clearway_surface
(Facultatif)

Specifies whether a clearway surface will be generated for departure runways.

  • GENERATE_CLEARWAY_SURFACEA clearway surface will be generated.
  • NOT_GENERATE_CLEARWAY_SURFACE A clearway surface will not be generated. This is the default.
Boolean
airport_control_point_feature_class
(Facultatif)

Supplies x-, y-, and z-geometry for displaced threshold features. If displaced thresholds are included, surfaces will be constructed based on their x-, y-, and z-geometry instead of their corresponding runway feature endpoint.

Feature Layer

Sortie obtenue

NomExplicationType de données
derived_outfeatureclass

The updated feature class containing the generated OIS.

Feature Layer

Exemple de code

FAA13A example 1 (stand-alone script)

The following Python window script demonstrates how to use the FAA13A function.

import arcpy

# set gp environment
arcpy.CheckOutExtension("Aeronautical")

# Input Runway Feature Class
inFeatures = r"C:\data\ois.gdb\RunwayCenterline"

# Feature class that will contain the OIS surface
outFeatures = r"C:\data\ois.gdb\ObstructionIdSurface"

# Airport variables
runway = "SMALL_AIRPLANES_APPROACH_SPEEDS_LT_50"

# Generate FAA13A OIS
arcpy.FAA13A_aviation(inFeatures, outFeatures, runway)

arcpy.CheckInExtension("Aeronautical")
FAA13A example 2 (stand-alone script)

The following Python window script demonstrates how to use the FAA13A function with the custom_json_file parameter.

import arcpy

# set gp environment
arcpy.CheckOutExtension("Aeronautical")

# Input Runway Feature Class
inFeatures = r"C:\data\ois.gdb\RunwayCenterline"

# Feature class that will contain the OIS surface
outFeatures= r"C:\data\ois.gdb\ObstructionIdSurface"

# Airport variables
runway = "DEPARTURE"
hiEndClearWay = 0  # parameter is disregarded for FAA13A, set Clearway dimension in Custom JSON
lowEndClearWay = 0 # parameter is disregarded for FAA13A, set Clearway dimension in Custom JSON
customJSON = r"C:\data\customOIS.json"
Clearway_Surface = “GENERATE_CLEARWAY_SURFACE”

# Generate FAA13A OIS
arcpy.FAA13A_aviation(inFeatures, outFeatures, runway, hiEndClearWay,
                      lowEndClearWay, customJSON, Clearway_Surface)

arcpy.CheckInExtension("Aeronautical")

Informations de licence

  • Basic: Non
  • Standard: Nécessite Airports or ArcGIS Aviation Charting
  • Advanced: Nécessite Airports or ArcGIS Aviation Charting