Résumé
Validates data using the Geospatial Analysis Integrity Tool (GAIT), which checks geometry, feature codes, attribute values and domains, and metadata.
Utilisation
You must have CYGWIN and GAIT installed to use this tool.
The tool writes the results as line and point shapefiles to an output directory.
GAIT can execute using 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 when 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 tool results are stored in two log files, GAITStdError.txt and GAITStdOutput.txt, located at C:\Users\<user_name>\AppData\Roaming\ESRI\Production<version>\Desktop.
Syntaxe
arcpy.defense.GAIT(in_features, gait_exe, folder, schema, project, format, metadata, silent, {reviewer_workspace}, {specfile})
Paramètre | Explication | Type de données |
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 | Specifies the metadata mapping table that corresponds to the data model of the input feature layer and the attribution schema.
| String |
silent | Specifies whether output messages from GAIT.exe will be limited as to the number of words.
| Boolean |
reviewer_workspace (Facultatif) | The workspace where the output features will be written. Each shapefile result record is written to the reviewer table in this workspace. | Workspace |
specfile (Facultatif) | A file that defines the custom checks. | File |
Sortie dérivée
Nom | Explication | Type de données |
out_featurelayers | The feature layers that have been validated through GAIT. | Feature Layer; Table View |
Exemple de code
GAIT example (stand-alone script)
This stand-alone Python script demonstrates running GAIT using MGCP data.
# GaitExample_Example.py
# Description: Runs a GAIT session against a feature layer
# Requirements: ArcGIS 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')
Environnements
Cet outil n'utilise pas d’environnement de géotraitement.
Informations de licence
- Basic: Non
- Standard: Requiert Defense Mapping
- Advanced: Requiert Defense Mapping