Configure Address Data Management

In this topic, you will learn how to configure the Address Data Management solution to meet specific needs in your organization.

Configure address data management project

The Address Data Management solution includes an ArcGIS Pro project and sample data you can use to explore data management workflows. When you are ready to configure the project, a series of tasks are included to help you review the schema, make modifications to the maps and layers, load your data, and optionally migrate into your ArcGIS Enterprise.

  1. Sign in to your ArcGIS organization and browse to the Address Data Management Application Template.
  2. Open the item page, click Download.
  3. Unzip and open the Address Data Management ArcGIS Pro project.
  4. On the View tab, in the Windows group, click Catalog Pane.
  5. In the Catalog pane, expand the Tasks folder, and double-click on the Address Data Management task item.
  6. In the Task pane, click on the Configure Address Data Management task group to expand the collection of tasks.

Review schema

Included in the solution is a data dictionary that describes the feature classes, relationship classes, and domains included in the Address Data Management geodatabase.

To review the data dictionary, browse to the Data Dictionary.Htm file included with the Address Data Management project and open in your default web browser.

Define spatial reference

The Address Data Management project comes with two file geodatabases. Address Data Management Sample.gdb contains data designed to help test workflows supported in the solution.

The Address Data Management.gdb is an empty geodatabase with the same schema and a spatial reference set to Web Mercator. This geodatabase can be used to define your spatial reference and load your data.

To define the spatial reference, follow the steps in the Define spatial reference task.

Configure maps, layers and rules

The Address Data Management solution leverages pre-configured attribute rules to automate many of the editing workflows. For example, when you create a new address point a unique id is automatically generated for the point.

In some cases, you may need to modify the default schema included with the solution to meet your organization’s needs. If you need to remove or rename fields that are used in any of the attribute rules, the rule will first need to be updated to remove the reference to the field. Adding new fields will not impact the rules. You may also want to add additional rules or configure the feature templates to set the default attributes applied when a feature is created.

To modify the schema, attribute rules, and feature templates of the layers, follow the steps in the Configure maps, layers and rules task.

Load your data

When you have completed any schema modifications you can load your existing data into the Address Data Management layers by following the steps in the Load your data task.

Load into ArcGIS Enterprise

While everything included with the Address Data Management solution is supported in a file geodatabase, some organizations may choose to manage this data in their ArcGIS Enterprise.

To copy the Address Data Management schema into ArcGIS Enterprise, follow the steps in the Load into ArcGIS Enterprise task.

Configure data validation

Data Reviewer can be used to validate, maintain, and improve the integrity of your address data. The Address Data Management map comes with a collection of preconfigured checks that help you identify and resolve common errors in your address data. You can add, remove or modify these checks to meet your organization’s needs.

To modify the Data Reviewer checks, follow the steps in the Configure data validation task.

Use logical block addressing

Logical block addressing uses the starting address, an interval or distance between unique addresses, and the length of the road segment to calculate the address range for the block. If your organization uses logical block addressing, you can configure attribute rules to automatically calculate the left and right to address from the left and right from address.

To enable the logical block addressing attribute rules, complete the following steps:

  1. Start the ArcGIS Pro application and open the Address Data Management project.
  2. In the Contents pane, right-click the Local Streets layer.
  3. From the Design menu select Attribute Rules.
  4. Select the Logical Block Addressing (Left) rule and open the Expression editor.
  5. Update the value for the addressIntervalDistance and unit to the distance your community uses between unique addresses along a road.
    // Specify the interval or distance between unique addresses
    var addressIntervalDistance = 10;
    
    // Specify the unity of measure. Valid options are feet, meters, yards, miles, kilometers
    var unit = "feet";
  6. Click OK.
  7. Click Enable Rule in the Attribute Rules group on the ribbon.
  8. Repeat for the Logical Block Addressing (Right) rule.
  9. Click Save in the Attribute Rules group on the ribbon.

Pull information from an intersecting feature

Additional attribute rules can be configured for the site address layer to automatically pull information from an intersecting feature when the address point is created or updated. For example, you might want to write the name of the municipality, zip code, or the property identification number (PIN) the address falls within and write it to a field within the site address point.

To add an intersecting feature attribute rule to your site addresses layer, complete the following steps:

Note:

This rule requires both the site addresses feature class and the intersecting feature class be in the same database.

  1. In ArcGIS Pro from the Contents pane, right-click the Site Addresses layer.
  2. From the Design menu, select Attribute Rules.
  3. From the Attribute Rules view, click the drop-down next to Add Rule and select Add Immediate Calculation Rule.
  4. Provide a Name and Description for your rule.
  5. From the Field drop-down, select the field in your Site Addresses layer you want to write the attribute from the intersecting feature to.
  6. Click the Expression button to open the Expression Builder.
  7. Copy and paste the code below into the Expression Builder.
    // replace 'FeatureClassName' with the name of the feature class to pull intersecting features from (ex. Cities, ZipCodes, Parcels)
    var intersectingFeatures = Intersects(FeatureSetByName($datastore, "FeatureClassName"), $feature);
    for (var feature in intersectingFeatures) {
         // replace 'fieldname' with the name of the field from the intersecting feature to pull the value from
         var value = feature.fieldname;
          if (IsEmpty(value)) continue;
         return value;
    }
    return null;
  8. In the code find and replace the text "FeatureClassName" with the name of the feature class to to pull intersecting features from (ex. Cities, ZipCodes, Parcels).
  9. In the code find and replace the text "fieldname" with the name of the field from the intersecting feature to pull the value from.
  10. Click the Verify button and click OK to close the Expression Builder.
  11. From Triggers, check Insert. If you would also like the rule to run when the address is moved as well, check Update.
  12. Click Save on the Attribute Rules tab on the ribbon.

    This button will be disabled if you have any pending feature edits. Save or discard your edits to enable the Save button.

    Note:

    The rule should now be active, when you create a new site address point the rule should run and pull the attribute of the intersecting feature into the field specified by the rule. You could repeat the steps above to add additional rules for different feature classes and field values.

    Tip:

    The code above is configured to return null if no intersecting features are found and if multiple intersecting features are found (overlapping polygons) it will return the first non-null feature attribute found. Below are some additional code samples for some other common scenarios.

Return multiple intersecting feature values as comma delimited list

Copy and paste this code into the Expression Builder to return a list.

// replace 'FeatureClassName' with the name of the feature class to pull intersecting features from (ex. Cities, ZipCodes, Parcels)
var intersectingFeatures = Intersects(FeatureSetByName($datastore, "FeatureClassName"), $feature);
var values = [];
for (var feature in intersectingFeatures) {
     // replace 'fieldname' with the name of the field from the intersecting feature to pull the value from
     var value = feature.fieldname;
     if (IsEmpty(value)) continue;
     values [Count(values )] = value;
}
return Concatenate(values, ", ");

Return multiple intersecting feature values as a statistic (Mean, Min, Max, Sum)

Copy and paste this code into the Expression Builder to return statistic values.

// replace 'FeatureClassName' with the name of the feature class to pull intersecting features from (ex. Cities, ZipCodes, Parcels)
var intersectingFeatures = Intersects(FeatureSetByName($datastore, "FeatureClassName"), $feature);
var values = [];
for (var feature in intersectingFeatures) {
     // replace 'fieldname' with the name of the field from the intersecting feature to pull the value from
     var value = feature.fieldname;
     if (IsEmpty(value)) continue;
     values[Count(values)] = value;
}
return Mean(values);

Publish address locators

The address locators described below can be authored in ArcGIS Pro from the layers managed in the Address Data Management solution:

  • Composite
  • Dual Range
  • Site address
  • Road name

Once the locators have been authored, they can be used in ArcGIS Pro to locate places using addresses along the left or right side of a road, rooftop address locations, and road names. The locators can also be shared with your organization and used in many ArcGIS Solutions.

Learn how to create an address locator and more about the components of an address locator in the ArcGIS Pro Help.