ValidateAddressGlobal

ValidateAddressGlobal provides enhanced address standardization and validation for addresses outside the U.S. and Canada. ValidateAddressGlobal can also validate addresses in the U.S. and Canada but its strength is validation of addresses in other countries. If you process a significant number of addresses outside the U.S. and Canada, you should consider using ValidateAddressGlobal.

ValidateAddressGlobal is part of the Universal Addressing Module.

ValidateAddressGlobal performs several steps to achieve a quality address, including transliteration, parsing, validation, and formatting.

Character Set Mapping and Transliteration

ValidateAddressGlobal handles international strings and their complexities. It uses fully Unicode enabled string processing which enables the transliteration of non-roman characters into the Latin character set and mapping between different character sets.

Character set mapping and transliteration features include:

  • Support for over 30 different character sets including UTF-8, ISO 8859-1, GBK, BIG5, JIS, EBCDIC
  • Proper "elimination" of diacritics according to language rules
  • Transliteration for various alphabets into Latin Script
  • Greek (BGN/PCGN 1962, ISO 843 - 1997)
  • Cyrillic (BGN/PCGN 1947, ISO 9 - 1995)
  • Hebrew
  • Japanese Katakana, Hiragana and Kanji
  • Chinese Pinyin (Mandarin, Cantonese)
  • Korean Hangul

Address Parsing, Formatting, and Standardization

Restructuring incorrectly fielded address data is a complex and difficult task especially when done for international addresses. People introduce many ambiguities as they enter address data into computer systems. Among the problems are misplaced elements (such as company or personal names in street address fields) or varying abbreviations that are not only language, but also country specific. ValidateAddressGlobal identifies address elements in address lines and assigns them to the proper fields. This is an important precursor to the actual validation. Without restructuring, "no match" situations might result.

Properly identified address elements are also important when addresses have to be truncated or shortened to fit specific field length requirements. With the proper information in the right fields, specific truncation rules can be applied.

  • Parses and analyzes address lines and identifies individual address elements
  • Processes over 30 different character sets
  • Formats addresses according to the postal rules of the country of destination
  • Standardizes address elements (such as changing AVENUE to AVE)

Global Address Validation

Address validation is the correction process where properly parsed address data is compared against reference databases supplied by postal organizations or other data providers. ValidateAddressGlobal validates individual address elements to check for correctness using sophisticated fuzzy matching technology and produces standardized and formatted output based on postal standards and user preferences. FastCompletion validation type can be used in quick address entry applications. It allows input of truncated data in several address fields and generates suggestions based on this input.

In some cases, it is not possible to fully validate an address. Here ValidateAddressGlobal has a unique deliverability assessment feature that classifies addresses according to their probable deliverability.

Resource URL

JSON endpoint:

http://server:port/rest/ValidateAddressGlobal/results.json

XML endpoint:

http://server:port/rest/ValidateAddressGlobal/results.xml

Example with JSON Response

The following example requests a JSON response:

http://myserver:8080/rest/ValidateAddressGlobal/results.json?​City.StateProvince=NY&Data.AddressLine1=1+Global+View&​Data.City=Troy&Data.Country=USA

The JSON returned by this request would be:

{"output": [{
   "Country.Input": "USA",
   "AddressLine1.Input": "1 Global View",
   "City.Input": "Troy",
   "Country": "UNITED STATES",
   "AddressLine1": "1 GLOBAL VW",
   "HouseNumber": "1",
   "StreetName": "GLOBAL",
   "StreetSuffix": "VW",
   "City": "TROY",
   "PostalCode": "12180-8371",
   "PostalCode.Base": "12180",
   "PostalCode.AddOn": "8371",
   "StateProvince": "NEW YORK",
   "County": "RENSSELAER",
   "LastLine": "TROY NY 12180-8371",
   "AddressBlock1": "1 GLOBAL VW",
   "AddressBlock2": "TROY NY 12180-8371",
   "ProcessStatus": "C4",
   "ProcessStatus.Description": "Corrected - all elements have been checked",
   "ModeUsed": "BATCH",
   "CountOverflow": "NO",
   "MailabilityScore": "5",
   "Confidence": "82.09",
   "ElementResultStatus": "88F088E0F000000000E0",
   "ElementInputStatus": "00600050600000000060",
   "ElementRelevance": "11101010100000000010",
   "AddressType": "S",
   "AMAS.Status": "EAM0",
   "user_fields": []
}]}

Example with XML Response

The following example requests an XML response:

http://myserver:8080/rest/ValidateAddressGlobal/results.xml?​Data.AddressLine1=1+Global+View&Data.City=Troy&​Data.Country=USA&Data.StateProvince=NY

The XML returned by this request would be:

<ns2:xml.ValidateAddressGlobalResponse
xmlns:ns2="http://www.precisely.com/spectrum/services/ValidateAddressGlobal">
   <ns2:output>
      <ns2:Address>
         <ns2:Country>UNITED STATES</ns2:Country>
         <ns2:AddressLine1>1 GLOBAL VW</ns2:AddressLine1>
         <ns2:HouseNumber>1</ns2:HouseNumber>
         <ns2:StreetName>GLOBAL</ns2:StreetName>
         <ns2:StreetSuffix>VW</ns2:StreetSuffix>
         <ns2:City>TROY</ns2:City>
         <ns2:PostalCode>12180-8371</ns2:PostalCode>
         <ns2:PostalCode.Base>12180</ns2:PostalCode.Base>
         <ns2:PostalCode.AddOn>8371</ns2:PostalCode.AddOn>
         <ns2:StateProvince>NY</ns2:StateProvince>
         <ns2:County>RENSSELAER</ns2:County>
         <ns2:LastLine>TROY NY 12180-8371</ns2:LastLine>
         <ns2:AddressBlock1>1 GLOBAL VW</ns2:AddressBlock1>
         <ns2:AddressBlock2>TROY NY 12180-8371</ns2:AddressBlock2>
         <ns2:ProcessStatus>C4</ns2:ProcessStatus>
         <ns2:ProcessStatus.Description>
              Corrected - all elements have been checked
         </ns2:ProcessStatus.Description>
         <ns2:ModeUsed>BATCH</ns2:ModeUsed>
         <ns2:CountOverflow>NO</ns2:CountOverflow>
         <ns2:MailabilityScore>5</ns2:MailabilityScore>
         <ns2:Confidence>85.09</ns2:Confidence>
         <ns2:ElementResultStatus>
              88F0F8E0F000000000E0
         </ns2:ElementResultStatus>
         <ns2:ElementInputStatus>
              00606050600000000060
         </ns2:ElementInputStatus>
         <ns2:ElementRelevance>
              11101010100000000010
         </ns2:ElementRelevance>
         <ns2:AddressType>S</ns2:AddressType>
         <ns2:AMAS.Status>EAM0</ns2:AMAS.Status>
         <ns2:user_fields/>
      </ns2:Address>
   </ns2:output>
</ns2:xml.ValidateAddressGlobalResponse>