Adding a Table to Table Attribute check

The Table to Table Attribute check allows you to compare table attributes to feature attributes. In a composite check, you can compare values in the one feature class or table to another feature class or table. For example, you could compare valid height values in a table to height attribute values on a feature class.

Learn more about the Table to Table Attribute check

手順:
  1. Start ArcMap.
    ヒントヒント:

    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. 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.

  4. Click Open.

    The Select a Batch Job File dialog box appears.

  5. Navigate to the composite check you want to open.
  6. Click Open.

    The Reviewer Batch Job Manager dialog box appears with the composite check and the group in which it is included.

  7. Double-click the name of the composite check you want to edit.

    The Composite Check Properties dialog box appears.

    A composite check that checks for bridges on roads and railroads
    A composite check that checks for bridges on roads and railroads
  8. Right-click in the Build A Composite Check list, then click Add Check Table to Table Attribute Check.

    The Table to Table Attribute Check Properties dialog box appears.

    The first feature class and the notes and severity information are populated with values from the Composite Check Properties dialog box.

  9. Click the Feature or Object Class/Subtype drop-down arrow in the Feature or Object Class 2 area and choose the feature class and subtype on which to run the 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 a SQL query.
  12. Choose an option for comparing attributes in the Attributes area.
    • If you want to compare all attributes between the feature class and table, choose Compare All Attributes.
      ヒントヒント:

      If you choose to compare all the attribute values, you can optional ignore common attributes between the two tables.

    • If you only want to compare certain attributes in the feature class and table, choose Compare Attributes.
  13. If you have chosen the Compare All Attributes option and want to ignore certain attributes, do the following:
    1. Check the Attributes to Ignore (Feature Level Metadata) check box.

      The Attributes To Ignore dialog box appears.

      Attributes To Ignore dialog box
    2. Check the check boxes next to the names of the attributes you want to ignore when finding spatial relationships.
      メモメモ:

      To check or uncheck all the check boxes next to the attribute names, click Select All or Clear All, respectively.

    3. Click OK.

      The Table to Table Attribute Check Properties dialog box appears.

    4. Proceed to step 15.
  14. If you have chosen the Compare Attributes option, do the following:
    1. Click Select Attributes.

      The Compare Attributes dialog box appears. Feature classes 1 and 2 automatically populate the Data Source 1 and Data Source 2 fields.

      Compare Attributes dialog box
    2. Click the Data Source 1 Attribute drop-down arrow and choose a field to use in the comparison.
    3. Click the Data Source 2 Attribute drop-down arrow and choose a field to use in the comparison.
    4. Click the Operator drop-down arrow and choose an operator to use in the comparison.
    5. Click Add.

      The condition is added to the Error Conditions list.

    6. Repeat steps 14b–14e as necessary.
    7. Click OK.

      The Table to Table Attribute Check Properties dialog box appears.

    8. Proceed to step 15.
  15. Click OK.

    The Composite Check Properties dialog box appears.

  16. Click OK.

9/17/2010