Unnecessary Nodes

Disponible avec une licence Data Reviewer.

Summary

The Unnecessary Nodes check finds polyline features that share a node and have matching attribute values.

Overview

When polyline features contain pseudo nodes and identical attribution on editable fields, the shared node is often unnecessary. Pseudo nodes occur when the end node on a feature connects to another end node with no other nodes present. Features found with this check can be merged without a loss of information and may result in enhanced database performance.

Supported workflows

ArcGIS Data Reviewer checks support multiple methods for implementing automated review of your data. The following table identifies the supported implementation methods for this check:

Validation			Constraint
Reviewer batch job	Reviewer map rule	Attribute (validation) rule	No
Yes	No	Yes

Syntax

Parameter	Required	Description	Workflow
Subtype	No	The subtype that the rule is applied to if the dataset has subtypes.	Validation
Attribute	No	A query that identifies the features to which the rule is applied.	Validation
Attributes to Ignore	No	The attribute values to ignore when evaluating for unnecessary nodes. The attribute values to ignore during evaluation. Only editable fields can be ignored.	Validation
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.	Validation
Description	No	Descriptive text of the error condition when noncompliant features are found. This information is used to provide guidance to facilitate corrective workflows.	Validation
Severity	No	Severity of the error created when noncompliant features are found. This value indicates the importance of the error relative to other errors. Values range from 1 to 5, with 1 being the highest priority and 5 being the lowest.	Validation
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.	Validation

Notes

• M- and z-values are ignored when evaluating the geometry of input features.
• The Attribute parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.