Enterprise Geocoding Module

Geocode Address GBR is deprecated

The EGM Geocode Address GBR stage has been deprecated. In its place use the Global Geocoding Module's Global Geocoding stage.

ZIP Centroid Returns using U.S. Master Location Data

The default behavior of Enterprise Geocoding Module for USA is to return matches from Master Location Data only for addressable locations that have an address-level geocode. ZIP Centroid returns are optionally available when matching to Master Location Data (MLD) in the Geocode US Address stage. For addresses that don't have a high-quality location, this provides access to the pbKey™ unique identifier, which can be used to unlock additional information about an address using GeoEnrichment data, as well as to realize operational processing efficiencies. This allows us to ensure maximum address coverage and integrity in geocoding. The inclusion of these addresses enables us to provide a higher match rate, lower false-positive match rate, and access to the pbKey™ unique identifier for all known addresses in the US.

Matching Enhancements for U.S. Enterprise Geocoding Module

Added Point of Interest Matching, and Expanded Firm and Building Matching

Significant improvements have been made in cases where the input address contains a firm, building or Point Of Interest name. For Master Location Data and HERE Points customers, the new, optional, POI Index file (poi.gsi) provides expanded support in alias name matching. When an alias match is made to the POI Index file, the IsAlias output field, or, in the case of a centerline match, CenterlineIsAlias field, returns A11.

Improved Handling of Hyphenated House Numbers

Improvements have been made in cases where the input address has a hyphenated house number (N-M). If the input street does not have a hyphenated range, the match is made using “N” as the house number and “M” as the unit number. For example, 18-20 Morton St., 02907 now returns 18 Morton St #20, 02907 since “Morton St” does not have a hyphenated range. In addition, in cases where the input address has a number, followed by a dash and an ordinal street, a match is now made and returns correct address information.

Enhancements in Handling of Misspelled Street Suffixes

Enhancements have been made to the handling of misspelled street suffixes. Additional matches are now made in spite of the misspellings. For example: 1861 Lincoln Hgy East, now matches to 1861 LINCOLN HWY E.

This enhancement also provides improved matches; for example, 5834 Brookstone Ovlk previously matched to 5834 BROOKSTON WALK NW, now returns a correct match to 5834 BROOKSTONE OVERLOOK NW.

Improved Matching of Addresses with Conjunction Tokens

Improved matching of addresses that contain conjunction tokens (AND, AT and &), such as:
  • Firms or POI’s that have conjunction tokens. For example: PARK & RIDE-OLDE TOWN ARVADA, 80002
  • Intersections that start with numeric/ordinal streets. For example: 6 1/2 W AND MILE 9 N, TX 78599
  • Addresses that start with a non-numeric house number. For example: 1504-B 3 AND 20 RD, EASLEY SC 29642
  • Street centroid matches where the street has a conjunction token. For example: HILL AND DALE RD, PLYMOUTH WI 53073

Improvement in Singleline Address Matching

Refinements have been made to singleline address matching to ensure the best address match is returned, regardless of geocode precision.

Significant Performance Improvement with Expanded Search

There is a significant improvement in performance when matching using the Expanded Search feature which allows specifying the search radius (up to 99 miles).