Global Address Verification:FAQ - Revision history

Admin at 23:28, 28 March 2024

2024-03-28T23:28:21Z

@@ Line 56: / Line 56: @@
 ::Max Verification Level: AV22
-==What speed can I expect from the Global Address Web Service?==
+==What can affect speeds from the Global Address Web Service?==
-:The response time of Global Address Web Service is highly dependent on a number of factors:
+The response time of Global Address Web Service is highly dependent on a number of factors:
-:With all of these factors, we cannot give a single throughput number that will cover all the different use cases and types of input. Our expectation is that the majority of users will see:
+*'''The country of the input.''' This is one of the most important factors as each country has its own engine in the background and its own verification paths and algorithms. A well-structured country like the US will be much faster than a less structured one like India. Also, a Latin-based address system will usually be faster than a non-Latin system.
-:*Between 50-250ms for real time single record lookups.
+*'''The quality of the address.''' A good address will be faster than a bad or partially bad address. Bad addresses will require extra steps, additional fuzzy matching logic, and extra parses before we either find a match or give up.
-:*Between 200K-500K/hour for batch processes.
+*'''Real time vs batch.''' Real time means sending one record at a time, while for batch you will send up to 100 records at a time and loop through your data. Processing 100 at a time will increase your overall per address speed by up to 25%-50%.
 ==How does the Global Address engine handle different Scripts?==

Admin at 17:56, 28 June 2022

2022-06-28T17:56:23Z

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

	==What type of global address information can I send?==		==What type of global address information can I send?==
	: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.

Admin at 00:19, 5 February 2022

2022-02-05T00:19:34Z

Show changes

Admin at 22:03, 10 March 2021

2021-03-10T22:03:32Z

← Older revision		Revision as of 22:03, 10 March 2021
Line 99:		Line 99:
	For a single address request, the vast majority of our records are between 50-250 ms. It can go higher based on the factors listed above.		For a single address request, the vast majority of our records are between 50-250 ms. It can go higher based on the factors listed above.

	For a batch of 1000 addresses, when being sent 100 at a time, we typically see the per address speed be around 25%-50% faster than the single address request.		For a batch of 1000 addresses, when being sent 100 at a time, we typically see the per address speed be around 25%-50% faster than the single address request. We typically see throughputs between 200K-500K an hour.


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Global Address Verification]]		[[Category:Global Address Verification]]

Admin at 20:34, 29 July 2019

2019-07-29T20:34:04Z

← Older revision		Revision as of 20:34, 29 July 2019
Line 91:		Line 91:

	The response time of the Global Address Web Service can depend highly on a number of factors:		The response time of the Global Address Web Service can depend highly on a number of factors:
	*The country of the input: Different countries have different algorithms and verification paths. A more structured country like the US would be faster than a less structured one like India.		*'''The country of the input:''' Different countries have different algorithms and verification paths. A more structured country like the US would be faster than a less structured one like India.
	*The quality of the addresses: A good address is faster than a bad addresses. Bad addresses, especially with extra unnecessary data requires more attempts and fuzzy logic to try and find a match before we give up.		*'''The quality of the addresses:''' A good address is faster than a bad addresses. Bad addresses, especially with extra unnecessary data requires more attempts and fuzzy logic to try and find a match before we give up.
	*The travel distance from your server to our server		*'''The travel distance''' from your server to our server.
	*The current load on our public server. Global Address Web Service is a shared service so high volume could potentially slow down processing speeds.		*'''The current load on our public server.''' The Global Address Verification Web Service is a shared service so high volume could potentially slow down processing speeds.
	*The protocol used. We have seen processing using SOAP be up to 10% slower than using XML or JSON.		*'''The protocol used.''' We have seen processing using SOAP be up to 10% slower than using XML or JSON.

	For a single address request, the vast majority of our records are between 50-250 ms. It can go higher based on the factors listed above.		For a single address request, the vast majority of our records are between 50-250 ms. It can go higher based on the factors listed above.

Admin at 20:31, 29 July 2019

2019-07-29T20:31:06Z

@@ Line 85: / Line 85: @@
 ==Encoding==
 The Global Address Web Service uses UTF-8. Make sure you are storing your address data in Unicode (nvarchar) and passing them to the web service in UTF-8. Be on the lookup for question marks (?), squares (▖) or other weird characters like �. They may be an indication of encoding issues and may result in data loss.
 [[Category:FAQ]]
 [[Category:Global Address Verification]]

Admin at 21:12, 5 October 2016

2016-10-05T21:12:49Z

← Older revision		Revision as of 21:12, 5 October 2016
Line 70:		Line 70:

	===DeliveryLines Options===		===DeliveryLines Options===
	:This option must be turned on. Please see [[~~Media~~:~~DQT_WS_Global_RG.pdf~~\|the ~~manual~~]] for information on how to do this.		:This option must be turned on. Please see [[Global Address Verification:Request#DeliveryLines\|the DeliveryLines option]] for information on how to do this.

	:;FormattedAddress		:;FormattedAddress

Admin at 21:10, 5 October 2016

2016-10-05T21:10:24Z

← Older revision		Revision as of 21:10, 5 October 2016
Line 56:		Line 56:

	==Outputs==		==Outputs==
	The Global Address Web Service has a decent number of output fields. These fields can return duplicate information so it is important to understand exactly what each field returns. Please see the [[~~Media~~:~~DQT_WS_Global_RG.pdf~~\|~~Reference Guide~~]] for more detailed information. For this FAQ, we will focus on which pieces will return you back a full address:		The Global Address Web Service has a decent number of output fields. These fields can return duplicate information so it is important to understand exactly what each field returns. Please see the [[Global Address Verification:Response\|Response Fields]] for more detailed information. For this FAQ, we will focus on which pieces will return you back a full address:

	===Normal Mode===		===Normal Mode===

Admin at 22:47, 9 December 2015

2015-12-09T22:47:31Z

← Older revision		Revision as of 22:47, 9 December 2015
Line 1:		Line 1:
	[[Global Address Verification\|← Global Address Verification]]		[[Global Address Verification\|← Global Address Verification]]
	~~__FORCETOC__~~

			{{CustomTOC}}
	==Result Codes==		==Result Codes==
	===How do I use Results Codes for the Global Address Web Service?===		===How do I use Results Codes for the Global Address Web Service?===

Admin at 22:47, 9 December 2015

2015-12-09T22:47:02Z

← Older revision		Revision as of 22:47, 9 December 2015
Line 1:		Line 1:
	[[Global Address Verification\|← Global Address Verification]]		[[Global Address Verification\|← Global Address Verification]]

	__FORCETOC__		__FORCETOC__