Finding polygon slivers

Polygon slivers can occur during extraction when small, thin polygons are accidentally created through an overlap with existing features. The factors that define a sliver polygon are the thinness ratio and the polygon's area. If the polygon is below a specified thinness ratio and value, it is considered a sliver.

The Polygon Sliver check finds sliver polygon geometries for features in the chosen feature class. The check can be run on an entire feature class, a subtype, or a set of features selected using a SQL query.

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 Polygon Sliver Check.

   The Polygon Sliver 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 to 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. Move the Thinness Ratio slider to the position that best describes the thinness of a sliver polygon.

   The farther right the slider is moved, the thicker the polygon must be so it is defined as a sliver.

9. Type a value in the Maximum Polygon Area text box.

   If the polygon's area falls below this value, it is considered a sliver.

   Nota:

   If the value is left at zero, all polygons are considered slivers, regardless of their size.

10. Click the Square drop-down arrow and choose the unit of measurement to use for the polygon area.

    The units you can choose include both page and map units. Page units include inches, points, millimeters, and centimeters. Map units include feet, yards, miles, nautical miles, kilometers, decimal degrees, decimeters, and unknown units.

11. If necessary, type descriptive text for the check results in the Notes text box in the Reviewer Remarks area.
12. 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.
13. Click OK.
14. Click the Run Data Check button on the Data Reviewer toolbar.

    The Features to Validate dialog box appears.
15. 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.
16. 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.

17. Click OK.