Skip To Content

Monotonicity

Available with Data Reviewer license.

Summary

The Monotonicity check finds polyline features that contain monotonic errors in either elevation or measure values (z- or m-values).

Overview

The purpose of the Monotonicity check is to identify features that contain z- or m-values that are not strictly increasing or decreasing in value. Features that contain non-monotonic values can impact the results of your analysis and models.

Features can also be evaluated to determine whether they are trending in a specific manner. Features that contain node values that do not trend as expected can impact the results of your analysis.

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

When configured as a validation rule, point error geometries will be returned for each feature vertex that is non-monotonic. In m-value validations, vertices that do not contain measure values (NaN) will also be returned as errors.

Industry scenarios

  • In water resource management, elevation values stored in streamline features are used to add detail to digital elevation models (hydro DEM conditioning) to enforce known drainage patterns.
  • In roadway management, roadway routes that have two or more consecutive vertices with the same measure may adversely affect length calculations, for example, United States Department of Transportation mileage reports.

Examples

Non-monotonic—The following image illustrates two line features with z- and m-values that are not strictly increasing or decreasing in value:

Monotonicity z- and m-values

Syntax

ParameterRequiredDescriptionWorkflows

Input Layers

Yes

The input feature layers evaluated by the rule.

Valid inputs for this rule type are polyline features that are z- or m-enabled. Click the Forward button Forward to apply filtering to specific features in the feature layer.

Reviewer rules

Evaluate

Yes

The property to be evaluated.

Select either z-values or m-values for evaluation.

Attribute rules

Reviewer 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.

  • Non-Monotonic Features—Feature vertices are returned when vertices are not strictly increasing or decreasing in value.
  • Level Values (From = To)—Features are returned when the From node is equal to the To node.
  • Decreasing Values (From > To)—Features are returned when the From node is greater than the To node.
  • Increasing Values (From < To)—Features are returned when the From node is less than the To node.

Attribute rules

Reviewer 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 (constraint)

Title/Name

No

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

Reviewer 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

Reviewer rules

Severity

No

Severity of the error created when noncompliant features are found.

This value indicates the importance of the Reviewer result relative to other results. Values range from 1 to 5, with 1 being the highest priority and 5 being the lowest.

Reviewer rules

Tags

No

Tag property of the Reviewer rule.

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

Attribute rules

Reviewer rules

Notes

  • Polyline features must be either z- or m-enabled to be used in this check. For more information, see Geometry properties.
  • Differences in z- or m-values between adjacent vertices that are within the z- or m-tolerance are not compared when evaluated for monotonicity. For more information, see Tolerance.
  • Polyline features must have a defined vertical coordinate system to be used in this check for evaluating z-values. For more information, see Vertical coordinate systems.
  • A feature’s From node and To node values are used to determine whether z- or m-values should be strictly increasing or decreasing when evaluated for monotonicity.
  • Vertices that are within x,y tolerance are not compared when evaluated for monotonicity. For more information, see Tolerance.
  • Multipart features are evaluated in part order (Part 0, Part 1, and so forth) when evaluated for monotonicity.
  • When configuring filter parameters, care should be taken when using database-specific SQL functions that differ from those supported in your production environment. For more information, see SQL reference for query expressions used in ArcGIS.

Related topics