Summary
Creates obstruction identification surfaces based on the FAA 18B specification. These surfaces describe airspaces that should be free of obstructions. Surfaces are used to support planning and design activities. 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 must be Z enabled.
The selection you make in Runway Classification will automatically populate most of the surface parameters.
When Runway Classification is set to Vertical Guidance, the output transitional surface will be split into four sections by a line perpendicular to the runway centerline. This does not apply when Output Features is set to TIN.
When Runway Classification is set to Vertical Guidance, the output conical and horizontal surfaces will be split into sections by a meridian and a parallel. The meridian intersects the Airport Elevation Point and the center point of the runway centerline. The parallel runs perpendicular to the meridian through the center point of the runway centerline. This does not apply when Output Feature Class is set to TIN.
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.
When this tool is run as a stand-alone Python script, horizontal and conical surfaces are not split. This is because the runway centerline cannot be analyzed to find the airport control points, which are used to split the surfaces.
Syntax
FAA18B_aviationois (in_features, runway_type, highend_clear_way_length, lowend_clear_way_length, airport_elevation, include_merged_surface, out_features)
| Parameter | Explanation | Data 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 in_features.
| String |
highend_clear_way_length | The length of the area at the high end of the runway, in feet. 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 feet. 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 feet. 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 |
include_merged_surface | Indicates whether merged horizontal and conical surfaces are included in the OIS, in addition to the regular surfaces.
| Boolean |
out_features | The output feature class or TIN that will contain the generated obstacle identification surfaces. | Feature Layer; Folder |
Code Sample
FAA18B example (stand-alone Python script)
The following Python window script demonstrates how to use the FAA18B tool.
import arcpy
# set gp environment
arcpy.CheckOutExtension("Aeronautical")
# Input Runway Feature Class
inFeatures = "C:\data\ois.gdb\RunwayCenterline"
# Feature class that will contain the OIS surface
outFeatures="C:\data\ois.gdb\ObstructionIdSurface"
# Airport variables
runway = "VERTICAL_GUIDANCE"
airportElev = 100
# Generate FAA1B OIS
arcpy.FAA18B_aviationois(inFeatures,runway,10,0,airportElev,
"INCLUDE_MERGED_SURFACE",outFeatures)
Environments
Licensing Information
- ArcGIS for Desktop Basic: No
- ArcGIS for Desktop Standard: Requires Airports or Aviation Charting
- ArcGIS for Desktop Advanced: Requires Airports or Aviation Charting