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 and TDS 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.
Syntax
GAIT(in_features, gait_exe, folder, schema, project, format, metadata, silent, {reviewer_workspace}, {specfile})| Parameter | Explanation | Data 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.
| String |
silent | Indicates the amount of output messages to return from GAIT.exe.
| 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 |
Derived Output
| Name | Explanation | Data Type |
| out_featurelayers | Feature layers that have been validated through GAIT. | Table View; Feature Layer |
Code sample
This stand-alone script demonstrates running the GAIT tool to validate MGCP topographic data against industry standards.
# Name: GAIT_sample.py
# Description: Use the GAIT tool to validate topographic data against industry standards
# Import System Modules
import arcpy
import os
# Check Out Extensions
arcpy.CheckOutExtension('Defense')
arcpy.CheckOutExtension('DataReviewer')
# Setting Local Variables
workspace = r'C:\Testing\GAIT\TDS_6_1.gdb'
gait_exe = r'C:\Program Files\GAIT-WINDOWS-25\gait25.exe'
project_folder = r'C:\Testing\GAIT'
project_name = 'GAIT_TEST_1'
# Generate list of features to validate
in_features = []
for dir_path, dir_names, file_names in arcpy.da.Walk(workspace, datatype='FeatureClass'):
for file_name in file_names:
in_features.append(os.path.join(dir_path, file_name))
# Create reviewer workspace to manage GAIT errors
reviewer_workspace = arcpy.management.CreateFileGDB(project_folder, project_name + '_DR', 'CURRENT').getOutput(0)
arcpy.reviewer.EnableDataReviewer(reviewer_workspace, '#', '#', '#')
# Use the GAIT tool to validate topographic data
arcpy.topographic.GAIT(in_features, gait_exe, project_folder, 'TDS6', project_name, 'USE_TDSMASTER', 'META_ESRI', 'SILENT', reviewer_workspace)
# Check In Extensions
arcpy.CheckInExtension('Defense')
arcpy.CheckInExtension('DataReviewer')Environments
Licensing information
- Basic: No
- Standard: Requires Defense Mapping
- Advanced: Requires Defense Mapping