Standardize Addresses (Geocoding) |
|
Release 9.2
Last modified March 30, 2008 |
![]() ![]() ![]() Print all topics in : "Tools" |
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
The input address data can be any table or feature class supported by ArcGIS.
If you are using an address locator style that geocodes addresses with house numbers (most address locator styles do this), you must include a field that contains a numeric value that represents the house number in the input address fields. Failing to do so will cause the Standardize Addresses tool to standardize the addresses, with missing house numbers, incorrectly. In most cases, the ObjectID field is a good choice, because this field is guaranteed to have a numeric value.
In most cases, you should choose the address locator style that you will later use to create an address locator using the output of the Standardize Addresses tool.
The output address fields that you select are the standardized address fields that will be written to the output table or feature class. If you are only using the Standardize Addresses tool to standardize the street names in the input table or feature class, then in most cases you will only need to write the standardized fields that contain components of the street name to the output table or feature class. If, however, you are using the Standardize Addresses tool to parse a field that contains an entire address (including the house number), then you should choose to write the standardized house number field to the output as well.
If you choose to create Static output, then all fields from the input table or feature class will be copied to the output table or feature class. The output table or feature class will be the same type (either a table or a feature class) as the input table or feature class.
If your input table or feature class and output table are in the same geodatabase workspace, you can choose to create dynamic output. If you choose this option, then the output table will contain only the standardized address fields that you choose, along with a field that contains a foreign key to the ObjectID in the input table or feature class. If you choose to create dynamic output, subsequent edits that you make to the address fields in the input table or feature class will automatically be reflected in the output table. The output of the Standardize Addresses tool is always a table if you choose to create dynamic output.
By default, the Standardize Addresses tool will create static output, unless you explicitly specify to create dynamic output.
The following environment settings affect this tool: Configuration keyword, workspace, and scratch workspace.
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.
|
Boolean |
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.
|
Boolean |
# 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)