Checking for invalid subtypes

The subtypes for a feature class provide ways to further categorize features within a feature class. For example, the Bridge line feature class could have separate subtypes for bridges, overpasses, and viaducts instead of combining them into one subtype. However, if the product specification does not allow for this type of granularity between feature types, these subtypes would be considered invalid.

The Subtype check can be run on an entire feature class or a set of features selected using a SQL query. You can optionally choose to include null subtypes. This means that features that have Null as the FCSubtype value are returned as errors. All other features that belong to invalid subtypes are also returned as errors.

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.

Schritte:

1. Start ArcMap.
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 Database Validation Checks, then click Subtype Check.

   The Subtype Check Properties dialog box appears.
4. If necessary, type a unique name for the check in the Check Title text box.
   Hinweis:

   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 Class/Subtype drop-down arrow to choose the feature class 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. To include null subtypes, check the Search for Null Subtypes check box.
9. If necessary, type descriptive text for the check results in the Notes text box in the Reviewer Remarks area.
10. 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.
11. Klicken Sie auf OK.
12. Click the Run Data Check button on the Data Reviewer toolbar.

    The Features to Validate dialog box appears.
13. 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.
14. To run the check only on features that have been edited in a versioned workspace, check the Changed Features Only check box.
    Hinweis:

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

15. Klicken Sie auf OK.