GeoStan Geocoding Suite
Spring 2021
Release Notes
This document highlights key changes across the suite of products.
Contents
Technical Support ... 1
Product Version Information ... 1
Regulatory: CASS Cycle O postponed due to COVID-19 ... 1
Product Updates ... 2
Database Compatibility ... 6
Platform-Specific Changes ... 6
Technical Support
Product documentation for this release is available on the GeoStan Support page. If you have any questions about the release or need further assistance, please go to support.precisely.com.
Note: Although we will continue to provide Level 1 technical support for the GeoStan Geocoding Suite in its version as of the Spring 2020 release, any future product updates will only be provided for the GeoStan Geocoding Suite in its Spring 2021 release version.
Product Version Information
The Spring 2021 release includes the following products and versions:
• AddressBroker 4.10
• Demographics Library 41.04
• Geographic Determination Library 41.04
• GeoStan 34.00
• GeoStan Canada - DEPRECATED
• Spatial+ 41.04
• Centrus Desktop 6.09.00.N
• GeoStan FileServer 2.2
• GeoStan Geocoding Utilities 1.0
Regulatory: CASS Cycle O postponed due to COVID-19
The CASS Cycle O publishing schedule has been postponed by the United States Postal Service® (USPS®).
The USPS Coding Accuracy Support System (CASS™) Cycle N will be valid through July 31, 2022. CASS Cycle O will become effective on August 1, 2022. Precisely will provide an update later this year to comply with the CASS Cycle O certification. The USPS reserves the right to modify the “valid through” date in the future if conditions warrant it.
Note: Centrus Desktop has not been CASS Certified for Cycle N in the 6.09.00.N release version. The CASS address matching rules continue to be used in the Desktop Software but it will no longer produce a CASS 3553 Report.
Product Updates
AddressBroker 4.10 and GeoStan 34.00
Street-Name Matching and Parsing Improvements
There were many address matching and parsing improvements in this release. These improvements not only improve the quality of the resulting addresses but also reduce the number of false positives.
• Non-standard abbreviations or misspellings now return more consistent results
Input Previous output New output
4120 HTCH RV PK E APT 12D No match 4120 HUTCH RVR PKWY E APT 12D 20607 N 103 D Multi-match between
20607 N 103RD LN 20607 N 103RD AVE 20607 N 103RD DR
20607 N 103RD DR
12262 W NEW MEX AVE 12262 W NEW MEXICO PL 12262 W NEW MEXICO AVE 7940 GEORGETOWN RD 7940 GEORGETOWN WOOD DR No match
14107 CHRISTOPHER RD 14107
CHRISTOPHER ROBIN WAY No match 2330 S INDUSTRIAL DRIVE 2330 S INDUSTRIAL PARK AVE No match
953 CLEAR CRK CY DR No match 953 CLEAR CREEK CANYON DR
14702 CAM PUNTA AREN No match 14702 CAMINITO PUNTA ARENAS
1511 ALAMEDA PAD SER No match 1511 ALAMEDA PADRE SERRA
• In Close mode, Spanish articles and prepositions in the street name such as LA, DE, and DEL now return quality matches. (This was implemented previously in CASS and Relaxed modes.)
Input Previous output New output
Input Previous output New output
5605 GLENRIDGE DRIVE NE STE 5605 GLENRIDGE DR 5605 GLENRIDGE DR 5605 GLENRIDGE DR
NORTHEAST STE No match 5605 GLENRIDGE DR
5605 GLENRIDGE DRIVE
NORTHEAST STE No match 5605 GLENRIDGE DR
• Improved street-name fuzzy matching
Input Previous output New output
3644 W VISTA RIDGE D No match 3644 VISTA RIDGE DR W
7866 S LAFAYETTE CY Multi-match
7866 S LAFAYETTE CT 7866 S LAFAYETTE WAY
7866 S LAFAYETTE CT
23820 NE KASKILLAH D No match 23820 NE KASKILLAH DR
1909 THOMAS BISHOP L No match 1909 THOMAS BISHOP LN
9603 RANSOME HILLS T No match 9603 RANSOM HILLS TER
8104 DIANE LE No match 8104 DIANE LN
3774 S WASHINGTON LO No match 3774 S WASHINGTON LOOP
11950B SUNHILLOW BE No match 11950B SUNHILLOW BND
• In some instances, we no longer return a result because a good match could not be found
Input Previous output New output
2201 PUP BAN 2201 PUP RUN No match
810 N MST 810 N ST No match
9569 W CAROL ANN 9569 W CAROL AVE No match
Fixed Change Requests
Change requests and software defects addressed in this release are listed below. Please review carefully to determine whether the following corrections apply to your situation.
Item Number Change Request Description
CENTRUS-11680 PRE-00061020 An input of “9 MAPLE AVE EXT” now correctly returns “9 MAPLE AVENUE EXT” instead of “9 MAPLE AVENUE”
CENTRUS-11752 PRE-00177310 In Close mode, Spanish articles or prepositions in the street name, such as EL, LA, LOS, DE, and DEL, no longer prevent a match (LA GRANGE vs LAGRANGE)
CENTRUS-11796 CENTRUS-10047
GeoStan street name matching improvements
As part of matching improvements, street name and street type no longer carry equal weight in matching score.
CENTRUS-11735 PRE-00139168 Improved handling of fully spelled-out address types
CENTRUS-11786 Last digit of the GeoStan match code now reflects changes in the address line when parsing modifications occur
Input = 4750 WALNUTSTREET
Matching parsing: name = WALNUT, type = ST
• match code previously returned “S80”
(0=no change in address line)
• now returns “S89”
(9 = street name and type changed)
CENTRUS-11832 Re-certify for CASS Cycle N because of street-name matching changes
Known Issues
To support DPV processing with point data, in addition to enabling the GS_FIND_DPV property, a new Find property must be set. The new GS_FIND_ENABLE_CLASSIC_SORT property sets the sort order to prioritize parcel centroids over other centroids. Setting this property restores the previous behavior to produce the expected DPV confirmation results for records that should DPV confirm. Default = False.
C GS_FIND_ENABLE_CLASSIC_SORT
COBOL GS-FIND-ENABLE-CLASSIC-SORT JAVA FIND_ENABLE_CLASSIC_SORT .NET GS_FIND_ENABLE_CLASSIC_SORT
• The false-positive report files are hard-coded in Geocoder, with the names DPVfalsePos.rpt and LACSfalsePos.rpt.
• DPV, LACSLink, and SuiteLink statistics are cumulative, containing a single set of statistics for all records processed thus far from all processes and threads.
• When you initialize DPV, LACSLink, and SuiteLink, GeoStan stores the directory paths in memory.
If you terminate GeoStan with DPV and LACSLink, you will receive a success indicator, which means that GeoStan has changed the DPV, LACSLink, and SuiteLink data directory paths.
However, the success is because GeoStan already has the paths loaded in memory, not because you have successfully changed the DPV, LACSLink, and SuiteLink directory. To successfully reset the DPV, LACSLink, and SuiteLink directory path, you must restart GeoStan.
• If using DPV, LACSLink, and SuiteLink data, we do not recommend limiting the memory being used by GeoStan. Because of the size of these files, we recommend that GeoStan operate on a
dedicated server, so that the maximum amount of memory is available for processing.
• When using auxiliary files, if House Number Parity, Side of Street, and Segment Direction contain erroneous input values, the following behavior occurs:
o House Number Parity - GeoStan rejects the record as invalid.
o Side of Street - GeoStan accepts the record and uses the centerline of the street as the address location.
o Segment Direction - GeoStan accepts the record but changes the value to F (forward).
NOTE: If the value is left blank, GeoStan uses the default value.
• Windows: Due to limitations with the Windows platform, the geocoder.exe sample application cannot support output files over 2 GB.
• AIX: By default, AIX processes use 256 MB of memory. Beginning with the release of GeoStan 33.00, the memory usage has been increased and we have seen some undesired behavior. To avoid encountering this behavior please update your environment with the variable list below prior to starting your daemon:
export LDR_CNTRL=MAXDATA=0xN0000000 rc.osseal start
Spatial+ 40.04
Known Issues
Importing an ESRI shape file fails if the associated DBF file contains fields with widths greater than 128 characters.
GeoStan Geocoding Utilities
Known Issues
When using any external indexes in a GSI file (such as POI, State-wide Intersection and Enhanced Alias), you cannot use WinSplit or GSD Split.
If data required to run WinSplit and GSD Split is not on a local directory, the utilities create empty files when extracting data from the use.gsd, uste.gsd, usw.gsd, and ustw.gsd files. Delete any empty GSD files to avoid mistaking them for valid GSD files.
Database Compatibility
NOTE: There are no data format changes to the street and point data sets for this release.
Platform-Specific Changes
For a complete list, please refer to the GeoStan Suite Supported Platforms document on the GeoStan Suite support site. For this release, the key changes are listed below.
New Platforms
• No platforms were added.
Retired Platforms
• No longer supporting 32-bit platforms.
Platform Retirement Notice
• No notices at this time.
Minimum Supported Levels
Minimum
Java 1.7
The following trademarks are owned by the United States Postal Service®: CASS, CASS Certified, DPV, eLOT, FASTforward, First-Class Mail, Intelligent Mail, LACSLink, NCOALink, PAVE, PLANET Code, Postal Service, POSTNET, Post Office, RDI, SuiteLink , United States Postal Service, Standard Mail, United States Post Office, USPS, ZIP Code, and ZIP + 4. This list is not exhaustive of the trademarks belonging to the Postal Service.
Precisely is a non-exclusive licensee of USPS® for NCOALink® processing.
Prices for Precisely software products, options, and services are not established, controlled, or approved by USPS® or United States Government. When utilizing RDI™ data to determine parcel-shipping costs, the business decision on which parcel delivery company to use is not made by the USPS® or United States Government.
1
1700 District Ave Ste 300 Burlington MA 01803-5231 precisely.com
© 1994, 2021 Precisely. All rights reserved.
