ArcMap

GAIT

Summary

Validates data using the Geospatial Analysis Integrity Tool (GAIT), checking geometry, feature codes, attribute values and domains, and metadata.

Usage

  • You must have CYGWIN and GAIT installed to use this tool.

  • The tool writes its results as line and point shapefiles to an output directory.

  • GAIT can execute against data in MGCP, GIFD, TDS, and VMap data models.

  • The attribution schema must match the schema of the input feature layer.

  • The inspection profile represents a set of checks to run during GAIT and depends on the data model set in the Attribution Schema parameter. Valid domain values are included in the tool messages.

  • Every time the GAIT tool is run where a Reviewer workspace is defined, a new Reviewer session will be created.

  • The values of the Metadata Mapping Table parameter depend on the attribution schema. Valid domain values are included in the tool messages.

  • The results of the tool process are stored in two log files: GAITStdError.txt and GAITStdOutput.txt. The log files are located at C:\Users\<user_name>\AppData\Roaming\ESRI\Production10.4\Desktop.

Syntax

GAIT(in_features, gait_exe, folder, schema, project, format, metadata, silent, {reviewer_workspace}, {specfile})
ParameterExplanationData Type
in_features
[in_features,...]

The features to validate.

Feature Layer; Table View
gait_exe

The path to the GAIT executable file.

File
folder

The shapefile export directory.

Folder
schema

The data model that corresponds to the data displayed in the input feature layer.

String
project

The name of the project. The project contains validation information, such as the checks run on the data and the results.

String
format

The set of checks to run on the data. This is specific to the data model listed in the attribution schema.

String
metadata

The metadata mapping table that corresponds to the data model of the input feature layer and the attribution schema.

  • META_ESRI —Esri metadata
  • META_INGR —Intergraph metadata
  • META_MGCPNGA —MGCP NGA metadata
String
silent

Indicates the amount of output messages to return from GAIT.exe.

  • SILENT —Limit messaging from GAIT.exe. This is the default.
  • VERBOSE —Run GAIT.exe in verbose mode.
Boolean
reviewer_workspace
(Optional)

The workspace to write the output features. Each shapefile result record is written to the reviewer table in this workspace.

Workspace
specfile
(Optional)

A file that defines custom checks.

File

Code sample

GAIT example (stand-alone script)

This stand-alone Python script demonstrates running GAIT against MGCP data.

# GaitExample_Example.py
# Description: Runs a GAIT session against a feature layer
# Requirements: Esri Defense Mapping solution

# Import arcpy module
import arcpy

#check out the extension
arcpy.CheckOutExtension('defense')

# Local variables for the GAIT tool params
AerofacA = "C:\\data\\mgcp.gdb\\MGCP\\AerofacA"
GAIT_exe = "C:\\GAIT\\GAIT.exe"
defense_data = "C:\\defense_data"
AerofacA_Layer = "AerofacA_Layer"

# Make a feature layer for the first param
arcpy.MakeFeatureLayer_management(AerofacA, AerofacA_Layer)

# Exec the GAIT tool
arcpy.GAIT_defense("AerofacA_Layer", GAIT_exe, defense_data, "MGCP", "MGCP_gait", "USE_MGCPMASTER", "META_MGCPNGA", "SILENT", "")

#Check in the extension
arcpy.CheckInExtension('defense')

Environments

This tool does not use any geoprocessing environments.

Licensing information

  • ArcGIS Desktop Basic: No
  • ArcGIS Desktop Standard: Requires Defense Mapping
  • ArcGIS Desktop Advanced: Requires Defense Mapping

Related topics