Skip To Content

Generate OIS Obstacle Data

Zusammenfassung

Generates a JSON string that is stored in the ObstacleJSON field on the Obstruction Identification Surface feature class that contains the data necessary to depict obstacles to safety of flight within the approach surfaces (in the form of points, lines, or polygons) in the Terrain and Obstacle Profile layout element.

For each runway feature, the tool finds each of the approach surfaces associated with that runway. With each approach surface, the tool uses the underlying elevation models and input obstacle to determine the highest elevations and heights of those obstacle features that intersect the approach surfaces extent. The resulting 3D points representing the highest-point cross section of each affected obstacle are created and stored in JSON format and saved in the corresponding approach OIS feature.

Verwendung

  • The Input Runway Features parameter must be z-aware and include one of the following fields:

    • RWYDESG
    • LANDINGSTRIPDESIGNATORIDENTIFIER
    • DESIGNATOR_TXT
    Tipp:

    Recommended input features are RunwayCenterline from the Airports data models (18B or 18C) or ADHPSurfaceLine from the AIS datamodel.

  • The Input Obstacle Features parameter must be z-aware and include the following fields:

    • TYPE_CODE
    • ELEV_VAL
    • HORIZACC_VAL
    • HORIZACC_UOM
    • VERTACC_VAL
    • VERTACC_UOM
    • DISTVERT_UOM
    Tipp:

    Recommended input features are VerticalStructurePoint, VerticalStructureLine, and VerticalStructurePolygon from the Airports 18B or 18C data models.

  • The Target OIS Features parameter must include the following fields:

    • RWYDESG or LANDINGSTRIPDESIGNATORIDENTIFIER or DESIGNATOR_TXT
    • Name
    • OBSTACLEJSON
      Tipp:

      Recommended input features are ObstructionIdSurface_MP from the Airports 18B or 18C data models.

      Hinweis:

      The field length must be at least 50,000 characters. A warning appears if the JSON output exceeds the length of the OBSTACLEJSON field.

  • If the tool is run repeatedly with different Input Obstacle Features, it will append the generated JSON data for each set of obstacles to each affected approach surface feature. Subsequently running the tool with an updated version of given Input Obstacle Features will selectively update the JSON data for those features without affecting the JSON data generated using other Input Obstacle Features.

  • The tool will use a flight path ID field (PATHID) to associate curved approach polylines with specific approach surfaces. This is required if you have an Input Flight Path Features value provided.

Syntax

GenerateOISObstacleData(in_runway_features, in_dems, in_obstacle_features, target_ois_features, {obstacle_height_field}, {obstacle_height_unit}, {in_flightpath_features}, {label_field})
ParameterErklärungDatentyp
in_runway_features

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

Feature Layer
in_dems
[in_dems,...]

The DEMs covering the runways and their approach obstruction identification surfaces.

Raster Layer
in_obstacle_features

The input obstacle features that will be analyzed. The feature class must be z-enabled.

Feature Layer
target_ois_features

The multipatch features with defined Airport schema. The feature class must be z-enabled.

Feature Layer
obstacle_height_field
(optional)

The field containing the height of the obstacle feature.

Text
obstacle_height_unit
(optional)

The unit of the obstacle height.

  • KILOMETERSKilometers
  • METERSMeters
  • DECIMETERSDecimeters
  • CENTIMETERSCentimeters
  • MILLIMETERSMillimeters
  • NAUTICAL_MILESNautical miles
  • MILESMiles
  • YARDSYards
  • FEETFeet
  • INCHESInches
  • DECIMAL_DEGREESDecimal degrees
  • POINTSPoints
  • UNKNOWNUnknown
Text
in_flightpath_features
(optional)

The polyline features that define curved approaches to the specified runways. If unspecified, all input features will be processed as straight approaches.

Feature Layer
label_field
(optional)

When an obstacle JSON generated by this tool is later used to create a Terrain and Obstacle Profile element in a Layout, the data from the field selected will be used to label the input point obstacles in that element.

The Obstacle Labels parameter only applies to Input Obstacle Features that contain point features.

Hinweis:

If no value is specified, the ObjectID will be applied by default.

String

Abgeleitete Ausgabe

NameErklärungDatentyp
out_ois_features

The updated feature class containing the generated obstruction identification surfaces.

Feature Layer

Codebeispiel

GenerateOISObstacleData example (stand-alone script)

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

import arcpy

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

# Input RunwayCenterline Feature Class
inRunwayFeatures = r"C:\data\ois.gdb\RunwayCenterlines"

# Input Terrain DEM Raster
inDEMRaster = [r"C:\data\ois.gdb\AirportFirstDEM",
               r"C:\data\ois.gdb\AirportSecondDEM"]

# Input Obstacle Feature Class
inOISObstacles = r"C:\data\ois.gdb\Obstacles"

# Input Obstruction Identification Surface Feature Class
targetOISFeatures = r"C:\data\ois.gdb\ObstructionIdSurface"

# Input Curved Approach Feature Class
inCurvedApproachFeatures = r"C:\data\ois.gdb\CurvedApproach"

# Processing GenerateOISObstacleData
arcpy.GenerateOISObstacleData_aviation(inRunwayFeatures, inDEMRaster,
                                       inOISObstacles, targetOISFeatures,
                                       "ELEV_Val", "Meters",
                                       inCurvedApproachFeatures)

arcpy.CheckInExtension("Airports")

Lizenzinformationen

  • Basic: Nein
  • Standard: Erfordert Aviation Airports
  • Advanced: Erfordert Aviation Airports

Verwandte Themen