Global Address Object:Result Codes: Difference between revisions
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
! style="color:black;"|[[Global Address Object:Introduction|Introduction]] | ! style="color:black;"|[[Global Address Object:Introduction|Introduction]] | ||
|- | |- | ||
|[[Global Address Object:Platforms and | |[[Global Address Object:Platforms and Methods|Platforms and Methods]] | ||
|- | |- | ||
|[[Global Address Object:Licensing|Licensing]] | |[[Global Address Object:Licensing|Licensing]] |
Revision as of 18:53, 27 August 2014
← Global Address Object Reference
For a complete list of result codes and their definitions, please see Result Codes.
AV Verification Codes
- AV2X denotes an address that has been verified to the highest possible level with the reference data.
- AV1X denotes a partially verified address, but NOT to the highest level possible with the reference data.
The second number indicates the level of verification. There are five levels:
[Image]
Administrative Area (level 1) verification is the most general verification area, with subpremise (level 5) being the most specific area. Ideally, all addresses should be verified to Premise (level 4) or subpremise (level 5.)
However this is dependent on the quality of the address data and the countries’ reference data. Some countries lack enough data to be verified to the subpremise. They may only have data to the Locality (level 2.) This is why it is possible to have an AV22 code. The address has been verified up to the Locality and the reference data only has verification up to that level.
For example:
a. AV25 indicates a maximum possible verification to the subpremise (level 5.) b. AV24 indicates a maximum possible verification to the Premise (level 4.) c. AV22 indicates a maximum possible verification to the Locality (level 2.)
This can occur if the reference data only contains data up to the Locality level.
d. AV14 indicates a partial verification to the Premise (level 4.) This indicates that the reference data has verification up to the subpremise (level 5.)
For a list of AV codes returned by Global Address Object, see Returned Result Codes.
MX Match Codes
During the process of validating or correcting an address the individual address elements are parsed and compared to Melissa’s reference international data. The results of this matching are returned as a series of possible match codes. The match code is defined with a type and a code. The type delineates the method of match; exact or synonym, and the code defines the element that was matched. For example, ME01 is an exact match for the input data against the postal code reference data.
'THESE MATCHCODES DO NOT MATCH ALL OUR OTHER MATCHCODES. THIS CAN CAUSE CONFUSION!!! NEED TO DOUBLE CHECK THIS'
Again these match codes can be very valuable as they are returned regardless of the AV code status.
For a list of MX codes returned by Global Address Object, see Returned Result Codes.
FX Fielding Codes
Before Global Address Object attempts to match data elements to reference data and verify results the input address data is fielded. This fielding processing allows for the removal and classification of residual data elements (names, phone numbers, etc.) which are not relative to address verification. This fielding also allows for the classification, and if necessary, detection of the country associated with the address input data. This is a powerful feature of the Global Address Object and allows for the accurate verification and processing of results.
For a list of FX codes returned by Global Address Object, see Returned Result Codes.
For a complete list of result codes and their definitions, please see Result Codes.