Address Object:Advisory - Revision history

Admin at 01:21, 21 February 2023

2023-02-21T01:21:57Z

@@ Line 5: / Line 5: @@
 ==Address Object and the 118th Congressional District Information==
 Congressional District numbers and the addresses they are assigned to are maintain and distributed by the USPS. This data for the 118th congress was first made available in the January 2023 release of Address Object. Since then, we have noticed some additional updates and corrections from the USPS in relation to congressional district numbers that they provide. We expect that the February and March updates will contain changes and fixes to the congressional district data. The USPS has not made any announcements about this, however we will continue to monitor and provide updates as we get them.
 [[Category:Advisory]]
 [[Category:Address Object]]

Admin: Admin moved page Advisory:Address Object to Address Object:Advisory

2023-02-21T01:20:03Z

Admin moved page Advisory:Address Object to Address Object:Advisory

← Older revision	Revision as of 01:20, 21 February 2023
(No difference)

Admin at 17:19, 17 February 2023

2023-02-17T17:19:59Z

← Older revision		Revision as of 17:19, 17 February 2023
Line 2:		Line 2:
	{{CustomTOC}}		{{CustomTOC}}
	Address Object Advisory Notices		Address Object Advisory Notices

			==Address Object and the 118th Congressional District Information==
			Congressional District numbers and the addresses they are assigned to are maintain and distributed by the USPS. This data for the 118th congress was first made available in the January 2023 release of Address Object. Since then, we have noticed some additional updates and corrections from the USPS in relation to congressional district numbers that they provide. We expect that the February and March updates will contain changes and fixes to the congressional district data. The USPS has not made any announcements about this, however we will continue to monitor and provide updates as we get them.

	==Notice #1==		==Notice #1==

Admin at 19:57, 11 March 2016

2016-03-11T19:57:25Z

← Older revision		Revision as of 19:57, 11 March 2016
Line 1:		Line 1:
			[[Address Object\|← Address Object]]
	{{CustomTOC}}		{{CustomTOC}}
	Address Object Advisory Notices		Address Object Advisory Notices

Admin at 19:56, 11 March 2016

2016-03-11T19:56:10Z

← Older revision		Revision as of 19:56, 11 March 2016
Line 15:		Line 15:
	==Notice #4==		==Notice #4==
	Effective January 17th, 2011- New Canada Post licensing restrictions require that the new Point of Call address data be utilized by SERP certified software for producing the Statement of accuracy SOA form, used to receive postal discounts. POC data is meant to code addresses with high accuracy (similar to DPV® in USPS® CASSTM processing). This Canada Post restriction will not allow any API products to utilize the POC data (only for batch Mail programs) so Address Object will no longer be permitted to generate SOA forms.		Effective January 17th, 2011- New Canada Post licensing restrictions require that the new Point of Call address data be utilized by SERP certified software for producing the Statement of accuracy SOA form, used to receive postal discounts. POC data is meant to code addresses with high accuracy (similar to DPV® in USPS® CASSTM processing). This Canada Post restriction will not allow any API products to utilize the POC data (only for batch Mail programs) so Address Object will no longer be permitted to generate SOA forms.

			==Notice #5==
			Effective February 29th, 2016 - Address object is now certified in Canadians Software Evaluation and Recognition Program (SERP). This release of Address Object will use the new Point of Call data from (mdCanadaPOC.db) to validate postal addresses and generate Statements of Accuracy (SOA). The Point of Call data is much more accurate and can identify all deliverable addresses in Canada.


	[[Category:Advisory]]		[[Category:Advisory]]
	[[Category:Address Object]]		[[Category:Address Object]]

Admin at 22:47, 31 July 2012

2012-07-31T22:47:04Z

← Older revision		Revision as of 22:47, 31 July 2012
Line 15:		Line 15:
	==Notice #4==		==Notice #4==
	Effective January 17th, 2011- New Canada Post licensing restrictions require that the new Point of Call address data be utilized by SERP certified software for producing the Statement of accuracy SOA form, used to receive postal discounts. POC data is meant to code addresses with high accuracy (similar to DPV® in USPS® CASSTM processing). This Canada Post restriction will not allow any API products to utilize the POC data (only for batch Mail programs) so Address Object will no longer be permitted to generate SOA forms.		Effective January 17th, 2011- New Canada Post licensing restrictions require that the new Point of Call address data be utilized by SERP certified software for producing the Statement of accuracy SOA form, used to receive postal discounts. POC data is meant to code addresses with high accuracy (similar to DPV® in USPS® CASSTM processing). This Canada Post restriction will not allow any API products to utilize the POC data (only for batch Mail programs) so Address Object will no longer be permitted to generate SOA forms.


			[[Category:Advisory]]
			[[Category:Address Object]]

Admin at 22:46, 31 July 2012

2012-07-31T22:46:24Z

← Older revision		Revision as of 22:46, 31 July 2012
Line 3:		Line 3:

	==Notice #1==		==Notice #1==
	Effective September 30th, 2010- the LACSLink® and ~~SuiteLinkTM~~ datafiles for Address Object have been merged into one file each namely: mdLacs.dat, and mdSuiteLink.dat. To leverage the enhanced performance and stability this affords, the Address Object library will need to be updated when installing these new data files.		Effective September 30th, 2010- the LACSLink® and SuiteLink™ datafiles for Address Object have been merged into one file each namely: mdLacs.dat, and mdSuiteLink.dat. To leverage the enhanced performance and stability this affords, the Address Object library will need to be updated when installing these new data files.

	Note: The older format ~~LACSLink~~ and ~~SuiteLink~~ have been deprecated and will no longer be produced after December 31st, 2010. This update requires a replacement of the Address Object to a build greater than Build 1632. The September release will have both the new and old format DVDs, along with a warning notice about upgrading Address Object as soon as possible. Customers are encouraged to update by running the Setup.exe program. Those who install manually will need to copy over the new files and Address Object from the disk.		Note: The older format LACS<sup>Link</sup> and Suite<sup>Link</sup> have been deprecated and will no longer be produced after December 31st, 2010. This update requires a replacement of the Address Object to a build greater than Build 1632. The September release will have both the new and old format DVDs, along with a warning notice about upgrading Address Object as soon as possible. Customers are encouraged to update by running the Setup.exe program. Those who install manually will need to copy over the new files and Address Object from the disk.

	==Notice #2==		==Notice #2==

Admin: Created page with "{{CustomTOC}} Address Object Advisory Notices ==Notice #1== Effective September 30th, 2010- the LACSLink® and SuiteLinkTM datafiles for Address Object have been merged into ..."

2012-07-31T22:44:37Z

Created page with "{{CustomTOC}} Address Object Advisory Notices ==Notice #1== Effective September 30th, 2010- the LACSLink® and SuiteLinkTM datafiles for Address Object have been merged into ..."

New page

{{CustomTOC}}
Address Object Advisory Notices

==Notice #1==
Effective September 30th, 2010- the LACSLink® and SuiteLinkTM datafiles for Address Object have been merged into one file each namely: mdLacs.dat, and mdSuiteLink.dat. To leverage the enhanced performance and stability this affords, the Address Object library will need to be updated when installing these new data files.

Note: The older format LACSLink and SuiteLink have been deprecated and will no longer be produced after December 31st, 2010. This update requires a replacement of the Address Object to a build greater than Build 1632. The September release will have both the new and old format DVDs, along with a warning notice about upgrading Address Object as soon as possible. Customers are encouraged to update by running the Setup.exe program. Those who install manually will need to copy over the new files and Address Object from the disk.

==Notice #2==
Effective January 1st, 2011- the older Canadian format Canada.db file will be officially deprecated and no longer be produced. This requires an update to the Address Object to builds greater than 1632.

==Notice #3==
Effective January 1st, 2011- the Address Object's MSA and PMSA return properties are deprecated and will return blank information. As this standard is more than 10 years old, it has been replaced by the newer Core Based Statistical Areas used in the 2010 Census. Because CBSA's require more precise location information than provided in the Address Object, they are only returned in the GeoCoder Object.

==Notice #4==
Effective January 17th, 2011- New Canada Post licensing restrictions require that the new Point of Call address data be utilized by SERP certified software for producing the Statement of accuracy SOA form, used to receive postal discounts. POC data is meant to code addresses with high accuracy (similar to DPV® in USPS® CASSTM processing). This Canada Post restriction will not allow any API products to utilize the POC data (only for batch Mail programs) so Address Object will no longer be permitted to generate SOA forms.