Mit der Data Reviewer-Lizenz verfügbar.
Features (or rows) in your GIS identified as not meeting data quality requirements are stored as a Reviewer error result. Error results are created when using the Data Reviewer automated and semi-automated tools within your quality control workflow and include metadata describing the issue and, optionally, a geometry. For example, error results are automatically created when using the Evaluate Rules tool in the Error Inspector pane to automate data validation based on attribute rules configured in a feature class or standalone table. Data Reviewer tools such as Flag Missing Features and Browse Features capture results based on semi-automated processes such as visual review.
Regardless of the source, feature and metadata error results follow a standard quality control life cycle process that passes through three distinct phases:
| Phase | Icon | Description |
|---|---|---|
Review |  | Error result is awaiting further review after discovery. |
Correction |  | Error result has been addressed either through corrective editing of the related feature or marked as an exception. |
Verification |  | Actions performed on the related feature are acceptable or the feature should be considered an exception. |
Ideally, an error result moves through each phase where it is reviewed and acted upon by multiple participants in the correction process. For example, a user identifies an issue with a feature and reports it as an error result using the Browse Features tool. As an identified error result, it appears in the Reviewer Results pane in the Review phase. During the Correction phase, a technician assesses the issue and resolves it either by correcting the feature using tools found in ArcGIS Pro or marking it as an exception. While in the Verification phase, an analyst assesses how the issue was resolved to determine whether the action is acceptable or unacceptable. Issues that are determined to have been resolved in an unacceptable manner are returned to the Review phase for additional work.
Feature and metadata results
Error results that identify errors in your GIS follow a three-phase workflow that enables tracking of correction and verification tasks. Information collected during this workflow aids in communicating how the error was corrected, who corrected and verified the error, and when the correction and verification was completed.
Review phase
A feature or metadata error's initial life cycle status is Review where it awaits evaluation to determine what (if any) corrective action is required. The status value is automatically populated by the tool that created the error result. Status values applicable to the Review phase include the following:
| Status | Code | Description | Next valid status |
|---|---|---|---|
Reviewed | 1 | Initial status for all feature and metadata error results | Mark as Exception |
Resolved | |||
Unacceptable | 6 | Error marked as Unacceptable in the Verification phase | Mark as Exception |
Resolved | |||
Unknown | 0 | Error assigned a custom status value prior to the 10.3 release | Mark as Exception |
Resolved | |||
Unresolved unacceptable | 6 | Error marked as Unresolved in the Correction phase and verified as Unacceptable prior to the 10.3 release | Mark as Exception |
Resolved |
Correction phase
The next phase in the Reviewer error result's life cycle is Correction and is when the feature is either edited to address the error condition or marked as an exception. The error result provides information to the editor regarding the error found on the feature, its severity and (optionally) a geometry indicating the location of the specific error. Once edits are completed on the feature, a Correction status is applied to the error result. Status values applicable to the Correction phase include the following:
| Status | Code | Description | Next valid status |
|---|---|---|---|
Resolved | 2 | Corrective action is taken to resolve the issue (as described in the Correction Notes). | Acceptable |
Unacceptable | |||
Mark as Exception | 3 | Error results are marked as an exception case. | Exception |
Unacceptable |
Verification phase
The last phase in an error result's life cycle is Verification. In this phase, any edits or exceptions that have been applied to the feature in error result are verified. Status values applicable to the Verification phase include the following:
| Status | Code | Description | Next valid status |
|---|---|---|---|
Acceptable | 4 | The action performed (as described in the Correction Notes) on the issue is acceptable. | Unacceptable |
Exception | 9 | Error results are verified as an exception case. | Unacceptable |
Unresolved exception | 9 | Error result is marked as Unresolved in the Correction phase and verified as an exception prior to the 10.3 release. | Unacceptable |
Hinweis:
Error results assigned a custom verification status prior to the 10.3 release will have a status of Unknown.
Exceptions
Exceptions are typically discovered during the Correction phase. These are features that may be discovered as the error result of an automated check or visual review and initially thought to be an error; however, during correction they are determined to be acceptable and not needing correction. Marking a error result that originated from an automated check as an exception ensures that the feature is not written as a new error in the future.
Tipp:
It is important not to delete these error results; mark them as exceptions to prevent duplicate results from being created during automated review.
Sampling results
Sampling is a technique used in data quality assessment when it's impractical to individually review all features in your GIS. Sampling results are created using the Sampling Check in ArcMap and follow a shortened life cycle workflow.
Sampling results are an exception to the standard three-phase life cycle process (Review, Correction, Verification) due to the unique role they serve in assessing data quality in semi-automated workflows.
Review phase
A sampling result's initial life cycle phase is Review with a status of New. Sampling results move directly from the Review phase to the Verification phase.
Status values applicable to the Review phase for samples include the following:
| Status | Code | Description | Next valid status |
|---|---|---|---|
New | 10 | Initial status for a sampling result | Fail |
Pass | |||
Unknown | 0 | Sample marked as Failed and processed as a feature result prior to the 10.3 release | Fail |
Pass |
Verification phase
After a sampling result has passed the Review phase, it progresses to the Verification phase with possible life cycle status values of Pass or Fail.
Status values applicable to the Verification phase for samples include the following:
| Status | Code | Description | Next valid status |
|---|---|---|---|
Passed | 11 | Sampled feature has passed inspection | Fail |
Fail | 12 | Sampled feature has failed inspection | Pass |