Enterprise Geocoding Module
PB Support Location for Geocoding Product Documentation
We now have a permanent location for geocoding product documentation on the PB Support Site at Geocoding Support. Go here first to find user guides, developer guides, database and software release notes for our geocoding products.
Deprecated Geocoding Legacy Stages for GBR and AUS
Two legacy Enterprise Geocoding Module stages/services for Great Britain and Australia have been deprecated and removed from the product. In their places are the geocode GBR and AUS addresses using the GlobalGecode Address stage in Enterprise Designer or Geocode Address Global service in Management Console.
Alias Returns for USA
- 13 - A match was made to USPS® ZIPMove data.
- 14 - A match was made to the expanded centroid file us_cent.gsc and/or the building centroid file bldgcent.gsc (files contained in the Master Location Structure Centroid dataset).
Improvements in Singleline Address Matching for USA
Prefer Input Street Information over PO Box
Improvements have been made in singleline processing to prefer the input street information over a PO Box. For example:
Input: MARVIN R BECK PT 1108 E PATTERSON/ POB 160 KIRKSVILLE MO 63501
Old match: PO BOX 160
New match: 1108 E PATTERSON ST
Embedded POIs
Enhancements have been made in singleline POI matching to recognize one or more embedded POIs. For example:
Input: FIRST SHORE FEDERAL SAVINGS & LOAN W GREEN ST & PEARL ST SNOW HILL
Result: FIRST SHORE FEDERAL SAVINGS & LOAN, SNOW HILL MD 21863
Ambiguous Street Names
Improvements have been made in handling of street names that could also be city names in singleline address processing. For example:
Input: BOX 58 ASHAWAY RI 02804
Previous match: 58 ASHAWAY RD, 02804
New match: BOX 58, ASHAWAY RI 02804
Post Office Box or #
Improved singleline matching for PO Boxes when entered as POST OFFICE BOX, or when the number is preceded by #.
Multiple Intersections
Improved handling and reporting of singleline matching of addresses containing multiple intersections when using Master Location Data. For example: 8th & laurel & 9th 21851.
Missing or Out of Range House Numbers
Improved handling of singleline input addresses with missing or out of range house numbers. Matches and non-matches are now returned more accurately.
Enhancements to POI Matching for USA
- Singleline input address containing a POI that ends with a city name that matches a given ZIP Code. For example: CHARTER HOSP OF DENVER 80228
- Singleline input address containing a POI that ends with a state name that matches a given ZIP Code. For example: BANK OF COLORADO 80720
- Two-line or singleline input address containing a POI that ends with a number. For example: KBIQ 102 7 80920
Matching Enhancements for USA
Addresses with PO Box #
Improvements have been made in the handling and matching of PO Box addresses that contain a “#” sign in front of the box number. For example: PO BOX #14.
Addresses with Underscore
Improvements have been made in the handling of input addresses containing underscores. For example: __4750 Walnut St. 80301_.
Custom Data Builder for USA
Custom Data Builder is a replacement tool for the User Dictionary Writer. Custom Data Builder is a utility that provides the capability to create a dataset for use in the Enterprise Geocoding Module for USA and web service API using your own location data.
You can try out the new Custom Data Builder by installing the Global Geocoding Module. The Custom Dataset Builder User Guide is included in the .zip file with the tool. Instructions are also provided in the Global Geocoding Module User Guide. If you do not want to install the Global Geocoding Module or have questions, contact Technical Support.