Difference between revisions of "Global Address Verification:Build History"

From Melissa Data Wiki
Jump to navigation Jump to search
 
Line 4: Line 4:
  
 
==Build 3.0.1.167==
 
==Build 3.0.1.167==
 +
===October 2021 Update===
 +
''Released October 2021''
 +
 +
<p class="sectionhead">General Information</p>
 +
:As we continue our on-going effort to improve our parsing result, we have made the following changes:
 +
:*Improved Great Britain parsing
 +
:*Fixed an issue where AE01 – General Error errors would incorrectly put parsed values in Building.
 +
 +
<p class="sectionhead">Country Specific Updates</p>
 +
:;AUSTRALIA
 +
:*Fixed a bug where it was possible to return a non-decimal and non-blank latitude and longitude value.
 +
 +
:;CANADA
 +
:*Improved the handling of duplicate address information. Please see examples in the notes for United States for more details.
 +
 +
:;GERMANY
 +
:*Fixed an issue where two different thoroughfares which has the same abbreviations would get matched to one another.
 +
 +
:;GREAT BRITAIN
 +
:*Improved parsing of partially coded records
 +
:*Fixed an issue where an address coded to AE05 – Multiple Match error would still return a valid AddressKey (UDPRN) and AddressType. This should not have been returned as we cannot fully verify the address.
 +
 +
:;ITALY
 +
:*Refined our matching logic to reduce matching thoroughfares that are very similar but in reality different thoroughfares. This is a logic especially applied to Italy because they have no many very similar thoroughfare names.
 +
 +
:;MEXICO
 +
:*Changed the AA value from <code>DF</code> to <code>CDMX</code>
 +
 +
:;SINGAPORE
 +
:*Improved recognition of subpremise types
 +
:*Improved input variation handling
 +
:*Fixed an issue where an address coded to AE05 – Multiple Match error would still return a valid AddressKey (UDPRN) and AddressType. This should not have been returned as we cannot fully verify the address.
 +
 +
:;UNITED STATES
 +
:*Major improvement in the handling of duplicate address data. Our engine will now look at the additional lines of input and if it detects that they contain only duplicate address information, that whole line will be removed. However, if there are other significant pieces of data in the additional lines, we will err of the side of caution and leave the input there as additional information.
 +
 +
::Example where A2 would be removed:
 +
<pre style="margin-left:40px;">A1: 12345 Main St
 +
A2: Main Street, Dallas Texas
 +
Locality: Dallas
 +
AdministrativeArea: TX
 +
PostalCode: 34521</pre>
 +
 +
::With the example above, if A2 were something like these, they would not be removed:
 +
<pre style="margin-left:40px;">A2: Main Street Dentist
 +
A2: Dallas Real Estate</pre>
 +
 +
<p class="sectionhead">Data Updates</p>
 +
:;Reference Data Update
 +
:*ALL COUNTRIES
 +
 +
:;Address Pattern Recognition Update
 +
:*AUSTALIA, CANADA, GERMANY, GREAT BRITAIN, ITALY, SINGAPORE, UNITED STATES
 +
 +
 +
===August 2021 Update===
 
''Released August 2021''
 
''Released August 2021''
  

Latest revision as of 23:58, 4 October 2021

← Global Address Verification


Build 3.0.1.167

October 2021 Update

Released October 2021

General Information

As we continue our on-going effort to improve our parsing result, we have made the following changes:
  • Improved Great Britain parsing
  • Fixed an issue where AE01 – General Error errors would incorrectly put parsed values in Building.

Country Specific Updates

AUSTRALIA
  • Fixed a bug where it was possible to return a non-decimal and non-blank latitude and longitude value.
CANADA
  • Improved the handling of duplicate address information. Please see examples in the notes for United States for more details.
GERMANY
  • Fixed an issue where two different thoroughfares which has the same abbreviations would get matched to one another.
GREAT BRITAIN
  • Improved parsing of partially coded records
  • Fixed an issue where an address coded to AE05 – Multiple Match error would still return a valid AddressKey (UDPRN) and AddressType. This should not have been returned as we cannot fully verify the address.
ITALY
  • Refined our matching logic to reduce matching thoroughfares that are very similar but in reality different thoroughfares. This is a logic especially applied to Italy because they have no many very similar thoroughfare names.
MEXICO
  • Changed the AA value from DF to CDMX
SINGAPORE
  • Improved recognition of subpremise types
  • Improved input variation handling
  • Fixed an issue where an address coded to AE05 – Multiple Match error would still return a valid AddressKey (UDPRN) and AddressType. This should not have been returned as we cannot fully verify the address.
UNITED STATES
  • Major improvement in the handling of duplicate address data. Our engine will now look at the additional lines of input and if it detects that they contain only duplicate address information, that whole line will be removed. However, if there are other significant pieces of data in the additional lines, we will err of the side of caution and leave the input there as additional information.
Example where A2 would be removed:
A1: 12345 Main St
A2: Main Street, Dallas Texas
Locality: Dallas
AdministrativeArea: TX
PostalCode: 34521
With the example above, if A2 were something like these, they would not be removed:
A2: Main Street Dentist
A2: Dallas Real Estate

Data Updates

Reference Data Update
  • ALL COUNTRIES
Address Pattern Recognition Update
  • AUSTALIA, CANADA, GERMANY, GREAT BRITAIN, ITALY, SINGAPORE, UNITED STATES


August 2021 Update

Released August 2021

General Information

One of the main focuses of this update is improved parsing, especially thoroughfare parsing. When we code an address, we are very confident in the parsed results that is returned back to the user. However, when we do not code the address, we will make a best attempt parse and do not always return results. In this update, we have focused on improving and returning the parsed results for addresses that do not code, specifically AE01 and AE05. There is still more room for improvement and we will continue to work on improving parsing, but we believe this update provides a massive improvement of parsed results.
We fixed an issue where AV24 was sometimes also returned with AE11 due to inconsistency of source data.
We have worked to cut down on address records that could take more than one second to verify, typically with a lot of junk or garbage data.

Country Specific Updates

AUSTRIA
  • Improved speed for more complex inputs that could take longer than normal
  • Will now return the first number of a multi-number address in the subpremiselevel.
For example, if you have an address such as Schulgasse 10/1/35, we will return:
PremisesNumber: 10
SubPremisesNumber: 1
SubPremisesLevelNumber: 35
FRANCE
  • Fixed an issue where a small number of records returned with a non-preferred version of the thoroughfare instead of the preferred version
  • Updated the CountrySubDivisionCode values to the more standard FR-## version.
GREAT BRITAIN
  • We have improved our matching engine to recognize more possible patterns, especially with addresses containing multiple sub-premises.
  • Improved the address format of records where the source data has a subbuilding that behaves more as a subpremise instead.
  • Improved coding of RoyalMail Multi-res records.
  • Updated the CountrySubDivisionCode value to be more accurate.
HONG KONG
  • Improved speed for more complex inputs that could take longer than normal
INDIA
We have been working on acquiring better more up to date data for India for some time. We also wanted to address the issue of over-aggressiveness due to the spotty nature of source data in India. To that end, we have completely redone India with new data and matching engine.
  • Improved Formatted Address to more closely match postal standards
  • Decreased over-aggressiveness and false coding
  • Improved parsing
JAPAN
  • Fixed some cases where an invalid address would partially code to the locality (AV12). They now correctly return AE01.
  • Fixed the CountrySubDivisionCode value returns for administrative area Shizuoka.
KOREA
  • Cut down on records that could take more than 1 second. A few long single line addresses may be affected.
PERU
  • Cut down on records that could take more than 1 second. A few long single line addresses may be affected.
  • Fixed the CountrySubDivisionCode value returns for administrative area Lima.
SINGAPORE
  • Improved speed for more complex inputs that could take longer than normal
SPAIN
  • MelissaAddressKey and MelissaAddressKeyBase numbers are now available.
  • Fixed an issue where some records could have returned an empty locality.
  • Improved data where some data with accents were corrupted from the data source
SWITZERLAND
We have updated our source data for Switzerland to use data that more closely matches Swiss Post. The changes you see in this country are derived from this data change. The new data is better and more official than the data previously used.
  • MelissaAddressKey and MelissaAddressKeyBase numbers are now available.
  • Improved Formatted Address to more closely match official postal standards in less common scenarios.
  • SubNationalArea and SubAdministrativeArea are no longer returned as they are not included in official data.
  • Improved Thoroughfare parsing
  • Locality and alias locality data have been improved
UNITED STATES
  • Improve data returned in the SubAdministrativeArea (County Name) for some addresses that were on the border of two counties.

Data Updates

Reference Data Update
  • ALL COUNTRIES
Address Pattern Recognition Update
  • AUSTRIA, FRANCE, GREAT BRITAIN, HONG KONG, INDIA, JAPAN, KOREA, SINGAPORE, SPAIN, SWITZERLAND, UNITED STATES


Build 3.0.1.151

March 2021 Update

Released March 2021

General Information

We have made a standardization to the way we treat FormattedAddress and CountryOfOrigin. The default functionality is described below:
  • If the CountryOfOrigin is not set, the FormattedAddress will contain the destination country name at the end*.
  • If CountryOfOrigin is set and the same as the destination country, the FormattedAddress will not contain the country name at the end.
  • If CountryOfOrigin is set and different than the destination country, the FormattedAddress will contain the country name at the end.
*There is an exception for this item which is US and CA. These countries will not have the country name at the end of FormattedAddress is CountryOfOrigin is not set. This is due to backwards compatibility reasons as the majority of our users use these two countries.

Country Specific Updates

BELGIUM
  • Added some improvement for typo handling
CANADA
  • Improved handling of AV24 vs AV25 codes.
Previously:
  • Case #1) 12-345 Main St -> AV24
  • Case #2) 345 Main St Ste 12 -> AV25
Now, we will identify both cases as AV25.
FRANCE
  • We have made CEDEX data available now in the database. CEDEX addresses are business addresses that have special postal codes and address data.
GERMANY
  • MelissaAddressKey and MelissaAddressKeyBase numbers are now available.
  • Improved recognition and handling of typos and misspellings.
HONG KONG
  • We have changed our data source to use the official land registry data for Hong Kong. This data includes the building information for addresses.
  • We have made changes to our engine to try and cut down on over-aggressive coding.
  • MelissaAddressKey and MelissaAddressKeyBase numbers are now available.
ITALY
  • MelissaAddressKey and MelissaAddressKeyBase numbers are now available.
  • We have added additional variation data to improve coding rates
  • We have sourced and added additional data for the South Tyrol region that often uses German versions of the address.
JAPAN
  • Improved matching of addresses that are all in one line
KOREA
  • We have transitioned to a new data provider for Korea we believe contains better overall data for the country.
  • Formatted Address now is closer sync with postal preference
  • Less overly aggressive false coding
  • MelissaAddressKey and MelissaAddressKeyBase numbers are now available.
MOROCCO
  • We have made improvements to this country to reduce occurrences of false coding.
NETHERLANDS
  • Corrected an issue where AC03 (Locality change) was being incorrectly reported.
SINGAPORE
  • We have improving handling of building data in Singapore. We will now only append the building information if we do not detect the input as already having building information. This is because we found the user often had correct and desired data but that was slightly different than the value in the database.
SPAIN
  • We have improved our pattern matching for better recognition of subpremise patterns. This will improve coding rates.
UNITED ARAB EMIRATES
  • Fixed a data issue for the Sharjah region.

Data Updates

Reference Data Update
  • ALL COUNTRIES
Address Pattern Recognition Update
  • BELGIUM, CANADA, FRANCE, GERMANY, HONG KONG, JAPAN, KOREA, MOROCCO, NETHERLANDS, SINGAPORE, SPAIN


November 2020 Update

Released November 2020

General Information

We are also working on upgrading our infrastructure and data source relationships so that we can start providing monthly updates for a number of countries. We expect this to be available first half of 2021. Some countries we expect to roll out with for Monthly updates are: United States, United Kingdom, France, Germany, and Netherlands.

Country Specific Updates

AUSTRALIA
  • MelissaAddressKey and MelissaAddressKeyBase values are now available
  • Removed some house numbers that were invalid
  • Subpremise values with are single letters are now capitalized
  • SubAdministrative Area data was deemed to be too inconsistent and no longer returned. This value is not used in the mailing address.
BELARUS
  • Postal code verification improved
CAMEROON
  • Data has been updated to a more comprehensive thoroughfare level data
  • Address format adjusted to close match country specifications
CHILE
  • Fixed area slotting for Region Nuble
COSTA RICA
  • We have updated the data source to be one that is much more comprehensive in the country. This data source does not have house numbers while the previous one did but has much better thoroughfare coverage throughout the country.
FRANCE
  • MelissaAddressKey and MelissaAddressKeyBase values are now available
  • Cleaned up some of the subadministrativea area, administrative area, and subnational area values for addresses near boundary borders
  • AV25 coding now possible
KYRGYZSTAN
  • Improvement in verification results with locality and thoroughfare levels.
SAO TOME AND PRINCIPE
  • Updated this country to thoroughfare level (AV-3) address coverage and Thoroughfare level Geocoding (G-3) coverage
SINGAPORE
  • MelissaAddressKey and MelissaAddressKeyBase values are now available
  • Updated values for Dependent Locality and Double Dependent Localities (These are not used in the mailing address)
MACAO
  • More addresses can now be verified to the house number level.
MOZAMBIQUE
  • Data updated to a new source with postal code information and engine revamped for this new data.
  • Decreased the chances of false coding to the wrong address
TAIWAN
  • Improved matching engine for more AV24 level coding
  • Increase number of rooftop level geocoding
  • AV22 for incomplete or not fully validated address no longer returned. We will instead return AV12 if the locality level data is correct but the full mailing address is not correct.
  • Decreased level of false coding
VIETNAM
  • We have changed to a new data source and adapted our engine.
  • MelissaAddressKey and MelissaAddressKeyBase values are now available
  • Improved Postal Code coverage
  • Less over-aggressive coding that will cause the engine to match to the incorrect address. This may result in some previous matches that happen to be correct to no longer match, but we believe that it is better overall to decrease false coding.
  • Results will now be in Vietnamese instead of transliterated Vietnamese. This is a much closer match to the data expected in the country.
  • For example:
Vietnamese: Phố Lê Đại
Transliterated Vietnamese: Pho Le Dai
  • AV22 for incomplete or not fully validated address no longer returned. We will instead return AV12 if the locality level data is correct but the full mailing address is not correct.
  • Formatted Address updated to be closer to specification expected for the country

Data Updates

Reference Data Update
  • ALL COUNTRIES
Address Pattern Recognition Update
  • BELARUS, COSTA RICA, KYRGYZSTAN, MACAO, SAO TOME AND PRINCIPE, MOZAMBIQUE, SENEGAL, TAIWAN, VIETNAM


August 2020 Update

Released August 2020

General Information

  • We have worked to improvement the speed of edge cases in our engine. The number of records that could trigger a hang in the engine should be greatly diminished. If you run into a record that takes a long time to process, please submit it to Melissa.
  • We have a new BETA version of the web service with new additional outputs. We are making the switch to this new version the week of September 7th. Please review the information about this switch here: https://www.melissa.com/quickstart-guides/global-address-update. This is only newly added inputs and outputs, there should be no compatibility problems.

Country Specific Updates

ÅLAND ISLANDS
  • After review, we found that the thoroughfare level data is not at a level to justify the AV-3 (Thoroughfare level) classification and can incorrectly code legitimate thoroughfare. We are moving this country to AV-2 (Locality level) while we work on finding better data.
ARGENTINA
  • Improved the area alignment for Ciudad Autónoma de Buenos Aires AdministrativeArea.
CANADA
  • Improved handling of Canadian addresses that start with the format of ###-#### and is all in address lines. Before, the engine would confuse this valid but rare subpremise number and house number format for a phone number. This would only happen if postal code and locality input fields were not used.
CURAÇAO
  • Improving handling of address1 only input handling.
BARBADOS
  • Improved our thoroughfare level data. You should expect much more AV23 than before.
  • Improved geocoding
CÔTE D'IVOIRE (IVORY COAST)
  • Improved our thoroughfare level data. You should expect much more AV23 than before.
  • Improved geocoding
NETHERLANDS
  • We have switched to a new premium level data source. This new data source contains highly accurate street level information and also new subpremise information. Additionally, it also includes highly accurate rooftop level geocoding.
  • Due to the addition of subpremise level data, you should start receiving many more AV25 Result codes.
  • SubPremise information and parsed fields will now be populated for AV25 records.
  • We will return rooftop level geocodes and GS05 for almost all coded records.
  • Formatted Address reviewed and ensured to match postal agency specifications. This includes double spaces beween the locality and postal codes.
  • In the BETA version, DeliveryIndicator is now available for Netherlands.
  • In the BETA version, MelissaAddressKey and MelissaAddressKeyBase is now available for Netherlands.
NIGERIA
  • Improved our data source to include much more extensive thoroughfare level data.
  • You should expect much more AV23 than before.
  • Improved our engine to cut down on false coding
  • Improved Geocoding
NORWAY
  • Updated our area values to match the new administrative region revamp instituted by the Norway government in 2020.
SRI LANKA
  • Improved our thoroughfare level data. You should expect much more AV23 than before.
  • Improved geocoding
TURKEY
  • We have added a new high quality data source and revamped our engine for that source.
  • Subpremise level data with Building data and AV25 coding now available.
  • Increased number of GS05 rooftop level geocoding.
  • Reviewed and revamped Formatted Address to ensure match with postal agency standards.
UNITED STATES
  • Changed handing of two unique zip codes (12345 and 88888) based on customer data. We will no longer allow any and all input to code as valid (as per CASS specifications) but require a recognized street. This will improve data quality as we see many fake inputs using these postal codes.

Data Updates

Reference Data Update
  • ALL COUNTRIES
Address Pattern Recognition Update
  • ALAND ISLANDS, CANADA, CURACAO, BARBADOS, IVORY COAST, NETHERLANDS, NIGERIA, PAKISTAN, SRI LANKA, TURKEY, UNITED STATES


Build 3.0.1.150

April 2020 Update

Released April 2020

General Information

  • Improved handling of postal codes for AV-2 (Locality level) countries.
  • Fixed an issue where some AV-2 countries returned the country code in the country name field.

Country Specific Updates

ARMENIA
  • Improved data to increase AV23 and AV24 coding
  • Addresses with valid localities but invalid addresses will no longer code to AV22
CANADA
  • Removed the comma between the locality and administrative area in the Formatted Address to be more in line with the formal address guidelines published by CanadaPost.
CAPE VERDE ISLANDS
  • After review, we found that the thoroughfare level data is not at a level to justify the AV-3 (Thoroughfare level) classification and can incorrectly code legitimate thoroughfare. We are moving this country to AV-2 (Locality level) while we work on finding better data.
CZECH REPUBLIC
  • Improved our data to put the regions of Prague (example: Praha 10) into the locality as expected instead of the dependent locality.
DOMINICA
  • After review, we found that the thoroughfare level data is not at a level to justify the AV-3 (Thoroughfare level) classification and can incorrectly code legitimate thoroughfare. We are moving this country to AV-2 (Locality level) while we work on finding better data.
ETHOPIA
  • Improved detection and coding of localities
GREAT BRITAIN
  • Fixed a bug where some addresses entered with a postal code without spaces could code to an incorrect address. A small percentage of addresses were affected.
  • Fixed an issue where the British territories of Jersey, Guernsey, and Isle of Man had the dependent locality slotted as the locality.
GABON
  • After review, we found that the thoroughfare level data is not at a level to justify the AV-3 (Thoroughfare level) classification and can incorrectly code legitimate thoroughfare. We are moving this country to AV-2 (Locality level) while we work on finding better data.
GRENADA
  • After review, we found that the thoroughfare level data is not at a level to justify the AV-3 (Thoroughfare level) classification and can incorrectly code legitimate thoroughfare. We are moving this country to AV-2 (Locality level) while we work on finding better data.
GUERNSEY
  • Fixed an issue where the dependent locality was being used as the locality. This would not have significantly altered the address as the locality and the country name are the same.
ITALY
  • Changed the aggressiveness of the engine to lower the possibility of changing the address from the intended location in an effort to code the address.
ISLE OF MAN
  • Fixed an issue where the dependent locality was being used as the locality. This would not have significantly altered the address as the locality and the country name are the same.
JAPAN
  • Major data update.
  • Slightly improved coding accuracy.
JERSEY
  • Fixed an issue where the dependent locality was being used as the locality. This would not have significantly altered the address as the locality and the country name are the same.
KUWAIT
  • We have adjusted the Formatted Address to better fit in country postal standards
  • We have changed data sources to one with better coverage of the thoroughfares, dependent localities, and postal codes while removing the incomplete house numbers. This will move the country from AV-4 (House number) to AV-3 (Thoroughfare) but we believe this is an overall improvement.
  • Improved coverage of PO Boxes.
RWANDA
  • After review, we found that the thoroughfare level data is not at a level to justify the AV-3 (Thoroughfare level) classification and can incorrectly code legitimate thoroughfare. We are moving this country to AV-2 (Locality level) while we work on finding better data.
SAO TOME AND PRINCIPE
  • After review, we found that the thoroughfare level data is not at a level to justify the AV-3 (Thoroughfare level) classification and can incorrectly code legitimate thoroughfare. We are moving this country to AV-2 (Locality level) while we work on finding better data.
SLOVENIA
  • We have added Interpolated Rooftop (G-4) latitude and longitude information back for this country.
  • We have added an additional area level available to the user in the Administrative Area.
SPAIN
  • Major data update related to recent election/census activity in the country.
  • Significant improvement in the number of AV24 coding.
  • Improved the number of rooftop latitude and longitude points by around 8%.
VATICAN
  • Removed duplicate Administrative Area that was always the same as the Locality

Data Updates

Reference Data Update
  • ALL COUNTRIES
Address Pattern Recognition Update
  • ARMENIA, CAPE VERDE ISLANDS, CZECH REPUBLIC, DOMINICA, ETHOPIA, GREAT BRITAIN, GABON, GRENADA, GUERNSEY, ITALY, ISLE OF MAN, JAPAN, JERSEY, KUWAIT, RWANDA, SAO TOME AND PRINCIPE, SLOVENIA, SPAIN


February 2020 Update

Released February 2020

General Information

We had to combine the 2019Q4 and 2020Q1 update due to data source provider issues. However, this update includes a significant and extensive update for Great Britain. Please make sure to review the Great Britain section.

Country Specific Updates

COLOMBIA
  • Moved Building information to AddressLine2 instead of the same line as the thoroughfare.
  • Now using a dash in the premise number to separate values instead of a space.
GREAT BRITAIN
We have been working on a major update for Great Britain and are pleased to be able to provide them to you in this update. This update should represent a major improvement in quality and feature set.
  • We have added the following new data sets from Royal Mail at no change in cost for our users:
  • Not Yet Build – Addresses in the planning or construction phase
  • Multiple Residence – Individual dwellings in multiple occupancy buildings that share a front door
  • BFPO –British forces personnel serving overseas
  • We have incorporated a new geolocation source with much more accurate rooftop points for Great Britain. This data is not available from Royal Mail.
  • We have made changes in the Administrative Area field. Administrative Area is not used in the mailing address. We will be following the Royal Mail Unitary Authority Name administrative county where available.
  • We are currently working on infrastructure to move GB to a monthly update cycle. Additionally, we are also working on the ability to expose additional UK elements like UDPRN/DeliveryPointSuffix.
ISRAEL
  • Modified the Formatted Address and address lines to match in country postal rules.
  • Building and subpremise information now returned at the end of address1 instead of in a new line as per our country research.
  • Engine will now preserve valid 7 digit postal codes
  • Post office box values now returns as PO Box instead of Ta Do'ar
JAPAN
We have done a major re-configuration for Japan. Our previous data source for Japan is no longer available so we have acquired a new equally good source.
  • We have turned down the aggressiveness of the engine that would change the premise number value in order to code the address. This will result in more AV13 coding and less AV24 but we believe it is better this way.
  • Will now return a 〒Prefix for the postal code in the Formatted Address as per in country postal standards.
  • Slight variations in area parsing for new data source
  • Some changes in the makeup of the address lines using the deliverylines option.
  • Japan uses both full width and half width numbers, the half width version being the one that most latin languages are used to. To bring Japan in line with our other countries and more consistent in its behavior, we will using full width numerals in the Formatted Address if the OutputScript is set to Native and half width numerals if the OutputScript is set to Latin. If it is set to Match, we will detect the width from the input. For Address lines and parsed fields will always use half width as they are designed for database storage, comparison, and matching.
MONGOLIA
  • Changed from AV23 to AV22 country. The street data available was too out of date and preventing legitimate locality verification. Working on finding and evaluating new providers.
MYANMAR
  • Change in configuration to keep more input data on output
  • Updated area vales
NICARAGUA
  • Changed configuration to recognize locality for more records
SYRIA
  • Changed from AV23 to AV22 country. The thoroughfare information was dated and unreliable given the current state of the country.
TURKS AND CAICOS ISLANDS
  • Change in configuration to keep more input data on output
  • Updated area vales
UNITED ARAB EMIRATES
  • Reduced the rate of false coding. May result in slightly lower matching rates.
  • Improved matching and parsing of house number and Villa information.
UZBEKISTAN
  • Changed from AV23 to AV22 country. The street data available was too out of date and preventing legitimate locality verification. Working on finding and evaluating new providers.
YEMEN
  • Changed configuration to recognize locality for more records

Data Updates

Reference Data Update
  • ALL COUNTRIES
Address Pattern Recognition Update
  • COLOMBIA, GREAT BRITAIN, ISRAEL, JAPAN, MONGOLIA, MYANMAR, NICARUGUA, SYRIA, TURKS AND CAICOS ISLANDS, UNITED ARAB EMIRATES, UZBEKISTAN, YEMEN


October 2019 Update

Released October 2019

General Information

This update is considered a partial update as we are still waiting for updated data from some of our sources. This update combined with the next update, scheduled to arrive before the end of the year, should cover all countries

Country Specific Updates

ARGENTINA
  • We have made a number of changes to better correspond to the postal preferences of the country:
  • Formatted Address has been slightly modified
  • The Locality and Postal code are now returned on separate address lines
  • Premise Numbers will be returned with a prefix of “N°”
  • SubPremise, Building, SubBuilding information now returned at the end of the address lines.
  • We have tweaked our matching engine to better avoid false positive matches that will incorrectly change the address.
BELIZE
  • We have re-evaluated our data source for Laos and decided that it was not good enough to justify being an AV-3 country. We have removed the spotty thoroughfare data and improved our locality data so that more records can be verified at AV22 instead of returning an error. We are looking for better data to use in the near future.
CHRISTMAS ISLANDS
  • Improved our locality matching
COMOROS
  • Improved our locality matching
COOK ISLANDS
  • Improved our locality matching
GAMBIA
  • We have re-evaluated our data source for Laos and decided that it was not good enough to justify being an AV-3 country. We have removed the spotty thoroughfare data and improved our locality data so that more records can be verified at AV22 instead of returning an error. We are looking for better data to use in the near future.
GERMANY
  • Fixed an issue where some Postfache and postal code values were not available
GREAT BRITAIN
  • Minor improvement in matching rate
JAPAN
  • We have fixed an issue where changes to the premise number did not trigger an AC20 change code.
  • We have fixed an issue where the ISO 3166-2 Country Sub Division Code of JP-23 was not returned
JORDAN
  • We have removed some matching logic that caused false or over-aggressive matches
LAOS
  • We have re-evaluated our data source for Laos and decided that it was not good enough to justify being an AV-3 country. We have removed the spotty thoroughfare data and improved our locality data so that more records can be verified at AV22 instead of returning an error. We are looking for better data to use in the near future.
PORTUGAL
  • Formatted Address is now returned in all capital letters based on the preferences of the CTT.
  • We have turned down the aggressiveness of the engine to lower the possibility of coding to the wrong address.
  • We have switched our data source to one that we believe is better aligned with the official CTT data.
URUGUAY
  • A hyphen is returned between postal code and locality as per postal preference
  • Sub Premise information returned at the end of the street address as per postal preference

Data Updates

Reference Data Update
  • ARGENTINA, BELIZE, CANADA, CHRISTMAS ISLANDS, COMOROS, COOK ISLANDS, GAMBIA, GERMANY, ITALY, JORDAN, LAOS, PORTUGAL, UNITED STATES, URUGUAY
Address Pattern Recognition Update
  • ARGENTINA, BELIZE, CHRISTMAS ISLANDS, COMOROS, COOK ISLANDS, GAMBIA, GREAT BRITAIN, JAPAN, JORDAN, LAOS, PORTUGAL, URUGUAY


August 2019 Update

Released August 2019

General Information

  • This update is later than usual due to the delay in the last build. We expect the next build to get back on track with the regular schedule.
  • We have changed the change code logic so that one input cannot be used against two output values in terms of the change code. This would apply in cases where two areas like the locality and administrative area are the same. If the input contained that value, in the past, we would not report any change code. However, now that single input will only be counted against a single output, and we would add a change code for appending the 2nd area value.

Country Specific Updates

ARGENTINA
  • Improved the alignment of the address area values
AUSTRALIA
  • Improved pattern recognition to increase coding rate
BULGARIA
  • Made an effort to decrease the number of false positive coding. This may result in some addresses coding before that do not now but we believe the overall quality is better now.
  • Improved parsing result
  • Standardized use of abbreviated thoroughfare types
BERMUDA
  • We have acquired and incorporated a better data source that includes thoroughfares and house numbers. The quality of the thoroughfares has also increased. Overall it is a dramatic improvement in the coding quality of this country.
  • Improved parsing
  • Administrative Area no longer returned for this country. It is unnecessary for a country of this size.
  • Improved Formatted Address structure
COLOMBIA
  • Improved recognition of addresses without thoroughfare leading types
EGYPT
  • Changed Formatted Address to better conform to country standards
FRANCE
  • We have standardized the latitude and longitude to 6 digits after the decimal to bring it in line with other countries. The 7th digit of the latitude/longitude corresponds to a variance of around 11 millimeters, which is insignificant for the use of coordinates in addressing.
ESTONIA
  • Improved coding quality
  • Improved address structure in Formatted Address
HUNGARY
  • Improved coding accuracy and thoroughfare name recognition
  • Improved recognition of real life address patterns, especially ones involving a period in the input premise number
ITALY
  • Improved recognition of abbreviations for better coding accuracy
PHILIPPINES
  • We have greatly improved our address pattern recognition for the Philippines so that our coding accuracy has increase dramatically.
  • Decreased cases of false coding
  • Will no longer return AV22 for bad address
  • Improved Parsing
QATAR
  • Decreases cases of false coding. This could affect addresses that have previously coded but overall we believe the quality is better
  • Moved Building information to before thoroughfare but on the same line in accordance to our research
ROMANIA
  • Greatly increase our coding accuracy and the return of AV24 results.
  • Restructured the Formatted Address in accordance with preference by the Romanian post office.
  • We are returning the Locality in all capitals in accordance with postal preference.
THAILAND
  • Improved detection of dependent locality

Data Updates

Reference Data Update
  • ALL Countries
Address Pattern Recognition Update
  • ARGENTINA, AUSTRALIA, BULGARIA, BERMUDA, COLOMBIA, EGYPT, FRANCE, ESTONIA, HAITI, HUNGARY, ITALY, NICARAGUA, PHILIPPINES, QATAR, ROMANIA, THAILAND, UNITED ARAB EMIRATES


April 2019 Update

Released April 2019

General Information

  • This update had been delayed due to some issues with getting data updates from several of our providers. Melissa apologizes for any inconvenience this may have caused and we are working to prevent delays like this in the future.

Country Specific Updates

BENIN
  • Decreased false address correction
BOTSWANA
  • Decreased false corrections
  • Improved address recognition and coding rates
BURKINA FASO
  • Decreased false address correction
BURUNDI
  • Greatly reduced false address corrections
  • Improved address pattern recognition
CAMEROON
  • Improving coding rates
  • Decreased false address correction
JORDAN
  • Greatly improved our address recognition engine and coding rates
  • Improved parsing
  • More accurate Formatted Address positioning and casing
MACEDONIA
  • Improved address recognition
MALAYSIA
  • We have made an effort to decrease the false positive that would change the address to a different one than intended in coding. This may result in some addresses not coding which did before, but we believe the tradeoff for better overall quality is worth it.
  • Improved general parsing and sub-premise level parsing
  • Improved change code detection
MALTA
  • Decreased false address correction
  • Improved parsing
PERU
  • Improving pattern recognition and coding rates
  • Improved parsing
  • We have researched and more closely aligned our output to postal authority documentation
  • Improving handling of sub-premise values
  • Addresses with errors no longer return AV22
SERBIA
  • We have moved to a new and improved data set that includes the most current postal code data for Serbia. This is the PAK (Post Office Location Code) which we are now appending to the address.
  • This new updated data set does not include geocoding, so latitude and longitude is currently not available. We are working hard on adding this information in on a future update.
  • Improved parsing of the address
  • Improving casing of the Formatted Address
UNITED STATES
  • Increased the number of addresses in our database that are real physical addresses but not serviced by the USPS

of subpremise values based on Sociedad Estatal de Correos y Telégrafos documentation

Data Updates

Reference Data Update
  • ALL Countries
Address Pattern Recognition Update
  • BENIN, BOTSWANA, BURKINA FASO, BURUNDI, CAMEROON, JORDAN, MACEDONIA, MALAYSIA, MALTA, PERU, SERBIA, UNITED STATES


Build 3.0.1.148

December 2018 Update

Released December 2018

Country Specific Updates

CYPRUS
  • Improved address parsed values
  • We have made an effort to decrease the false positive that would change the address to a different one than intended in coding. This may result in some addresses not coding which did before, but we believe the tradeoff for better overall quality is worth it.
  • Based on the Cypus Post, we have fixed the format placement of the premise number in the address.
FRENCH GUIANA
  • Improved data source
  • Improved parsing and coding accuracy
GUADELOUPE
  • Improved data source
  • Improved parsing and coding accuracy
GREECE
  • Improved address parsed values
  • We have made an effort to decrease the false positive that would change the address to a different one than intended in coding. This may result in some addresses not coding which did before, but we believe the tradeoff for better overall quality is worth it.
  • Per preference of Hellenic Post ELTA, locality will be capitalized in the formatted address.
LATVIA
  • Improved parsed values
  • As per VAS Latvijas Pasts, we have adjusted the address lines and formatted address to more closely resemble the postal preferred format. Postal code now has the “LV-“ prefix in formatted address.
  • We have made an effort to decrease the false positive that would change the address to a different one than intended in coding. This may result in some addresses not coding which did before, but we believe the tradeoff for better overall quality is worth it.
LUXEMBOURG
  • Improved parsed values
  • As per Post Luxembourg, SubNationalArea is no longer used and will not be returned. Locality will be capitalized in FormattedAddress. PostalCode will be prefixed with a “L-“ as per postal preference.
  • Will now return area information based on the thoroughfare name, which can be in French or Luxembourgish.
MARTINIQUE
  • Improved data source
  • Improved parsing and coding accuracy
MAYOTTE
  • Improved data source
  • Improved parsing and coding accuracy
REUNION
  • Improved data source
  • Improved parsing and coding accuracy
SAINT PIERRE AND MIQUELON
  • Improved data source
  • Improved parsing and coding accuracy
SLOVAKIA
  • Greatly improved the output parsed values
  • Reduced the number of false positives when coding the address
  • Improved parsing of subpremise information
  • Improved handling of premise number. Will append the town description number to the premise number when available.
SLOVENIA
  • Removed extra space value in the address lines after postal code
  • Removed the dependent locality data from the formatted address as per postal standards
  • Improved casing as per postal preference
  • Improved parsing output values
SPAIN
  • We have improved the coverage of the country, particular in rural towns
  • We have improved our coding algorithm to decrease the number of false postives
  • Greatly Improved address parse values
  • Improved casing of parsed values
  • Improved casing and handling of subpremise values based on Sociedad Estatal de Correos y Telégrafos documentation
UNITED STATES
  • Added additional addresses into our Non-USPS database of real physical addresses that is not serviced by the USPS.
  • Now will recognize and return back the PMB (Private Mailbox) value in the Address1 line as well as the PostBox field.
  • Fixed the case where if an street address and po box address was in the same input, the position of each address could change depending on if the DELIVERYLINES option was set.

Data Updates

Reference Data Update
  • ALL Countries
Address Pattern Recognition Update
  • CYPRUS, GREECE, LATVIA, LUXEMBOURG, KOREA, SLOVAKIA, SLOVENIA, SPAIN, UNITED STATES


September 2018 Update

Released September 2018

General Updates

  • We have improved the logic of detecting the country name if it is not in the country input field. This is still not a recommended approach to not have the country input field populated, but we will make a best effort to identify the country name if it is in another part of the address.
  • We have added additional variations of country names that we recognize.

Country Specific Updates

BELGIUM
  • Belgium has three official languages. We are not returning the language of the full address based on the language of the input Thoroughfare. In the past, there was potential for the thoroughfare value to be in one language and the locality to be in another language.
  • Improved parsed value
CROATIA
  • Improved parsed values
  • Improved casing of thoroughfare types
  • Improved casing of attached characters in Premise and Subpremise numbers
  • Removed the dependent locality from returning in address lines or formatted address as they are not normally used.
ITALY
  • We have revamped our Italian data and engine from the ground up. We have acquired and integrated more accurate address and geocoding data as well as performed extensive research into the country’s postal standards.
  • As per Poste Italiane SpA’s strong preference that the address on mail pieces are written in all capital letters, we have changed our FormattedAddress field to contain all capital letters as the FormattedAddress is meant to simulate a mailing label. The address lines 1 through 8 are still in title case.
  • We have improved the coding rate while lowering the number of false address changes. To limit the number of false address changes, we may lose a few records that coded before but don’t now. However, the overall accuracy should be significantly improved.
  • We have improved our database and filled in thoroughfare and house numbers for almost all records. This will result in dramatically less AV23 (if we only had the thoroughfare) and AV22 (if we only had the locality) coding.
  • Greatly Improved address parse values
  • Improved casing of parsed values
  • For addresses with both a street address and a po box, we are making the street address the dominant address. The service is only designed to verify a single logical address at a time.
LITHUANIA
  • Improved address parse values
  • Improved casing of thoroughfare types

Data Updates

Reference Data Update
  • BELGIUM, CROATIA, ITALY, LITHUANIA
Address Pattern Recognition Update
  • BELGIUM, CROATIA, ITALY, LITHUANIA


Build 3.0.1.143

Released July 2018

General Updates

  • We have revamped our change code system from the ground up, with an emphasis on the AC01 (Postal Code), AC03 (Locality), AC10 (Thoroughfare), and AC20 (House Number) codes. We know that the change code system is not perfect before and not perfect now. However, we have redesigned the infrastructure to allow us to make fixes easier and faster in the future. Please review our result code usage guide for more information:
http://wiki.melissadata.com/index.php?title=Global_Address_Verification%3AResult_Codes#Change_Code_System

Country Specific Updates

ALBANIA
  • Fixed issue where one known record would cause the engine to hang
  • Improved parsing logic for increased AV25 coding
  • Improved address format to match in country expectation
  • Improved parsing
  • Improved output consistency
ANDORRA
  • Improved handling of full input addresses
  • General coding rate improvement
  • Improvement in geocoding level
  • Improved parsing
BRAZIL
  • General coding improvements
  • Improved locality and dependent locality area level slotting
  • Improved diacritic matching for thoroughfares
CANADA
  • Fixed a bug where diacritic input could be converted to bad characters in the output for some non-codable addresses.
CHINA
  • The country subdivision code values have been updated to a newer of the code. The old version used number (CN-01) while the new version uses letters (CN-SH).
FRANCE
  • We have revamped our France data and engine from the ground up. We have reviewed and revamped all of our rules and algorithms as well as performed extensive research into French postal standards. There will be a lot of changes overall, we are very confident that the new engine is superior to the old one. The major changes are:
  • As per La Poste strong preference that the address on mail pieces are written in all capital letters, we have changed our FormattedAddress field to contain all capital letters as the FormattedAddress is meant to simulate a mailing label. The address lines 1 through 8 are still in title case.
  • We have fixed a bug where an arrondissement on input can sometime be duplicated on the output.
  • We have improved the coding rate while lowering the number of false address changes. To limit the number of false address changes, we may lose a few records that coded before but don’t now. However, the overall accuracy should be significantly improved.
  • We have improved our database and filled in thoroughfare and house numbers for almost all records. This will result in dramatically less AV23 (if we only had the thoroughfare) and AV22 (if we only had the locality) coding.
  • Greatly Improved address parse values
  • Improved casing of parsed values
  • For addresses with both a street address and a po box, we are making the street address the dominant address. The service is only designed to verify a single logical address at a time.
GERMANY
  • Removed historical but currently invalid PO Box postal code records
GHANA
  • Improved general coding accuracy
  • Changed engine to return partial error AV12 instead of AV22 when only locality could be verified but there are additional source data for those areas
GIBRALTAR
  • Reclassified the geocoding level to G4 (interpolated rooftop) based on a review of the data and expected coverage
  • Improved Parsing
GREAT BRITAIN
  • Slightly improved coding rates
KIRIBATI
  • Improvement in area level detection
  • Improvement in parsing
LESOTHO
  • Data quality metric downgraded from AV-4 (premises) to AV-3 (Thoroughfare) after a re-evaluation of the data source
LICHTENSTEIN
  • Improved handling of duplicate or extra information
  • Improved parsing
MONTENEGRO
  • Improved handling of premise number indicators
  • Improved handling of sub-premise types
  • Improved Parsing
NEW ZEALAND
  • Improved handling of addresses with delimiters
  • We have worked to decrease false coding rates. This may result in some addresses that coded before but not now. However, we believe the overall accuracy is improved.
  • Increase number of thoroughfare types that are recognized
  • Improved coding when thoroughfare types are not present
  • Improved handling of duplicate and extra information
  • We are losing access to some sub-premise, po box, and rural postal code delivery data. Premise level data is still available and will remain available.
POLAND
  • After research and review of in country postal standards, we are returning the locality in all capital letters in the formatted address, as per postal preference.
  • Improved handling of addresses with delimiters
  • We have worked to decrease false coding rates. This may result in some addresses that coded before but not now. However, we believe the overall accuracy is improved.
  • Improved handling of multi part subpremise like “1A/lok. 1”
  • Added handling of the premise number before the thoroughfare
ROMANIA
  • After research and review of country postal standards, we are revising the output format for addresses in Romania from “Building SubBuilding [newline] Thoroughfare Premise” to “Thoroughfare Premise Building SubBuilding”
SAN MARINO
  • Improved handling of premise and sub-premise types
  • We have removed sparse old database records with the full postal code for the country. Currently, we have the first 3 characters of the postal code and will assume the remaining digits are valid.
  • Decrease the occurrence of coding to the wrong address.
SINGAPORE
  • After research of in country postal standards, we are removing some area level data that is not used for delivery from the address lines and formatted address.
  • Improved parsing and coding ability when the postal code is not present
  • We have decided to not rely so heavily on the postal code. Since the postal code in Singapore is unique to an individual address, we have previously been relying on the postal code almost entirely and could simply replace the entire rest of the address to match the postal code. We have decided to place less emphasis on the postal code and also use the other parts of the address more in the very possible case there is a typo in the postal code. This will decrease our coding rate in the country but will decrease coding to the wrong address, which we consider much worse than not coding. As a work-around, if you enter just the postal code, we will fill in the rest of the address.
SOUTH AFRICA
  • Improve handling of inputs with range delimiters
  • Improved handling of duplicate and extra data
  • Improved parsing
  • Our PO Box data has grown too dated to be reliable, so we are converting PO Box coding from AV25 to AV22.
SVALBARD & JAN MAYEN ISLANDS
  • Improved area level coding
  • Improved parsing
THE DEMOCRATIC REPUBLIC OF CONGO
  • General coding improvement
  • Improved parsing
  • Improved thoroughfare detection
UNITED STATES
  • Added new pattern recognition for private mailboxes at commercial mail receiving agencies (CMRA). Example: 123 Main Dr Ste 10-123 where Ste 10 is the CMRA and 123 is the private mailbox.

Data Updates

Reference Data Update
  • All countries
Address Pattern Recognition Update
  • ALBANIA, ANDORRA, BRAZIL, CANADA, FRANCE, GERMANY, GHANA, GIBRALTAR, GREAT BRITAIN, KIRIBATI, LESOTHO, LICHTENSTEIN, MONTENEGRO, NEW ZEALAND, POLAND, PORTUGAL, ROMANIA, SAN MARINO, SOUTH AFRICA, SVALBARD & JAN MAYEN ISLANDS, THE DEMOCRATIC REPUBLIC OF CONGO, UNITED STATES

Build 3.0.1.142

Released May 2018

General Updates

  • Fixed an issue with the DeliveryLine option when using a LineSeparator that is the default
  • General improvement in false AC code detection
  • General improvement in GS03 (Community level) geocoding

Country Specific Updates

AUSTRALIA
  • Fixed issue where one known record would cause the engine to hang
  • Improved parsing logic for increased AV25 coding
BELGIUM
  • Fixed error that resulted in CountrySubDivisionCode of BE-VWV not always returning.
BRAZIL
  • Addition of PostBox numbers to the data to increase verification rates of po boxes
CANADA
  • Fixed a bug where in rare cases, some invalid characters could be returned in the result.
  • Fixed some rare cases where an AV code would not be returned.
  • Fixed bug where sometimes, the formattedAddress output field would be empty when it was not supposed to be.
  • Fixed issue of correctly identifying thoroughfare trailing type vs thoroughfare leading type
CZECH REPUBLIC
  • Improved coding and matching logic to improve coding rates. Now can recognize and correct more addresses to drastically improve the rate of AV24 coding.
FINLAND
  • Improved the handling of the two main languages in Finland, Swedish and Finnish. The language used will now be consistent across the full address and will use the thoroughfare as the main decider of which language to use.
GERMANY
  • Improved parsing logic
GREAT BRITAIN
  • Improvement in GS05 (rooftop level) geocoding
JAPAN
  • Improved data normalization to ensure all parts of the address are verified
  • Improved parsing logic
UNITED STATES
  • Improved the return consistency of the AE08 result code (sub-premise number invalid) when an AV14 error is found.
  • Fixed the rare occurrence that the response for a US territory will not be fully populated.
  • Improved the AC code logic for US territories.

Data Updates

Reference Data Update
  • All countries
Address Pattern Recognition Update
  • ANDORRA, BRAZIL, CAYMAN ISLANDS, CZECH REPUBLIC, FINLAND, GREECE, ICELAND, JAPAN, KOREA, LATVIA, SAUDI ARABIA, SLOVAKIA, THAILAND


Build 3.0.1.139

Released December 2017

General Updates

  • General Bug Fixes
  • Fixed an issue where records with a lot of non-address or junk data can cause the engine to hang for a long period of time
  • Fixed a bug where DeliveryLine was not being populated for records with only AE codes.
  • Improved the accuracy of changes codes

Country Specific Updates

AUSTRALIA
  • Most of the geocodes in Australia has been reclassified from Rooftop (GS05) to Interpolated Rooftop (GS06). The actual longitude coordinates have not changed and most of the coordinates are effectively at Rooftop level, but due to ranged information in the geocode source, GS06 is the more technically accurate code.
  • Resolved issue where a few good or partially good addresses were returning AE05 – Multiple Match Error
  • Resolved issue that prevented some addresses with spelled out or non-standard level type indicators from verifying
  • Fixed formatting of Formatted Address when a subpremise level is present without a subpremise
CANADA
  • Fixed an issue where FormattedAddress was sometimes blank
  • Fixed an issue where diacritic values were occasionally not being outputted correctly when classified by the engine as extra non-address info.
GREAT BRITAIN
  • The Geocode levels for Great Britain have been re-evaluated and modified. Some previously rooftop level (GS05) has been reclassified as Interpolated Rooftop (GS06). Additionally, many postal code level (GS03) has been reclassified as Interpolated (GS06) when only a few addresses are in the candidate list because the postal code coordinates in Great Britain are quite accurate.
  • The engine is now able to append Organization in more instances when there are no conflicts or multiple possibilities detected.
IRELAND
  • Fixed a bug that resulted in FormattedAddress being blank for a good address
NEW ZEALAND
  • Performed review of data alignment in country and improved data consistency.

Data Updates

Reference Data Update
  • All countries except for ANGUILLA , ANTARCTICA, ARGENTINA, BARBADOS, BELARUS, BELGIUM, BOLIVIA, BONAIRE, BOUVET ISLAND, BRAZIL, BULGARIA, CROATIA, DENMARK, DGYPT, FIJI, FINLAND, INDIA, ISREAL, ITALY, JAMAICA, JAPAN, KAZAKHSTAN, SOUTH KOREA, KYRGYZSTAN, LATVIA, MACAO, MOROCCO, MOZAMBIQUE, NEPAL, NICARAGUA, PAPUA NEW GUINEA, PERU, ROMANIA, RUSSIA, SAN MARINO, SINT MAARTEN, SOUTH AFRICA, TAIWAN, TURKEY, UKRAINE, URUGUAY, UZBEKISTAN, VENEZUELA, VITENAM
Address Pattern Recognition Update
  • ANDORRA, AUSTRALIA, CANADA, COLOMBIA, FRANCE, FRENCH POLYNESIA, INDONESIA, IRELAND, LITHUANIA, GREAT BRITAIN, MOROCCO, NEW ZEALAND, UNITED STATES

Global Email Object

Reference Data Update
  • New domains added

Global Phone Object

Reference Data Update
  • All countries

Global Name Object

Reference Data Update
  • Data for Mexico names added to the data file


Build 3.0.1.133

Released June 2017

General Updates

  • Added AC22 for Organization Change
  • Update country coverage for CountrySubdivisionCode values
  • Improved fuzzy matching logic for correcting misspelled thoroughfares

Country Specific Updates

AUSTRALIA
  • Fixed coding issue where some streets with a very large number of premises did not correctly get coded
DENMARK
  • Improved area alignment and general engine coding effectiveness
FRANCE
  • Removed certain abbreviations and standardization from triggering change codes
GERMANY
  • Fixed some misc. coding issues
GREAT BRITAIN
  • Fixed an issue were an input record would result in an engine crash
POLAND
  • Removed certain abbreviations and standardizations from triggering change codes
SPAIN
  • Removed certain abbreviations and standardizations from triggering change codes
SWEDEN
  • Improved area alignment and general engine coding effectiveness

Data Updates

  • Reference Data Update: ALL Countries
  • Address Pattern Recognition Update: DENMARK, EGYPT, FRANCE, HONG KONG, KOREA, MOZAMBIQUE, NEW ZEALAND, SWEDEN


Build 3.0.1.121

Released January 2017

General Updates

  • Fixed handling of alpha-numeric house numbers and house ranges (eg: 10-12, 10A-12, 10A-12B etc).
  • Fixed several cases of AC03 being triggered without locality change (targeted for FR, LU, and BE)
  • Fixed a case of triggering of AC11 without thoroughfare trailing change (targeted for DK)
  • Fixed some cases of AC20 being incorrectly triggered (targeted for GB)
  • Changed PO Box number errors with correct postal code or localities from AV22,AE12 to AV12,AE12 (targeted for AU,DE,NL,GB)

Country Specific Updates

BELGIUM
  • Fixed some cases of addresses returning in mixed languages
FINLAND
  • Improved area alignment
GERMANY
  • Improved recognition of postal codes with a prefix
  • Improved data issue in “Rüsselsheim am Main”
GREAT BRITAIN
  • Fixed some incorrect postal code changes in Great Britain
  • Improved coding accuracy in Great Britain
INDIA
  • Improved parsing for inputs containing landmark elements
IRELAND
  • Fixed matching logic that resulted in too many AE05 - multiple match errors.
  • Fixed issue with the DeliveryLines option not removing all area values into the parsed fields
  • Improving coding accuracy
MEXICO
  • Fixed several cases with missing CountrySubdivisionCode
NETHERLANDS
  • Fixed cases of coding invalid PO Boxes
  • Improved recognition for organization name in Addressline1
  • Improved area alignment

Data Updates

  • Reference Data Update: ALL Countries
  • Address Pattern Recognition Update: ARGENTINA, AUSTRALIA, BRAZIL, BULGARIA, COLOMBIA, DENMARK, ECUADOR, FINLAND, GERMANY, GREAT BRITAIN, INDONESIA, IRELAND, KOREA, MALAYSIA, NEW ZEALAND, PHILIPPINES, PORTUGAL, RUSSIA, SERBIA, SPAIN, TAIWAN, THAILAND, TURKEY, UNITED ARAB EMIRATES, VIETNAM


Build 3.0.1.116

Released September 2016

General Updates

  • Added Packstation data for Germany
  • Fixed records with missing CountrySubdivision in Mexico

Data Updates

  • Reference Data Update: GERMANY


Build 3.0.1.115

Released October 2016

General Updates

  • Speed Improvement for many countries
  • Coding improvement for Great Britian, can now code address with just postal code and house number
  • Company detection improvement for Australia
  • Multiple fixes for Germany
  • Misc address issue fixes

Data Updates

  • Reference Data Update: All countries
  • Parsing Logic Update: ARGENTINA, AUSTRALIA, BRAZIL, BULGARIA, CHILE, CHINA, CZECH REPUBLIC, EGYPT, GREECE, GERMANY, GREAT BRITAIN, LITHUANIA, POLAND, ROMANIA, THAILAND, VIETNAM, ZIMBABWE
  • Address Handling Update: LAOS


Build 3.0.1.114

Released May 2016

General Updates

  • Added AddressType return for Canada (previously US only)
  • Bug fixes in Germany, United Kingdom, United States
  • Fixed problem with selected address separator not being used in FormattedAddress
  • Misc address issue fixes

Data Updates

  • Reference Data Update: All countries
  • Parsing Logic Update: AUSTRALIA, CHILE, FRANCE, GREAT BRITAIN, JAPAN, KOREA, NETHERLANDS
  • Address Handling Update: BRAZIL, CHILE, CHINA, EGYPT, FRANCE, GREAT BRITAIN, IRELAND, JAPAN, KOREA, NETHERLANDS, NORWAY, TAIWAN


Build 3.0.1.109

Released November 2015

General Updates

  • Added new CountrySubdivisionCode output field. Only populated for some countries
  • Bug fixes in Germany
  • Fixed error in the service when blatant non-address data (like email addresses) were sent in
  • Misc address issue fixes

Data Updates

  • Reference Data Update: All countries
  • Parsing Logic Update: AUSTRALIA, CHINA, COLOMBIA, FRANCE, GREECE, KOREA
  • Address Handling Update: ARGENTINA,AUSTRALIA,CHILE,CHINA,FINLAND,FRANCE,GREECE,HONG KONG,INDIA,IRELAND,KOREA,NORWAY,POLAND,TAIWAN,UNITED KINGDOM,


Build 3.0.1.105

Released July 2015

General Updates

  • Implemented Significant Speed improvements
  • Added handling of new South Korean postal code format
  • Misc address issue fixes

Data Updates

  • Reference Data Update: All countries
  • Parsing Logic Update: AUSTRALIA, GREECE, JAPAN, SOUTH KOREA, TAIWAN,
  • Address Handling Update: AUSTRALIA, CHINA, FRANCE, GREECE, IRELAND, ITALY, JAPAN, SOUTH KOREA, PORTUGAL, TAIWAN, THAILAND, UNITED KINGDOM


Build 3.0.1.103

Released May 2015

General Updates

  • Coding improvements for Germany
  • Addresses that do not code will now return back the input in address lines when DELIVERYLINES option is ON
  • Misc bug fixes

Data Updates

  • Reference Data Update: CHINA, ECUADOR, GREENLAND, IRAQ, QATAR
  • Parsing Logic Update: ARGENTINA,BRAZIL,CHINA,DENMARK,DOMINICAN REPUBLIC,FRANCE, INDIA,ITALY,KOREA REPUBLIC OF,NEW ZEALAND, NORWAY, POLAND, PORTUGAL, QATAR,SPAIN, UNITED KINGDOM
  • Address Handling Update: CHINA, TAIWAN


Build 3.0.1.101

Released February 2015

General Updates

  • Made coding improvements to Germany
  • Added PO Box data for Germany
  • Improved verification speed for China
  • Improved title casing for all countries
  • Misc bug fixes

Data Updates

  • Reference Data Update: All countries
  • Parsing Logic Update: AUSTRIA,CHINA,SOUTH AFRICA,UNITED KINGDOM,AUSTRALIA,CANADA,CROATIA,CZECH REPUBLIC,FRANCE,GERMANY, GREECE,INDIA,IRELAND,ITALY,KOREA REPUBLIC OF,LIBYA,NEW ZEALAND,PHILIPPINES,UNITED ARAB EMIRATES
  • Address Handling Update: AUSTRIA, CHINA, SOUTH AFRICA, UNITED KINGDOM


Build 3.0.1.99

Released January 2015

General Updates

  • Added JSONP functionality to the web service
  • Improved coding accuracy and parsing capability for Germany
  • Fixed an issue that prevented output in NATIVE script
  • Misc bug fixes


Build 3.0.1.94

Released November 2014

General Updates

  • Improved casing for Australia
  • Fixed case where thoroughfare change not being reported in result codes
  • Improved Canadian PO Box parsing
  • Increase recognition of variations of US country names
  • Misc bug fixes

Data Updates

  • Reference Data Update: All countries
  • Parsing Logic Update: ARMENIA, AUSTRALIA, BAHAMAS, BELGIUM, BOTSWANA, BRAZIL, CZECH REPUBLIC, GREECE, HONG KONG, INDIA, INDONESIA, IRAQ, MACAO, NEW ZEALAND, SLOVAKIA, SPAIN, TAIWAN, UKRAINE, GREAT BRITAIN
  • Address Handling Update: BELGIUM


Build 3.0.0.90

Released August 2014

General Updates

  • Improved formatting for some New Zealand and China addresses
  • Fixed issue with some Australian suite/apartment addresses
  • Fixed crashes on certain addresses
  • Fixed street name parsing to building issue in Netherlands
  • Fixed several Dutch parsing issues
  • Improved Hebrew transliteration and processing
  • Other smaller misc fixes

Data Updates

  • Reference Data Update: All countries
  • Parsing Logic Update: AUSTRALIA, BELGIUM, BRAZIL, CHINA, FRANCE, GIBRALTAR, HONG KONG, HUNGARY, INDIA, JAPAN, MACAO, MEXICO, PHILLIPINES, PORTUGAL, RUSSIA, SINGAPORE, SPAIN, TAIWAN, GREAT BRITAIN
  • Address Handling Update: AUSTRALIA, BELGIUM, CHINA, GERMANY, INDONESIA, ITALY, JAPAN, MALAYSIA, NETHERLANDS, NEW ZEALAND, ROMANIA, TURKEY, GREAT BRITAIN


Build 3.0.0.89

Released June 2014

General Updates

  • Improved spelling correction logic
  • Improved coding rates France, Great Britain, and Germany when an Organization is present
  • Addition of an AV code when an AE05 (multiple match error) occurs so the user can still see level to which the address was valid
  • Improved handling of extra address lines in the US and Canada so data is not lost
  • Improved matching for floors and incorrect postal codes
  • Fixed a Taiwanese parsing issue
  • Fixed street parsing issue in Paris, FR
  • Fixed a consistency issue with Ireland addresses
  • Fixed issues with Germany and Australia mangled addresses

Data Updates

  • Reference Data Update: All countries
  • Parsing Logic Update: ARGENTINA, AUSTRALIA, BELGIUM, BRAZIL, CHINA, COLOMBIA, FRANCE, GERMANY, HUNGARY, INDONESIA, IRELAND, ISRAEL, ITALY, JAPAN, SINGAPORE, UNITED KINGDOM
  • Address Handling Update: AUSTRALIA, CHINA, HUNGARY


Build 3.0.0.73

Released November 2013

General Updates

  • Improved data for New Zealand and Great Britain
  • Improved Transliteration
  • General Bug fixes


Build 3.0.0.54

Released June 2013

General Updates

  • Improved data for Albania, Angola, Azerbaijan
  • General Bug fixes


Build 3.0.0.27

Released November 2012

General Updates

  • Allow AddressLines only input (without parsed out locality/admin area/postal code) for US and Canada
  • General Bug fixes


Build 1.0.0.0

Released June 2012

  • Initial Release