FAA 13 Runway Protection Surfaces (Aviation)

Disponible avec une licence Aviation Airports.

Disponible avec une licence Aviation Charting.

Synthèse

Generates runway protection surfaces based on the FAA Advisory Circular AC 150/5300-13B specification.

Safe and efficient landing and takeoff operations at an airport require that certain areas on and near the airport are clear of objects or restricted to objects with a certain function, composition, or height. These clearing standards and criteria are established to create a safer environment for the aircraft operating on or near the airport.

Utilisation

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

• The Target OIS Features parameter value must be z-enabled.

• This tool generates runway protection surfaces in an existing polygon or multipatch feature class. If a feature class is used for the Target OIS Features parameter value, it must have a vertical spatial reference. It should have Name and Description text attributes, which will be populated in the output features. Suitable Target OIS Features parameter values can be the following features classes from the Airports 18B schema (Airports18B_NAD83_GX.xml): Airspace\ObstructionIdSurface, ObstructionIdSurface_MP, or RunwayProtectArea.

• This tool generates runway protection surfaces based on design matrices defined by the FAA. A design matrix consists of an approach category and approach design group. Use the Approach Category and Approach Design Group parameters to set the design matrix for the surfaces.

  Some design matrices only apply to aircrafts under 12,500 pounds. Use the Aircraft Type parameter to specify the design matrix for an aircraft.

• If the Runway End Features parameter is specified, the corresponding field values in this layer will override the values specified in the Approach Category, Aircraft Design Group, and Approach Guidance parameters. This is useful for providing specific input per runway end. The Airfield\RunwayEnd feature class is suitable input for this parameter with the Approach Category, Approach Guidance, and Design Group fields populated.

• High end of the runway refers to runway direction identifiers 19 through 36. Low end of the runway refers to runway direction identifiers 01 through 18.

• The Airport Elevation parameter has a default value of 0. If you use an elevation value greater than 0, it takes precedence and overrides any existing airport elevation value read from the Input Airport Control Point Feature 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.

• To create a .json file for the Custom JSON File parameter value, use the CustomizeOIS.exe file that is part of the ArcGIS Aviation data package available from My Esri.

Paramètres

Boîte de dialogue

Étiquette	Explication	Type 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
Surfaces to Generate	Specifies the type of surface that will be generated. Runway Safety Area—A runway safety area (RSA) will be generated. Runway Object Free Area—A runway object free area (ROFA) will be generated. Runway Obstacle Free Zone—A runway obstacle free zone (ROFZ) will be generated. Precision Obstacle Free Zone—A precision obstacle free zone (POFZ) will be generated. Approach Runway Protection Zone—An approach runway protection zone (RPZ) will be generated. Departure Runway Protection Zone—A departure runway protection zone (RPZ) will be generated.	String
Visibility Minimums (Facultatif)	Specifies the visibility minimums that will be used for the runways. Visual—Visual flight rules will be used. This is the default. Not lower than 1 mile—Visibility minimums will not be lower than 1 mile. Not lower than 3/4 mile—Visibility minimums will not be lower that 3/4 mile. Lower than 3/4 mile—Visibility minimums will be lower than 3/4 mile.	String
Approach Category (Facultatif)	Specifies the approach category that will be used to generate surfaces. A—The approach category A will be used. This is the default. B—The approach category B will be used. C—The approach category C will be used. D—The approach category D will be used. E—The approach category E will be used.	String
Aircraft Design Group (Facultatif)	Specifies the approach design group that will be used to generate surfaces. I—The approach design group I will be used. This is the default. II—The approach design group II will be used. III—The approach design group III will be used. IV—The approach design group IV will be used. V—The approach design group V will be used. VI—The approach design group VI will be used.	String
Aircraft Type (Facultatif)	Specifies whether surfaces will be generated with the small aircraft design matrix. Remarque : This parameter only applies when the Approach Category parameter is set to A or B. Small aircraft—Surfaces will be generated with the small aircraft design matrix. Not small aircraft—Surfaces will not be generated with the small aircraft design matrix. This is the default.	String
Approach Guidance (Facultatif)	Specifies the type of approach guidance that will be used at the end of the runway. Precision Category I—Precision Category I approach operations will be used for the runway. This is the default. Precision Category II—Precision Category II approach operations will be used for the runway. Precision Category III A—Precision Category III A approach operations will be used for the runway. Precision Category III B—Precision Category III B approach operations will be used for the runway. Precision Category III C—Precision Category III C approach operations will be used for the runway. Precision Category III D—Precision Category III D approach operations will be used for the runway. Non-vertical—Nonvertical approach operations (nonprecision approach category) will be used for the runway. Vertical—Vertically guided approach operations will be used for the runway. Visual—Only visual approach operations will be used for the runway.	String
Runway Direction (Facultatif)	Specifies the end of the runway where the approach surface will be created. High end to low end—The approach surface will be created from the high end of the runway to the low end. If a displaced threshold point exists at the high end of the runway, that point will be honored when creating the OIS. Low end to high end—The approach surface will be created from the low end of the runway to the high end. If a displaced threshold point exists at the low end of the runway, that point will be honored when creating the OIS. Both ends—The approach surface will be created from both the low end and high end of the runway.	String
Airport Elevation (Facultatif)	The highest elevation on any of the runways of the airport. The value should be in the vertical coordinate system linear units of the target feature class. If no value is provided, the highest point from the Input Runway Features parameter value will be used.	Double
Input Airport Control Point Feature (Facultatif)	The point features containing an Airport Elevation parameter feature, displaced threshold features, or both. Values provided for the Airport Elevation parameter will take precedence over these point features.	Feature Layer
Runway End Features (Facultatif)	The input runway end point features associated with each runway. The corresponding field values in this layer will override the values specified in the Approach Category, Aircraft Design Group, and Approach Guidance parameters.	Feature Layer
Last Low End Approach Light (Facultatif)	The distance in feet of the Approach Lighting System (ALS) from the end of the low end of the runway. If no value is provided, it is assumed that there is no ALS at the low end of the runway.	Double
Last High End Approach Light (Facultatif)	The distance in feet of the Approach Lighting System (ALS) from the end of the high end of the runway. If no value is provided, it is assumed that there is no ALS at the high end of the runway.	Double
Custom JSON File (Facultatif)	The import configuration, in JSON format, that will create the custom OIS.	File

Sortie obtenue

Étiquette	Explication	Type de données
Output OIS Features	The output obstruction identification surface (OIS) features.	Feature Layer

Python

arcpy.aviation.FAA13RunwayProtectionSurfaces(in_features, target, surfaces_to_generate, {visibility_minimums}, {approach_category}, {approach_design_group}, {aircraft_type}, {approach_guidance}, {runway_direction}, {airport_elevation}, {airport_control_point_feature_class}, {runway_end_features}, {last_low_light}, {last_high_light}, {custom_json_file})

Nom	Explication	Type 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
surfaces_to_generate [surfaces_to_generate,...]	Specifies the type of surface that will be generated. RUNWAY_SAFETY_AREA—A runway safety area (RSA) will be generated. RUNWAY_OBJECT_FREE_AREA—A runway object free area (ROFA) will be generated. RUNWAY_OBSTACLE_FREE_ZONE—A runway obstacle free zone (ROFZ) will be generated. PRECISION_OBSTACLE_FREE_ZONE—A precision obstacle free zone (POFZ) will be generated. APPROACH_RUNWAY_PROTECTION_ZONE—An approach runway protection zone (RPZ) will be generated. DEPARTURE_RUNWAY_PROTECTION_ZONE—A departure runway protection zone (RPZ) will be generated.	String
visibility_minimums (Facultatif)	Specifies the visibility minimums that will be used for the runways. VISUAL—Visual flight rules will be used. This is the default. NOT_LOWER_THAN_1_MILE—Visibility minimums will not be lower than 1 mile. NOT_LOWER_THAN_3_4_MILE—Visibility minimums will not be lower that 3/4 mile. LOWER_THAN_3_4_MILE—Visibility minimums will be lower than 3/4 mile.	String
approach_category (Facultatif)	Specifies the approach category that will be used to generate surfaces. A—The approach category A will be used. This is the default. B—The approach category B will be used. C—The approach category C will be used. D—The approach category D will be used. E—The approach category E will be used.	String
approach_design_group (Facultatif)	Specifies the approach design group that will be used to generate surfaces. I—The approach design group I will be used. This is the default. II—The approach design group II will be used. III—The approach design group III will be used. IV—The approach design group IV will be used. V—The approach design group V will be used. VI—The approach design group VI will be used.	String
aircraft_type (Facultatif)	Specifies whether surfaces will be generated with the small aircraft design matrix. Remarque : This parameter only applies when the approach_category parameter is set to A or B. SMALL_AIRCRAFT—Surfaces will be generated with the small aircraft design matrix. NOT_SMALL_AIRCRAFT—Surfaces will not be generated with the small aircraft design matrix. This is the default.	String
approach_guidance (Facultatif)	Specifies the type of approach guidance that will be used at the end of the runway. PRECISION_CAT_I—Precision Category I approach operations will be used for the runway. This is the default. PRECISION_CAT_II—Precision Category II approach operations will be used for the runway. PRECISION_CAT_IIIA—Precision Category III A approach operations will be used for the runway. PRECISION_CAT_IIIB—Precision Category III B approach operations will be used for the runway. PRECISION_CAT_IIIC—Precision Category III C approach operations will be used for the runway. PRECISION_CAT_IIID—Precision Category III D approach operations will be used for the runway. NON_VERTICAL—Nonvertical approach operations (nonprecision approach category) will be used for the runway. VERTICAL—Vertically guided approach operations will be used for the runway. VISUAL—Only visual approach operations will be used for the runway.	String
runway_direction (Facultatif)	Specifies the end of the runway where the approach surface will be created. HIGH_END_TO_LOW_END—The approach surface will be created from the high end of the runway to the low end. If a displaced threshold point exists at the high end of the runway, that point will be honored when creating the OIS. LOW_END_TO_HIGH_END—The approach surface will be created from the low end of the runway to the high end. If a displaced threshold point exists at the low end of the runway, that point will be honored when creating the OIS. BOTH_END—The approach surface will be created from both the low end and high end of the runway.	String
airport_elevation (Facultatif)	The highest elevation on any of the runways of the airport. The value should be in the vertical coordinate system linear units of the target feature class. If no value is provided, the highest point from the in_features parameter value will be used.	Double
airport_control_point_feature_class (Facultatif)	The point features containing an airport_elevation parameter feature, displaced threshold features, or both. Values provided for the airport_elevation parameter will take precedence over these point features.	Feature Layer
runway_end_features (Facultatif)	The input runway end point features associated with each runway. The corresponding field values in this layer will override the values specified in the approach_category, approach_design_group, and approach_guidance parameters.	Feature Layer
last_low_light (Facultatif)	The distance in feet of the Approach Lighting System (ALS) from the end of the low end of the runway. If no value is provided, it is assumed that there is no ALS at the low end of the runway.	Double
last_high_light (Facultatif)	The distance in feet of the Approach Lighting System (ALS) from the end of the high end of the runway. If no value is provided, it is assumed that there is no ALS at the high end of the runway.	Double
custom_json_file (Facultatif)	The import configuration, in JSON format, that will create the custom OIS.	File

Sortie obtenue

Nom	Explication	Type de données
derived_outfeatureclass	The output obstruction identification surface (OIS) features.	Feature Layer

Exemple de code

FAA13RunwayProtectionSurfaces example (stand-alone script)

The following stand-alone script demonstrates how to use the FAA13RunwayProtectionSurfaces function.

# Name: FAA13RunwayProtectionSurfaces_sample.py

# Import system modules
import arcpy

# Check out extensions
arcpy.CheckOutExtension("Airports")

arcpy.env.workspace = "D:/data.gdb"

in_features = "RunwayCenterline"
target = "ObstructionIdSurface_MP"
surfaces_to_generate = ["RUNWAY_SAFETY_AREA", "RUNWAY_OBSTACLE_FREE_AREA"]
visibility_minimums = "VISUAL"
approach_category = "A"
approach_design_group = "I"
small_aircraft = "SMALL_AIRCRAFT"
approach_guidance = "VISUAL"
runway_direction = "BOTH_END"
airport_elevation = 97.2
airport_control_point_feature_class = "AirportControlPoint"
runway_end_features = "RunwayEndPoints"
last_low_light = 0.0
last_high_light = 0.0
custom_json_file = "D:/config.json"

# Call the FAA13RunwayProtectionSurfaces tool
arcpy.aviation.FAA13RunwayProtectionSurfaces(in_features, target, surfaces_to_generate,\
                                             visibility_minimums, approach_category,\
                                             approach_design_group, small_aircraft,\
                                             approach_guidance, runway_direction,\
                                             airport_elevation,\
                                             airport_control_point_feature_class,\
                                             runway_end_features, last_low_light,\
                                             last_high_light, custom_json_file)


# Check in extensions
arcpy.CheckInExtension("Airports")

Environnements

Cet outil n’utilise pas d’environnement de géotraitement.

Informations de licence

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