Address Verification |
The Address Verification processor (AV) is used to verify and standardize address data from any country. It also provides geocoding.
Note: If the processor has not been correctly installed it will still run but all the output fields will be left blank, except for av.Accuracy Code, which will have a value of -1.0.
Use the Address Verification processor:
Note: This processor always appears with a re-run marker, indicating that it will be completely re-executed each time the process is run, regardless of whether or not its configuration has changed. This will also mean that processors that are downstream of the processor will need to be rerun. This is because there may be changes made outside of the EDQ application that could lead to different results on subsequent executions.
Note: The Input attribute mappings are used as clues by the processor as to which Input attributes may contain specific data types, according to the initial structure of the address data. It is not normally necessary to parse addresses fully into all the different Input attributes before putting data through Address Verification. In many cases, it is sufficient to simply add address data to the Input address lines (as long as a country is provided), as the Address Verification processor itself will internally parse addresses before matching them against country-specific reference data. However, if addresses are well structured, more effective verification results may be seen if the corresponding input attribute mappings are used (for example, if an Input attribute normally contains postal codes, it is best to map it to the Postal Code input attribute rather than simply mapping it in as an address line.)
Note: The Country input must be populated with a country name or code. Without it, Address Verification cannot verify an address or produce an Accuracy Code.
| Option | Description | Settings |
|---|---|---|
| Processing mode |
Whether to verify the input address or search all installed data and return multiple results.
|
Verify (Best Match): 1 to 1 - Checks the reference data and returns the best match. Verify (Allow Multiple Results): Attempts to verify the input address 1 to 1, but allows Address Verification to return multiple possible results if the input address has an Ambiguous verification result. Search: 1 to Many - Checks the reference data and returns multiple matches. Allows searching across countries, for example. |
| Maximum number of results |
An optional upper limit on number of results that can be returned.
|
Numeric field, maximum of 15 characters.
|
| Geocode |
Whether matching geocodes are to be returned. |
Yes No |
| Output address separator |
The symbol used to separate the address elements. |
Selection of punctuation symbols and special characters. |
| Output script |
The output is converted into the script selected. |
Drop-down list of available scripts. Native - the default - returns the output in its original script. |
| Output Casing |
The case the output is returned in. |
The available options are Title (default - the first character of each word is upper case, the others are lower case), Upper or Lower. |
| Additional options |
Free-text field. |
There are additional options available that are not listed on the Address Verification: Options tab. To use these options, enter them and the specified value in this free-text field. For example: RangeDecompose=Match ToolInfo=Yes Note:
|
|
Flag name |
Details |
| av.AccuracyCode | A code that indicates how accurately each address has been identified and matched. Note: For the multiple output options (Verify: Allow Multiple Results and Search), an Accuracy Code is returned for each result found. |
| av.ResultCount | Number of addresses returned. Always "1" for Verify mode. |
| av.MatchScore | The match between the input and the closest reference match, expressed as a percentage. This is extracted from the Accuracy code. |
| av.GeoAccuracy | A code that indicates whether one or more Geocodes associated with the address have been identified. |
Note: If the Returned field status flag? option on the Options tab of the processor is set to Yes, an additional flag will generated for each output attribute, with a numeric value indicating the verification status of each one.
|
Code |
Description |
| 0 | Not Applicable: Field is not applicable to return field status. |
| 1 | Verified No Change: Field has been verified using relevant reference data, no changes were needed. |
| 2 | Verified Alias Change: Field has been verified using relevant reference data, an alias change was made during parsing (see 7: Identified Alias). |
| 3 | Verified Small Change: Field has been verified using relevant reference data, a small spelling change was made. |
| 4 | Verified Large Change: Field has been verified using relevant reference data, a large spelling change was made. |
| 5 | Added: Field has been added using relevant reference data. |
| 6 | Identified No Change: Field has been identified using relevant lexicon data, no changes were needed. e.g. an input value of "PO Box 1234" may be identifiable as a PostBox, but if it is unable to be verified then status 6 will be returned. |
| 7 | Identified Alias: Field has been identified using relevant lexicon data, an alias change was made. e.g. an input value of ‘Avnue’ may be identifiable as an alias to the ThoroughfareType ‘Ave’. |
| 8 | Identified Context: Field has been identified using relevant context rules. e.g. an input Address of "123 sdovnsdv San Bruno CA USA" may identify the word "sdovnsdv" as a Thoroughfare, but only because of the context in which it appears (after an identifiable Premise Number, and before an identifiable Locality). |
| 9 | Empty: Field is empty. |
| 10 | Unrecognized: Field is unrecognized. |
Also known as the Geocode, this flag consists of two values:
| Value | Description | Settings |
|---|---|---|
| Geocoding Status | Indicates whether a Geocode for the address has been found. |
P: Point - A single geocode was found matching the input address I: Interpolated - A geocode was interpolated from the input address's location in a range A: Average Multiple - Candidate geocodes were found to match the input address, and an average of these was returned U: Unable to geocode - A geocode was not able to be generated for the input address |
| Geocoding Level | Indicates the geographical accuracy of the Geocode. |
5: Delivery Point (PostBox or SubBuilding) 4: Premise (Premise or Building) 3: Thoroughfare 2: Locality 1: Administrative Area 0: None |
|
Execution Mode |
Supported |
| Batch | Yes |
| Real-Time Monitoring | Yes |
| Real-Time Response | Yes |
The Address Verification processor presents no summary statistics on its processing.
In the Data view, each input attribute is shown with the output attributes to the right.
None.
The below screenshot shows the output of the Address Verification processor on some sample addresses. In this case, the Results Browser has chosen to Show flags in order to see the output AccuracyCode and other flags:
Oracle ® Enterprise Data Quality Help version 11
Copyright ©
2006,2013 Oracle and/or its affiliates. All rights reserved.