Status codes and other informational output

The Address Verification stage status codes indicate how an address was validated or modified during processing. In your output columns, you can view return status codes that result from processing your data.

Validation status

You view output columns to assess the validity of addresses. The status value in the columns indicates whether the input address is correct or can be corrected. The status indicates whether an address entry is accurate enough for delivery or whether the entry was not corrected. If the validation process fails, the processing defaults to the parsing process.

The following reporting columns for validation status are available:

AccuracyCode_QSAV

Contains an alphanumeric code that describes the status of verification and parsing and the level of processing and postal codes for each address entry. The code also includes a match score. A sample accuracy code is V33-I33-P6-100. In the following table, each position of the code is described.

Table 1. Character position and description of accuracy code
Character position	Description
First	The verification status.
Second	The postprocessed match level.
Third	The preprocessed match level.
Fourth	Hyphen (-).
Fifth. Follows the first hyphen (-).	The parsing status.
Sixth	The lexicon match level.
Seventh	The context match level.
Eighth	Hyphen (-).
Ninth and 10th. Follows the second hyphen (-)	The postal code status.
11th	Hyphen (-).
12th to 14th. Follows the third hyphen (-)	The accuracy match score. See Match score for information about match scores.

An accuracy code of V33-I33-P6-100 indicates that the input data was verified and that the match verification level for the address entry did not change after processing. By looking at the status code, you can also interpret that address lexicons and address context matched at the same level. The lexicon match process did not provide a more accurate or less accurate address entry match than the context match process.

Verification status

Describes the results of attempts to match the input record with the reference data. The status codes are listed in the following table.

Table 2. Values and descriptions of verification statuses
Value	Status	Description
V	Verified	A complete match was made between the input data and one record in the reference data.
P	Partially Verified.	A partial match was made between the input data and a single record from the available reference data.
U	Unverified.	The data could not be verified. Output fields contain the input data.
A	Ambiguous	More than one close match was made between the input data and reference data
C	Conflict	More than one close match was made between the input data and reference data but several values conflict.
R	Reverted	Record cannot be verified at the specified acceptable level. The output fields contain the input data.

The verification status values are also used in the GeoAccuracy_QSAV column.

In the example status code V33-I33-P6-100, the V character in the first character position indicates that the input data was verified.

Preprocessed and postprocessed match level

Provide the level at which the input data matches the reference data. Preprocessing and postprocessing levels are provided so that you can compare and assess improvement. The postprocessed level is the state of an address entry after all changes and additions are made.

In the example status code V33-I33-P6-100, the characters 3 and 3 are in the second and third character positions. These characters indicate that the input data matched the reference data at the thoroughfare level before and after processing occurred.

Parsing status

Indicates the degree to which address entries are parsed. The status codes are listed in the following table.

Table 3. Values and descriptions of parse statuses
Value	Status	Description
I	Identified and Parsed.	Input data was identified and placed into components.
U	Unable to parse	Not all input data was identified and parsed.

In the example status code V33-I33-P6-100, the I character in the fifth character position indicates that the input data was identified and parsed.

Lexicon match level

Lexicon matching is done by using pattern matching. An example of lexicon matching is identifying rd as equal to the thoroughfare pattern type, in this case, Road. The value London is identified as matching the pattern type of locality. The match level is the level at which the input data has some recognized form. For example, a number value is matched against a pattern type for premise numbers. See Table 5.

In the example status code V33-I33-P6-100, the 3 character in the sixth character position indicates that the lexicon matched at the thoroughfare level.

Context match level

Context matching is less accurate than lexicon matching. Context matching is based on identifying an entry by assessing the entries around it. For example, to identify thoroughfare, the stage assesses the value type of the preceding field, such as premise. Then the stage assesses the value type of the field that follows, verifying that the following value fits the type locality. The types of premise and locality are identified through a match against the reference data or the lexicon (pattern). The match level is the level at which the input data can be recognized based on the context in which it is used. The match level in the thoroughfare example is 3. See Table 5.

In the example status code V33-I33-P6-100, the 3 character in the seventh character position indicates that the context matched at the thoroughfare level.

Postal code status

Provides details about the postal code and processing for each address entry. The status codes are listed in the following table.

Table 4. Values and descriptions of postal code statuses
Value	Description
P8	PostalCodePrimary and PostalCodeSecondary verified
P7	PostalCodePrimary verified, PostalCodeSecondary added or changed
P6	PostalCodePrimary verified
P5	PostalCodePrimary verified with small change
P4	PostalCodePrimary verified with large change
P3	PostalCodePrimary added
P2	PostalCodePrimary identified by lexicon match
P1	PostalCodePrimary identified by context match
P0	PostalCodePrimary empty

In the example status code V33-I33-P6-100, the characters P6 in the ninth and tenth character positions indicates that the PostalCodePrimary was verified.

Table 5 shows the level values used for postprocessed, preprocessed, lexicon, and context match levels, and also the geocoding level.

Table 5. Address levels used in statuses and descriptions
Level	Description
5	Delivery point, post office box, or subbuilding.
4	Premise or building.
3	Thoroughfare. An example might be a suburb, a neighborhood, or section of a town or city.
2	Locality. An example might be an area that is outside of a city or town but within a specific radius.
1	Administrative area. An example might be a province, district, or county.
0	No validation processing performed. Addresses that cannot be validated or corrected are left unchanged in the output.

Geocode status

You can include information about the geographic location of addresses. You can select the geographic location option when you configure the stage for address validation. The output includes columns that contain geographic information and status about the addresses. The output columns for geocoding are as follows:

GeoAccuracy_QSAV: An indication of accuracy and geocoding level. The GeoAccuracy code consists of accuracy status and level. A sample of a status code is P3. P is the status, Partially verified, and 3 is the level, thoroughfare. For level definitions, see Table 5. For geographic value definitions, see Table 6.

Latitude_QSAV: Provides the latitude for addresses. For example: 42.53930

Longitude_QSAV: Provides the longitude for addresses. For example: 71.50399

Table 6 shows the values used for geocoding status.

Table 6. Geocoding values and descriptions
Value	Description
P	Point. A single geocode was found that matches the input address.
I	Interpolated. A geocode was able to be interpolated from the input addresses location in a range.
A	Average. Multiple candidate geocodes were found to match the input address, and an average of these geocodes was returned.
U	Unable to geocode. A geocode was not able to be generated for the input address.

Match score

Input data is compared with the reference data. The degree of similarity is called the match score. The last three character positions in the AccuracyCode_QSAV column are the match score. The accuracy match score indicates the similarity between the input data and closest reference data match as a percentage in the range of 0 - 100. 100% indicates complete similarity.

When you validate addresses and include the AccuracyCode_QSAV column in the output, you see match scores for input addresses that are considered whole. You can also, optionally, include match scores for each address field entry in the output.

The output columns for field-specific match scores are generally titled clearly. For example, HouseNumberMatchScore_QSAV is the match score for a house number field in an address entry. SubBuildingNumberMatchScore_QSAV is the match score of a subbuilding number in an address entry.

Address field status

The address field status codes describe how each address field was handled during the validation process. The status codes are listed in the following table.

Table 7. Values and descriptions of address fields statuses
Value	Description
0	Field is not applicable to returned field status.
1	Field was verified by using relevant reference data. No changes were needed.
2	Field was verified by using relevant reference data. An alias change was made.
3	Field was verified by using relevant reference data. A minor spelling change was made.
4	Field was verified by using relevant reference data. A large spelling change was made.
5	Field was added by using relevant reference data
6	Field was identified by using relevant lexicon data. No changes were needed.
7	Field was identified by using relevant lexicon data. An alias change was made.
8	Field was identified by using relevant context rules.
9	Field is empty.
10	Field was unrecognized.