GeoCoder Object Build History
Below is a list of changes and
additions to GeoCoder Object.
BUILD 1930 Released 2/12
- COMPATIBILITY SUMMARY
- No compatibility issues. Use of AddressKey in GeoCode() and GeoPoint() required for new Non-USPS addresses but using Zip, Plus4, and DeliveryPoint will still work for all regular addresses.
- HPUX DEPRECATION NOTICE
- HP-UX versions of Geocoder is no longer available and is no longer
supported.
- INTERFACE CHANGES
- FUNCTIONALITY CHANGES
- The Geocode() and GeoPoint() methods can now also accept an 11 character AddressKey as the first parameter. AddressKey is a key unique to each address that is returned by Address Object. This was added to support the addition of Non-USPS addresses. If you need to geocoding information for Non-USPS addresses, you must use the AddressKey. Please reference the manual for more details.
- Improved geocoding accuracy for addresses containing suites.
- DATA FILE CHANGES
- This update of Geocoder contains the new 2010 Census information.
Build 1885 Released 10/11
- INTERFACE CHANGES
- FUNCTIONALITY CHANGES
- A few postal code that were coded as valid but did not have latitude and longitude values fixed.
- Spaces at the end of CBSATitle and CBSATitleDivision properties trimmed.
Build 1826 Released 8/11
- COMPATIBILITY SUMMARY:
- No compatibility issues. New data file and features added, but there is no effect on existing applications.
- INTERFACE CHANGES
- Added new method SetPathToGeoCanadaDataFiles(). Using this method will allow you to geocode Canadian records. Please reference the documentation for more information.
- FUNCTIONALITY CHANGES
- Geocode() and GeoPoint() methods can now geocode Canadian records if SetPathToGeoCanadaDataFiles() is set correctly and your license
allows for Canadian geocoding. Simply pass in the postal code as the ZipCode parameter.
- New GetResults value of GE05 added. This code indicates that you are trying to geocode for a country that you license is not enabled for.
- GetResults value of GS01 (and deprecated StatusCode value of 9) now covers both US and Canadian records. If the record is a US record, GS01 indicates the record was geocoded to the zip+4. If the record is a Canadian record, GS01 indicates the record was geocoded to the full 6 digit Canadian postal code. Similarly, GS03 indicates geocoded to the Zip code level for US, and geocoded to the 3 digit postal code level for Canada.
- DATA FILE CHANGES
- New data file named mdGeoCanada.db now included. This file will be used to geocode Canadian records.
Build 1787 - Released 05/11
Build 1733 Released 2/11
- GeoPoint lat/long pointing to property instead of street
- GeoPoint latitude and longitude coordinates have been modified to mostly point to the address property instead of the street in front of the address. This was done to make drawing boundary maps easier.
- CBSA information available for 5-digit coded PO Boxes
- CBSA information is now available for PO boxes that can only be coded to the 5-digit Zip because there are no plus4’s for them.
Build 1676 Released 10/2010
- New GetLicenseExpirationDate() method
- This method retrieves the date that your license string will
expire.
- New Interpolated Rooftop Result
- New rooftop address points have been added to Geocoder based
on street shape maps. Please see the manual for more
details. A new Result of GS06 and Status of A has been added
to Results and StatusCode properties for a interpolated
rooftop result.
- Rooftop data now Multi-source
- Geocoder rooftop data is now multi-sourced. We have combined
data from multiple vendors to provide the most complete
rooftop coverage possible.
** Warnings: Please take note. GeoPoint users must update
both the data files and the Geocoder Object library. If you
do not, your GeoPoint records would contain the letter A or
B at the end of the Longitude. Please update to take
advantage of the new Geocoding features described below.
Build 1602 Released 04/15/2010
-
New Data Format
- GeoCoder now uses the new Multinet
data format.
- Precision Changes
- Geo Information have be adjusted to
more accurately identify the 9 digit and 5 digit zip codes.
There are PO box addresses that have repeating Latitude and
Longitude information in the GeoCoder Database. We used to
code them at the 9 digit level, now we correctly code them 5
digit level.
Build 1492 Released 10/15/2009
- Two
new data files (mdGeoCbsa.dat and mdGeoCbsa.idx are now required
for initialization).
-
Eight
new properties/methods have been added. To use, simply call them
after a Geocode(). They are as follows:
- TimeZone / GetTimeZone()
- TimeZoneCode / GetTimeZoneCode()
- CBSACode / GetCBSACode()
- CBSATitle / GetCBSATitle()
- CBSALevel / GetCBSALevel()
- CBSADivisionCode / GetCBSADivisionCode()
- CBSADivisionTitle / GetCBSADivisionTitle()
- CBSADivisionLevel / GetCBSADivisionLevel()
Please reference the manual for more details on these new
properties/methods.
Build 1451 Released Summer '09
- "Geocoder Object has been recompiled using Visual Studio C++
2008. To use Geocoder Object for Windows, VC++ 2008 libraries
must be installed on your computer. Running setup.exe will
ensure the necessary libraries are installed.
However, if you are installing the objects manually, you may
need to install Visual Studio 2008 C++ x86 redistributable,
which can be found in extras\redist."
Build 1395 Released Spring '09
- This release of Geocoder Object introduces the GeoPoint
Add-on. The GeoPoint add-on allows you to obtain 11-digit
rooftop level latitude and longitude coordinates while regular
Geocoder remains at 9-digit zip+4 level accuracy. To use the
GeoPoint add-on, initialize by setting the PathTo* properties
and InitializeDataFiles(), and call GeoPoint() instead of
Geocode() with the zip, plus4, and delivery point.
Build 1115 Released 3/15/07
The
Census Block property has reverted back to returning a 4
character string. It was originally reduced down to a 1
character string due to imprecise data, but better and more
accurate data has been received to return back to a 4 character
string.
Build 1049 Released 7/15/06
Two
new properties are now available with Geocoder Object.
- PlaceName property (60 chars):
The official census name for the area described
by the ZIP+4 Code. This may differ for the city
name in the ZIP Code database.
- laceCode property (7 chars):
The corresponding code for the place name.
Build 151 Released 1/15/06
- Linux
and Solaris objects now available.
- The
Census Block property now returns a 1 character string instead
of a 4 character string. This was done to eliminate imprecisions
and overlaps that occurred in the data. Now, only the block
group is returned for more accurate results.
Build 122.WIN.IA32 version 4.0.0.4 Released 3/25/05
- Fixed
crash from invalid characters in the zip field
- Fixed
other minor bugs
Build 120.WIN.IA32 version 4.0.0.3 Released 9/25/04
- Renamed
the following data files:
- Geocode.dat, mdGeo.dat
- Geocode.idx, mdGeo.idx
- County.txt, mdGeo.cty
- Added
the following data file:
mdGeo.lic Must be in same directory as mdGeo.idx
- The
Build Number format has been updated to reflect the following
information:
Current Build Number -- 120.WIN.IA32
- 120 --> Build Number
- WIN --> Windows Platform
- IA32 --> Intel 32bit Chipset
- Because
the Geo Object was compiled in Visual Studio 2003, the following 5
system files must reside in the same directory as GeoObj.dll:
- Atl71.dll (Located in the ATL71_U folder for Windows 2000 & UP)
(Located in the ATL71_A folder for Windows 98)
- Mfc71.dll
- Mfc71u.dll
- Msvcp71.dll
- Msvcr71.dll
|