Pitney Bowes MapMarker USA - Manual (Page 54)

Understanding the Geocoding Process
MapMarker USA 25
54
User Guide
• General Guidelines for Optimizing Geocoding on page 55
• Specify Input Address Columns on page 56
• Specify Output Address Columns on page 56
• Interpreting Census Block IDs on page 59
• Output Field Size and Column Names on page 62
• Mixed Case Street Output on page 62
• Setting Startup Preferences on page 64
Supported File Formats
MapMarker supports (opens and writes) files in the following data formats:
• TAB – MapInfo TAB files
• DBF – dBASE format
• CSV – comma-delimited text files (Desktop only)
• TXT – other delimited text file (Desktop only)
Delimited text files can use various delimiters (comma, semicolon, tab, slash, or other). If you open a
CSV file, a comma delimiter is assumed.
L
MapMarker USA 25 can export TAB, DBF, CSV, and TXT files to ESRI Shapefile (SHP)
format. Shapefile export is described in
Exporting to Shapefiles on page 71 .
See Opening a Table or Text File on page 66 for instructions on opening an input file in
MapMarker. See Defining Properties of Delimited Text Files on page 67 for information on
managing delimited text files.
See the following topics:
Geocoding Flexibility and Trade-offs
General Guidelines for Optimizing Geocoding
Specify Input Address Columns
Specify Output Address Columns
Output Column Type/Width Requirements
Interpreting Census Block IDs
Output Field Size and Column Names
Mixed Case Street Output
Setting Startup Preferences
Geocoding Flexibility and Trade-offs
MapMarker uses a relative matching system that gives you a great deal of control over geocoding
accuracy and scope.
The optimal level of geocoding depends on your application and goals. You may require highly
accurate address matching, or possibly a close positional matching is suitable for your purposes. Or
you may want to retrieve as many records as possible in an area (postal code) without concern for
exact address matching.