Author and share Reviewer rules in a map

Available with Data Reviewer license.

Tutorial summary

In this tutorial, you will assume the role of a technical lead who identifies data quality requirements and the workflows that implement them. You will do this by implementing automated quality control using ArcGIS Data Reviewer’s validation checks to assess the quality of features referenced in a map. You will then share this map so that others in your organization can assess the quality of their own data.

Estimated time	25 minutes
Software requirements	ArcGIS Pro 2.1 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: Go to the Data Reviewer for ArcGIS Pro Tutorial page. Click Download. Extract the files to a convenient location on your computer, such as C:\Data_Reviewer_for_ArcGIS_Pro_Tutorial.

Open the project

In this exercise, you will open a project package using ArcGIS Pro and verify its content you will assume the role of a quality manager. You will assess organizational business rules and create a set of Reviewer rules for others in your organization to use. Your data will include reference layers and critical feature classes that must be validated in your geodatabase.

1. 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.

2. 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.

3. On the Open page, under Open, click Computer and click Browse .
4. Browse to the Data_Reviewer\Exercise_2 folder on the Open Project dialog box.

   Note:

   The Data_Reviewer\Exercise_2 folder is located in the directory where the Data Reviewer for ArcGIS Pro tutorial package was extracted.

5. Click DataReviewerArcGISProTutorial_Exercise2.ppkx.
6. Click OK.
The project opens with a topographic basemap containing city data zoomed to Naperville, Illinois.

Author Reviewer rules in a map

Reviewer rules are configured checks that validate features based on specific conditions. They can include checks that validate spatial relationships, attribute consistency and feature integrity. Reviewer rules can be authored and stored in a map that contains the feature layers to be validated. Features in your map are validated using the Run Reviewer Rules command.

In this exercise, you will author a series of Reviewer rules and apply them to relevant layers in your map. The following table outlines a subset of data quality requirements that support address-finding workflows. You will implement these rules as Reviewer rules to ensure that all address-related features are compliant with these requirements.

ID	Requirement	Check	Participating layers
1	Road centerline FROMLEFT attribute values must not be zero and must be odd. Road centerlines must also be owned by Our Agency.	Query Attributes (with filter)	Road Centerline
2	Road centerline FROMRIGHT attribute values must not be zero and must be even. Road centerlines must also be owned by Our Agency.	Query Attributes (with filter)	Road Centerline
3	Polyline and polygon features must not contain an angle less than 25 degrees.	Cutbacks	Road Centerlines, Building Footprints, Railroads, and Waterlines

1. Click the View tab.
2. In the Windows group, click Reviewer Rules .

   The Reviewer Rules view appears.

Implement requirement ID 1

Perform the following steps to implement requirement ID 1 from the table above—Road centerline features owned by Our Agency must not have FROMLEFT values equal to zero and must be odd.

1. On the Reviewer Rules tab, in the New Rule group, click Query Attributes to add a new rule.

   The new rule appears in the Reviewer Rules view with a red row header, indicating that required parameters are missing from the rule configuration.

   

2. On the Query Attributes check panel, in the Data Sources group, click the Road Centerlines check box.

   

3. Configure a filter on the Road Centerlines layer so that validation will only return results on roads that are owned by Our Agency.
   1. Hover over Road Centerlines and click the Forward button .

      The filter parameters for the selected layer appear in the pane.

   2. Click the New expression drop-down arrow and click Create a new expression.
   3. Construct the following clause: Owned By is equal to 1-Our Agency.
   4. Click the Verify the SQL expression is valid button to validate the SQL expression.
   5. Click the Back button to return to the Query Attributes check panel.
4. On the Query Attributes check panel, hover over the information icon to the right of Road Centerlines to confirm that the filter has been applied.

   Note:

   The above query is only associated with the Road Centerlines layer.

5. On the Query Attributes check panel, in the Check Parameters group, click the New expression drop-down arrow and click Create a new expression in SQL to configure the Search Goal parameter.
   1. Construct the following SQL query in the Search Goal text box: FROMLEFT <> 0 AND (MOD (FROMLEFT, 2) = 0).

      Tip:

      The SQL MOD function is used to get the remainder from a division. In this example, features that have a FROMLEFT value that does not have a remainder when divided by 2 will be returned as a result.

   2. Click the Verify the SQL expression is valid button to validate the SQL expression.
   3. Click Apply.
6. On the Query Attributes check panel, in the Result Details group, configure the properties that will be stored for each result that has features that fail validation.
   1. Type Road Centerline From Left address must be odd in the Title text box.
   2. Type Update From Left Address value in the Notes text box.
   3. Click the Severity drop-down arrow and choose 2 to set the relative importance for results of this type compared to others.
   4. Type LGIM 2016, thematic accuracy, attributes in the Tags text box.

      Tip:

      Tags can be used to enable requirements traceability. Consider including the data model and version for which the rule is related or possibly including an ISO-19157 data quality element, such as thematic accuracy.

Implement requirement ID 2

Perform the following steps to implement requirement ID 2 from the table above—Road centerline features owned by Our Agency must not have FROMRIGHT attribute values equal to zero and must be even.

1. On the Reviewer Rules tab, in the New Rule group, click Query Attributes to add a new rule.

   The new rule appears in the Reviewer Rules view with a red row header, indicating that required parameters are missing from the rule configuration.

2. On the Query Attributes check panel, in the Data Sources group, click the Road Centerlines check box.

   

3. Configure a filter on the Road Centerlines layer so that validation will only return results on roads that are owned by Our Agency.
   1. Hover over Road Centerlines and click the Forward button .

      The filter parameters for the selected layer appear in the pane.

   2. Click the New expression drop-down arrow and click Create a new expression.
   3. Construct the following clause: Owned By is equal to 1-Our Agency.
   4. Click the Verify the SQL expression is valid button to validate the SQL expression.
   5. Click the Back button to return to the Query Attributes check panel.
4. On the Query Attributes check panel, hover over the information icon to the right of Road Centerlines to confirm that the filter has been applied.

   The above query is only associated with the Road Centerlines layer.

5. On the Query Attributes check panel, in the Check Parameters group, click the New expression drop-down arrow and click Create a new expression in SQL to configure the Search Goal parameter.
   1. Construct the following SQL query in the Search Goal text box: FROMRIGHT <> 0 AND (MOD (FROMRIGHT, 2) = 1).

      Tip:

      The SQL MOD function is used to get the remainder from a division. In this example, features that have a FROMRIGHT value that does not have a remainder when divided by 2 will be returned as a result.

   2. Click the Verify the SQL expression is valid button to validate the SQL expression.
   3. Click Apply.
6. On the Query Attributes check panel, in the Result Details group, configure the properties that will be stored for each result that has features that fail validation.
   1. Type Road Centerline From Right address must be even in the Title text box.
   2. Type Update From Right Address value in the Notes text box.
   3. Click the Severity drop-down arrow and choose 2 to set the relative importance for results of this type compared to others.
   4. Type LGIM 2016, thematic accuracy, attributes in the Tags text box.

Implement requirement ID 3

Perform the following steps to implement requirement ID 3 from the table above—Polyline and polygon features must not contain an angle less than 25 degrees.

1. On the Reviewer Rules tab, in the New Rule group, click Cutbacks to add a new rule.

   The new rule appears in the Reviewer Rules view with a red row header, indicating that required parameters are missing from the rule configuration.

   1. On the Cutbacks Check panel, in the Data Sources group, click the Road Centerlines, Railroads, Waterlines, and Building Footprints check boxes.

      

   2. On the Cutbacks Check panel, in the Check Parameters group, type 25 in the Minimum Angle Size (Required) text box.
2. On the Cutbacks Check panel, in the Result Details group, configure the properties that will be stored for each result that has features that fail validation.
   1. Type Sharp angle detected in the Title text box.
   2. Type Edit feature to remove sharp angle in the Notes text box.
   3. Leave the default Severity option set to 3 to set the relative importance for results of this type compared to others.
   4. Type LGIM 2016, spatial accuracy, geometry in the Tags text box.
3. On the Quick Access Toolbar, click Save to save the project.

   Tip:

   Rule configurations are not stored until the project is saved.

Share Reviewer rules

In this exercise, you will save and share maps containing Reviewer rules with other members of your organization. This can be accomplished in two ways.

Save Reviewer rules as a template

Maps that contain Reviewer rules can be saved in a project template that serves as a starting point when creating new projects. This enables data validation to be standardized by creating new projects from the template. Follow the steps below to save a project as a template.

1. Click the Share tab.
2. In the Save As group, click Project Template .

   The Create Project Template pane appears.

3. Click the Save template to file option.

   

4. Under Name, click the Browse file button .
5. Browse to the location where you want to save your project template (.aptx).
6. Name the template MyReviewerRules.
7. Click Save.
8. Type Reviewer rules used to validate features used in geocoding in the Summary text box.
9. Type Reviewer rules, geocoding, validation in the Tags text box.
10. Click Analyze to validate the project template.

    Note:

    You must resolve all errors. If any issues are discovered, they appear on the Messages tab. Right-click each message to get more information, read the help for the error or warning, and implement suggested fixes.

11. Click Create to create the project template.
12. If you are prompted to save the project, click Yes.

Save Reviewer rules as a map file

Another way to share Reviewer rules is to save them as a map file (.mapx). This method is used if a map needs to be shared between projects. Follow the steps below to save Reviewer rules as a map file:

1. On the Contents pane, under Drawing Order, right-click Map and click Save As Map File.
2. Name the new map file MyReviewerRulesMap.
3. Click Save.
4. On the Quick Access Toolbar, click Save to save the project.

In this exercise, you opened an existing ArcGIS Pro project and authored Reviewer rules in a map that will be used to validate layers used in address-finding workflows. Maps which contain Reviewer rules can be shared in a variety of ways, two of which you tried in this exercise.

Once maps that contain Reviewer rules are shared via one of the methods outlined above, members of your organization have a consistent way of validating data to ensure it meets your business requirements.