Show Navigation | Hide Navigation
You are here:
Geoprocessing tool reference > Geocoding toolbox > Tools

Standardize Addresses (Geocoding)

Release 9.2
Last modified March 30, 2008
E-mail This Topic Printable Version Give Us Feedback

Print all topics in : "Tools"


Related Topics

Standardizes the address information in a table or feature class.

When you create an address locator, the address fields in the reference data that you use for the locator should be standardized according to the geocoding rules used by the address locator. Doing so will increase the geocoding match rate that you can achieve with the address locator.


Usage tips

Command line syntax
An overview of the Command Line window
StandardizeAddresses_geocoding <in_address_data> <in_input_address_fields; in_input_address_fields...> <in_address_locator_style> <in_output_address_fields; in_output_address_fields...> <out_address_data> {Static | Dynamic}

Parameter Explanation Data Type
<in_address_data>

The table or feature class containing address information that you want to standardize.

Table View
<in_input_address_fields; in_input_address_fields...>

The set of fields in the input table or feature class that, when concatenated, form the address to be standardized.

String
<in_address_locator_style>

The address locator style to use to standardize the address information in the input table or feature class. When you specify an ArcSDE address locator style from the command line or within a scripting environment, you must qualify the name of the locator style with the ArcSDE workspace that contains it, as shown in the example below. This parameter does not use the Workspace environment variable.

Address Locator Style
<in_output_address_fields; in_output_address_fields...>

The set of standardized address fields to include in the output table or feature class.

String
<out_address_data>

The output table or feature class to create containing the standardized address fields.

Dataset
{Static | Dynamic}

Indicates whether to create a static or dynamic output dataset.

  • Static — Creates a static copy of the rows or features in the input table or feature class in the output table or feature class.
  • Dynamic — Creates a table containing the standardized address fields that is automatically updated when address fields in the input table or feature class are edited.
By default, the Standardize Addresses command creates Static output. The Dynamic option only works if both the input and output datasets are contained in the same geodatabase workspace.

Boolean
Data types for geoprocessing tool parameters


Command line example

Workspace "D:\Workspace\Madison"
StandardizeAddresses MadisonStreets.shp FID;FULLNAME "US Streets" PreDir;PreType;StreetName;SufDir;SufType StandardizedStreetNetwork.shp

Workspace "D:\Workspace\Madison\Madison.mdb"
StandardizeAddresses MADISON_STREET_NETWORK ID;FULL_STREET_NAME "US Streets" PreDir;PreType;StreetName;SufDir;SufType StandardizedStreetNetwork Static

Workspace "D:\Workspace\Madison\Madison.gdb"
StandardizeAddresses MADISON_STREET_NETWORK ID;FULL_STREET_NAME "US Streets" PreDir;PreType;StreetName;SufDir;SufType StandardizedStreetNetwork Static

Workspace "Database Connections\\mendota.Madison.sde"
StandardizeAddresses Madison.SDE.STREET_NETWORK ID;FULL_STREET_NAME "Database Connections\\mendota.Madison.sde\Address Locator Styles\SDE.US Streets" PreDir;PreType;StreetName;SufType;SufDir StandardizedStreetNetwork Dynamic

Scripting syntax
About getting started with writing geoprocessing scripts
StandardizeAddresses_geocoding (in_address_data, in_input_address_fields, in_address_locator_style, in_output_address_fields, out_address_data, in_relationship_type)

Parameter Explanation Data Type
in_address_data (Required)

The table or feature class containing address information that you want to standardize.

Table View
in_input_address_fields (Required)

The set of fields in the input table or feature class that, when concatenated, form the address to be standardized.

String
in_address_locator_style (Required)

The address locator style to use to standardize the address information in the input table or feature class. When you specify an ArcSDE address locator style from the command line or within a scripting environment, you must qualify the name of the locator style with the ArcSDE workspace that contains it, as shown in the example below. This parameter does not use the Workspace environment variable.

Address Locator Style
in_output_address_fields (Required)

The set of standardized address fields to include in the output table or feature class.

String
out_address_data (Required)

The output table or feature class to create containing the standardized address fields.

Dataset
in_relationship_type (Optional)

Indicates whether to create a static or dynamic output dataset.

  • Static — Creates a static copy of the rows or features in the input table or feature class in the output table or feature class.
  • Dynamic — Creates a table containing the standardized address fields that is automatically updated when address fields in the input table or feature class are edited.
By default, the Standardize Addresses command creates Static output. The Dynamic option only works if both the input and output datasets are contained in the same geodatabase workspace.

Boolean

Data types for geoprocessing tool parameters


Script example

# Example 1:
#   Standardize a street centerline shapefile and write the results to a new shapefile.
#   Fields containing the standardized address components are added to the new shapefile.
import arcgisscripting
GP = arcgisscripting.create()

try:
    GP.Workspace = "D:\Workspace\Madison"
    input_shapefile = "MadisonStreets.shp"
    address_fields = "FID;FullName"
    locator_style = "US Streets"
    standardized_fields = "PreDir;PreType;StreetName;SufType;SufDir"
    standardized_shapefile = "StandardizedStreetNetwork.shp"
    GP.StandardizeAddresses(input_shapefile, address_fields, locator_style, standardized_fields, standardized_shapefile)

except:
    print GP.GetMessages(2)

# Example 2:
#   Standardize a street centerline feature class in a personal or file geodatabase. Use the Static 
#   option to create a new feature class inside the same personal or file geodatabase. Edits made to the input feature class
#   will not be reflected in the standardized feature class.
import arcgisscripting
GP = arcgisscripting.create()

try:
    # Modify the following line to specify a file geodatabase workspace such as "D:\Workspace\Madison\Madison.gdb"
    GP.Workspace = "D:\Workspace\Madison\Madison.mdb"
    input_feature_class = "MADISON_STREET_NETWORK"
    address_fields = "ID;FULL_STREET_NAME"
    locator_style = "US Streets"
    standardized_fields = "PreDir;PreType;StreetName;SufType;SufDir"
    standardized_feature_class = "StandardizedStreetNetwork"
    GP.StandardizeAddresses(input_feature_class, address_fields, locator_style, standardized_fields, standardized_feature_class, "Static")

except:
    print GP.GetMessages(2)

# Example 3:
#   Standardize a street centerline feature class in an ArcSDE geodatabase. Use the Dynamic option
#   to create a new table inside the ArcSDE database that contains the standardized address fields. A relationship
#   class to the original feature class ensures that updates to the original feature class are automatically reflected
#   in the standardized table.
import arcgisscripting
GP = arcgisscripting.create()

try:
    GP.Workspace = "Database Connections\\mendota.Madison.sde"
    input_feature_class = "Database Connections\\mendota.Madison.sde\\Madison.SDE.STREET_NETWORK"
    address_fields = "ID;FULL_STREET_NAME"
    locator_style = "Database Connections\\mendota.Madison.sde\\Address Locator Styles\\SDE.US Streets"
    standardized_fields = "PreDir;PreType;StreetName;SufType;SufDir"
    standardized_table = "StandardizedStreetName"
    GP.StandardizeAddresses(input_feature_class, address_fields, locator_style, standardized_fields, standardized_table, "Dynamic")

except:
    print GP.GetMessages(2)

Please visit the Feedback page to comment or give suggestions on ArcGIS Desktop Help.
Copyright © Environmental Systems Research Institute, Inc.