Pitney Bowes MapMarker USA - Manual (Page 92)

Re-Geocoding a Table
MapMarker USA 25
92
User Guide
Re-Geocoding a Table
After you have geocoded a table, existing records may be updated or new records may be added, so
you may need to geocode again. New or previously ungeocoded records (records that do not have
result codes) can simply be re-geocoded. By default. MapMarker automatically geocodes only
unmatched records. This means that for a large database, previously matched records are not re-
matched, thus saving time.
Records that already contain coordinates, but are incorrect (due to a change in address for
example), should be identified and the result codes should be deleted. MapMarker treats any record
without a result code as an unmatched record and attempts to find a match. MapMarker also
re-geocodes records with “N” or “ND” codes.
Your records may already include geometry objects (such as points) that were added from another
source (such as from MapInfo Professional). MapMarker can replace the points for matched
geocoded records (if you specify that action in the Geocode dialog). MapMarker deletes existing
points for records that it cannot match.
Using Geocoding Options
This section discusses geocoding options that affect the conditions under which MapMarker
attempts to match a record. This includes automatic or interactive geocoding, match settings,
fallback options, how to handle multiple matches, log files, table attribution, CASS settings, and
many other choices.
Geocoding options and preferences give you a great deal of control over the accuracy and precision
of your geocoding operation. Among the capabilities are:
• Specify the level of geocoding precision, automatic or interactive geocoding, and the range of
records to geocode.
• Specify criteria that must be matched (match settings) to return a candidate.
• Use search level settings to implement expanded search or to limit results to finance area or city.
• Prefer ZIP Code™ match over city name match
• Provide fallback options to broaden the possible candidate list in case a close match is not
initially identified.
• Determine how to choose candidates when multiple candidates are identified as close matches.
Changing match settings can affect the hit rate of successfully geocoded records. It can also affect
the time it takes for MapMarker to geocode a table, as well as the precision with which the geocoded
record is displayed on a map. It is important to keep in mind your intended use of geocoded data
when setting these conditions. These settings are set for individual tables and the information is
stored in the table’s metadata.
Accept or change any of the matching criteria to fit your needs. For example, by deselecting Exact
Match requirements, MapMarker can potentially match more records, but may return some false
positives.