Skip To Content

Evaluate Polygon Perimeter and Area

Mit der Data Reviewer-Lizenz verfügbar.

Summary

The Evaluate Polygon Perimeter and Area check finds polygon features based on the area or perimeter of the entire polygon or its individual parts or segments.

Overview

The purpose of the Evaluate Polygon Perimeter and Area check is to identify features that meet either area or perimeter conditions that are considered to be invalid. This can include an evaluation of the feature's entire geometry or its constituent parts or segments.

When configured as a constraint rule, an error notification is returned upon the creation or modification of a feature based on the specified conditions defined in the parameters of the rule.

Industry scenarios

  • In facility mapping, certain types of structures, such as sheds, must have an area less than a specified size, otherwise they should be coded with a different structure type.
  • In topographic mapping, features must have segment lengths greater than a specified value to maintain consistency in products generated from multiple data sources.

Syntax

Parameter Required DescriptionWorkflows

Subtype

No

The subtype that the rule will be applied to if the dataset has subtypes.

Attribute rules

Evaluate

Yes

The geometric property of the feature evaluated by the check.

  • Area—Evaluates the area of the entire feature or its individual parts.
  • Perimeter—Evaluates the length of the entire feature or its individual parts or segments.

Attribute rules

Type

Yes

The method used when evaluating a feature's area or perimeter.

  • Polygons—Evaluates the area or perimeter of the entire polygon feature.
  • Parts—Evaluates the area or perimeter of individual parts of a polygon.
  • Segments—Evaluates the perimeter of the segments of a polygon

Attribute rules

Search Goal

Yes

Error conditions evaluated by the rule. Any feature whose values match those defined in the rule are returned as an error.

  • Is equal to—The perimeter or area is equal to the number of units specified.
  • Is not equal to—The perimeter or area is not equal to the number of units specified.
  • Is greater than—The perimeter or area is greater than the number of units specified.
  • Is greater than or equal to—The perimeter or area is equal to or greater than the number of units specified.
  • Is less than—The perimeter or area is less than the number of units specified.
  • Is less than or equal to—The perimeter or area is equal to or less than the number of units specified.
  • Is 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) values.
  • Is between (excluding bounds)—The perimeter or area is between the number of units specified in the lower bound (minimum) and upper bound (maximum) values.
  • Is not between (including bounds)—The perimeter or area is not equal to or between the number of units specified in the lower bound (minimum) and upper bound (maximum) values.
  • Is not between (excluding 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) values.

Additional input is required if you choose an operator with upper and lower bounding values.

Attribute rules

Triggers

Yes

The editing events that trigger the rule to take effect.

  • Insert—Triggers the rule when a new feature is added.
  • Update—Triggers the rule when a feature is updated.
  • Delete—Triggers the rule when a feature is deleted.

Attribute rules

Title/Name

Yes

A unique title or name for the rule.

This information is used to support data quality requirement traceability, automated reporting, and corrective workflows.

Attribute rules

Notes/Description

No

Descriptive text of the error condition when noncompliant features are found.

This information is used to provide guidance to facilitate corrective workflows.

Attribute rules

Tags

No

Tag property of the rule.

This information is used in rule authoring and management workflows to support traceability and reporting of data quality requirements.

Attribute rules

Notes

The features found by this check will differ depending on whether the entire feature or its parts or segments is evaluated.

Verwandte Themen