Available with Data Reviewer license.
ArcGIS Data Reviewer provides the following options for implementing automated review:
- Reviewer rules in a geodatabase
- Run data checks
- Reviewer batch jobs
Legacy:
ArcMap-based Reviewer workflows will soon be deprecated. It is recommended that current users begin converting their workflows from Reviewer batch jobs to Data Reviewer attribute rules.
These capabilities are flexible and scalable to accommodate both small and large deployments. Depending on the needs of your organization and your deployment, you can automate data review of features from multiple sources, such as those stored in shapefiles, geodatabase feature classes and stand-alone tables, and web feature layers from ArcGIS Enterprise.
Reviewer rules in a geodatabase (attribute rule-based workflows)
Reviewer geodatabase rules are configured Data Reviewer checks that validate geodatabase feature classes and stand-alone tables using attribute rule-based workflows. Rules are created using tools in ArcGIS Pro and are stored in a geodatabase that can be shared by exporting to a CSV or XML workspace document file.
Consider the following licensing requirements when implementing Reviewer-based attribute rule workflows:
- A Data Reviewer license for ArcGIS Pro and an ArcGIS Pro Standard or Advanced license are both required to create or modify a Reviewer-based attribute rule.
- A Data Reviewer license for ArcGIS Pro and an ArcGIS Pro Standard or Advanced license are both required to evaluate a Reviewer-based validation attribute rule in a file or mobile geodatabase.
- A Data Reviewer license for Enterprise and an ArcGIS Server Standard or Advanced license are both required to evaluate a Reviewer-based validation attribute rule in a branch versioned enterprise geodatabase.
Consider the following when implementing automated review using Reviewer geodatabase rules:
- Rules are created using tools in ArcGIS Pro.
- Geodatabase rules enable assessment of a feature’s quality during (constraint attribute rule) and after editing (validation attribute rule).
- Features and rows stored in geodatabase feature classes and stand-alone tables are supported.
- Errors are stored in system-maintained tables along with production data.
- Global IDs and editor tracking are required.
- Error phase and status information are managed automatically for errors created using validation attribute rules.
Run Data Checks
The Run Data Checks tool includes Data Reviewer checks that validate feature layers referenced in a map quickly without having to complete the full attribute-rule based workflow and configuration. The check results are stored in a temporary geodatabase and added to the map as feature layers for review.
Consider the following when implementing automated review using the Run Data Checks tool:
- Rules are created using tools in ArcGIS Pro.
- A read-only permission on source data is required for creating rules.
- Validation of features is supported using ArcGIS Pro (Run Data Checks command).
- Features from file and mobile geodatabases are supported.
- Errors are stored in a temporary geodatabase created during an ArcGIS Pro session. The geodatabase gets deleted once ArcGIS Pro is closed.
- Global IDs and editor tracking are not required.
Reviewer batch jobs
Reviewer batch jobs contain configured Data Reviewer checks that validate features stored in feature classes (for example, geodatabase feature classes or shapefiles) and stand-alone tables. Batch jobs are created using tools in ArcMap and stored in a file (.rbj) that can be shared using project templates and packages in ArcGIS Pro.
Consider the following when implementing automated review using batch jobs:
- Rules are created using tools in ArcMap.
- A read-only permission on source data is required to create rules.
- Validation of features is supported using ArcMap (Batch Validate tool), geoprocessing (Execute Reviewer Batch Job tool), and ArcGIS Workflow Manager (Classic) (Run Reviewer Batch Job step).
- Features from multiple data sources (geodatabases and shapefiles) are supported.
- Nonversioned and traditional versioned geodatabase sources are supported.
- Errors are stored in a specified geodatabase in a Reviewer dataset.
- Error phase and status information are managed manually using ArcMap (Reviewer table) or ArcGIS Pro (Reviewer Results pane).
Learn more about migrating from ArcMap to ArcGIS Pro for data validation