Validating data with batch jobs using the Reviewer Batch Validate tool

Mit der Data Reviewer-Lizenz verfügbar.

Once you have created batch jobs using the Reviewer Batch Job Manager, you can use them to validate data in your database with the Reviewer Batch Validate tool. When you run a batch job, all the checks included in the batch job are run using the feature classes, subtypes, and selection sets you have specified. The records that correspond with the criteria for each check are then written to the Reviewer table for correction or further inspection.

Any default checks you have chosen on the Default Checks tab on the Reviewer Session Manager dialog box are also included with the batch jobs you are going to use with your data.

Hinweis:

The default checks are not run if the batch job you run on the data only includes database validation checks (Connectivity Rules, Domain, Relationships, or Subtype) or table checks (Execute SQL, Regular Expression, Table to Table Attribute, or Unique ID). This is because the default checks validate spatial conditions and do not include attribute validation.

After you choose the extent on which to run the batch job, you can validate the individual checks to determine which checks can be run on your data. Depending on the extent you choose, you might not be able to run all the checks in the batch job. For example, if you have only parcel polygons selected and you are running the Reviewer Batch Validate tool with the Selection Sets option, a check that validates street centerlines would be visible but would not generate any records, since street centerlines are not part of the selection set.

You can also change the workspace for the entire batch job or individual checks within it. This allows you to use an existing batch job with a different data source.

After the batch job has been run, a log file is generated that provides information on each individual check, the number of features it has been run against, and the number written to the Reviewer table. This log file is located in the %Appdata%\ESRI\Production<release> directory.

1. Start ArcMap.
2. If necessary, load data in the map.
3. On the main menu, click Customize > Toolbars > Data Reviewer.
4. Start a Reviewer session in one of the following:
   • A file, personal, or SQL Server Express geodatabase
   • An enterprise geodatabase
   • An existing Reviewer workspace
5. Click the Reviewer Batch Validate button on the Data Reviewer toolbar.

   The Batch Validate dialog box appears.

   

6. Click Add from File.

   The Select Batch Job File dialog box appears.

7. Navigate to the batch jobs you want to run with the Reviewer Batch Validate tool.

   Hinweis:

   You can add multiple batch jobs by pressing Ctrl or Shift when you select the batch jobs.

8. Click Open.

   The Batch Validate dialog box appears. The checks in the batch job appear in the Batch Jobs area.

   If there are multiple workspaces referenced in the batch job, the Update to Single Workspace dialog box appears so you can choose the workspace you want to validate with the batch jobs.

   When there is only one workspace in ArcMap, the batch job's workspace is automatically updated to the current workspace.

   Tipp:

   To remove a batch job group from the Batch Jobs area of the Batch Validate dialog box, click the batch job group and click Remove. If only one batch job group is listed in the Batch Jobs area, the default checks are also deleted. To quickly select and deselect checks, you can also use Select All Groups and Unselect All Groups by right-clicking in the Batch Jobs area.

9. Optionally click Validate All to ensure that all the feature classes that correspond with the checks are loaded in the map and to add any default checks.

   Tipp:

   The default checks are selected on the Reviewer Session Manager dialog box on the Default Checks tab.

10. Choose an extent to use in the Features to Validate area.
    • Selection Sets—The currently selected features. If you have a definition query defined for any of the feature classes you are using with the check, it is applied to the feature class.
    • Current Extent—The current extent in the map display. If you have a definition query defined for any of the feature classes you are using with the check, it is applied to the feature class.
    • Definition Query—The extent defined by layer definition queries for each feature class. If you have a definition query defined for any of the feature classes you are using with the check, it is applied to the feature class.
    • Full Database—The entire feature class.
    • Changed Features Only—If you are validating data in a versioned geodatabase, you can also choose to run a check only on features that have been edited. It's enabled when the production workspace references an enterprise geodatabase. This setting limits validation to those features that have changed from the parent to child version and only applies to a check's primary feature class (Feature Class 1). All features in secondary data resources (Feature Class 2+) are used in the validation.

      Hinweis:

      Changes between versions include the following:

      • Features inserted in the child version but not the parent
      • Features changed in the child version and unchanged in the parent
      • Features changed in both child and parent versions
      • Features changed in the child version and deleted in the parent

11. Click Validate All.

    All the checks are validated against the extent you have chosen. All checks with corresponding data loaded in the table of contents are enabled, and those that do not have the appropriate data loaded in the table of contents are disabled.

12. Click Run.

    Tipp:

    Once a batch job is added on the Batch Validate dialog box, you can minimize and maximize the groups in the batch job. This also minimizes and maximizes the default checks that are included.

    The default checks and the checks included with the batch job are run against the extent you have chosen. When the batch job has finished running, a message appears notifying you of the number of records that have been written to the Reviewer table.

13. Klicken Sie auf OK.
14. If necessary, click the Reviewer Table button to open the Reviewer Table window and review the batch job results.