Running a GAIT session in Defense Mapping

To validate certain types of data used with the Defense Mapping Solution, it may be required that the GAIT utility be used. The GAIT Command allows you to configure and run a GAIT session through Defense Mapping on all the features loaded in the map or a selection set. GAIT can be used with MGCP, GIFD, TFDM, and VMap data, and with GAIT version 14 or higher.

To configure the GAIT session, you need to specify the following:

• Location of the GAIT executable file—The path to the GAIT executable file.
  Hinweis:

  This only needs to be defined the first time you use the GAIT Command.

• Shapefile export location—The directory to which the shapefiles will be exported.
• Attribution schema being used—The data model that corresponds with the data.
• GAIT project name—The name of the project, which contains the validation information, such as the checks run on the data and the results.
• Inspection profile—The set of checks that will be run on the data. This is specific to the data model that corresponds with the data.
• Metadata mapping table—The metadata mapping table that matches the data model.

Once this information is specified and the tool is run, the map features or selection set are exported to shapefiles based on their subtypes, and the checks in the inspection profile are run. The results of the checks are consolidated into line and point shapefiles.

If you are using GAIT version 15 or higher, you can choose to run the GAIT session silently. This allows the utility to run in the background and does not display any messages on-screen until the process is complete. Once the process is complete, as with the unsilent method, you are asked whether you want to add the results of the GAIT checks to the map or write them to the Reviewer table.

If a Reviewer session has been started when the tool is run, you can write the check results to the Reviewer table. Each feature in the consolidated shapefile is added as a record in the Reviewer table. The ORIGINCHECK field contains the name of the shapefile initially created based on the feature subtypes. The name of the GAIT check is written to the ORIGINCHECK field, and the NOTES field contains a description of the feature's error condition.

When you interact with the records in the Reviewer table, there are two types of geometry that are referenced: feature and Reviewer. Feature geometry has a direct association with the shapefiles that are created based on the features in the map. Reviewer geometry is associated with the consolidated line and point shapefiles generated by GAIT.

Schritte:

1. Start ArcMap.
   Tipp:

   If the ArcMap - Getting Started dialog box appears, you can open a new or existing map document. You can also check the Do not show this dialog box in the future check box and click Open.

2. If necessary, load data in the map.
3. On the main menu, click Customize > Toolbars > Production Editing.
4. On the main menu, click Customize > Toolbars > Defense Mapping.
5. Click the Production Start Editing button on the Production Editing toolbar.
   Hinweis:

   The Manage Features and Create Attributes, Update Attributes, or Metadata Attributes windows automatically appear when you start an edit session using the Production Start Editing tool.

   Tipp:

   If the Create Attributes, Update Attributes, or Metadata Attributes window does not appear when you start an edit session, click the Link Feature Manager To Attributes Window button on the Manage Features window.

6. If you only want to run GAIT on a selected set of features, select the features on which you want to run GAIT.
7. Click the GAIT Command button on the Defense Mapping toolbar.

   The GAIT Command dialog box appears.

8. Click the ellipsis (...) next to the Select GAIT executable text box.

The Browse to GAIT Executable dialog box appears.

9. Navigate to the gait.exe file.
10. Click Open.

    The GAIT Command dialog box appears.

11. Click the ellipsis (...) next to the Select shapefile export location text box.

    The Browse For Folder dialog box appears.

12. Navigate to the directory in which you want to store the shapefiles that are initially created based on the features in your map.
13. Click OK.

    The GAIT Command dialog box appears.

14. Click the Select attribution schema drop-down arrow and choose the schema that corresponds with the map or selected set.
15. Click the ellipsis (...) next to the GAIT project folder text box.

    The Browse For Folder dialog box appears.

16. Navigate to the folder in which you want to store the GAIT project files.
17. Click OK.
18. Type a name for the GAIT project in the Specify project name to create text box.
19. Click the Select inspection profile drop-down arrow and choose the set of checks that corresponds with the map or selected set.
20. Click the Select metadata mapping table drop-down arrow and choose the metadata mapping table that corresponds with the map or selected set.
21. If you are using GAIT 15 or higher, you can check the Run GAIT silently check box to run the process in the background.
22. Click OK.

    The features are exported to a shapefile, and the GAIT session is run.

    Once the process is complete, the GAIT Summary dialog box appears with all the check boxes checked.

    Hinweis:

    The Write results to the current Reviewer session item does not appear if you have not started a Reviewer Session.

23. Do one or more of the following if you do not want an action to occur once the GAIT Summary dialog box is closed:

    To not add the results of the GAIT session to the table of contents and map	Uncheck the Add results to map check box.
    To not view the project summary files	Uncheck the View project summary files check box.
    To not write the results to the Reviewer table	Uncheck the Write results to the current Reviewer session check box.

24. Click OK.