Comparing table attributes

Tables and features contain fields that can correspond with one another. When the fields in both contain similar information, you may want to compare a feature attribute with values in a table. For example, you may want to compare scale values in a table with those in a feature class to ensure they are the same.

You could also compare values in two feature classes or tables. For instance, you may want to confirm that bridges and the transportation features associated with them have the same value for the Existence Category attribute.

The Table to Table Attribute check can compare values in two different tables, two different feature classes, or a table and a feature class. This check can be run on all features in the selected feature class, a subtype, or a set of features selected using a SQL query. Features and table rows that meet error conditions are written to the Reviewer table.

Once you have defined the criteria for the check, you can configure the notes and a severity rating. The notes allow you to provide a more specific description for the feature that has been written to the Reviewer table and are copied to the Notes field in the Reviewer table. The severity rating allows you to indicate how important the results from a check are in terms of your quality assurance/quality control processes. The lower the number, the greater the priority the check's results have.

Pasos:
  1. Start ArcMap.
    SugerenciaSugerencia:

    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 Select Data Check drop-down arrow on the Data Reviewer toolbar, click the plus sign (+) next to Table Checks, then click Table to Table Attribute Check.

    The Table to Table Attribute Check Properties dialog box appears.

    Table to Table Attribute Check Properties dialog box
  4. If necessary, type a unique name for the check in the Check Title text box.
    NotaNota:

    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.

  5. Click the Feature or Object Class/Subtype drop-down arrow in the Feature or Object Class 1 area and choose the feature class and subtype on which to run the check.
  6. To run the check on the entire feature class and save this setting, check the Always Run on Full Database check box.
  7. To run the check on specific features in a feature class, click SQL to construct a SQL query.
  8. Repeat steps 5–7 for Feature or Object Class 2.
    NotaNota:

    If you want to run the check using selected features in feature class or object class 1 and all the features in feature class or object class 2, check the Always Run on Full Database check box.

  9. Choose an option for comparing attributes in the Attributes area.
    • Compare All Attributes—Compares all attributes between the tables
    • Compare Attributes—Compares certain attributes in the tables

    If you only want to compare specific attributes, proceed to step 11.

    If you want to compare all attributes and ignore specific fields, proceed to step 12.

  10. 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 11b–11e as necessary.
    7. Click OK.

      The Table to Table Attribute Check Properties dialog box appears.

    8. Proceed to step 12.
  11. 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.
      NotaNota:

      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 12.
  12. If you want to find attributes that do not match, check the Not - find rows that do not match check box.
  13. If necessary, type descriptive text for the check results in the Notes text box in the Reviewer Remarks area.
  14. 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.
  15. Click OK.
  16. Click the Run Data Check button Run Data Check on the Data Reviewer toolbar.

    The Features to Validate dialog box appears.

    Features to Validate dialog box
  17. Choose an option in the Features to Validate area.
    • Selection Set—The check is run on the features that are currently selected in the map.
    • Current Extent—The check is run on the current map extent, which is controlled by the map scale.
    • Definition Query—The check is run on the features that are displayed based on definition queries that have been created for the feature class.
    • Full Database—The check is run on all the features in the feature class.
  18. To run the check only on features that have been edited in a versioned workspace, check the Changed Features Only check box.
    NotaNota:

    The Changed Features Only option is available only for a versioned database.

  19. Click OK.

9/30/2010