Once edits are completed on the feature, a Correction status is applied to the error result.FAQ: What are the build numbers for releases of ArcGIS Desktop? Question 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. 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.
#Arcgis 10.3 release date verification
Initial status for all feature and metadata error resultsĮrror marked as Unacceptable in the Verification phaseĮrror assigned a custom status value prior to the 10.3 releaseĮrror marked as Unresolved in the Correction phase and verified as Unacceptable prior to the 10.3 release Status values applicable to the Review phase include the following: The status value is automatically populated by the tool that created the error result. Review phaseĪ feature or metadata error's initial life cycle status is Review where it awaits evaluation to determine what (if any) corrective action is required. 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. Issues that are determined to have been resolved in an unacceptable manner are returned to the Review phase for additional work.Įrror results that identify errors in your GIS follow a three-phase workflow that enables tracking of correction and verification tasks. While in the Verification phase, an analyst assesses how the issue was resolved to determine whether the action is acceptable or unacceptable.
#Arcgis 10.3 release date pro
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. As an identified error result, it appears in the Reviewer Results pane in the Review phase. For example, a user identifies an issue with a feature and reports it as an error result using the Browse Features tool.
Ideally, an error result moves through each phase where it is reviewed and acted upon by multiple participants in the correction process. Regardless of the source, feature and metadata error results follow a standard quality control life cycle process that passes through three distinct phases: PhaseĮrror result is awaiting further review after discovery.Įrror result has been addressed either through corrective editing of the related feature or marked as an exception.Īctions performed on the related feature are acceptable or the feature should be considered an exception. Data Reviewer tools such as Flag Missing Features and Browse Features capture results based on semi-automated processes such as visual review.
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. 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. Features (or rows) in your GIS identified as not meeting data quality requirements are stored as a Reviewer error result.
0 kommentar(er)
