Available with Data Reviewer license.
Tutorial summary
After adding attribute rules to the data, the evaluation process runs the rules on the data to ensure rules are followed. The evaluation method used depends on the rule type and properties. Validation rules are evaluated manually or at the specified time you set, while constraint rules are evaluated immediately during an edit operation. In this exercise, you will use the Reviewer attribute rules from the previous exercises to identify features that do not meet quality requirements.
Note:
This exercise is preloaded with the Reviewer attribute rules in case you didn't complete the previous exercises.
You will use the errors found during data review to identify and correct features that do not meet quality requirements.
Estimated time | 25 minutes |
Software requirements | ArcGIS Pro 2.7 or later |
Data requirements | The data for this tutorial is available from the Data Reviewer for ArcGIS Pro Tutorial page. This package contains an ArcGIS Pro project package and a subset of the Local Government sample data. To download the data, follow these steps:
|
Open the project
In this exercise, you will open a project package using ArcGIS Pro and verify its contents.
- Start
ArcGIS Pro and sign in if necessary.
Caution:
If you have not already downloaded the Data Reviewer for ArcGIS Pro tutorial data, see the data requirements listed above.
- On the start page, under your recent projects, click Open another project.
Note:
If you already have a project open, click Open on the Quick Access Toolbar and go to step 4.
- On the Open page, under Open, click Computer and click Browse .
- Browse to the folder where you downloaded and extracted the tutorial data: <extracted location>\DataReviewer_AttributeRules\Evaluating_features_with_Attribute_Rules.
- Click DataReviewer_AttributeRulesTutorial_EvaluatingFeaturesWithAttributeRules.aprx.
- Click OK.
The project opens with a topographic basemap containing city data zoomed to Naperville, Illinois.
Evaluate attribute validation rules
The following table outlines a subset of data quality requirements that support address-finding workflows, for which attribute validation rules were created. You will use these attribute validation rules to ensure that all address-related features are compliant with these requirements.
ID | Requirement | Check | Participating feature class/table |
---|---|---|---|
1 | Road features must not contain duplicates. | Duplicate Feature | Road Centerline |
2 | Road vertices must not exist within one foot from each other. | Duplicate Vertex | Road Centerline |
3 | Road centerline Full Road Name attribute values must match the master street index. | Table to Table Attribute | Road Centerline, Master Road Name |
Validate features with attribute validation rules
Validation rules are evaluated at the time you specify. In this exercise, you'll use the Error Inspector pane to run the rules on a file geodatabase.
- In the Contents pane, right-click any layer in the Site Addresses or Roads group, and click Add Error Layers.
The error layers are added to the map.
- On the Map tab, click Bookmarks and choose Study Area to adjust your map extent.
- On the Edit tab, in the Manage Edits group, click Error Inspector .
The Error Inspector pane opens and displays any existing error results.
- On the Error Inspector pane, on the Evaluate Rules button , click the drop-down arrow and uncheck the Batch Calculation option.
Tip:
Ensure that Visible Extent is checked to limit the evaluation area to your current map extent.
- Click the Evaluate Rules button .
Review and correct an error result
You will now review and fix an error in the Error Inspector pane.
- Click the options button and click Show Status.
- In the Filter group, click Fields .
- In the Severity section, check the 1 check box to sort by severity of 1.
One error remains with the rule name Road name missing from master street list.
- Double-click on the empty column next to the error phase to highlight the feature that has the error.
- On the Edit tab, click the Attributes button to open the Attributes pane.
- Click the Select By Rectangle button and select the road with the error.
The road appears in the Attributes pane.
- Click Summit Hills Lm to select it.
- In the attributes, scroll to Full Road Name and change Lm to Ln, then press Enter.
- Click Apply.
- Click the Save Edits button on the Edit tab and click Yes to save your edit.
- Click the Clear Selected button to clear your selection.
- Click the Evaluate Rules button .
The error you corrected appears in the Error Inspector pane with the verified status.
Validate features with attribute constraint rules
In this exercise, you will edit data and introduce errors so that you can see how the attribute constraint rules checks that your edits meet the quality requirements.
The following table outlines a subset of data quality requirements that support address-finding workflows, for which attribute constraint rules were created. You will use requirement #3 where the road length must be greater than 20 feet to ensure that your edits are compliant.
ID | Requirement | Check | Participating feature class/table |
---|---|---|---|
1 | Road centerline must split at an intersection. | Feature on Feature | Road Centerline |
2 | Road centerline must not have sharp angles of 15 degrees or less. | Cutbacks | Road Centerline |
3 | Road length must be greater than 20 feet. | Evaluate Polyline Length | Road Centerline |
- In the Edit tab, click the Create Features button .
The Create Features pane appears.
- Click the Roads: Local Streets template in the Create Features pane.
- Draw a small road in the map.
An error appears in the Create Features pane that details the requirements of the rule and informs you that the edit could not be completed.
- Draw the road with a distance greater than 20 feet to correct the error.
- Click the Save Edits button on the Edit tab and click Yes if asked to save your edits.
You have completed the quality assurance workflow by evaluating rules and error results to validate your data using configured checks implemented using Reviewer attribute rules.