Finding duplicate vertices

Duplicate vertices are created in a variety of ways, including digitizing errors, use of data at a smaller scale than that for which is was collected, and loading data from a database with one precision to another.

For each errant feature, the Duplicate Vertex check finds vertices that are within a specified tolerance of one another. The check can be run on an entire feature class, a subtype, or a set of features selected using a SQL query. For example, you could have vertices on a line or polygon that are either co-located or very close to one another. If the tolerance specified in the check is small enough, one of the vertices would be returned as a check result.

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.

手順:
  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 Select Data Check drop-down arrow on the Data Reviewer toolbar, click the plus sign (+) next to Duplicate Geometry Checks, then click Duplicate Vertex Check.

    The Duplicate Vertex Check Properties dialog box appears.

    Duplicate Vertex Check Properties
  4. If necessary, type a unique name for the check in the Check Title text box.
    メモメモ:

    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. Type a value in the Tolerance text box to use as the allowable tolerance between two vertices.
  9. Click the Tolerance drop-down arrow and choose the units of measurement to use.

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

  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 Run Data Check on the Data Reviewer toolbar.

    The Features to Validate dialog box appears.

    Features to Validate dialog box
  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.
    メモメモ:

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

  16. Click OK.

9/17/2010