Address Object:FAQ - Revision history

Admin at 23:34, 10 May 2021

2021-05-10T23:34:24Z

← Older revision		Revision as of 23:34, 10 May 2021
Line 169:		Line 169:

	:;[[Term:EWS\|EWS]]		:;[[Term:EWS\|EWS]]
	::EWS stands for Early Warning System from the USPS. EWS addresses are flagged by Address Check when they are scheduled for inclusion in the USPS database but are not added yet. The addresses are typically new high rises, or new housing subdivisions that are being assigned deliverable mail addresses. The EWS file when present in the Address Object directory ensures that addresses not present in the USPS master file will not be eliminated or coded inaccurately. The EWS file is updated weekly and can be downloaded via the Melissa Data ~~FTP~~ site to give customers the freshest new address information.		::EWS stands for Early Warning System from the USPS. EWS addresses are flagged by Address Check when they are scheduled for inclusion in the USPS database but are not added yet. The addresses are typically new high rises, or new housing subdivisions that are being assigned deliverable mail addresses. The EWS file when present in the Address Object directory ensures that addresses not present in the USPS master file will not be eliminated or coded inaccurately. The EWS file is updated weekly and can be downloaded via the Melissa Data HTTPS site to give customers the freshest new address information.


Line 175:		Line 175:
	;Answer:		;Answer:
	:There is some lag in the data updates for new streets. It may take anywhere from a week to a month for that data to make it to us once the USPS adds the new street to their database. Additionally, since our updates are shipped every two months, it may take even longer for the new data to reach you [MelissaData does offer monthly instead of bi-monthly updates for faster updates]. So, depending on when the street name was added, it could take up to two months before the update reaches you.		:There is some lag in the data updates for new streets. It may take anywhere from a week to a month for that data to make it to us once the USPS adds the new street to their database. Additionally, since our updates are shipped every two months, it may take even longer for the new data to reach you [MelissaData does offer monthly instead of bi-monthly updates for faster updates]. So, depending on when the street name was added, it could take up to two months before the update reaches you.
	:However, there is a system in place call EWS (Early Warning System) that will alert you that although a street don’t not officially exist in the official database, it is scheduled for addition in the next update. The EWS file (which can be downloaded here: ~~ftp~~://~~ftp~~.melissadata.com/Updates/ews.txt) is updated every week and will give you an error code of “W” if the street in contained in the EWS file. While EWS will be able to pick up new streets in one week of its addition to the USPS database, it will not be able to verify ranges on that street. You must wait for the official update for that.		:However, there is a system in place call EWS (Early Warning System) that will alert you that although a street don’t not officially exist in the official database, it is scheduled for addition in the next update. The EWS file (which can be downloaded here: https://download.melissadata.com/Updates/ews.txt) is updated every week and will give you an error code of “W” if the street in contained in the EWS file. While EWS will be able to pick up new streets in one week of its addition to the USPS database, it will not be able to verify ranges on that street. You must wait for the official update for that.

	:For details on how to use EWS, please review the [[Media:DQT_API_Address_RG.pdf\|Address Object Reference Guide]].		:For details on how to use EWS, please review the [[Media:DQT_API_Address_RG.pdf\|Address Object Reference Guide]].

Admin at 19:13, 5 June 2020

2020-06-05T19:13:47Z

← Older revision		Revision as of 19:13, 5 June 2020
Line 15:		Line 15:

	*;Note:		*;Note:
	:Since addresses change and are added frequently, this is ~~not~~ a number that constantly changes. It is important to put a buffer to account for future cases. Our recommended maximum lengths below of coded records are based on this information.		:Since addresses change and are added frequently, this is a number that constantly changes. It is important to put a buffer to account for future cases. Our recommended maximum lengths below of coded records are based on this information.

Admin at 23:04, 1 May 2020

2020-05-01T23:04:52Z

← Older revision		Revision as of 23:04, 1 May 2020
Line 16:		Line 16:
	*;Note:		*;Note:
	:Since addresses change and are added frequently, this is not a number that constantly changes. It is important to put a buffer to account for future cases. Our recommended maximum lengths below of coded records are based on this information.		:Since addresses change and are added frequently, this is not a number that constantly changes. It is important to put a buffer to account for future cases. Our recommended maximum lengths below of coded records are based on this information.


	<p class="sectionhead">USPS</p>		<p class="sectionhead">USPS</p>

Admin at 23:04, 1 May 2020

2020-05-01T23:04:22Z

← Older revision		Revision as of 23:04, 1 May 2020
Line 15:		Line 15:

	*;Note:		*;Note:
	:Since addresses change and are added frequently, this is not a number constantly changes. It is important to put a buffer to account for future cases. Our recommended maximum lengths below of coded records are based on this information.		:Since addresses change and are added frequently, this is not a number that constantly changes. It is important to put a buffer to account for future cases. Our recommended maximum lengths below of coded records are based on this information.

	<p class="sectionhead">USPS</p>		<p class="sectionhead">USPS</p>

Admin at 23:05, 30 April 2020

2020-04-30T23:05:38Z

← Older revision		Revision as of 23:05, 30 April 2020
Line 19:		Line 19:
	<p class="sectionhead">USPS</p>		<p class="sectionhead">USPS</p>
	:{\| class="alternate01"		:{\| class="alternate01"
	!Field Name !! Recommended Maximum Length		!style="min-width:6rem;"\| Field Name !! Recommended Maximum Length
	\|-		\|-
	\|Company\|\|75 characters (The company name is usually returned as is based on the input)		\|Company\|\|75 characters (The company name is usually returned as is based on the input)
Line 43:		Line 43:
	<p class="sectionhead">CanadaPost</p>		<p class="sectionhead">CanadaPost</p>
	:{\| class="alternate01"		:{\| class="alternate01"
	!Field Name !! Recommended Maximum Length		!style="min-width:6rem;"\|Field Name !! Recommended Maximum Length
	\|-		\|-
	\|Company~~        ~~\|\|75 characters (The company name is usually returned as is based on the input)		\|Company\|\|75 characters (The company name is usually returned as is based on the input)
	\|-		\|-
	\|Address1\|\|65 characters		\|Address1\|\|65 characters

Admin at 22:53, 30 April 2020

2020-04-30T22:53:41Z

← Older revision		Revision as of 22:53, 30 April 2020
Line 45:		Line 45:
	!Field Name !! Recommended Maximum Length		!Field Name !! Recommended Maximum Length
	\|-		\|-
	\|Company\|\|75 characters (The company name is usually returned as is based on the input)		\|Company        \|\|75 characters (The company name is usually returned as is based on the input)
	\|-		\|-
	\|Address1\|\|65 characters		\|Address1\|\|65 characters

Admin at 22:47, 30 April 2020

2020-04-30T22:47:51Z

Admin at 21:51, 30 April 2020

2020-04-30T21:51:04Z

@@ Line 1: / Line 1: @@
 [[Address Object|&larr; Address Object]]
 {{CustomTOC}}
 ==Can we submit Unicode characters to Address Object?==
 ;Answer:

Admin at 22:33, 15 December 2016

2016-12-15T22:33:43Z

← Older revision		Revision as of 22:33, 15 December 2016
Line 199:		Line 199:
	addrobj.PathToDPVDataFiles = “Path to DPV Data files”		addrobj.PathToDPVDataFiles = “Path to DPV Data files”

	//set ~~license string~~		//set License Key
	addrobj.SetLicenseString(“License”)		addrobj.SetLicenseString(“License”)

Admin at 20:01, 11 March 2016

2016-03-11T20:01:52Z

← Older revision		Revision as of 20:01, 11 March 2016
Line 1:		Line 1:
	~~__FORCETOC__~~		[[Address Object\|← Address Object]]
			{{CustomTOC}}
	==Can we submit Unicode characters to Address Object?==		==Can we submit Unicode characters to Address Object?==
	;Answer:		;Answer:

← Older revision		Revision as of 22:47, 30 April 2020
Line 9:		Line 9:
	;For addresses that we do not code:		;For addresses that we do not code:
	We will return the input (sometimes with a few standardizations, if possible) back to the user. This effectively makes the output length the same as the input length. We do not truncate the input data to fit a pre-determined field length.		We will return the input (sometimes with a few standardizations, if possible) back to the user. This effectively makes the output length the same as the input length. We do not truncate the input data to fit a pre-determined field length.


	;For addresses that we do code:		;For addresses that we do code:
Line 24:		Line 25:
	\|Address1\|\|65 characters		\|Address1\|\|65 characters
	\|-		\|-
	\|Address2\|\|Address2 is not part of the official address. Extra data like care of information will be ~~retuned~~ here based on the input.		\|Address2\|\|Address2 is not part of the official address. Extra data like care of information will be returned here based on the input.
	\|-		\|-
	\|Suite\|\|20 characters (This is one where we can code the address to the house number put pass through a suite from the input that is only any length)		\|Suite\|\|20 characters (This is one where we can code the address to the house number put pass through a suite from the input that is only any length)
Line 48:		Line 49:
	\|Address1\|\|65 characters		\|Address1\|\|65 characters
	\|-		\|-
	\|Address2\|\|Address2 is not part of the official address. Extra data like care of information will be ~~retuned~~ here based on the input.		\|Address2\|\|Address2 is not part of the official address. Extra data like care of information will be returned here based on the input.
	\|-		\|-
	\|Suite\|\|20 characters (This is one where we can code the address to the house number put pass through a suite from the input that is only any length)		\|Suite\|\|20 characters (This is one where we can code the address to the house number put pass through a suite from the input that is only any length)
Line 61:		Line 62:

	<p class="sectionhead">Recommendations</p>		<p class="sectionhead">Recommendations</p>
	:Based on this information we recommend the maximum field lengths as:		Based on this information we recommend the maximum field lengths as:
	:*Set the maximum field length to at least match the input maximum data length		*Set the maximum field length to at least match the input maximum data length
	:*Set the maximum field length to far beyond (100+ characters) the numbers of the source data above. In this day and age, storage space is much less a limiting factor than before. We suggest setting a length that ~~guareentees~~ nothing gets truncated.		*Set the maximum field length to far beyond (100+ characters) the numbers of the source data above. In this day and age, storage space is much less a limiting factor than before. We suggest setting a length that guarantees nothing gets truncated.