Preparing data for address management

Esri Roads and Highways provides tools to manage address data, including address block ranges, site address points, and street names on top of an LRS. If you are a state or federal government, these tools enable you to manage address data for geocoders for data provided from local government agencies on your LRS. If you are a local government, you can use the LRS to not only manage roadway inventory data but also address data, thereby managing one centerline for both.

The following sections discuss how to model and load your address block ranges, site address points, and street names data into the data model needed by Esri Roads and Highways.

Model

The following are the model's expectations:

Address block ranges

Address block ranges are modeled as a linear event layer (event feature class) on a network, with referent columns that need to be populated with intersection referents.

If using the ArcGIS for Local Government data model, the RoadCenterline feature class should be used as the Address block range event layer. Add the missing columns from the list below.

For more information about LRS events, see Event types.

For more information, see Storing referent and offset information for event location.

The following fields are required:

Field	Data Type	Length	IsNullable	Description
EventID	String	Between 32 and 255	Yes	Unique ID for each event record.
RouteID	String	Length of the Network RouteID field or greater	Yes	Unique ID for each route in the network.
FromDate	Date	8	Yes	The date the event became active on the route.
ToDate	Date	8	Yes	The date the event was retired on the route.
FromMeasure	Any Numeric		Yes	The measure on the route where the beginning of the event will be located.
ToMeasure	Any Numeric		Yes	The measure on the route where the end of the event will be located.
FromReferentMethod	Short Integer	5	Yes	Method of referencing the offset feature. Can be X,Y coordinates, Stationing, Length, LRS Network, Event, Intersection, or other point feature class. For the Block range event, it will be the Intersection feature class.
FromReferentLocation	String	Between 50 and 255	Yes	Location of the offsetting feature. Can be an X,Y coordinate, Feature/EventID, or IntersectionID. For the Block range event, it will be the IntersectionID.
FromReferentOffset	String	Between 50 and 255	Yes	The offset measure. Saved in the unit of measure configured when configuring offset fields. Since block range goes from intersection to intersection, this value will be zero.
ToReferentMethod	Short Integer	5	Yes	Method of referencing the offset feature. Can be X,Y coordinates, Stationing, Length, LRS Network, Event, Intersection, or other point feature class. For the Block range event, it will be the Intersection feature class.
ToReferentLocation	String	Between 50 and 255	Yes	Location of the offsetting feature. Can be an X,Y coordinate, Feature/EventID, or IntersectionID. For the Block range event, it will be the IntersectionID.
ToReferentOffset	String	Between 50 and 255	Yes	The offset measure. Saved in the unit of measure configured when configuring offset fields. Since block range goes from intersection to intersection, this value will be zero.
RightFromAddress	Any Numeric		Yes	Stores the lowest address value on the right side of the road.
RightToAddress	Any Numeric		Yes	Stores the highest address value on the right side of the road.
LeftFromAddress	Any Numeric		Yes	Stores the lowest address value on the left side of the road.
LeftToAddress	Any Numeric		Yes	Stores the highest address value on the left side of the road.
FullStreetName	String	Length of the full street name from Master street table or greater	Yes	The full street name including its prefix or suffix.

Site address points

Site address points are modeled as a point feature class that store the rooftop location of an address.

If using the ArcGIS for Local Government data model, the SiteAddressPoint feature class should be used as the Site Address points layer. For more information, see Local Government Information Model.

The following columns are required:

Field	Data Type	Length	IsNullable	Description
addressNumber	Any Numeric		Yes	Address number field that stores the address number
FullStreetName	String	Length of the full street name from Master street table or greater	Yes	Street name field, which will save the full street name including its prefix or suffix

Master street table

The Master street table stores the unique street names along with other street name attributes.

If using the ArcGIS for Local Government data model, the MasterStreetName table should be used as the Master street table.

The following columns are required:

Field	Data Type	Length	IsNullable	Description
FullStreetName	String	Length of the full street name from Master street table or greater	Yes	Street name field, which will save the full street name including its prefix or suffix

The Address Management tools can be configured against the ArcGIS for Local Government data model or your own custom model, given that your model contains the required fields mentioned above.

Prerequisite

For more information about Esri Roads and Highways linear referencing model and the data loading process, see ALRS Data Model and Creating and loading the ALRS.

Use following steps to set up the address management data using Esri Roads and Highways.

1. Create an ALRS if you have not already in the enterprise geodatabase of your choice.

   For more information, see Creating a new ALRS.

2. Create an LRS network if you do not already have one.

   For more information, see Creating an LRS network.

   Note:

   If you are using the ArcGIS for Local Government data model and do not currently use linear referencing as a means to manage roadway data, then you may want to create an LRS network that is based on the spatial geometry length for measures.

3. Prepare the data to load as routes. If you are managing the block range information on a road centerline, then most likely you need to dissolve them to get single polyline geometry for each route.

   The following diagram explains the concept of dissolving the block ranges to the route, which is expected by Esri Roads and Highways.

   

   1. Open the Dissolve geoprocessing tool.
   2. Choose a dissolve field.

      In this example, Route ID is used.

      Note:

      If you are using the ArcGIS for Local Government data model, you can create a new field by concatenating the full road name with any other field that can help you identify the unique route or use full road name if it is unique.

   3. Select Multipart feature as True.

      The following image shows a sample screen capture of the Dissolve geoprocessing tool:

      

4. Load the routes to the network.

   For more information, see Loading Routes.

5. Create an LRS intersection class.

   For more information, see Creating an LRS intersection class.

   1. Select the option Add measure column to the intersection feature class during generation or registration.

      

   2. Use the same route network when creating an LRS intersection class.

      

6. Prepare block range data to register as an event.

   If your block range feature class does not have the measures associated with it, which will be the case if you do not use linear referencing as a means to manage roadway data, use the Locate Features Along Routes geoprocessing tool to populate the measures as follows. For more information, see Locate features along routes.

   1. Use your block range feature class as an event layer input.
   2. Use the network registered in step 2 as an input for the input route feature class.
   3. The route ID field should be populated and should match with routes you loaded.
   4. The output of the tool is a new feature class, so use the output feature class going forward.

      You can archive the existing block range feature class. The following image shows the sample screen capture of the Locate Features Along Routes geoprocessing tool:

      

7. Register an LRS line event with referent location for the Block Range data.
   1. Register an LRS event by route and measure.

      For more information, see Registering an event by route and measure. The following is a sample screen capture of the event registration step:

      

   2. During registration in the Event Behavior Rules dialog box, for the CartoRealign Route activity choose the Honor Referent location event behavior, and for all other edit activities, choose the Stay Put event behavior.

      For more information, see Event behaviors. The following is a sample screen capture of the event registration step:

      

8. For each block range event, populate From and To reference intersection information.

   For more information about reference information, see Storing referent and offset information for event location. You need to do it manually using ArcGIS tools or a Python script. The following diagram explains the concept of populating From and To reference intersection information, which is expected by Esri Roads and Highways.

   

   1. Intersect the start point of the block range line feature class with the intersection point feature class.
   2. From the intersect output, filter out the result that does not match the RouteID of block range.
   3. When the event's EventID and RouteID matches the intersect output derived from step b, populate the referent offset fields.
   4. Populate the code for your interaction class from the dReferentMethod domain into the From Referent Method.
   5. Populate the IntersectionID into the From Referent Location field.
   6. Since block ranges go from intersection to intersection, the From Referent Offset is zero.
   7. Repeat steps a through f for the block range end point to populate the To Referent fields.
9. Once you have your data prepared, you can publish a map service.
   1. Create a map document and minimally add Route layer, Intersection layer, Block range event layer, Site address point feature layer, and Master street Table.
   2. Publish the map document with ArcGIS for Server and enable the Esri Roads and Highways for Server Linear Referencing and Feature Access capability.
10. Deploy the Roadway Characteristics Editor.

    For more information, see the Roadway Characteristics Editor deployment guide.

11. Configure the Roadway Characteristics Editor.

    For more information, see Configuring the Roadway Characteristics Editor web application.

12. Configure the Address Management widget.

    For more information, see Configuring the Address Management widgets.