Evaluating polygon perimeters and areas

Polygon perimeters and areas can be evaluated based on conditions set forth in a product specification. For example, if building polygons can be no larger than 50 meters square, you can search for all building polygons that have an area greater than 2,500 square meters and report them as results or errors. Minimum area polygons and polygon parts can also be found.

The Evaluate Polygon Perimeter and Area check allows you to specify parameters for the validity of polygons based on their parts and area. You can use this check with polygons, polygon parts, polygon rings, and polygon segments. Any features that meet the conditions specified in the check are returned as results.

The check can also 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.

Schritte:
  1. Start ArcMap.
    TippTipp:

    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 Evaluate Polygon Perimeter and Area Check.

    The Evaluate Polygon Perimeter and Area Check Properties dialog box appears.

    Evaluate Polygon Perimeter and Area Check Properties dialog box
  4. If necessary, type a unique name for the check in the Check Title text box.
    HinweisHinweis:

    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. Click an option in the Type area to indicate the type of feature to be checked.

    You can choose a polygon, rings, parts, or segments. Polygons would be complete area features, while rings, parts, and segments represent parts of a polygon feature.

  9. Click an option in the Dimension area to indicate what aspect of the feature to check.
    • Area can be used in association with the entire feature, rings, and parts.
    • Perimeter can be used for any linear feature.
  10. Click the Square drop-down arrow and choose a unit of measurement to use with the polygon.
  11. Click the Operation drop-down arrow and choose the operation to use with respect to the polygon's area or perimeter.
    • Less than—The perimeter or area is less than the number of units specified.
    • Less than or equal—The perimeter or area is equal to or less than the number of units specified.
    • Greater than—The perimeter or area is greater than the number of units specified.
    • Greater than or equal—The perimeter or area is equal to or greater than the number of units specified.
    • Not equal to—The perimeter or area is not equal to the number of units specified.
    • Equal to—The perimeter or area is equal to the number of units specified.
    • In Between (Including Bounds)—The perimeter or area is between or equal to the number of units specified in the Lower Bound (minimum) and Upper Bound (maximum) text boxes.
    • In Between (Not Including Bounds)—The perimeter or area is between the number of units specified in the Lower Bound (minimum) and Upper Bound (maximum) text boxes.
    • Not In Between (Including Bounds)—The perimeter or area is equal to or not between the number of units specified in the Lower Bound (minimum) and Upper Bound (maximum) text boxes.
    • Not In Between (Not Including Bounds)—The perimeter or area is not between the number of units specified in the Lower Bound (minimum) and Upper Bound (maximum) text boxes.

    The operation text box appears. If you choose an operation with bounding values, Lower Bound and Upper Bound text boxes appear.

  12. Type the number of units to use with the operation.

    If you choose an operation with bounding values, you must indicate two values: one each for the minimum and maximum ranges of the tolerance.

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

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

  19. Click OK.

9/30/2010