Finding invalid hole features

Polygons with holes can have features that somehow have a spatial relationship with features from other feature classes. For example, a road feature can be contained within a hole in a built-up area polygon.

The Invalid Hole Feature check searches for features that are spatially related to holes in a polygon feature class. The check can be used with the entire feature class, a subtype, or a set of features selected using a SQL query. Once the features are recorded in the Reviewer table, they can be individually visited and evaluated.

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

   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 Polygon Checks, then click Invalid Hole Feature Check.

   The Invalid Hole Feature Check Properties dialog box appears.
4. If necessary, type a unique name for the check in the Check Title text box.
   Nota:

   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 and choose the feature class and subtype on which to run the check in the Feature Class 1 area.

   This is the feature class or subtype that contains holes.

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 in the Feature Class 2 area.

   This is the feature class that contains features that intersect the holes in feature class 1.

   Nota:

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

9. Click the Type drop-down arrow and choose the type of spatial relationship to use.
   • Crosses—Features from feature class 2 cross holes in features from feature class 1.
   • Touches—Features from feature class 2 touch holes in features from feature class 1
   • Contains—Features from feature class 2 are completely contained in holes in features from feature class 1.
   • Overlaps—Features from feature class 2 overlap holes in features from feature class 1.
   • Intersects—Features from feature class 2 intersect holes in features from feature class 1.
   • Within—Features from feature class 2 are completely within holes in features from feature class 1.
10. If necessary, type descriptive text for the check results in the Notes text box in the Reviewer Remarks area.
11. 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.
12. Click OK.
13. Click the Run Data Check button on the Data Reviewer toolbar.

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

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

16. Click OK.