Global Address Object:FAQ - Revision history

Admin at 17:56, 28 June 2022

2022-06-28T17:56:42Z

← Older revision		Revision as of 17:56, 28 June 2022
Line 1:		Line 1:
	[[Global Address Object\|← Global Address Object]]		[[Global Address Object\|← Global Address Object]]
	{{CustomTOC}}		{{CustomTOC}}
			{{FAQ-GlobalAddressProCon}}

	==What are the minimum hardware and OS requirements for the Global Address On-Premise API?==		==What are the minimum hardware and OS requirements for the Global Address On-Premise API?==
	:The Global Address On-Premise API does not have strict minimum requirements; it will run on most systems but just slower. Our recommended system environment is:		:The Global Address On-Premise API does not have strict minimum requirements; it will run on most systems but just slower. Our recommended system environment is:

Admin at 00:15, 5 February 2022

2022-02-05T00:15:07Z

← Older revision		Revision as of 00:15, 5 February 2022
Line 15:		Line 15:
	:Global Address is designed to take full standard addresses. This means that the address must, in most cases, have a house number, a street (or thoroughfare) and identifiable area data (like postal code and locality). The service will not behave particularly well for partial addresses, point of interest information (like a park or plot of land without a formal address), Directions (e.g. "across the street from ABC Bank") or non-address information (like phone numbers). The reason for this is that address verification relies on having a good address data source behind it in order to confirm its validity, and non-formal address data is not good enough to power our verification solution.		:Global Address is designed to take full standard addresses. This means that the address must, in most cases, have a house number, a street (or thoroughfare) and identifiable area data (like postal code and locality). The service will not behave particularly well for partial addresses, point of interest information (like a park or plot of land without a formal address), Directions (e.g. "across the street from ABC Bank") or non-address information (like phone numbers). The reason for this is that address verification relies on having a good address data source behind it in order to confirm its validity, and non-formal address data is not good enough to power our verification solution.

	==What are the minimum input fields ~~are~~ required?==		==What are the minimum input fields required?==
	:The only field that is really required is the country input. We cannot verify an address without a country. Secondly, almost all addresses must effectively have an AddressLine input. While it is theoretically possible to verify an address with a very unique piece of information like a postal code in certain countries and areas, that is very rare.		:The only field that is really required is the country input. We cannot verify an address without a country. Secondly, almost all addresses must effectively have an AddressLine input. While it is theoretically possible to verify an address with a very unique piece of information like a postal code in certain countries and areas, that is very rare.

Admin at 00:13, 5 February 2022

2022-02-05T00:13:31Z

Show changes

Admin at 23:21, 25 January 2018

2018-01-25T23:21:56Z

@@ Line 61: / Line 61: @@
 |Hang||Hangul (South Korea)
 |}
 [[Category:FAQ]]
 [[Category:Global Address Object]]

Admin: Created page with "← Global Address Object {{CustomTOC}} ==What are the DLLs required for the global address engine to work?== mdGlobalAddr.dll is the main global ..."

2017-08-10T22:23:21Z

Created page with "← Global Address Object {{CustomTOC}} ==What are the DLLs required for the global address engine to work?== mdGlobalAddr.dll is the main global ..."

New page

[[Global Address Object|← Global Address Object]]
{{CustomTOC}}
==What are the DLLs required for the global address engine to work?==
mdGlobalAddr.dll is the main global address engine that the application program will be accessing. mdAddr.dll, mdGeo.dll, mdRightFielder.dll are helper libraries used by mdGlobalAddr.dll in certain cases. These libraries are not to be used directly.

==What are the default locations for global address engine DLLs?==
The default location for these DLLs is address\windows\dll_64bit

==Where are the data files located?==
The location on the download is \address\data. When the product is installed, it defaults to D:\Program Files\Melissa DATA\DQS\Data unless the path is changed in the setup prompt.

==Which architecture do these DLLs support?==
There is support only for 64-bit architecture.

==What are the operating systems that the object supports?==
The object is currently available across windows and linux platforms.

==What are the programming languages in which the application can be designed in order to use these objects?==
For windows platform, there are wrappers available for Java, .NET and Python. For linux platform, there are wrappers available for Java, Perl, PHP, Python and Ruby.

==How does the update process work?==
For each update, the two items that will change are the dll’s and the data files. Those are the files that must be updated, and should be updated in conjunction. To perform the update, you can do either of the following steps:

#Run the installer. The installer will automatically copy over the new dll’s and new data files.
#Manually copy the dll’s and data files. To do this, follow these steps:
##Go to /address/windows/dll_64bit or /address/linux/dll_64bit and copy all the object (.dll for windows, .so for linux) and replace your current objects.
##Go to /address/data and copy all files and/or directories over your current data files.

Note that the update process will likely require that any applications using the objects or data files be restarted.

==What are the languages/scripts supported by the Global Address Object?==
Global Address Object supports the native language and script for each country that we support. For countries with native languages that does not use latin script, transliterated version of the address can be provided. We currently support the following languages:

{|class="alternate01" cellspacing="0"
!Output Value!!Definition
|-
|Latn||Latin (English transliteration wherever possible)
|-
|Cyrl||Cyrillic (Russia)
|-
|Grek||Greek (Greece)
|-
|Hebr||Hebrew (Israel)
|-
|Hani||Kanji (Japan)
|-
|Hans||Simplified Chinese (China)
|-
|Arab||Arabic (United Arab Emirates)
|-
|Thai||Thai (Thailand)
|-
|Hang||Hangul (South Korea)
|}

[[Category:FAQ]]
[[Category:Global Address Object]]