Understanding the Master Index Standardization Engine

Address Data Standardization Components

Standardization engines use tokens to determine how each field is standardized into its individual field components and to determine how to normalize a field value. Tokens also identify the field components to external applications like a master index application. The following table lists each token generated by the Master Index Standardization Engine for address data along with the standardization component they represent. You can only specify the predefined field tokens that are listed in this table for addresses unless you create a new data type or variant.

Table 3 Address Data Tokens


Token	Description
BoxDescript	Represents the PO box type from a standardized address field. By default, this is stored in the `field_name`_StName field in a master index database.
BoxIdentif	Represents the parsed PO box number from a standardized address field. By default, this is stored in the `field_name`_HouseNo field in a master index database.
CenterDescript	Represents the parsed structure description from a standardized address field. This address component is not included in the default master index standardization structure, but you can add it if needed.
CenterIdentif	Represents the parsed structure identifier from a standardized address field. This address component is not included in the default master index standardization structure, but you can add it if needed.
ExtraInfo	Represents any extra information that was not included in any of the other parsed components. This address component is not included in the default standardization structure, but you can add it if needed.
HouseClass	Represents the parsed house classification from a standardized address field. This address component is not included in the default master index standardization structure, but you can add it if needed.
HouseNumber	Represents the parsed house number from a standardized address field. By default, this is stored in the `field_name`_HouseNo field in a master index database.
HouseNumPrefix	Represents the parsed house number prefix from a standardized address field (such as the “A” in “A 1587 4th Street”). This address component is not included in the default master index standardization structure, but you can add it if needed.
HouseNumSuffix	Represents the parsed house number suffix from a standardized address field (such as the “B” in “5900 B Arnett Avenue”). This address component is not included in the default master index standardization structure, but you can add it if needed.
MatchPropertyName	Represents the parsed match property name from a standardized address field and is used internally by the standardization engine for blocking and phonetic encoding. This address component is not included in the default master index standardization structure, but you can add it if needed.
MatchStreetName	Represents the parsed and standardized street name from a standardized address field and is used internally by the standardization engine. If you want to store the standardized street name in the database (recommended), map this field to the street name field in the database. By default, this is stored in the `field_name`_StName field in a master index database.
OrigPropertyName	Represents the parsed original property name (such as the name of a complex or business park) from a standardized address field. This address component is not included in the default master index standardization structure, but you can add it if needed.
PropDesPrefDirection	Represents the parsed property direction from a standardized address field. This field ID handles cases where the direction is a prefix to the property description. By default, this is stored in the `field_name`_StDir field in a master index database.
PropDesPrefType	Represents the parsed property type from a standardized address field. This field ID handles cases where the street type is a prefix to the property description. By default, this is stored in the `field_name`_StType field in a master index database.
PropertySufDirection	Represents the parsed property direction from a standardized address field. This field ID handles cases where the direction is a suffix to the property description. By default, this is stored in the `field_name`_StDir field in a master index database.
PropertySufType	Represents the parsed property type from a standardized address field. This field ID handles cases where the street type is a suffix to the property description. By default, this is stored in the `field_name`_StType field in a master index database.
RuralRouteDescript	Represents the parsed rural route description from a standardized address field. By default, this is stored in the `field_name`_StName field in a master index database.
RuralRouteIdentif	Represents the parsed rural route identifier from a standardized address field. By default, this is stored in the `field_name`_HouseNo field in a master index database.
SecondHouseNumber	Represents the parsed second house number prefix from a standardized address field. This address component is not included in the default master index standardization structure, but you can add it if needed.
SecondHouseNumberPrefix	Represents the parsed second house number prefix from a standardized address field (such as “25” in “25 319 10th Ave.”). This address component is not included in the default master index standardization structure, but you can add it if needed.
SecondStreetNameSufDirection	Represents the parsed second street direction from a standardized address field. This address component is not included in the default standardization structure, but you can add it if needed.
SecondStreetNameSufType	Represents the parsed second street type from a standardized address field. This address component is not included in the default standardization structure, but you can add it if needed.
OrigSecondStreetName	Represents the parsed second street name from a standardized address field (for example, an address might include a cross-street or a thoroughfare and dependent thoroughfare). This address component is not included in the default master index standardization structure, but you can add it if needed.
OrigStreetName	Represents the parsed street name from an address field. If you want to store the original street name in the database, map this field to the street name field in the database. This address component is not included in the default standardization structure, but you can add it if needed.
StreetNamePrefDirection	Represents the parsed street direction from a standardized address field. This field ID handles cases where the direction is a prefix to the street name. By default, this is stored in the `field_name`_StDir field in a master index database.
StreetNamePrefType	Represents the parsed street type from a standardized address field. This field ID handles cases where the street type is a prefix to the street name. By default, this is stored in the `field_name`_StType field in a master index database.
StreetNameSufDirection	Represents the parsed street direction from a standardized address field. This field ID handles cases where the direction is a suffix to the street name. By default, this is stored in the `field_name`_StDir field in a master index database.
StreetNameSufType	Represents the parsed street type from a standardized address field. This field ID handles cases where the street type is a suffix to the street name. By default, this is stored in the `field_name`_StType field in a master index database.
StreetNameExtensionIndex	Represents the parsed street name extension from a standardized address field. This address component is not included in the default standardization structure, but you can add it if needed.
WithinStructDescript	Represents the parsed internal descriptor (such as “Floor”) from a standardized address field. This address component is not included in the default standardization structure, but you can add it if needed.
WithinStructIdentif	Represents the parsed internal identifier (such as a floor number) from a standardized address field. This address component is not included in the default standardization structure, but you can add it if needed.