Domain

Available with ArcGIS Pro Standard and Data Reviewer licenses.

Summary

The Domain check finds features that contain attribute values that do not comply with domain constraints. This includes numeric values that are greater or less than those specified in a range domain and attribute values that are not found in a coded value domain.

Overview

The purpose of the Domain check is to identify range or coded value domain values outside the domain constraints. Attribute field domains can either be coded values or ranges. When a value is entered, especially if the field is a range field, the value can be greater or less than the allowed values. This is especially true if validation was not performed when attributes were edited. In addition, if data has been loaded from an external source, features may exist that violate both range and coded value domains.

Industry scenarios

This check can be used in the following scenarios:

  • In topographic mapping, elevation contours with invalid values in the domain-restricted Hypsography Portrayal Type (HQC) attribute impact cartographic production when symbolizing features.
  • In water utility management, incorrect values in the diameter properties of features such as water mains and lateral lines can impact the results of hydraulic modeling of the utility network.

Supported workflows

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

ValidationConstraint

Reviewer batch job

Attribute (validation) rule

No

Yes

Yes

(ArcGIS Pro 2.7 or later)

Note:

Map-based Reviewer rules are deprecated and are no longer available for use. It is recommended that you migrate automated review workflows to Data Reviewer capabilities available in attribute rules. Opening or saving a map document (.aprx) at ArcGIS Pro 3.0 removes all the existing map rules from the document.

Syntax

ParameterRequired DescriptionWorkflows

Subtype

No

The subtype to which the rule is applied.

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 during evaluation. Only editable fields can be ignored.

Validation

Search for Null Values

No

Attribute values that are <Null> (no value) are returned as an error.

Validation

Name

Yes

A unique name for the rule.

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

Validation

Description

No

A description you define of the error when a noncompliant feature is found.

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

Validation

Severity

No

The severity of the error assigned when a noncompliant feature is 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

The 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

Keep the following in mind when using the check:

  • Features or table records that are assigned to a subtype are evaluated based on the domains defined by the subtype.
  • Features or table records assigned to an invalid subtype are not evaluated by this check. Use the Subtype check to find features assigned to invalid subtypes and correct them before using this check.
  • The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, IS NULL) operators.
  • An error message that mentions the fields only supports 256 characters. If you are using hundreds of fields with the check, break them up with multiple domain rules using the Attributes to Ignore parameter.

Related topics