Adding a composite check

When you create a composite check, you are actually creating a series of checks that are going to be conditionally run on features. Feature Class 1, the first feature or object class you choose, is the one whose features are going to be run through all the checks in the composite check. For example, if you want to find bridges that do not intersect roads or railroads, BridgeL would be Feature Class 1 for the composite check. The subsequent checks you add to the composite check would check for bridges that do not overlap a road or a railroad.

The checks you can include in a composite check are the Geometry on Geometry and Table to Table Attribute checks. The Geometry on Geometry check allows you to find a variety of spatial relationships that can exist between features from Feature Class 1 and other feature classes. The Table to Table Attribute check allows you to compare table attributes to feature attributes. You can use one or the other, or a combination of both, in your composite check.

Learn more about the Geometry on Geometry check

Learn more about the Table to Table Attribute check

Similar to other data checks, you can apply a SQL query to Feature Class 1 to specify which features should be used in the check. These features are used with all of the Geometry on Geometry or Table to Table Attribute checks you create in your composite check. However, depending on the conditions you are checking, the geometry type of the check results may not match that of the features in Feature Class 1.

Since the composite check is created based on a number of different conditions you specify, you can assign the check a title that is appropriate for its purpose. For example, the composite check that searches for bridges that are not on roads or railroads could be called "Bridges Not Overlapping Roads/Railroads."

You can also add information such as text for the error description, notes, and the severity of all results of the composite check. Information from all three of these fields is used to populate the Reviewer table when records are written based on the composite check. The error description describes the record when it is initially written to the Reviewer table, which populates the REVIEWSTATUS field, while the notes and severity fields provide extra information that helps you to further comment on and assign a priority to Reviewer table records.

A composite check that checks for bridges on roads and railroads
A composite check that checks for bridges on roads and railroads

Once you are finished configuring the composite check, you can save it so it can be reused on different workspaces, or as changes are made to your data. A composite check is included in a group within a batch job, so it is saved as a Reviewer batch job (.rbj) file.

  1. Start ArcMap.
  2. On the main menu, click Customize > Toolbars > Data Reviewer.
  3. Click the Reviewer Batch Job Manager button Reviewer Batch Job Manager on the Data Reviewer toolbar.

    The Reviewer Batch Job Manager dialog box appears.

    Initial view of the Reviewer Batch Job Manager dialog box

  4. Right-click the blank area at the top of the dialog box and click New Group.

    A new group appears in the field.

  5. Click the group name to make it editable.
  6. Type a new name for the group and press Enter.
  7. Right-click the new group and click Add Check > Composite Check.

    The Composite Check Properties dialog box appears.

    Composite Check Properties dialog box

  8. If necessary, type a unique name for the check in the Check Title text box.

    The check title can be used to describe the conditions you are looking for with the check. This is useful when you have multiple instances of the same check to validate the same feature classes or tables but with different validation parameters.

  9. Click the Feature or Object Class/Subtype drop-down arrow and choose the feature class on which you want to base all the checks in the composite check.

    The feature class or table you choose is used as Feature Class 1 in the checks you create as part of the composite check.

  10. To run the check on the entire feature class and save this setting, check the Always Run on Full Database check box.
  11. To run the check on specific features in a feature class, click SQL to construct an SQL query.
  12. Right-click in the Build A Composite Check list, point to Add Check, and choose the check you want to add.
  13. Configure the check as appropriate.

    For more information on configuring either of the two available checks, see Adding a Geometry on Geometry check or Adding a Table to Table Attribute check, respectively.

  14. Click OK.

    The Composite Check Properties dialog box appears.

  15. Repeat steps 12–14 to add checks as needed.
  16. Type a description for the check results in the Error Description (Review Status) text box.
  17. If necessary, type descriptive text for the check results in the Notes text box in the Reviewer Remarks area.
  18. If necessary, click the Severity drop-down arrow and choose a value that indicates the priority of the check's results in the Reviewer Remarks area.

    The severity indicates the importance of the check result. The values range from 1 to 5, with 1 being the highest priority and 5 being the lowest.

  19. Click OK.

    The Reviewer Batch Job Manager dialog box appears.

  20. Click Save.

    The Save As dialog box appears.

  21. Type a name for the batch job in the File name text box.
  22. Click Save.

    The Reviewer Batch Job Manager dialog box appears.

  23. Click OK.