Pitney Bowes Software Inc. MapMarker USA Geocoding User Guide

MapMarker USA

Version 23

USER GUIDE

Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of Pitney Bowes Software Inc., One Global View, Troy, New York 12180-8399.

©2010 Pitney Bowes Software Inc. All rights reserved. MapInfo, Group 1 Software, and

MapMarker

are trademarks of Pitney Bowes Software Inc. All other marks and trademarks are property of their respective holders.

United States:

Phone: 518.285.6000

Fax: 518.285.6070

Sales: 800.327.8627

Government Sales: 800.619.2333

Technical Support: 518.285.7283

Technical Support Fax: 518.285.6080

pbinsight.com

Canada:

Phone: 416.594.5200

Fax: 416.594.5201

Sales: 800.268.3282

Technical Support:.518.285.7283

Technical Support Fax: 518.285.6080

pbinsight.ca

Europe/United Kingdom:

Phone: +44.1753.848.200

Fax: +44.1753.621.140

Technical Support: +44.1753.848.229

pbinsight.co.uk

Asia Pacific/Australia:

Phone: +61.2.9437.6255

Fax: +61.2.9439.1773

Technical Support: 1.800.648.899

pbinsight.com.au

Contact information for all Pitney Bowes Software Inc. offices is located at:

http://www.pbinsight.com/about/contact-us

.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

The following trademarks are owned by the United States Postal Service: LACS

Link

P.O. Box USPS, U.S. Postal Service and United States Postal Service.

, Suite

Link

, DPV, ZIP + 4, ZIP Code, ZIP, CASS, CASS Certified, Post Office,

Pitney Bowes Software Inc. is a non-exclusive DPV and LACS

Link

Licensee of the United States Postal Service

®

AD#1.08

Portions © 2010 Tele Atlas, Inc.

Portions © 2010 DataMap Intelligence LLC

Shapefile C Library v. 1.2.10 is licensed under the MIT Style License. The license can be downloaded from:

http://shapelib.maptools.org/license.html

.

©1998-2004 Frank Warmerdam. The source code for this library is available from

http://shapelib.maptools.org/dl

.

October 2010

Table of Contents

Table of Contents

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

What Is MapMarker? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

MapMarker Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

MapMarker Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Intersection Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

PlaceName Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Unformatted (Single-line) Address Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Postcode Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Geographic Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Address Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Multiple File Formats as Input Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

User Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

User Dictionary Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Attribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Automatic and Interactive Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Batch Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Saving and Using Project Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Display Geocoded Points on Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Quick Find and Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Segment IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Wide Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Centerline Offset for Point Candidates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Expanded Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

MapMarker Desktop Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

MapMarker Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Developer Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Integration with MapInfo Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

New in This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

MapMarker Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

MapMarker User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

MapMarker USA Developer Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

MapMarker Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Publications on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

MapMarker Streets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Getting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Before You Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

MapMarker 23 3 User Guide

Table of Contents

The Support Tracking System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Expected Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Exchanging Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Accessing the Pitney Bowes Software Inc. FTP site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Software Defects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 2: Installing MapMarker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Shared Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

About the Address Dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Operating Requirements and Performance Recommendations. . . . . . . . . . . . . . . . . .27

Operating Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Hardware and Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

JVM Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Web Server Requirements (Developer Edition Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Optimizing Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Installing MapMarker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Install Using the Graphical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Installing Silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Modifying the MapMarker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Modify Using the Graphical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Modify Silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Upgrading the MapMarker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Upgrade Using the Graphical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Upgrade Silently. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Uninstalling MapMarker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Uninstall Using the Graphical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Uninstall Silently. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Client Workstation Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Starting MapMarker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Starting the Desktop Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Starting the MapMarker Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Chapter 3: Geocoding with MapMarker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Geocoding Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Understanding the Geocoding Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Supported File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Geocoding Flexibility and Trade-offs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

General Guidelines for Optimizing Geocoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Specify Input Address Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Specify Output Address Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Output Column Type/Width Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

MapMarker 23 4 User Guide

Table of Contents

Interpreting Census Block IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Output Field Size and Column Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Mixed Case Street Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Setting Startup Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Running MapMarker – Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Opening and Running a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Running a Project from a Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Opening a Table or Text File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Defining Properties of Delimited Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Delimited File Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Exporting to Shapefiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Selecting Input and Output Address Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Selecting Input Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Selecting Output Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Adding a Column. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Geocoding Your Table Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Geocoding Your Table Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Making the Most of Interactive Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Change Matching Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Map the Match Candidates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Using Wide Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Edit Your Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Remote Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Intersection Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Using Single Line Addresses in Geocoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Single Line Geocoding Capabilities and Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Examples of Single Line Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Using Address Range Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Address Range Geocoding Capabilities and Guidelines . . . . . . . . . . . . . . . . . . . . . . . .78

Examples of Address Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Postal Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Geographic Geocoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Displaying Geocoded Records in MapInfo Professional. . . . . . . . . . . . . . . . . . . . . . . .82

Re-Geocoding a Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Using Geocoding Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Geocode Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Geocode Precision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Street Level Geocoding Method Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Type of Rows to Geocode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Range to Geocode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Matched Case Preference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Attribution Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

MapMarker 23 5 User Guide

Table of Contents

Log File Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Match Settings Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Match Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Exact Match On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

CASS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Additional Match Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Fallback Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Multiple Match Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Saving TAB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Creating and Saving a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Creating a Project-Based Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Multiple Pass Batch Geocoding Strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Chapter 4: MapMarker System Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Startup Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Dictionary Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Offset System Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Maps System Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

Chapter 5: Match Settings and Strategies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Choosing Match Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Maximizing the Match Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Maximizing Geographic Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Balancing Match Rate and False Positives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Picking Your Strategy: An Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

First Pass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Second Pass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Third Pass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

One Pass Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Impact of Relaxing Match Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Relaxing ZIP Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Relaxing City Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Relaxing Street Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Relaxing House Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Matching to Street Intersections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Geocoding to ZIP Centroids versus Falling Back to ZIP Centroid . . . . . . . . . . . . . . . .110

Preferring User Dictionary Matches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Viewing Match Candidates on a Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Setting the Street Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Viewing Match Candidates With Interactive Geocoding . . . . . . . . . . . . . . . . . . . . . . .111

A Closer Look at Multiple Matches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

MapMarker 23 6 User Guide

Table of Contents

Chapter 6: Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Single Match (S category) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Interpreting Complete S and M Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Interpreting S8 Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Interpreting S7 Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

Interpreting S6 Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

Interpreting S5 Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

S and Z Result Codes: What is the Difference?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Best Match From Multiple Candidates (M category) . . . . . . . . . . . . . . . . . . . . . . . . . .119

Postal Centroid Matches (Z category). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Geographic Matches (G category). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Non-match Codes (N category) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Using the Georesult Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

Chapter 7: Specialized Geocoding Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

CASS Report Required Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

CASS Report Optional Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Geocoding in CASS Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

LACS

Link

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Using LACS

Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

LACS

Link

Output Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

DPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Using DPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Street Directionals with DPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Enhanced ZIP + 4 and DPV Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

DPV Data and CASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

DPV Output Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Footnote Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

DPV and LACS

Link

Usage Guidelines and Requirements . . . . . . . . . . . . . . . . . . . . . .135

Creating the False Positive Report for DPV or LACSLink . . . . . . . . . . . . . . . . . . . . . .135

Submitting a False Positive Report and Obtaining New Security Key . . . . . . . . . . . . .137

Suite

Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Using Suite

Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Returning Abbreviated Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

Returning Abbreviated City Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Geocoding Dual Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

Two-Line Dual Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

One-Line Dual Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Geocoding Remote Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141

Geocoding dBASE Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Geocoding Delimited, CSV, and SHP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Using Quick Geocode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

MapMarker 23 7 User Guide

Table of Contents

Finding Address with Quick Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Finding Candidates Using Quick Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Viewing Quick Find Candidates on a Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Displaying Address Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Copying Information from the Quick Find Candidate List . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Browsing Candidates Using Quick Find. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Quick Find Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148

Finding Airports with Locate Airport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

Finding Highway Exits with Locate Highway Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Batch Geocoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Creating a Batch Geocoding File from a TAB File . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Manually Creating a Batch File from a TAB File . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

Batch Geocoding Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

Batch File Contents for TAB and Other File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Running the Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Table Settings and Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

CASS Geocoding in a Batch Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Input and Output Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Table Attribution with MapMarker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

Opening the Table for Attribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

Selecting an Attribution Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Creating a Column to Receive Attribution Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

Binding Attributes – Output Point Attribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

Binding Attributes – Column Value Attribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Adding Attributes to Your Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

Adding Attributes By Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

Adding Attributes Using Batch Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

Stopping Attribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

Clearing Attribute File Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

Tips for Using Attributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

Chapter 8: Geocoding Remote Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Remote Tables and Spatial Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

Mappable Tables and the MapInfo Map Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

Supported Spatial Index Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

Preparing to Geocode Remote Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Creating a Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Preparing the Remote Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

Creating a Map Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Making a Remote Table Mappable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Accessing a Remote Table for Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

Editing Records Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171

MapMarker 23 8 User Guide

Table of Contents

Writing Geocoding Output to Another Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

Relationship Between Source and Results Tables . . . . . . . . . . . . . . . . . . . . . . . . . . .173

Setting Up for Related Table Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

Remote Table-to-Table Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

Optimizing MapMarker for Related Table Geocoding . . . . . . . . . . . . . . . . . . . . . . . . .176

Remote Database Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

Related Table Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

Additional Considerations for Remote Table Geocoding . . . . . . . . . . . . . . . . . . . . . .177

Sort by ZIP Code™ for Faster Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Geocoding Unmatched Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Transaction Control with ODBC Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

Remote Database Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178

Rollback Segment Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178

Supported Unique Index and Primary Key Data Types by Database . . . . . . . . . . . . .178

Chapter 9: Custom User Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

User Dictionary Capabilities and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180

User Dictionary Only Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180

Source Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181

Required Input Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181

Optional (Recommended) Input Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

User Dictionary File Names and Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183

Additional User Dictionary Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183

Data Access License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

CASS Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

Address Range Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

Street Intersections and Customized User Dictionaries. . . . . . . . . . . . . . . . . . . . . . . .184

Creating a Custom User Dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

Using the MapMarker User Dictionary Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185

Adding the User Dictionary to the Desktop Application . . . . . . . . . . . . . . . . . . . . . . . .187

Preferring User Dictionary Matches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Appendix A: MapMarker User Interface Reference . . . . . . . . . . . . . . . . . . . . . . 190

About MapMarker command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

Arrange Icons command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

Batch Add Attributes command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

Cascade command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

Choose Font command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

Clear File Selections command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Close command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Close Project command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Create Batch File command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

MapMarker 23 9 User Guide

Table of Contents

Create Project-based Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

Create/Save Project command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

Create User Dictionary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

Exit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

Export to ESRI Shapefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

Geocode command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

Help Topics command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

Locate Airport command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

Locate Highway Exit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

Logfile command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

MapMarker on the World Wide Web command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

Open Browser List command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

Open ODBC Table command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

Open Project command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

Open Table command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Quick Find command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Quick Geocode command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Recent File List command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Select Attribute Files command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Select Columns command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Status Bar command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Stop Attribution command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Submit Problem Report to Technical Support command . . . . . . . . . . . . . . . . . . . . . . .199

Summary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

System Preferences command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Table Summary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Tile command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

Toolbar command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

MapMarker Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

About MapMarker dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

Add Columns dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202

Automatic Geocode dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

Bind Attribute Table Columns to Output Columns dialog. . . . . . . . . . . . . . . . . . . . . . .204

Candidate Map dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205

Describe Table Relationships dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208

Dictionary Preferences dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209

Export to dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210

Export to ESRI Shapefile dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211

Fallback dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212

Filter Tables dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

Font dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214

MapMarker 23 10 User Guide

Table of Contents

Geocode dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215

Geocoding Summary dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

GeoResult dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217

Interactive Geocode dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218

Locate Airport dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220

Locate Highway Exit dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222

Log File dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223

Maps Preferences dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

Match Settings dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Modify Table Structure dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228

Multiple Match dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230

Offset Preferences dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

Open Project dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232

Open Table dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233

Quick Find dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234

Quick Find Settings dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236

Related Table dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239

Save As dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240

Save Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240

Save Project File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240

Export to Shapefile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241

Save Table Summary As dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241

Select Attribute Tables dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242

Select Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242

Select input columns from your table dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244

Select output columns from your table dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246

Select Project Files dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247

Select Table dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

Select Table Type dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249

Startup Preferences dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250

Table Georesult Summary dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251

Text File Wizard (Step 1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252

Text File Wizard (Step 2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253

Text File Wizard (Step 3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

User Dictionary Wizard (Step 1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254

User Dictionary Wizard (Step 2 of 3) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256

User Dictionary Wizard (Step 3 of 3) dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

Appendix B: Creating a Map Catalog Manually . . . . . . . . . . . . . . . . . . . . . . . . . 259

Adding Rows to the MapInfo_MapCatalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261

Specifying Point Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Specifying Line Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

MapMarker 23 11 User Guide

Table of Contents

Specifying Fill Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Appendix C: Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Q: I have a table that I cannot geocode because I get the error “Unable to update row.”

What does this mean and how can I fix it?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Q: I open a table in MapInfo Professional and I am able to open that same table in

MapMarker. Is this safe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Q: How can I improve MapMarker’s performance? . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Q: What determines if a row is unmatched? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268

Q: After geocoding, some of my records have a result code of “ND.” What does this mean? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268

Q: What is the breakdown of the Census Block code? . . . . . . . . . . . . . . . . . . . . . . . .268

Q: What is the MapMarker Geoengine API and how can I use it?. . . . . . . . . . . . . . . .269

Q: When geocoding, how can I prevent firm names from matching to street names?.269

Q: What is the difference between the Desktop product and the Developer Product? 269

Q: Why am I generating different results from the GeoEngine APIs vs. the MapMarker

Desktop (UI)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270

Appendix D: MapMarker Utility Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Running FindAddress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272

Append . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

Running Append . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

Append Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Append Input File Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

APPEND.MSG File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Considerations when Running Append . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

Appendix E: U.S. ZIP Code Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

MapMarker 23 12 User Guide

Introduction

Welcome to MapMarker USA, one of the premier address matching and geocoding offerings from Pitney Bowes Business Insight. MapMarker USA enables you to assign geographic coordinates to large tables of American address records in a single session.

In this chapter:

Š

What Is Geocoding?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Š

What Is MapMarker? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Š

New in This Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Š

MapMarker Documentation Set. . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Š

MapMarker Streets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Š

Getting Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

1

Chapter 1:

What Is Geocoding?

What Is Geocoding?

Geocoding is the process of assigning geographic coordinates to data that contain addresses. The coordinates assigned to each address turn each record into a geographic object that can be displayed on a map using MapInfo Professional or MapXtreme.

Geocoding turns ordinary data records containing address information into geographic objects that can be displayed on a map. A list of customers, stores, or anything with a street address or postal code may be matched using the comprehensive street and postal code files provided in the Address

Dictionary. The result of geocoding is an xy coordinate linked to a specific address. When displayed, this enables you to better visualize the relationships in your data.

You can display coordinates by creating maps in MapInfo Professional or via MapXtreme and add to other map objects to give your data a geographic reference. You can then perform a wide variety of functions to analyze your data in geographic terms. Data that once was only readable in column and row format can be now viewed with a whole new perspective, thereby disclosing patterns and clusters you never knew existed.

Visualizing your records on a map can make the relationships among your data clearer. You can display your geocoded records against a street map, a postal centroid map, a local map, or whatever is most appropriate to your needs. You can then use the wide variety of functions available in MapInfo mapping software to perform querying, create thematic maps, create territories, and perform many other types of geographic analysis.

Beyond visualizing data on a map, location data can be leveraged in many ways. See

Location

Intelligence Products

and related parts of the Pitney Bowes Business Insight web site for details on how your organization can use location information to make better decisions.

What Is MapMarker?

MapMarker is a powerful geocoding tool produced by Pitney Bowes Software Inc. MapMarker enables you to assign geographic coordinates to large tables of U.S.-based address records in a single session. This is a key step toward mapping and analyzing your business data. MapMarker adds geographic coordinates to every record in your database that it matches against its comprehensive Address Dictionary, a database of USPS

®

street addresses, street geometry and the latest ZIP + 4

®

centroids.

MapMarker assigns coordinates to an address based on how well it matched in the Address

Dictionary. The precision of the match can vary. For each address you geocode, you may get back a single perfect, street-level match, a list of street-level match candidates from which you choose the best match. You may get a less precise match, for example a ZIP Code centroid match if you provided a ZIP Code or a city-level centroid match.

To identify the match precision, MapMarker also returns a result code for each address that it geocodes. The precision that you require for your geocoded records depends on how you plan to use your data.

MapMarker USA 23

14

User Guide

Chapter 1:

MapMarker Features

MapMarker Features

MapMarker USA allows a great deal of flexibility in geocoding. This section briefly describes the major features of MapMarker USA.

See the MapMarker USA Release Notes for new features, Address Dictionary updates, and behavioral changes that you may notice with MapMarker. The Release Notes also describe fixes to customer-reported issues and known issues that customers must be aware of. The MapMarker USA

Release Notes are located at the Pitney Bowes Business Insight

Product Documentation

site.

MapMarker Installer

The MapMarker USA 23 installer is designed to simplify the installation and provide more feedback during installation. The installer accommodates:

• Typical and custom installs

• Upgrading software and data or upgrading data only

• Silent installation and modification

• Selecting and installing the JVM

• Installing the sample application (for Server installation)

• Selecting default and custom locations for installing software and data

• Choosing shortcut locations

• Uninstalling MapMarker

L

Note You must have administrator rights to install MapMarker software. This is true for all operating systems.

If you select the street level geocoding operation, MapMarker will match your full address record against its Address Dictionary and/or User Dictionary (If you have created and selected a User

Dictionary.). This process will correct misspelled street addresses and city/town names. It can also correct postal code information, or add postcodes if your data does not already include them. After

MapMarker completes the address cleaning step, it will geocode your records in accordance with the other preferences you have set.

Addresses that are geocoded to a street level return an S or M result code. See

Result Codes

for a description of these and other result codes.

Intersection Geocoding

MapMarker USA can geocode to street intersections. Using any of several ways to designate a street intersection, MapMarker can find the position of the intersection of two street segments within a given postal code or city. See

Intersection Geocoding

.

Addresses that are geocoded to an intersection return an SX result code. See

Result Codes

for a description of all result codes.

MapMarker USA 23

15

User Guide

Chapter 1:

MapMarker Features

PlaceName Geocoding

PlaceNames are included in the data and can be geocoded by MapMarker USA. PlaceNames can include business names, building names, government offices, or other companies and organizations that are included in the data source of the MapMarker USA Address Dictionary.

PlaceName geocoding is also supported by User Dictionaries. You can create and implement User

Dictionaries based on your own data or third-party data sources. Your custom data may include place names, intersections, airports, business or organization names, building names, or any other

POI (Point of Interest) that you want to use for geocoding purposes.

Unformatted (Single-line) Address Input

MapMarker can geocode single line addresses, in which all address components appear on a single line rather than in separate fields.

Postcode Geocoding

If you choose Postcode Geocoding, MapMarker will geocode your records based on their postal code in accordance with the other preferences you have set. You can also fallback to Postcode geocoding if a street level match was not possible.

A postal code represents an area (polygon). A postal code can be related to one locality, or to multiple localities in metropolitan areas. In some regions (such as Northern Territory) this may not be true.

USPS

®

may identify several official and unofficial locality names for a single postal code (especially in urban areas). MapMarker USA can interpret addresses that refer to official (gazetted) or unofficial locality names, but will always return the official locality name in the address cleansing process.

Addresses that are geocoded to a postal code return a Z result code. See

Postal Centroid Matches

(Z category)

for a description of Z result codes.

Geographic Geocoding

If the input address consists of a valid combination of city and state, but no further address information, you can still geocode to the city centroid. You can also fallback to Geographic geocoding if a street level match was not possible.

MapMarker USA can interpret addresses that refer to official (gazetted) or unofficial locality names, but will always return the official locality name in the address cleansing process.

Addresses that are geocoded to a geography return a G result code. See

Geographic Matches (G category)

for a description of G result codes.

MapMarker USA 23

16

User Guide

Chapter 1:

MapMarker Features

Address Dictionaries

The default Address Dictionary is based on Tele Atlas

®

Street data and USPS sources. This includes millions of American street addresses and placenames with corresponding address range, street geometry and postal code data and is used for matching addresses and assigning coordinates during the geocoding process. This Address Dictionary can be purchased and licensed for all of

USA or for individual regions.

A number of other street range and point-based Address Dictionaries are available. See the

MapMarker USA Release Notes located at the Pitney Bowes Business Insight

Product

Documentation

site for information on the available Address Dictionaries and data vintages for your version of MapMarker USA.

Multiple File Formats as Input Data

MapMarker USA reads any MapInfo table (TAB format), CSV, delimited text files (TXT), fixed-width text files, or any dBASE (DBF) format table. MapMarker supports multiple character sets for dBASE files.

In addition, MapMarker, via Open Database Connectivity (ODBC) can geocode data stored in remote databases, including Microsoft Access, Microsoft SQL Server, and Oracle using the X and Y data type.

User Dictionaries

A User Dictionary is similar to the provided Address Dictionary, but it is created by the user from their own source data. User-defined dictionaries can contain a variety of customized address-related data that may provide improved address matching rates and add value to the address validation and geocoding process. User Dictionaries can also be based on parcel/point data, which can provide an even higher level of geocoding accuracy.

You can create any number of custom dictionaries. User Dictionaries can be used in combination with or in preference to the Address Dictionary.

See

Custom User Dictionaries

.

User Dictionary Utility

The User Dictionary Utility simplifies the steps for creating User Dictionaries. This graphic utility can be installed with the MapMarker USA Server product. Alternatively, this utility is available for download from the MapInfo

Geocoding web site

.

Attribution

You can add attribute values from other tables as part of a geocoding pass, or as a separate process. For example, MapMarker can attach information (such as lifestyle codes), stored in a boundary or point file to a record in your database when it makes a match. All that is necessary is a common link between the two tables.

MapMarker USA 23

17

User Guide

Chapter 1:

MapMarker Features

Automatic and Interactive Geocoding

MapMarker USA runs in both automatic and interactive mode. You can use either automatic or interactive geocoding or you can combine these techniques in multiple geocoding passes to optimize your results.

Batch Geocoding

MapMarker USA supports batch geocoding for processing one or more tables without user interaction. This feature is useful for overnight processing of large databases or when a table is updated regularly.

See

Creating a Project-Based Batch File

.

Saving and Using Project Files

You can create MapMarker projects to preserve all current geocoding settings, matching and fallback preferences, table attributes settings, and system preferences. Project files also provide a way to do batch geocoding on delimited text files and fixed-width text files.

See

Creating and Saving a Project

for information on opening a project and creating a project.

Display Geocoded Points on Map

MapMarker can create point objects for geocoded records automatically. You can display the points using MapInfo mapping software (such as MapInfo Professional.). Optionally, MapMarker can write the X and Y coordinates directly to your table. Points created with MapMarker will overwrite any points already existing in the table.

See the

Viewing Match Candidates on a Map

for information on viewing candidates on a map.

Quick Find and Browsing

The Quick Find Feature in the Desktop Application enables you to quickly geocode a single address or business name without using the Geocode dialog. The Quick Find dialog is located under the

Search menu of the Desktop Application. Enter the address information in the Quick Find dialog and click Search. MapMarker returns geocoding results based on the currently set geocoding preferences.

You can also use the Quick Find dialog to browse the Address Dictionary for the correct spelling of a street name or business. Provide the postal code and at least the first letter of the street or business and click Browse. The city/town and state fields are optional. MapMarker returns a list of streets or businesses that meet your criteria. Browsing does not geocode the record, but you can use the browse results to confirm and correct your address and then geocode based on this information.

See the

Finding Address with Quick Find

for information on the Quick Find feature.

MapMarker USA 23

18

User Guide

Chapter 1:

MapMarker Features

Result Codes

MapMarker USA returns a result code for each record it attempts to match. This enables you to see whether a match was made, which dictionary was the source of the match, and how precisely each address component matched. The result codes are stored in your table. When the records display in a Map window, each result code is represented by a color-coded symbol. This allows you to visually recognize the precision level and distribution of the matches.

See

Result Codes

.

Segment IDs

Segment IDs are numeric codes that uniquely identify each point or street centroid candidate. The

MapMarker USA 23 geocoder returns the Segment ID for each S8, S7, S6, S5 and S4 candidate

(providing that the segment ID information is available in the Address dictionary.

L

Segment IDs are available with the Developer (Server) product only (not with the Desktop

Application).

Wide Search

You can increase the probability of a match by using Relaxed mode in combination with wide search.

Wide search considers all streets that begin with the first letter of the input street name, and therefore can identify more potential candidates.

Wide search is not implemented by default, but is supported at both the API level and in the Desktop application.

See

Using Wide Search

for an explanation of using this feature with interactive geocoding. You can

also set wide search in the

Match Settings dialog

and the

Quick Find Settings dialog

,

Centerline Offset for Point Candidates

If a point candidate is returned from a point dictionary, you can return the coordinates at a specified offset from the associated street segment (rather than at the original point). This feature is available if you are using a point-based Address Dictionary (such as Centrus Points or Tele Atlas Points). See

Address Dictionaries

for an overview of the available Address Dictionaries.

The centerline offset capability is disabled by default, but you can enable and control it through the

Offset Preferences dialog. See

Offset System Preferences

.

Expanded Search

MapMarker USA implements expanded search, which allows MapMarker to search for an address within a given radius of the input address. Expanded search helps to find a match when the input address contains limited or inaccurate city or ZIP Code information.

MapMarker USA 23

19

User Guide

Chapter 1:

MapMarker Features

Expanded search is not implemented by default, but is supported at both the API level and in the

Desktop application.

MapMarker Desktop Application

The MapMarker Desktop Application can be installed on a single machine, or on a network to be shared by other users. The Desktop Application gives you a great deal of control over the geocoding process.

Following is a partial list of MapMarker features:

• Supports a number of different file formats, including MapInfo TAB files, DBF files, CSV, delimited text files (TXT), and ESRI Shapefiles (SHP). See

Supported File Formats

.

• Geocode interactively (you make the final decision if it is a match) to maximize the number of matches and to control error rate.

• Geocode a portion of your table using the Quick Geocode feature.

• Geocode a large database of addresses in batch mode.

• Geocode a portion of your table using the Quick Geocode feature.

• Geocode to street address ZIP Code centroids or to street intersections.

• Identify result codes quickly tell how the address match was made and how precise the match is.

•

Standardize addresses to meet USPS CASS™. See

CASS Geocoding

for a description of

Coding Accuracy Support System requirements using MapMarker Address Dictionary.

• Use DPV

®

. See

Using DPV

for a description of using Delivery Point Validation in conjunction with CASS to verify whether an address is a valid USPS delivery point.

• Geocode remote tables via ODBC.

L

CASS and DPV functionality are available with MapMarker.

MapMarker Server

MapMarker Server is a server-based engine that is designed to be integrated into business processes. The Server product enables multiple simultaneous geocoding requests to be served from a single MapMarker engine.

Developer Tools

The MapMarker Server product includes developer tools provides a Java API and an XML (.NET

Framework) API. Developers can use these tools to build and deploy client/server or standalone geocoding applications.

Integration with MapInfo Professional

MapInfo Professional users can run MapMarker USA or Envinsa 4.3.1 or later as a geocoding service from within MapInfo Professional 8.5 or later. This direct connection enables users to take advantage of MapMarker address validation and geocoding capabilities within the powerful MapInfo

Professional mapping and analysis environment.

MapMarker USA 23

20

User Guide

Chapter 1:

New in This Release

New in This Release

This release is numbered MapMarker USA 23 to reflect the major enhancements and underlying consistency of all USA Pitney Bowes Business Insight geocoding products.

See the MapMarker USA 23 Release Notes for a summary of new features, address dictionary updates, and behavioral changes that you may notice with MapMarker USA 23. To see these

Release Notes and other MapMarker documentation, go to the

Product Documentation page

on the Pitney Bowes Business Insight web site.

The Release Notes also describe fixes to customer-reported issues and known issues that you should be aware of.

One major new feature for MapMarker USA 23 is the availability of multiple and updated datasets.

You will be able to purchase and license monthly updates of Tele Atlas

®

Points and other parcel level datasets (Centrus

®

Points, and others).

When installing MapMarker, you now will be asked for a single license file. Unlock codes are no longer used.

MapMarker USA 23 supports export to ESRI

®

Shapefile format. See

Exporting to Shapefiles

for

more information on this feature.

MapMarker Documentation Set

The documentation set for MapMarker includes PDF and online resources to help you make the most of the product. The set includes:

• MapMarker User Guide in PDF format.

• Online Help for the MapMarker Desktop Application.

• MapMarker Developer Guide in PDF format.

• Release Notes that provide updated information on new features, behavioral changes in the software, fixes for customer-reported issues, and known issues. To see these Release Notes and other MapMarker documentation, go to the

Product Documentation page

on the Pitney

Bowes Business Insight web site.

MapMarker User Guide

This guide is designed to help you use MapMarker to the fullest. It introduces you to the product, and explains how to use the MapMarker Desktop Application. Coverage includes:

• Installing MapMarker

• Geocoding in MapMarker

• Using system preferences

• Configuring settings for optimum geocoding results

• Explaining result codes

• Geocoding remote tables

• Creating a customized user dictionary

MapMarker USA 23

21

User Guide

Chapter 1:

MapMarker Documentation Set

The User Guide also contains a chapter on more specialized features, including CASS™ geocoding and DPV

®

; finding airports, highway exits, single address geocoding, batch geocoding, and table attribution.

This guide also includes appendixes that provide reference information for MapMarker.

• User Interface Reference – Illustrates and explains the dialogs, buttons, and menu commands in the MapMarker user interface.

• Creating a Map Catalog – Describes how to create a Map Catalog manually so that you can make remote tables mappable.

• MapMarker Utility Programs – Explains the FindAddress and Append utilities.

• Frequently Asked Questions – A list of frequently asked questions.

• MapMarker Program Files – A list of the files that are installed with MapMarker.

• U.S. ZIP Code Ranges – A list of the ZIP Code ranges in the United States.

Online Help

In addition to the User Guide, MapMarker includes online help for the Desktop Application. Online help is instantly available while you are running MapMarker or the installation wizard. To access help, either select the Help menu, press the F1 key, or click Help for help about a dialog.

MapMarker USA Developer Guide

This explains the server and API components of the developer product. This also describes and illustrates the sample application, a Java client that illustrates how to geocode American addresses.

MapMarker Release Notes

The MapMarker Release Notes are posted to THE Pitney Bowes Business Insight

Product

Documentation

web site, and contain a brief summary of the following:

• New features

• Operating requirements

• Bug fixes

• Known issues

Publications on the Web

The MapMarker documentation and Release Notes are available from the

Product Documentation

page on the Pitney Bowes Business Insight web site.

Documentation on the web site may be updated if corrections are necessary or if new information becomes available.

MapMarker USA 23

22

User Guide

Chapter 1:

MapMarker Streets

MapMarker Streets

Once you have geocoded your table you can display geocoded points in the MapMarker Desktop

Application through Candidate Visualization. You may want to add other layers of information to your map to give your records a geographic reference. MapMarker Streets is a U.S. network of fast displaying streets, highways, municipal boundaries, water features, and points of interest to complement your MapMarker geocoded data.

MapMarker Streets is provided on separate media with your MapMarker product.

Getting Technical Support

Pitney Bowes Business Insight offers a free support period on all new software purchases and upgrades, so you can be productive from the start. Remember to provide your serial number, partner number, or customer agreement number when contacting Technical Support.

Contact the technical support personnel for your area:

The Americas

Support: 800 552 2511

Fax: 518.285.6080

E-mail:

[email protected]

Hours: Monday - Friday from 8:00am - 7:00pm EST, excluding company holidays.

Europe/Middle East/Africa:

Support: +44 1634.880.141 (option 1)

Fax: +44 1634.880.383

E-mail:

[email protected]

Hours: Monday - Friday from 9am to 5pm GMT, excluding company holidays.

Asia-Pacific Headquarters

Support: 1800 648 899

Hours: Monday–Friday from 8:00am and 6:00pm (EST) Australian Eastern Standard Time, excluding company holidays.

Fax: 61.2.9439.1773

Main Office Phone (Sydney): 61. 2.9437.6255

E-mail:

[email protected]

Before You Call

Have the following information ready when contacting us for assistance on MapMarker:

1. Serial Number. You must have a registered serial number to receive Technical Support.

2. Your name and organization. The person calling must be the contact person listed on the support agreement.

MapMarker USA 23

23

User Guide

Chapter 1:

Getting Technical Support

3. Version of the product you are calling about.

4. The operating system name and version.

5. A brief explanation of the problem. Some details that can be helpful in this context are:

• Error messages

• Context in which the problem occurs

• Consistency – is the problem occurring consistently or erratically?

The Support Tracking System

The Support Tracking System is used internally by the Technical Support department to manage and track customer issues. The system also has the ability to track calls with accountability. This system helps Tech Support respond to all customer issues quickly and effectively.

Expected Response Time

Most issues can be resolved during the customer’s initial call. If quick resolution is not possible, a response is issued before the end of the business day. A Technical Support representative will provide you with the status each business day until the issue is resolved.

Support requests submitted by e-mail are handled using the same guidelines as telephone support requests. However, there is an unavoidable delay of up to several hours for message transmission and recognition.

Exchanging Information

Occasionally a Technical Support representative will ask you to provide sample data in order to duplicate your scenario. In the case of our developer tools, a small subset of sample code may be requested to help duplicate the issue.

The preferred method of exchanging information is either via e-mail or our FTP site. Use the following e-mail address:

• Globally –

[email protected]

Accessing the Pitney Bowes Software Inc. FTP site

For information regarding our FTP site, contact Technical Support. If information cannot be provided electronically, Pitney Bowes Software Inc. also accepts information in the following media formats:

• CD

• DVD

Software Defects

If the issue is recognized as a defect in the software, the Technical Support representative will log the issue in our incident database and assign an incident number that can be used for tracking purposes.

MapMarker USA 23

24

User Guide

Installing MapMarker

This chapter contains instructions for installing MapMarker. Refer to this chapter for step-by-step instructions and other issues related to installation.

In this chapter:

Š

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Š

Operating Requirements and Performance Recommendations .27

Š

Installing MapMarker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Š

Modifying the MapMarker Installation . . . . . . . . . . . . . . . . . . . . . .36

Š

Upgrading the MapMarker Installation . . . . . . . . . . . . . . . . . . . . . .37

Š

Uninstalling MapMarker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Š

Client Workstation Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Š

Starting MapMarker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

2

Chapter 2:

Installation Overview

Installation Overview

MapMarker is available as Desktop and Server editions. The features available during installation are as follows:

MapMarker Desktop Edition The Desktop edition includes the Desktop Application, which includes the graphical user interface for geocoding addresses and the MapMarker Address

Dictionary. You can purchase data for all 50 states (plus D.C. and Puerto Rico), regional state bundles, or individual state data.

The Desktop Application runs on Microsoft Windows only.

MapMarker Server Edition The Server edition enables multiple simultaneous geocoding requests to be served from a single MapMarker engine. It also includes the tools necessary for developing

MapMarker solutions using the Java API or XML API. These tools include the MapMarker SDK, native code libraries, and examples. A preconfigured Apache Tomcat servlet is provided to run

MapMarker as a geocoding server.

The Server edition also includes one license for the MapMarker Desktop Application.

MapMarker is delivered on one DVD, which includes both the software and the data. An installer is provided to install and configure MapMarker in one easy procedure.

The MapMarker installer program can be used for the following purposes:

•

New installation. See

Installing MapMarker on page 29

.

• Modifying existing installation to add or remove features. For example, you could add new data

or add a feature to an existing installation. See

Modifying the MapMarker Installation on page 36

.

• Upgrading existing installation. For example, when a point release version of MapMarker is available, you could upgrade from version 23.1 to 23.2 with the same set of features that are

already installed. See

Upgrading the MapMarker Installation on page 37

•

Uninstalling. See

Uninstalling MapMarker on page 39

.

L

After you complete the installation, contact Pitney Bowes Business Insight Customer Service and provide your e-mail address. This will be necessary to receive future license file updates.

Contact Customer Service at 800 552 2511. This and other contact information also appears in the Quick Reference Card enclosed in the product box.

Shared Install

The MapMarker data can be shared among a group of users who wish to run the MapMarker

Desktop Application. To do so, the system administrator does a shared installation of MapMarker.

This must include the Desktop Application feature and the Address Dictionary in a common network location. Once the shared installation is complete, the system administrator must share the data folder across the network.

MapMarker 23

26

User Guide

Chapter 2:

Operating Requirements and Performance Recommendations

After the system administrator has made the shared data available across the network, client users can browse to that location and run the Desktop Application installer (desktop\ClientSetup.exe) to install the MapMarker Desktop Application on their workstations. Client users can then run the

MapMarker Desktop Application and access the shared Address Dictionary.

For instructions on installing the client Desktop Application for use with a shared installation, see

Client Workstation Install on page 40

.

About the Address Dictionary

The MapMarker Address Dictionary is installed during the installation of the MapMarker software. All of the data is installed in the same dictionary (not separated by state). You will not see indication of different states, but you will only be able to geocode those states for which you are licensed. You can choose to install DPV

®

or LACS

Link

™ data, assuming that you are licensed for those datasets.

The Address Dictionary must be stored on a local hard drive or a network drive.

Operating Requirements and Performance Recommendations

Note the following recommendations in order to maximize the performance of your MapMarker installation.

Operating Requirements

Optimizing Performance

Operating Requirements

This section describes the basic software and hardware requirements for MapMarker. See your version-specific Release Notes for more detailed descriptions and additional information on supported software and hardware.

Hardware and Memory Requirements

Supported Operating Systems

JVM Requirements

Database Requirements

Web Server Requirements (Developer Edition Only)

Hardware and Memory Requirements

The minimum system requirements for MapMarker USA are:

The minimum system requirements for MapMarker 23 are:

• 1 Ghz Pentium

®

processor or equivalent

• 1 GB RAM

• 5 GB available disk space (including 1 GB for Address Dictionary)

MapMarker 23

27

User Guide

Chapter 2:

Operating Requirements and Performance Recommendations

For optimal performance we recommend:

• Dual core processor or better

• 2GB RAM

• 10 GB available disk space.

Supported Operating Systems

MapMarker runs on:

• Microsoft Windows

• Solaris

• HP-UX

• Red Hat Linux

• SUSE Linux

See the product Release Notes for detailed information on supported operating systems for your specific version of MapMarker.

JVM Requirements

MapMarker requires a Java Virtual Machine (JVM) to run. See your version-specific MapMarker

Release Notes for detailed JVM support information for your MapMarker product. MapMarker 23 ships with the following.

• Sun JRE v. 1.5.0_09 (for Microsoft Windows and Sun Solaris)

• HP JRE 1.5.0._04 (for HP-UX)

• Sun JRE 1.5.0_11 (for Linux)

See the product Release Notes for detailed JVM support information for your specific version of

MapMarker.

During the installation, you will have the option of installing the JVM that ships with MapMarker or using one that you already have installed on your computer. See the product Release Notes for detailed JVM support information for your specific version of MapMarker.

MapMarker 23

28

User Guide

Chapter 2:

Installing MapMarker

Database Requirements

MapMarker 23 supports selected ODBC databases and drivers for SQL Server, Microsoft Access and Oracle.

See the product Release Notes for updated database support information for your specific version of

MapMarker.

Web Server Requirements (Developer Edition Only)

The MapMarker server allows you to develop geocoding applications on any Java Platform,

Enterprise Edition (Java EE) application server that supports JDK 1.5 or JDK 1.6.

MapMarker USA ships with:

• Apache Tomcat 5.5.20 (installed if the Web Application feature is selected during the Developer

Product installation)

Your product Release Notes may contain additional information on web server support information for your specific version of MapMarker.

Optimizing Performance

To get the greatest benefit from the MapMarker geocoding capabilities, you can follow some

optimization and performance guidelines. See

General Guidelines for Optimizing Geocoding

.

Installing MapMarker

This section describes the typical MapMarker installation procedures for Microsoft Windows users and for UNIX/Linux users. The graphical installer interface guides you through the procedure. You can also install silently, without user interaction.

L

You must have administrative privilege on your machine to install MapMarker 23.

Install Using the Graphical Interface on page 30

Installing Silently on page 35

MapMarker 23

29

User Guide

Chapter 2:

Installing MapMarker

Install Using the Graphical Interface

Follow these steps for typical installation using the graphical installer program:

1. Begin the installation procedure as follows, depending on whether you are installing on Windows or on UNIX/Linux:

• On Microsoft Windows, place the MapMarker DVD into your DVD drive. The installation starts automatically. Click Install Product in the list of options. In the Install Product dialog,

click Install MapMarker USA. Proceed to

step 2

.

If the installation does not automatically run, from the Windows 2003/XP Start menu, select

Run. From the Run dialog, type D:\SETUP.EXE in the Open command box (where D is the drive letter of your DVD-ROM). On Microsoft VISTA, from the Windows VISTA Start menu, type D:\SETUP.EXE in the search box provided, where D is the drive letter of your DVD-

ROM.

• On Solaris, Linux, or HP-UX, run the shell script from the root of the DVD-ROM using the command: sh startinstall.sh

Proceed to

step 2

.

To bypass the startinstall.sh script, go to the /instdata folder of the DVD-ROM, and run the executable appropriate for your operating system. For example, on a Linux operating system: sh linux/install.bin

2. In the Introduction dialog, click Next to display the What’s New dialog. This has a brief summary of new features for MapMarker 23 and has data vintage information.

3. From the What’s New dialog, click Next to display the License Agreement dialog.

4. After reading the License Agreement, click I accept the terms of the License Agreement and then click Next to display the Licensing dialog.

5. In the Licensing dialog, enter the location of your license file.

MapMarker 23

30

User Guide

Chapter 2:

Installing MapMarker

After entering the path to the license file, click Next.

If you entered valid license file path, you see the Choose Install Set dialog. If you did not point to a valid license file, you receive an error message and can to re-enter the license file.

L

During installation, the license file is copied into the MapMarker Data folder. The license file remains in that folder after an uninstall.

6. In the Choose Install Set dialog, the default Typical Install Set shows all the software and data available. To see a description of each feature, click on the feature to highlight it. A description of the selected feature appears in the Description box.

Note that all data is in the same dictionary (not separated by state). You will not see indication of different states, but you will only be able to geocode those states for which you are licensed.

MapMarker 23

31

User Guide

Chapter 2:

Installing MapMarker

Check the boxes for the features that you want to install and clear the check boxes of the features that you do not want to install. Product documentation is always installed.

After choosing the features to install, click Next to display the Choose Install Folders dialog

7. In the Choose Install Folder dialog, select the locations to install MapMarker software and data.

MapMarker 23

You can use the default locations, or click Choose to display the Browse for Folder dialog. From the Browse folder you can navigate to the desired location. Click OK in the Browse for Folder dialog when you are finished.

If you decide after selecting an alternative location that you would prefer the default location, click Restore Default Folder in the Choose Install Folder dialog.

When you have selected the software and data install folders, click Next.

32

User Guide

Chapter 2:

Installing MapMarker

8. If you selected the Desktop Application feature in the Choose Install Set dialog (in

step 6

), the

Desktop Application Settings dialog appears. If you are not installing the Desktop Application,

skip to

step 11

.

In the dialog, choose whether the installation is for this workstation only or whether the installation is shared by others on the network.

Select The installation is for this workstation only if you want a local installation of

MapMarker software and data. This is not shared with other users.

Select The installation will be shared if this workstation of MapMarker serves as a host that provides a group of users on the same network a common location for the software and data.

Users who wish to access the shared software and data that resides on the host workstation must do a separate client installation. See

Client Workstation Install on page 40

for more information.

After choosing a workstation only or shared installation, click Next to continue.

9. If you chose a shared installation (

step 8

), the dialog asks if you want to install the MapMarker

Desktop Application on this workstation (the host workstation). If you specified that the

installation would be for this workstation only, proceed to

step 11

.

If you plan to use the MapMarker application on this workstation (the one on which you are doing the Shared installation), check Install the Desktop Application on this workstation. If you are installing the software only for other users to access, do not check this box.

Click Next to continue.

10. The Desktop Application Settings dialog now shows the path to the shared data folder. Confirm or correct the path to the Shared Data Folder. Universal Naming Convention (UNC) paths are preferred (for example: \\ruready-W1\MapMarker_USA_v23\Data). This ensures that users running MapMarker on other machines are able to access the shared data. If the network share

MapMarker 23

33

User Guide

Chapter 2:

Installing MapMarker

name or shared folder does not already exist, it must be created before you can use the

MapMarker application.

L

The install program does not ensure that the data folder is shared to others on the network or is visible on the network. The person doing the installation is responsible for entering a valid path to the data folder and making this data folder accessible.

After you have confirmed the shared data folder location, click Next to continue.

11. In the Choose Java Virtual machine dialog, do one of the following:

• Select Install a Java VM specifically for this application to install the Java virtual machine that comes with MapMarker.

• Select Choose a Java VM already installed on this system to select a Java virtual machine that you already have installed on the computer. Then select Search for Others to search your computer for an installed JVM. After the search is completed, the dialog is populated with a list of the JVMs that were found on your workstation. Select the JVM that you want to use.

L

See your MapMarker version-specific Release Notes for complete information on operating requirements and recommendations, including information on the supported and recommended JVMs.

After selecting the JVM, Click Next to display the Choose Shortcut Folder dialog. If you select a

JVM that is already installed on your system, and that JVM is invalid or cannot be found, you receive an error message.

12. In the Choose Shortcut Folder dialog, choose where you want to create the product icons. You can create a new Program Group, place the icons in an existing Program Group, or make other choices. After making your selection, click Next to continue.

13. In the Pre-Installation Summary dialog, review the product features that you have chosen to install, disk space requirements and other details. To edit any selections, click Previous to go back to the earlier dialogs.

14. When you are satisfied with your installation choices, click Install. A progress dialog reports progress as the software and data is installing.

An installation of MapMarker and the entire Address Dictionary may be time-consuming. The amount of time required to install depends on how much data you are installing and machine processing power. Do not cancel the install process if there is hard drive or DVD drive activity. To verify that the installation is progressing, check the directory where the data is targeted to reside.

New files are added as the process continues.

15. When the installation is finished, the Install Complete message appears. Click Done to exit the installer.

MapMarker 23

34

User Guide

Chapter 2:

Installing MapMarker

Installing Silently

You can install MapMarker 23 without using a graphical interface and without user interaction. This allows you to install MapMarker in environments that do not provide a graphical user interface.

To do a silent install, use the properties file located in the root folder on the DVD. The file is named: silentinstall.properties

This file defines the values for the installer to use when installing in silent mode.

You must edit the file to suit your particular needs. This file includes extensive comments to assist you in this process. After editing this file, you can then launch the silent install and pass this properties file to the installer program.

To edit the silentinstall.properties file:

1. Copy the silentinstall.properties template file to a location on the target machine and open the file in a text editor.

2. In the properties file, specify information for the install properties and set the software and data features that you want to install. The file contains instructions for changing each of the values.

You must specify the following:

• Licence File (LICENSE_FILE=)

• Install location of the application files and data

• Java Virtual Machine

• Shortcuts/links location

• Features to install

• Web Application configuration

• Desktop Application configuration

3. To launch the silent install, use the following command line arguments:

On Unix/Linux (where media/CDROM is the location of the installation media and /tmp is the location of the silentinstall.properties file).

/media/CDROM/startinstall.sh -f /tmp/silentinsall.properties

On Windows operating systems (where D: is the drive location of the installation media and

C:\tmp is the location of the silentinstall.properties file).

start /w D:\instdata\windows\install.exe -f C:\tmp\silentinstall.properties

L

You must use an absolute path for the properties file.

MapMarker 23

35

User Guide

Chapter 2:

Modifying the MapMarker Installation

Modifying the MapMarker Installation

After you have installed MapMarker, you can run the Install program to modify the MapMarker installation. For example, you may want to add tools that you are licensed for but did not previously install. Or you may want to remove features that you had previously installed. These changes are characterized as modifications.

L

To modify your installation, you must use the same installer program that was originally used to install MapMarker. If you use a different installer program (for a different version of

MapMarker) you will not be able to modify the installation.

A modification is distinct from an upgrade. With an upgrade, currently installed software and/or data components are updated to their latest version. A modification adds features to or removes features from the currently installed version.

L

Some things cannot be modified, such as the paths for software and data.

Since MapMarker is already installed on your system, the install program opens to the Introduction dialog. This bypasses the Licensing dialog, since you have already accepted the License

Agreement. You can then proceed to modify your installation.

Modify Using the Graphical Interface on page 36

Modify Silently on page 37

Modify Using the Graphical Interface

To modify your MapMarker 23 installation, do the following:

1. Start the installer as described in

step 1

of

Install Using the Graphical Interface on page 30

.

2. At the Introduction dialog, click Next.

3. In the Licensing dialog, enter the location of your license file, then click Next. For a modification, this information is already populated in the dialog.

4. The Choose Install Set dialog appears and shows a checked box for every MapMarker feature that is installed. This is where you can install licensed features that you previously chose not to install, or uninstall selected features. Do the following:

a. Uncheck any feature that you want to remove. For example, you can uncheck and remove

Examples (sample application) that you previously installed. Click Next.

b. Check features that you want to install. You see only features that are licensed to you. Click

Next.

5. The Pre-installation Summary dialog shows a list of product features to be installed. If you chose to install new features, they are listed. If you chose to uninstall any features, those features are absent from the list of product features.

6. After verifying the product features, click Install.

MapMarker 23

36

User Guide

Chapter 2:

Upgrading the MapMarker Installation

7. The Install Complete dialog confirms your actions. Click Done.

Modify Silently

You can modify MapMarker 23 without using a graphical interface and without user interaction. To do a silent modify, edit the silentinstall.properties file to suit your needs. See

Installing Silently on page 35

for information on the location and use of the properties file.

The FEATURE_LIST variable of the silentinstall.properties file must include all the MapMarker features that you want to install. For example, if you already had the User Dictionary utility (udgui) installed and wanted to remove it, simply remove udgui from the FEATURE_LIST before launching the silent install.

You cannot use the silent modify procedure to change any of the following settings:

• Program paths

• JVM

• Shortcuts and links

You cannot use the silent modify procedure to change the configuration of a previously installed Web

Application (for Developer Edition). Similarly, you cannot change the shared/unshared configuration of the previously installed Desktop Application. If you want to make any of these changes in your installation, you must uninstall then reinstall MapMarker.

Upgrading the MapMarker Installation

Major releases can be upgraded when point releases become available. Similarly, one point release can be upgraded to the next point release. When doing an upgrade, all currently installed software and/or data components are updated to their latest version. All settings and configurations remain unchanged.

If you want to add or remove features or change settings, you must first upgrade and then run the installer again to modify your installation (see

Modifying the MapMarker Installation on page 36

).

Alternatively, you may uninstall and then re-install MapMarker if you have changes that cannot be done using the Modify option.

L

You cannot upgrade from one major release to another. For example, you cannot upgrade from MapMarker 14.x to 23. You must do a new installation of MapMarker 23. You can then upgrade from version 23 to a 23.x point release, when that becomes available.

You can have different major releases on the same workstation (such as MapMarker USA Version

14 and Version 22), but you cannot have different point releases installed on the same workstation

(For example, version 23.0 and version 23.1 cannot be on the same workstation.)

Upgrade Using the Graphical Interface on page 38

Upgrade Silently on page 39

MapMarker 23

37

User Guide

Chapter 2:

Upgrading the MapMarker Installation

Upgrade Using the Graphical Interface

To upgrade from MapMarker 23 do the following:

1. Start the installer as described in

step 1

of

Install Using the Graphical Interface on page 30

.

2. In the Introduction dialog, click Next to display the What’s New dialog.

3. In the What’s New dialog, click Next to display the Licensing Agreement dialog.

4. After reading the License Agreement, click I accept the terms of the License Agreement and then click Next to display the Choose Upgrade Type dialog.

5. The Choose Upgrade Type dialog presents the opportunity to upgrade data only, or software plus data. For example:

Make one of the upgrade selection (upgrading both software and data is generally recommended). The software option is included only if there has been a software upgrade; otherwise Upgrade Data Only is the only option.

L

Some releases may present more restrictive options. For example, if a new data component requires updated software, then the Confirm Upgrade dialog explains that both software and data must be updated.

Because this is an upgrade, you will not be prompted to select installation features, folders, or application settings. Nor will you be asked for a license file. All of this information is gathered from the original installation, and cannot be changed during an upgrade. If you want to change the installation feature set, you must modify (rather than upgrade) the installation. See

Modify

Using the Graphical Interface on page 36

.

Click Next to display the Pre-Installation Summary dialog.

6. In the Pre-Installation Summary dialog, verify the information, including the data folders. Click

Install to begin the upgrade.

MapMarker 23

38

User Guide

Chapter 2:

Uninstalling MapMarker

7. When the Upgrade Complete dialog appears, click Done.

Upgrade Silently

You can upgrade MapMarker v23 to a point release without using a graphical interface and without

user interaction. Start the silent installer as described in

Installing Silently on page 35

. Any

changes to the installation reflected in the properties file are ignored by the silent upgrade.

Uninstalling MapMarker

When uninstalling MapMarker, you have two options: a complete uninstallation, or a removal of certain features only. A complete uninstall removes the MapMarker program directories, groups, and icons. Files and folders created after the installation are not removed or affected in any way.

You can uninstall specific features (rather than a complete uninstall) if you use the graphical interface uninstall. The silent uninstall always does a complete uninstall.

Uninstall must be done using the same mode (graphical interface or silent) as the previous installation, modify, or upgrade. So if your previous install, modify, or upgrade was done using the graphical interface, then the uninstall is run using the graphical interface.

Uninstall Using the Graphical Interface on page 39

Uninstall Silently on page 40

Uninstall Using the Graphical Interface

If MapMarker was installed as a shared installation, the uninstaller removes the MapMarker Desktop

Application if it was previously installed on that workstation. Each user who accesses the shared application must use Add/Remove Programs on their own workstation to remove the MapMarker

Desktop Application.

1. Begin the uninstall procedure as follows, depending on whether you are uninstalling on Windows or on UNIX/Linux:

• On Microsoft Windows, from the Control Panel Add or Remove Programs utility select

MapMarker USA v23 and click Change/Remove. Proceed to

step 2

.

• On Solaris, Linux, or HP-UX Run the shell script from the root of the DVD-ROM using the command: sh /opt/MMv23/Uninstall_MapMarker_USA_v23/Uninstall_MapMarker_USA_v23 where /opt/MMv23 is the directory into which MapMarker 23 was installed.

2. In the Uninstall MapMarker USA dialog, click Next.

3. Select Complete Uninstall or Uninstall Specific Features, then click Next.

4. If you selected Complete Uninstall in

step 3

, the uninstall program runs immediately and

MapMarker 23 is completely uninstalled.

If you selected Uninstall Selected Features in

step 3

, uncheck the product features that you want to uninstall, then click Uninstall to uninstall those features only.

MapMarker 23

39

User Guide

Chapter 2:

Client Workstation Install

5. When the uninstall completes, click Done.

Uninstall Silently

If your previous installation, modify, or upgrade of MapMarker was done silently, the uninstall runs silently as well. Launch the uninstall by running the command appropriate for your operating system

shown in

step 1

of

Uninstall Using the Graphical Interface

. Remember, a silent uninstall always does a complete uninstall of MapMarker.

Client Workstation Install

If the system administrator has done a Shared installation of MapMarker and shared the program folder and data folder across the network, users on the network can run client installations on their local workstations. Client users can then run the MapMarker Desktop Application and access the shared Address Dictionary.

For instructions on doing a Shared installation, see

Shared Install on page 26

.

To set up a client workstation to access MapMarker from a shared installation, follow these steps:

1. Browse to the location of the shared installation of MapMarker on the network server. (You may need to check with the System Administrator for the location.)

2. From the shared machine, run the setup program (ClientSetup.exe) in the desktop folder of the

MapMarker program directory. The Welcome dialog appears.

3. In the Welcome dialog, click Next to display the Destination Folder dialog.

4. You can click Next to accept the default destination folder or click Change to display the Change

Current Destination Folder dialog and navigate to another location. Click OK in the Change

Current Destination Folder dialog when you have specified the new location, then click Next to display the Ready to Install the Program dialog.

5. At the Ready to Install the Program dialog, click Install.

6. When the installation wizard completes, click Finish.

All the components necessary to run the MapMarker Desktop Application using the shared Address

Dictionary are installed. This includes MDAC and the Microsoft Jet engine with their desktop ODBC drivers.

To uninstall the client application, from the Control Panel select the Add or Remove Programs utility. Select MapMarker 23 Desktop and click Change/Remove.

MapMarker 23

40

User Guide

Chapter 2:

Starting MapMarker

Starting MapMarker

After successfully installing MapMarker 23, you can start the Desktop Application, if you installed that feature on your workstation, or start the MapMarker Server if you installed the Web Application.

Starting the Desktop Application on page 41

Starting the MapMarker Server on page 41

Starting the Desktop Application

If you installed the Desktop Application feature of MapMarker, you can start the MapMarker Desktop as follows:

• From the Start Menu or the program group where you installed the MapMarker icons, click the icon named MapMarker Desktop. The Desktop Application starts.

If you chose not to install icons, open the directory where you installed MapMarker, and in the subdirectory named desktop double-click on the file mapmarkr.exe

. The Desktop

Application starts.

Starting the MapMarker Server

If you installed MapMarker 23 Web Application feature (available with the Developer Edition), you can start the MapMarker server as follows, depending on whether you are installing on Windows or on UNIX/Linux:

• On Microsoft Windows, from the Start Menu or the program group where you installed the

MapMarker icons, click the icon named Start MapMarker USA v23 Server . The

MapMarker Server starts.

If you chose not to install icons, open the directory where you installed MapMarker, and in the subdirectory named sdk\tomcat\bin double-click on the file startup.bat

. The

MapMarker Server starts.

• On Solaris, Linux, or HP-UX, from the directory where you installed the MapMarker icons, run: sh Start_MapMarker_USA_v23_Server

If you chose not to install icons, run the following command from the installation directory: sh sdk/tomcat/bin/startup.sh

L

On all operating systems, Administrator privilege is required to start the MapMarker Server.

MapMarker 23

41

User Guide

Geocoding with

MapMarker

After you have prepared your address data, you are ready to geocode your table. This chapter describes how to run MapMarker and how to start geocoding your records. This chapter also describes the basic geocoding workflow and illustrates the major MapMarker geocoding features.

In this chapter:

Š

Geocoding Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Š

Understanding the Geocoding Process . . . . . . . . . . . . . . . . . . . . .46

Š

Running MapMarker – Overview. . . . . . . . . . . . . . . . . . . . . . . . . . .57

Š

Opening and Running a Project . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Š

Opening a Table or Text File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Š

Selecting Input and Output Address Columns . . . . . . . . . . . . . . .64

Š

Geocoding Your Table Automatically . . . . . . . . . . . . . . . . . . . . . . .69

Š

Geocoding Your Table Interactively . . . . . . . . . . . . . . . . . . . . . . . .70

Š

Making the Most of Interactive Geocoding . . . . . . . . . . . . . . . . . .73

Š

Intersection Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Š

Using Single Line Addresses in Geocoding . . . . . . . . . . . . . . . . .76

Š

Using Address Range Geocoding . . . . . . . . . . . . . . . . . . . . . . . . .78

Š

Postal Geocoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Š

Geographic Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Š

Displaying Geocoded Records in MapInfo Professional . . . . . . .82

Š

Re-Geocoding a Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Š

Using Geocoding Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Š

Saving TAB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

3

Chapter 3:

Geocoding Terminology

MapMarker products use a common set of geocoding terms. We use these terms consistently in the

MapMarker documentation, and describe the terms more fully where appropriate.

address address dictionary address interpolation candidate

CASS™ centroid close match

MapMarker 23

Term

Geocoding Terminology

Definition

Information that identifies the location of a site, for example, a home or business.

The search dictionary used for matching addresses during geocoding.

A mathematical means of estimating an address location based on a street segment and the address ranges associated with that segment. This method of interpolation assigns coordinates to address records in relation to the position of address point candidates in the data, providing greater positional accuracy to the geocoded points.

An address record that is a potential match to the input address information.

A candidate is returned by the geocoding process. See also

geocoding

.

Coding Accuracy Support System. This is a process by which mailing addresses are standardized to meet U.S. Postal Service

® requirements for bulk mailing discounts. When CASS mode is enabled, MapMarker will perform this address standardization under strict matching conditions set by the USPS

®

. Geocoding in

CASS mode matches records to the exact house number, street name, and ZIP Code™. Other geocoding preferences are overridden.

A point at the calculated center of a polygon, often used to attach attribute information to an area. The centroid is used for labeling and geocoding, for example.

For an irregularly shaped area, region, or polygon, the centroid is derived mathematically and is weighted to locate the point at the approximate "center of gravity."

If an input address corresponds closely to one or more known records in the address dictionary, then the returned candidates are considered close matches. The specified matching criteria may include house number, street name, city name, locality, or postal code.

43

User Guide

Chapter 3:

CMRA

DPV

®

EWS geocoding

LACS

Link®

Term

geographic geocoding match strategy must match

PMB

Geocoding Terminology (continued)

Definition

Commercial Mail Receiving Agencies

Delivery Point Validation. DPV is technology available from the U.S.

Postal Service

®

. Used in conjunction with CASS mode geocoding,

DPV enables you to verify whether an address is a deliverable

USPS

®

address.

Early Warning System. The EWS file contains addresses that did not make it into the current USPS

®

update, and therefore do not match. Records that have no match because they are in the EWS file can be flagged in the EWS output column. EWS usage is not required for CASS discounts.

The process determining the X and Y coordinates of a location by its address.

Candidate coordinates are based on state, county, or city centroids.

This not very precise, but may be suitable for certain applications.

Locatable Address Conversion System. LACS

Link

allows business mailers to electronically update their rural-style addresses with locatable street-style addresses resulting from 911 emergency response address conversions.

For example, and address like RR 1 Box 32 might be converted to a street-style address like 141 Morrison Ave.

An approach to geocoding a table that achieves the desired geocoding results. For example, if geocoding hit rate is more important than accuracy, then looser match criteria would ensure that more records in the table are geocoded.

Or if you required greater accuracy, you could use stricter geocoding criteria, such as an exact match on street name and house number.

Must Match options are used for deciding whether returned candidates are close matches. A Must Match option does not eliminate non-close matches.

Private Mailbox

MapMarker 23

44

User Guide

Chapter 3:

Term

postal geocoding postcode post-directional post-type pre-directional result code street level geocoding

Suite

Link

™

Geocoding Terminology (continued)

Definition

Candidate coordinates are based on postal codes. This is faster but not as accurate as street level geocoding. Also, postal geocoding of rural areas is generally less accurate than that of urban areas. For

P.O. Box and rural route addresses, MapMarker automatically geocodes to a ZIP Code™ centroid, as required by CASS standards.

A unique identifier for postal mailing zones.

For the U.S.A. this is the ZIP Code system. See

ZIP Code™ on page 46

.

The letters following a street name that give a direction to the address, for example 18th Street N. This shows that the location is on the north side of 18th street.

Not every address has a post-directional component.

Street type that follows the street name. These are also known as street suffixes. For example, Main St.

See Publication 28, Postal

Addressing Standards Appendix C

for a complete list of street suffix abbreviations recognized by the USPS

®

and MapMarker.

Not every address has a post-type component.

The letters preceding a street name that give a direction to the address, for example W 18th Street. This shows that the location is on the west side of 18th street.

Not every address has a pre-directional component.

An alphanumeric code that describes the type and accuracy of the geocoding match.

MapMarker returns a result code (georesult) for each record it attempts to match. These codes allow you to determine the success and precision of the geocoding match. Result codes are

described in more detail in

Result Codes

.

Candidate coordinates are interpolated along a street segment.

This is a highly accurate level of geocoding.

Suite

Link

™ is the USPS® business name database that provides suite numbers for businesses located in high-rise buildings. This allows delivery sequencing where it would not otherwise be available.

MapMarker 23

45

User Guide

Term

user dictionary

ZIP Code™

Chapter 3:

Understanding the Geocoding Process

Geocoding Terminology (continued)

Definition

A customized search dictionary of addresses and coordinates that can be used in place of, or in addition to, the application’s address dictionary.

The system of numeric codes that identifies the individual post office or metropolitan area delivery station associated with an address.

Understanding the Geocoding Process

MapMarker is based on a model of relative matching that is governed by a set of weights that scores each portion of the address against candidate records (possible matches) in the Address Dictionary.

The resulting scores are summed and the candidate’s total score is used to determine the best match or matches. An exact match is made when a candidate scores well above other candidates. If there is no clear best match, several (non-close) candidates may be returned.

If a record is not geocoded, you can still attempt to match that record during interactive geocoding where you can pick what you consider the best match from a list of candidates.

The basic MapMarker workflow is to open your MapInfo Table or other input file, specify which columns contain address information, and then geocode your records. MapMarker automatically matches your records to those in its Address Dictionary, determines if there is a match, and assigns the geographic coordinates.

The following topics provide an overview of the supported file formats, basic steps, input, and expected output.

Subsequent topics in this chapter provide more detail.

•

Supported File Formats on page 46

•

Geocoding Flexibility and Trade-offs on page 47

•

General Guidelines for Optimizing Geocoding on page 48

•

Specify Input Address Columns on page 48

•

Specify Output Address Columns on page 49

•

Interpreting Census Block IDs on page 51

•

Output Field Size and Column Names on page 54

•

Mixed Case Street Output on page 55

•

Setting Startup Preferences on page 56

Supported File Formats

MapMarker supports (opens and writes) files in the following data formats:

• TAB – MapInfo TAB files

• DBF – dBASE format

MapMarker 23

46

User Guide

Chapter 3:

Understanding the Geocoding Process

• 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 23 can export TAB, DBF, CSV, and TXT files to ESRI Shapefile (SHP) format.

Shapefile export is described in

Exporting to Shapefiles on page 62

.

See

Opening a Table or Text File on page 58

for instructions on opening an input file in

MapMarker. See

Defining Properties of Delimited Text Files on page 59

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.

There are trade-offs that you must consider with respect to how you intend to use the geocoded data. When setting up a geocoding session, consider questions such as the following:

• What level of matching accuracy are you looking for: a unique address match or close match?

• What level of geographic accuracy do you need for your geocoded points: street-level centroid or postal code centroid?

• Is your goal to geocode as many records as possible?

The answers to these questions are driven by how you intend to use the geocoded records. When determining the location of a new retail store, you need to know the distribution of current and potential customers. In this case, you would need to geocode as much of the customer base as possible but you might not need an exact street address match for each customer. Geocoding to postal code centroid would be suitable for this analysis.

MapMarker 23

47

User Guide

Chapter 3:

Understanding the Geocoding Process

Street level geocoding with strict matching preferences would be useful for cases in which it is necessary to know exactly where your customers are. For example, if you are a utility service coordinator and need to know exactly where your customers are in relation to neighborhood gas lines, the positional accuracy of each customer is of critical importance to you.

In addition, the matching routine uses the geocoding preferences that are set for the table to determine whether certain matching conditions are required or not. For example, the MapMarker default preferences do not require a match on street name and ZIP Code, but require an exact match on the house number. This generally gives the best combination of hit rate with the fewest erroneous matches (false positives) and the best performance.

For an overview of geocoding match strategies, see

Choosing Match Strategies

.

General Guidelines for Optimizing Geocoding

MapMarker 23 has been optimized for high performance. Follow these guidelines to achieve even faster performance.

In general, you will achieve faster and more accurate geocoding if you standardize and format your data. By reducing the ambiguity in the input data, MapMarker 23 will be able to find appropriate candidates faster. For complete information on addressing practices and conventions and ZIP

Codes, see the

ZIP Code Lookup

page on the USPS web site.

Also consider the following guidelines to optimize your results and performance.

• Use the fastest processor available to you. Pitney Bowes Business Insight recommends 2.5 Ghz dual processor or better.

• Have enough memory so that the operating system can allocate some memory to your disk cache. Pitney Bowes Business Insight recommends 2 GB RAM or better.

• Have at least 10 GB available disk space.

• Store the Address Dictionary on a local hard drive.

• Sort your table by postal code before geocoding.

• Use Must Match (exact match) criteria for the most precise geocoding results. However, note that this strategy requires more processing and may reduce performance.

• Do not create points automatically.

• Remove indexes on any table output columns before geocoding.

Specify Input Address Columns

MapMarker reads the addresses stored in your table and matches it against address records in the

Address Dictionary. MapMarker then assigns geographic coordinates (geocodes) each address that it can process.

You must specify the columns that contain your addresses. The Select Input Columns dialog is the first area where you specify that information. For street level geocoding, you must have at least one street address column plus one column each for city and state or ZIP Code. For ZIP Code centroid matching, you do not need to specify a street address or city and state.

MapMarker 23

48

User Guide

Chapter 3:

Understanding the Geocoding Process

MapMarker can also geocode single line addresses, where all address components appear on a

single line rather than in separate fields. That strategy is described in

Using Single Line

Addresses in Geocoding on page 76

.

For instructions on selecting input columns, see

Selecting Input Columns on page 65

.

See also the following topics:

Supported File Formats

Geocoding Flexibility and Trade-offs

General Guidelines for Optimizing Geocoding

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

Specify Output Address Columns

MapMarker can store longitude/latitude coordinates and geocoding result codes in your table. For supported output file formats, you can either prepare the table ahead of time by adding columns to store this information, or specify that MapMarker automatically creates the columns for you. For

ODBC (remote) tables, you or your database administrator must add the columns before you run

MapMarker.

L

The longitude/latitude columns are required if you do not want MapMarker to create points automatically. A result code column is optional, but it is recommended.

If you want MapMarker to return the matching address for you to compare with your input address, you must provide columns for that information. For supported file formats, you can either prepare your table ahead of time, or create the columns by clicking Modify Columns on the Select input columns from your table or Select output columns from your table dialogs. For remote tables, add the columns before opening the file in MapMarker. If you store your input addresses in two fields, note that MapMarker only returns the matching address to a single field. ZIP Code and ZIP + 4

®

are returned to two fields.

MapMarker can also return attributes (such as demographic data) from other tables during geocoding, so you must first prepare columns from the Select Input Columns dialog as described in

Specify Input Address Columns on page 48

.

For instructions on selecting output columns, see

Selecting Output Columns on page 66

.

See the following topics:

Supported File Formats

Geocoding Flexibility and Trade-offs

General Guidelines for Optimizing Geocoding

Specify Input Address Columns

Output Column Type/Width Requirements

MapMarker 23

49

User Guide

Chapter 3:

Understanding the Geocoding Process

Interpreting Census Block IDs

Output Field Size and Column Names

Mixed Case Street Output

Setting Startup Preferences

Output Column Type/Width Requirements

The following table lists the type and width requirements for output columns.

The asterisked columns are required for generating a CASS™ report (not for geocoding to CASS standards, but simply for generating the report.)

For more information on LACS

Link®

and DPV

®

output requirements, see the following topics.

LACSLink Output Columns

DPV Output Columns

Result Code

Output Column

Long (X)

Lat (Y)

Firm

*

Address

*

Address2

*

City

*

State

*

Output County

ZIP Code

*

ZIP + 4

*

Urb

*

Delivery Pt

*

Check Dig

*

LACS

*

Carrier Route *

MapMarker 23

char(4) char(30) char(2) char(1) char(1) char(4)

Type (Width)

char(13)

Decimal (11,6) or Float

Decimal (10,6) or Float char(30) char(64) char(64) char(30) char(2) char (40) char(5)

50

User Guide

Chapter 3:

Understanding the Geocoding Process

Output Column

DefaultFlag *

PMB

*

PMB range

* char(1) char(4) char(8)

Type (Width)

Census Block ID

EWS flag * char(15) char(1)

RecordType * char(1)

County char(40)

DPV ConfCode *

DPV Cmra *

DPV falsePos *

DPV FtNote1 * char(1) char(1) char(1) char(2)

DPV FtNote2 *

DPV FtNote3 * char(2) char(2)

LACS Indicator *

LACS

Link

Code *

* required field for generating CASS report char(1) char(2)

See the following topics:

Supported File Formats

Geocoding Flexibility and Trade-offs

General Guidelines for Optimizing Geocoding

Specify Input Address Columns

Specify Output Address Columns

Interpreting Census Block IDs

Output Field Size and Column Names

Mixed Case Street Output

Setting Startup Preferences

Interpreting Census Block IDs

MapMarker can return Census Block IDs as output, or partial Census information, depending on the quality of the match.

MapMarker 23

51

User Guide

Chapter 3:

Understanding the Geocoding Process

The complete Census Block ID is a 15-character code and is made up of the following:

SSCCCTTTTTTGBB(B) where S=State FIPS (Federal Information Processing Standard) code (two characters)

C=County FIPS code (three characters)

T=Census Tract (six characters)

G=Census Block Group (one character)

B=Census Block (typically two characters, sometimes three)

MapMarker can return the full 15-character Census Block ID for geocoded records with S2, S3, S5,

S7, or S8 geocoding result codes The S4 result code can return a 15-character Census Block ID if the block groups on each side of the street are the same.

L

Result codes are very important in evaluating the accuracy of your geocoded results. For a more complete discussion of this topic, see

Result Codes

.

Some S codes and Z codes may return partial census information if ZIP + 4

®

information is supplied.

Others may not return any census information because certain information is missing.

The following table shows what census information is returned, if any, for specific geocoding result codes.

S8

S7

Geocoding Result Codes Related to Census Block Information

Result Code Census Block ID Output

S8 results are matched to either the single point associated with an address point candidate, or to an address point candidate that shares the same house number.

An S8 result is possible only if you are using a point/parcel dictionary.

The S8 indicates that the address candidate corresponds to an exact point. No interpolation is required.

S8 results can return complete 15-character Census Block ID.

S7 results are matched to an interpolated point along a street segment. An S7 result is possible only if you are using a point/parcel dictionary in addition to a street segment dictionary. Since the S7 interpolation is based on known point addresses, the interpolation is more accurate than interpolation based on a segment dictionary alone

(which would produce an

S5

result).

S7 results can return a complete 15-character Census Block ID. You must enable address point interpolation to generate S7 result codes.

See

Dictionary Preferences

and check the Use Address Point

Interpolation check box to enable address point interpolation during geocoding.

MapMarker 23

52

User Guide

S6

S5

S4

S3

S2

S1

SX

SC

Chapter 3:

Understanding the Geocoding Process

Geocoding Result Codes Related to Census Block Information

Result Code Census Block ID Output

S6 results are matched to a point ZIP centroid. A point ZIP is a 5-digit

ZIP Code™ that represents a unique ZIP such as a single site, building, or organization.

S6 is the same level of geocoding accuracy as a

Z6

result.

S5 results are matched to an interpolated point along a street segment. An S5 result is based on a street segment dictionary only.

This interpolation is not a accurate as an

S7

result.

When using the Address Dictionary, this can return a complete

15-character Census Block ID.

S4 results are matched to a street centroid point.

S4 results can return complete 15-character Census Block ID, but only if the block groups on each side of the street are the same. A house number is also required for Census Block IDs.

S3 results are matched to ZIP + 4

®

locations. S3 is the same level of

geocoding accuracy as a

Z3

result.

S3 results can return complete 15-character Census Block ID if the

ZIP + 4 location is contained in one Census Block. However a ZIP + 4 location may cover more than one Census Block, in which case S3 may return a 12-character Census Block Group number.

S2 results are matched to ZIP + 2 locations. This may return partial census information if ZIP + 4 is supplied.

S2 is the same level of geocoding accuracy as a

Z2

result.

S1 results are matched to ZIP centroid locations. This may return partial census information if ZIP + 4 is supplied.

S1 is the same level of geocoding accuracy as a

Z1

result.

SX results are matched to a point located at street intersection.

SC results represent a match where the original point has been moved a specified distance (usually along a perpendicular line) toward or away from the associated street segment. An SC result is possible only when both a point/parcel dictionary and a street segment dictionary are available and when you are using the centerline offset feature.

MapMarker 23

53

User Guide

Z6

Z3

Z2

Z1

Chapter 3:

Understanding the Geocoding Process

Geocoding Result Codes Related to Census Block Information

Result Code Census Block ID Output

Z6 results are matched to a point ZIP centroid. Point ZIPs are 5-digit

The Z6 code indicates that these special ZIPs are actual point locations, not an area. Point ZIPs include unique single sites, buildings, or organizations.

May return partial census information if ZIP + 4 is supplied. Z3 results are matched to ZIP + 4 locations.

May return partial census information if ZIP + 4 is supplied. Z2 results are matched to ZIP + 2 locations.

May return partial census information if ZIP + 4 is supplied. Z1 results are matched to ZIP centroid locations.

For more information on result codes, see

Result Codes

.

See the following topics:

Supported File Formats

Geocoding Flexibility and Trade-offs

General Guidelines for Optimizing Geocoding

Specify Input Address Columns

Specify Output Address Columns

Output Column Type/Width Requirements

Output Field Size and Column Names

Mixed Case Street Output

Setting Startup Preferences

Output Field Size and Column Names

MapMarker can return output information (such as firm names, apartment numbers, and suites) that exceeds the recommended width of the output fields for Street and Firm. When this happens,

MapMarker truncates the information in the respective output field.

In the Input Column and Output Column dialogs, if a field name is too long to be seen in its entirety in the list box, hold the cursor over the field name to display a popup box with the full name of the field.

See the following topics:

Supported File Formats

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

MapMarker 23

54

User Guide

Chapter 3:

Understanding the Geocoding Process

Mixed Case Street Output

Setting Startup Preferences

Mixed Case Street Output

This optional feature adds the ability for output street addresses to have mixed case. The capability is supplied in the MapMarker Desktop Application only. This geocoding preference located on the

Geocode tab of the Geocode dialog. When the Mixed Letter Case check box is selected, the output street is in mixed case for a match. The input street column remains unchanged.

See

Geocoding Your Table Automatically on page 69

for a description of the Geocode dialog.

An output address without a house number remains in uppercase. This is to accommodate cases such as PO BOX 233. Streets such as McFly are handled so that the letter following Mc is capitalized. However, a word like MacIntosh is not handled because it cannot be differentiated from a word like Macoun.

See the following topics:

Supported File Formats

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

MapMarker 23

55

User Guide

Chapter 3:

Understanding the Geocoding Process

Setting Startup Preferences

Setting Startup Preferences

MapMarker has Startup preferences that apply to all of your geocoding sessions. This allows you to start MapMarker with a consistent appearance and behavior. These Startup preferences are available on the System Preferences dialog.

To display the System Preferences dialog, click System Preferences on the Options menu, and then click the Startup tab.

You can use any and all preferences available in this dialog. For the file open choices, if you select either Show for MapInfo or dBASE files or Show for ODBC tables, the Open dialog appears automatically when you start MapMarker. If you have both options selected, MapMarker prompts you with another dialog at startup to choose which type of table you want to open.

You may also control which of the setup dialogs, if any, display on startup. Choose from:

• Show Select Column Dialog On Open (selected by default)

• Select Attribute Files After Selecting Columns

• Show Geocode Dialog After Selecting Columns (selected by default)

By selecting all three options, when you start MapMarker, it walks you through the geocode and attribution setup phase. The settings are saved to the table as metadata and used as new defaults when you open the table again.

Other system preferences are discussed in

Setting System Preferences on page 100

.

See the following topics:

Supported File Formats

Geocoding Flexibility and Trade-offs

General Guidelines for Optimizing Geocoding

Specify Input Address Columns

MapMarker 23

56

User Guide

Chapter 3:

Running MapMarker – Overview

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

Running MapMarker – Overview

MapMarker geocodes your records to street level, ZIP Code™, or geographic centroid either automatically (making a match without user interaction) or interactively (allowing you to decide the match from a list of suggestions). You can use a number of strategies to geocode your records. A basic scenario is to run MapMarker and follow these steps:

1. Open the table to be geocoded and identify the columns that contain specific address components (see

Selecting Input and Output Address Columns on page 64

.

2. Geocode your records automatically to match as many records as possible. See

Geocoding

Your Table Automatically on page 69

.

3. Geocode remaining unmatched records interactively by choosing from a list of candidates. See

Geocoding Your Table Interactively on page 70

.

4. Display geocoded records in Pitney Bowes Software Inc. mapping software. See

Displaying

Geocoded Records in MapInfo Professional on page 82

.

5. Analyze the result codes. See

Result Codes

.

After opening an input table, you must identify the input columns that contain address information to use for matching purposes.

Opening and Running a Project

A project preserves settings preferences and restores these settings the next time the project is opened. A project file overrides any existing metadata settings associated with a TAB file.

To create or save a project, see

Creating and Saving a Project on page 96

. That topic also

describes the specific items that are saved with a project.

To open an existing project:

1. From the MapMarker menu, select File > Projects > Open Project.

2. Navigate to the folder that contains the project, select the project name (with a PROJ file extension), and click Open.

MapMarker 23

57

User Guide

Chapter 3:

Opening a Table or Text File

L

You can open only one project at a time.

After opening the project you can geocode using the column mappings and geocoding preferences that were saved with the project. Or you can you make changes before proceeding with geocoding.

If you are using an old project, you may get an initialization error when you try to run the project in

MapMarker 23. This is because your project is pointing to an older Address Dictionary. You can ignore this error message, and the project will then use the MapMarker 23 Address Dictionary. To eliminate this error message, see the

Note

on

page 97

with

Creating and Saving a Project

.

Running a Project from a Batch File

You can run a project from a command line batch file. For this syntax see

Creating a Project-Based

Batch File on page 97

.

Opening a Table or Text File

The following steps describe how to select and open your input file. See

Supported File Formats on page 46

.

L

This procedure applies to opening local files. For instructions on opening remote tables, see

Geocoding Remote Tables

.

1. Start MapMarker from the Windows Start menu or Shortcut menu.

2. Select File > Open Table, click or click the right mouse button to display a shortcut menu.

The Open Table dialog appears. Select the folder that contains your tables and click Open.

MapMarker 23

58

User Guide

Chapter 3:

Opening a Table or Text File

3. From the File of type drop-down list, select one of the following file types:

• MapInfo Tables (*.TAB)

• DBF Files (*.DBF)

• Comma-delimited text (*.CSV)

• Other delimited files

All files associated with the selected file type will appear. See

Supported File Formats on page 46

for a description of MapMarker supported input file formats.

4. Select the file that you want and click Open. If you open a MapInfo TAB file, you will now identify address input and output columns. Continue with

Selecting Input and Output Address

Columns on page 64

If you open a text file (CSV, TXT, or possibly other file extension), the Text File Wizard appears.

Continue with

Defining Properties of Delimited Text Files

Defining Properties of Delimited Text Files

After you open any CSV or TXT input file, the Text File Wizard appears. This wizard allows you to define the properties of the input file.

L

The wizard creates or modifies a format file that governs the properties of its associated text file. The format file is created in the same folder that contains the input file. If this folder is not writable, the format file is created in My Document\MapMarker USA\ folder. The format file is given the same name as the associated text file, but with an FMT file extension. In most cases you will not have to examine or maintain the format file in any way.

The following steps follow one likely scenario and show how to use the Text File Wizard for a comma-delimited text file This example assumes that you are opening the file for the first time and the first row of the table is used for column titles (rather than data).

First, open the text file as described in

Opening a Table or Text File on page 58

. Use the File of

Type drop-down list to select TXT file extensions.

1. Step 1 of the Text File Wizard displays the Input Table dialog with the name of the CSV or TXT file that was previously opened, as described in

Opening a Table or Text File on page 58

. The

list box area of the dialog will display up to the first 20 records of the opened file.

MapMarker 23

59

User Guide

Chapter 3:

Opening a Table or Text File

Text File Type: If the text file is a delimited file, the appropriate button will be selected in the wizard.

Delimited is selected if the text file is a CSV file.

Delimiter Type: If the delimiter is recognized it will be selected and the other choices are disabled.

For example, with a CSV file a comma delimiter is recognized and the other group selections are disabled. Semicolon, tab, or slash can also be used as delimiters. If one of these standard delimiters is not recognized in your text file, you can select Other and type the delimiter character. For example, your text file might use a pipe symbol (|) as a delimiter. Not all characters and symbols can be used as delimiters. You will receive an appropriate message if you try to specify a disallowed character.

First Line Used for Column Titles: You can use the first line of the text file as column titles or as data.

To use the first line as column titles, check the First Line Used for Column Titles check box.

This will replace the generic FIELD_1, FIELD_2... labels and use the first row of the text file to name the columns.

If First Line Used for Column Titles is not checked, the first line will be used as data just as any other line in your text file. In this example, we will assume that the first line of the text file is used for column titles.

When you have finished with step 1of the wizard, click Next to go to

step 2

of the wizard.

2. Step 2 of the text file wizard allows you to examine the fields (columns) in the input table and change the field name.

MapMarker 23

60

User Guide

Chapter 3:

Opening a Table or Text File

Click a field name to see all the relevant information for that field. You can also change the name of fields. For example, you could change the name of the first field from Business to

Organization Name. The name change is committed after you proceed to step 3 of the wizard.

Some fields cannot be changed, depending on they type of file that you opened.

Click Next to update your changes to go to

step 3

of the wizard.

3. Step 3 of the text file wizard allows you to select the output file. This file contains the output columns in which MapMarker will store the address components, result codes, and coordinate information for each matched record after you geocode.

Typically, the output file uses the same base name as the input file with _out appended to the file name. This prevents you from accidentally overwriting the data in the original input file. Click OK.

L

By default, the output file is created the same folder that contains the input file. If this folder is not writable, the output file is created in My Document\MapMarker USA\ folder. If the output file already exists, you can choose to overwrite or change the file name.

4. Click OK.

5. Select the input columns from your table. See

Selecting Input Columns on page 65

.

6. Select output columns. Standard address column names will be named with the OUT_ prefix (for example, OUT_STATE and OUT_ZIPCODE) and these column names will be pre-populated in

output column selections. See

Selecting Output Columns on page 66

.

MapMarker 23

61

User Guide

Chapter 3:

Exporting to Shapefiles

Delimited File Guidelines

The Text File Wizard helps you manage how delimited files are interpreted and used in MapMarker.

The following guidelines may help you when using the Text File Wizard.

• If you use the first line of the file for column titles (see

First Line Used for Column Titles: on page 60

), you can change these column titles in step 2 of the wizard. This change is committed

when you proceed to step 3 of the wizard.

• Settings are remembered when you subsequently open the file. If you subsequently want to change the way first line is interpreted, you must delete the appropriate FMT file and re-run the wizard. For a description of the FMT file, see the see the

Note

on

page 59

with

Defining

Properties of Delimited Text Files

• If you want to ignore the first row in the text file (that is, not use it for either column title or data), you should remove the row from the data file. When you geocode, you can specify which rows to

geocode, so you can select or skip row 1. See

step 3

of

Geocoding Your Table Automatically

for an example of selecting a range of rows to geocode.

• Delimited text files can be geocoded automatically or interactively. See

Geocoding Your Table

Automatically on page 69

and

Geocoding Your Table Interactively on page 70

.

Exporting to Shapefiles

MapMarker 23 can export TAB, DBF, CSV, and TXT files to ESRI Shapefile (SHP) format.

For example, a MapMarker 23 can open any of the following file types for Shapefile export:

• MapInfo Table (TAB)

• Delimited text (CSV, TXT)

• DBF

L

There are some limitations on how attributes of the original files are preserved and exported to SHP files:

• For DBF files, binary, memo, and OLE data types are not supported and are not exported to the SHP file.

• For CSV files, numbers are exported as strings.

• For TAB files, date and time fields are exported as strings, and decimal numbers are truncated to six places of precision.

The following steps describe how to select, open, and export your input file.

1. Start MapMarker from the Windows Start menu or Shortcut menu.

2. Open a Table or text file. Follow the steps in

Opening a Table or Text File on page 58

.

3. From the Table menu, select Export to ESRI Shapefile.

4. In the Export To dialog, select a file name for export. The SHP file extension is automatically selected for ESRI Shapefiles.

MapMarker 23

62

User Guide

Chapter 3:

Exporting to Shapefiles

MapMarker checks for write permission on the directory that you are exporting the Shapefile to. If write permission is verified, the process continues. You will receive a message if you do not select a valid file name, or if the directory does not have write permission, or the Shapefile already exists.

MapMarker also checks whether the opened file is a DBF file. If the input is a DBF file, the export file name will be named with a _out suffix. For example, if the input file was Customer.dbf the export file name will be Customer_out.shp.

After specifying the SHP file name, click Save.

5. In the Export to ESRI Shapefile dialog, do one of the following:

a. If the table in not mappable or does not contain points, Use X/Y Columns will be selected.

For TAB files, Long (X) and Lat (Y) are initially populated with the appropriate column names as determined from table metadata. If the TAB file metadata does not contain this information, MapMarker will look for typical names for coordinate columns and populate those column names into the Long (X) and Lat (Y) fields. If no typical names are found (or if you want to change the Long (X) and Lat (Y) column names), you can select columns from the drop-down lists.

MapMarker 23

CSV, TXT, or DBF files do not contain metadata.

63

User Guide

Chapter 3:

Selecting Input and Output Address Columns

b. Alternatively, if the table is mappable and there are points in the table the Use Point

Geometry will be initially checked. If the table is not mappable, the Use Point Geometry choice will be disabled (grayed out).

6. Click Export. If you selected Use X/Y Columns, MapMarker verifies the type of the selected

Long/Lat columns. The acceptable types are decimal, float, and string.

If the opened table is a DBF file, or the user doesn’t have write permission, the Export To dialog

re-appears. This dialog is described in

step 4

.

7. A progress bar appears and a confirmation message indicates the success of the Export.

L

See the

Note

at the beginning of this section to understand limitations on date/time and other

data that is exported to SHP files.

Selecting Input and Output Address Columns

After opening your input file, you are ready to identify the address input address columns and output address columns. These are the columns that contain address information to use for the purposes of geocoding matching.

See the following topics:

Selecting Input Columns on page 65

Selecting Output Columns on page 66

MapMarker 23

64

User Guide

Chapter 3:

Selecting Input and Output Address Columns

Selecting Input Columns

For MapMarker USA, the key input address columns are:

MapMarker U.S.A. Input Address Columns

Input Address Example

Firm

Address

Address2

(optional secondary address line)

City

State

ZIP Code™

Pitney Bowes Business Insight

One Global View

Suite 175

Troy

NY

12180

8337

ZIP + 4

®

Urb

(Urbanization)

Parc Sabana (used for Puerto Rico addresses only).

The following steps describe how to identify the address input columns in your input file. After identifying the input columns, you can begin geocoding, either interactively or automatically.

1. Choose the table you wish to geocode. Click Open.

2. Click OK. A progress bar appears as your table is being updated. Then a browser window appears, displaying the Table. You will see a dialog box titled: Select input columns from your table.

MapMarker 23

65

User Guide

Chapter 3:

Selecting Input and Output Address Columns

3. Select the input columns that contain the appropriate address components. If your table has separate columns for ZIP Code™ and ZIP + 4

® information, identify each column in the

ZIP Code and ZIP + 4 boxes.

MapMarker attempts to choose the address columns for you. It can make some determinations for fields, but if this is the first time this table has been opened in MapMarker, be sure to verify these columns. Once you have geocoded the table, the column settings are saved to the table as metadata and used for future geocoding sessions.

Single line address input is recognized in the Address field. See

Using Single Line Addresses in Geocoding on page 76

for details on geocoding single line addresses.

County Level Geocoding

Use the County input field only if you want to explicitly geocode to the county centroid. You may need to add the County column to your input table. (Click Modify/Add Columns and see

Adding a Column on page 68

. For county centroid geocoding, you should also use the State input field because identically named counties are found in several states.

4. When you are finished selecting input columns, click Next. You are now ready to select output

columns. See

Selecting Output Columns

.

Selecting Output Columns

After you have selected input columns, you will see a dialog box titled: Select output columns from your table.

1. Select columns in your output table where you want MapMarker to store the address components, result codes, and coordinate information for each matched record. From the list of at the left, drag column names to the appropriate output address column. Use <Clear> selection to clear a column selection.

MapMarker 23

66

User Guide

Chapter 3:

Selecting Input and Output Address Columns

To avoid overwriting your input data, use output columns that have different names than the corresponding input columns. If your output columns and input columns have the same name, you receive a Warning message when you click Finish in

step 3

. If you click Yes, you will

overwrite your input data. Click No to change your output column selections.

2. In the Select output columns from your table dialog box, continue with the following steps, as necessary.

a. If you do not want MapMarker to create points for your table, clear the check box marked

Create points in MapInfo table. In that case, you must select longitude and latitude columns to proceed with geocoding. (Create points is not available if you are geocoding a text file rather than a TAB file.)

b. If you are using CASS™ and want to generate a CASS report, all output fields with the exception of asterisked fields are required. Note that this is not required for geocoding with

CASS, but only for generating a CASS report.

c. Identify a Census output column if you want MapMarker to return the Census Block code for the matched address. MapMarker returns the code that represents the state and county FIPS code, census tract, and tabulation block, depending on the match type.

d. For geographic geocoding (returned candidates based on state, county, or city centroids), identify a County output column if you want MapMarker to geocode to the county centroid.

You may need to add the County column to your output table.

e. If you are using DPV, LACS

Link

, or Suite

Link

, select Show DPV and LACSLink Columns.

Note that the DPV and LACSLink columns are required for generating the CASS report (but not required for CASS address matching). The SuiteLink column is optional for CASS reports.

MapMarker 23

67

User Guide

Chapter 3:

Selecting Input and Output Address Columns

3. Once you have provided all the information in the Select output columns from your table, click

Finish. You are then returned to the Geocode dialog box.

If your output columns and input columns have the same name, you will receive a Warning message when you click Finish. To avoid overwriting your input data, click No at the Warning message, and specify output columns that have different names than the corresponding input columns. If you need to add a uniquely named output column, click Modify /Add and follow the instructions in

Adding a Column on page 68

.

After selecting the input and output columns, you can begin geocoding, either interactively or automatically.

See the following topics:

Geocoding Your Table Automatically on page 69

Geocoding Your Table Interactively on page 70

Adding a Column

1. You may need to add a column to either your input or output table. For example, you may want to add a uniquely named column to an output table so that you do not overwrite your input data during geocoding.

2. Click Modify/Add Columns to access the Modify Table Structure dialog.

3. Click Add Column to add a new column to the table. The Columns list box displays a new default 10-character column named Field# (where # is the column number in the table).

4. In the Column Information group, define the Name, Type, and Width of the new column containing the new attributes. If you are adding a new output column, this column should have a unique name but have the same type and width as the corresponding input column. For example, if the input table Firm column is defined as type Character with a width of 10, you could define and Output_Firm column with the same type and width parameters.

MapMarker 23

68

User Guide

Chapter 3:

Geocoding Your Table Automatically

5. Click OK when done editing the new column information.

6. A message appears telling you that the table must be closed and re-opened for update. Click

Yes to continue.

Geocoding Your Table Automatically

To geocode automatically:

1. If the Geocode dialog is not automatically displayed upon leaving the Select Output dialog, do one of the following:

• Select Table > Geocode from the MapMarker menu.

• Click .

• Click the right mouse button, and select Geocode from the pop-up menu.

2. In the Geocode Precision group, select Street Level and select Automatic from the Method drop-down list.

Alternatively, you could geocode to ZIP Centroid or Geographic Centroid.

3. Select the Range to Geocode and Row Numbers to geocode. By default, MapMarker automatically geocodes the unmatched rows. For previously geocoded tables, you may be able to improve matching by re-geocoding records that had a georesult below a specified level.

4. Set additional geocoding preferences by selecting the appropriate tabs and check boxes. For an explanation of these preferences, see

Using Geocoding Options on page 83.

In particular, see

MapMarker 23

69

User Guide

Chapter 3:

Geocoding Your Table Interactively

Match Settings Dialog on page 88

to apply a range of restrictive or looser match criteria, and

Fallback Dialog on page 93

to permit a less precise geocoding match if the original criteria do not produce a match.

5. Click Geocode to begin geocoding. The Automatic Geocode dialog appears showing a progress bar that updates the match count every 25 records.

6. At the completion of the geocoding run, the Cancel button changes to Done. Click Done to leave the Summary dialog. MapMarker opens the log file if you selected Automatically open

log file after geocoding in the Log File dialog.

The log file contains a history of the geocoding pass, including the number of matched, unmatched and previously matched records, and the number of matched records by result code.

Information from subsequent passes is appended to the top of the log file. The log file size limit is

1 MB.

7. To create a summary of the geocoding results for a table, select Table > Table Summary.

Specify the column containing the georesult and save the information as a text file.

L

The summary is for the active table (the frontmost browser). If you run multiple tables in a single session, you have addresses open for each table. To obtain the summary information for the desired table, click on the browser title bar to make it active and select

View > Summary.

To view information about previous geocoding passes, view the log file by selecting View > Log file.

See the following topics:

Automatic Geocode dialog

Making the Most of Interactive Geocoding on page 73

Interactive Geocode dialog

Quick Geocode command

Geocoding Your Table Interactively

MapMarker allows you to geocode records interactively by choosing from a list of candidates. Using interactive geocoding, you can expand the search for a match, map potential matches, move back up the table to an earlier record, and correct your records directly from the MapMarker dialog.

L

Interactive geocoding is not completely interactive. MapMarker attempts to geocode the row first. Only when it fails to find a single close match is the record displayed in the Interactive dialog.

1. Do one of the following:

• Select Table > Geocode from the MapMarker menu.

• Click .

• Click the right mouse button, and select Geocode from the pop-up menu.

MapMarker 23

70

User Guide

Chapter 3:

Geocoding Your Table Interactively

2. In the Geocode Precision group, select Street Level and select Interactive from the Method drop-down list.

3. Select the range and type of rows to geocode.

4. Click Geocode. The Interactive Geocode dialog appears and shows the first unmatched record and a list of suggested matches. The matches contain a result code category, address number, street name, city, state, and ZIP Code™.

5. Select Geocode if you agree that the highlighted suggested match is the correct match.

MapMarker assigns coordinates from that row and moves on to display the next unmatched record. To choose a different candidate in the list, move the highlight with your cursor to your choice and select Geocode.

6. Select Next if MapMarker offers no match suggestions or if you do not agree with the choices in the match list.

When you click Next, a dialog is displayed asking if you want to mark the record as

“Non-geocodable.” This means that you do not want MapMarker to attempt to match this record during future geocoding passes. This is useful when you know the record does not geocode and you do not want it to display again in future geocoding passes. You have several choices in this dialog:

• Click Yes to have MapMarker mark the record with the result code NG (non-geocodable).

This dialog is displayed each time you click Next.

• Click Yes to All if you want to mark all future “Ignore” records in this geocoding session as

NG. The dialog is not displayed again during the session.

• Click No if you do not wish to mark the record as NG. The dialog is displayed each time you click Next on a record.

• Click No to All if you do not want to mark any “Ignore” records as NG. The dialog is not displayed again during the session.

MapMarker 23

71

User Guide

Chapter 3:

Geocoding Your Table Interactively

7. To expand the search area, check Expand Search and specify a radius up to 99 miles. Select the check box labelled Limit to current state if desired. This feature helps to find a match when the input address contains limited or inaccurate city or ZIP Code information.

8. To change the interactive matching conditions, click Options. The tabs, Match Settings,

Fallback, and Multiple Match appear. Make the necessary changes to increase the potential for a match.

For more information on controlling these geocoding match settings and preferences, see:

Match Settings Dialog on page 88

Fallback Dialog on page 93

Multiple Match Dialog on page 94

9. Click Search to search the Address Dictionary using the new matching conditions.

10. Edit the record by entering new text that may increase the likelihood of a match. Click Search to bring up a new list of suggestions that may better match the edited record.

Add the edits into your table by selecting the Write selected address below to database on

Geocode check box. Choose the match from the list and click Geocode. MapMarker geocodes the record and updates your table with your edits.

11. To see an expanded list of ranges, including apartment numbers, office suites, etc., select

Ranges. A detailed list of address ranges for the highlighted street appears. Click Ranges again to close the list of ranges.

12. Click Back to move backward in the table to re-display a record.

13. Click Map to view the match candidates in a map window. The match candidates are displayed with color-coded symbols that indicate their match potential to the input address. See

Displaying Geocoded Records in MapInfo Professional on page 82

for a description of the

symbols.

The map feature is available if you have set the location for street data in the Maps tab in the

System Preferences dialog, as described in

Maps System Preferences

. Also see

Viewing

Match Candidates on a Map

, for related information.

14. Click Close. A Geocoding Summary is displayed showing the results of the session

15. Click Done. To view the summary again, select View > Summary.

16. To create a summary of the geocoding results for a table, select Table > Table Summary.

Specify the column containing the georesult and save the information as a text file.

MapMarker 23

72

User Guide

Chapter 3:

Making the Most of Interactive Geocoding

See the following topics:

Automatic Geocode dialog

Geocoding Your Table Automatically

Interactive Geocode dialog

Quick Geocode command)

Making the Most of Interactive Geocoding

Interactive geocoding allows you to control the matching process because you can accept or ignore a potential match from the list of suggestions that MapMarker generates for the record.

See the following topics:

Change Matching Conditions on page 73

Map the Match Candidates on page 73

Using Wide Search on page 73

Edit Your Records on page 74

Change Matching Conditions

MapMarker follows the settings in the Geocode dialog or responds to your changed settings as you progress through the interactive pass. To increase the list of suggested matches, you can use less restrictive matching criteria. You can do this at the beginning of an interactive pass or change the settings for each record by clicking Options on the

Interactive Geocode dialog

.

You can also return to a previous record in the table by selecting Back and changing settings as needed. This feature can help you maximize the potential for a match.

Map the Match Candidates

To help you choose the best match for your record, display the candidates on a map via Map in the

Interactive dialog. This requires that you have street data on your system and you specify its location in the System Preferences > Maps tab.

See

Viewing Match Candidates on a Map

for a complete discussion of visualizing match

candidates.

Using Wide Search

From the Interactive Geocode dialog, you can increase the probability of a match by using Relaxed mode combined with wide search. Wide search considers all streets that begin with the first letter of the input street name, and therefore can identify more potential candidates. Wide search is most commonly used in combination with Relaxed mode, although is can be used with other match modes or custom constraints.

MapMarker 23

73

User Guide

Chapter 3:

Making the Most of Interactive Geocoding

Although wide search can potentially identify more candidates, it reduces the performance (speed of geocoding) and may return some false positive candidates, depending on the quality of your input data. By default wide search is disabled.

A two-pass geocoding strategy can give you the optimal results.

Pass 1: Geocode addresses using Close mode without wide search. Good quality addresses will be successfully geocoded.

Pass 2: Choose the non-matching addresses from Pass 1 and re-geocode these addresses using

Relaxed mode with wide search enabled. You can also use wide search in combination with Must

Match constraints to more finely control your geocoding results.

This two-pass strategy provides the advantages of best geocoding accuracy, good performance, and fewer false positive candidates.

To use wide search, select Use Wide Search from the Match Settings dialog. See Wide search can also be selected with Quick Find. See

Quick Find Settings

.

See also:

•

Match Modes on page 88

for a description of match modes.

•

Use Wide Search

(with interactive geocoding).

•

Match Settings dialog

(Use Wide Search check box).

•

Quick Find Settings dialog

(Use Wide Search check box).

The MapMarker USA 23.0 Developer Guide describes the API methods that control this feature.

Edit Your Records

Interactive geocoding also allows you to correct your record to improve the possibility of a match. If you choose, your table can be updated to reflect the newly edited record, all from within the

Interactive Geocode dialog.

By manually correcting the fields to put the firm, street, city, and state into their proper locations, the record is more logical and MapMarker can make better suggestions on possible matches. After editing the record, click Search to display a new list of match candidates.

To write these changes to the base table, select the Write modified address above to Input Fields

on Geocode check box and click Geocode to confirm the match.

L

Your edits overwrite the address data in the respective fields, so be sure not to alter the fields containing the correct address data.

Remote Tables

Note that when you geocode remote tables interactively, MapMarker cannot overwrite the Input

Address fields of the source table. That is why the check box Write modified address above to

Input Fields on Geocode is unavailable in the Interactive Geocode dialog.

MapMarker 23

74

User Guide

Chapter 3:

Intersection Geocoding

Intersection Geocoding

MapMarker enables you to geocode to street intersections in two ways. The method that you choose depends on how you prefer to store the street and cross street information in your table.

Intersection addresses stored in one column. With this method of intersection geocoding,

MapMarker reads input street addresses that contain intersection tokens (such as “&&”) between the street and the cross street. If you do not have the information in your table, you must create a column that contains the street and the cross street.

Street 1 and Street 2 names can be separated by one of the following intersection tokens: “and”,

“at”, “&”, “&&”.

For example, to specify the intersection of Main Street and Washington Avenue, the column input address could look like:

Main Street && Washington Avenue

Main St & Washington Ave.

Main St at Washington Ave

Main St and Washington Ave

You can omit spaces between the token and the street name, but the space is required for the ”and” separator.

To use this single-column method to geocode to street intersections, do the following:

1. Open the table you want to geocode.

2. In the Select input columns from your table dialog, specify the columns that have the appropriate address components. Map the column that contains the intersection information to the Address box.

3. Click Next. In the Select output columns from your table dialog, select the columns in which you want to store the output

4. Click Finish.

5. If the Geocode dialog does not display automatically, select Table > Geocode.

6. Click Geocode.

Intersection addresses stored in separate columns. In this method of intersection geocoding, the street and cross street are stored in separate columns. An option in the Select input columns

from your table dialog enables you to specify which column to use as the cross street. To use this method to geocode to street intersections, do the following:

1. Open the table you want to geocode.

2. In the Select input columns from your table dialog, specify the columns from your table that have the appropriate address components. Map the columns that have the street and cross street information to the Address and Address2 boxes.

3. Select the Use Address2 Column as Intersection Cross Street check box.

4. Click Next. In the Select output columns from your table dialog, select the columns to store the output.

MapMarker 23

75

User Guide

Chapter 3:

Using Single Line Addresses in Geocoding

5. Click Finish.

6. If the Geocode dialog does not display automatically select Table > Geocode.

7. Click Geocode.

For an example of intersection geocoding see

Intersection Geocoding on page 75

:

Using Single Line Addresses in Geocoding

MapMarker can geocode single line addresses, in which all address components appear on a single line rather than in separate fields.

Each line of your single line input data must appear in the order:

<street address> <city> <state> <ZIP> <country>.

Not all of these address components are required. If you omit the ZIP Code™ and country,

MapMarker still geocodes the address based on street address, city, and state.

If you use delimiters (comma, semicolon, or colon) between each component of the address,

MapMarker parses the address accordingly. For example, if your input was:

One Global View, Troy, NY, 12180

The delimiters are recognized and the address is parsed as:

Main Address

City

State

ZIP Code

Country

One Global View

Troy

NY

12180

U,S.A. (default for MapMarker U,S.A.)

If delimiters are missing in the input address, MapMarker recognizes spaces as separators and uses internal parsing rules to identify address components. In the example above, MapMarker would still successfully geocode the address even if some or all of the delimiters were missing in the input.

However, non-delimited or partially delimited addresses may take longer to geocode.

Punctuation (such as quotation marks) are ignored for geocoding purposes.

See the following topics:

Single Line Geocoding Capabilities and Guidelines on page 77

Examples of Single Line Addresses on page 77

MapMarker 23

76

User Guide

Chapter 3:

Using Single Line Addresses in Geocoding

Single Line Geocoding Capabilities and Guidelines

MapMarker can recognize single line addresses that have the following characteristics:

• P.O. boxes

• Address units such as apartment or suite numbers

• Addresses with Private Mailbox (PMB) information

• Dual addresses (such as addresses containing both a P.O. Box and street)

• U.S military addresses

Single line address geocoding works within the following guidelines:

• The country is not required for U.S.A.

• You must include either (City plus State) or ZIP Code™ as the last address element. For example, either Phoenix AZ or 85068-3049 (an Arizona ZIP Code) would be sufficient. However, the City or State alone would not be sufficient.

• Specific delimiters (comma, semicolon, or colon) between each address component improve geocoding results. MapMarker can geocode space-delimited addresses, but it takes longer and may not be as accurate. Partially delimited addresses are acceptable.

• Your input table can have formatted addresses, single line addresses, or a combination of both.

MapMarker recognizes the input formats and geocodes accordingly. Single line addresses are recognized in the Address field of the Select input columns table. See

step 2

of

Selecting Input

Columns

for a description of that dialog.

• You can still specify output columns. See

step 1

of

Selecting Output Columns

for a description of that dialog.

• Single line input is supported in Quick Find geocoding. See

Finding Address with Quick Find

.

Whether you identify address input columns in your input file, or use single line style input addresses, you can geocode your data automatically or interactively.

•

Geocoding Your Table Automatically on page 69

•

Geocoding Your Table Interactively on page 70

Examples of Single Line Addresses

Following are examples of single line addresses that can be geocoded with a close match.

• 2901 GRANT ST UNIT 140 # 8351 Mobile AL 36606-4743 (unit type and number, no delimiters)

• 2901 GRANT ST UNIT 140 # 8351, Mobile, AL, 36606-4743 (unit type and number, comma delimiters)

• 2901 GRANT ST UNIT 140 # 8351; Mobile; AL; 36606-4743 (unit type and number, semicolon delimiters)

• P.O.Box 33049 Phoenix Arizona 85068-3049 (P.O. Box, no delimiters)

• P.O.Box 33049, Phoenix, Arizona, 85068-3049 (P.O. Box, comma delimiter)

• 1 Global St Troy New York 12180-8399 (street type corrected from St. to Vw, no delimiters)

• 2901 GRANT ST UNIT 140 # 8351 Mobile AL (unit type and number, no delimiters, no ZIP Code)

• 2901 GRANT ST UNIT 140 # 8351, Mobile, AL (unit type and number, comma delimiters, no

ZIP Code)

• P.O.Box 33049 Phoenix 85068-3049 (P.O. Box, no delimiters, no State)

• P.O.Box 33049, Phoenix, 85068-3049 (P.O. Box, comma delimiters no State)

MapMarker 23

77

User Guide

Chapter 3:

Using Address Range Geocoding

• 2901 GRANT ST UNIT 140 # 8351, Mobile AL (unit type and number, no delimiters, no

ZIP Code)

• 2901 GRANT ST UNIT 140 # 8351 Mobile, AL (unit type and number, partially delimited, no

ZIP Code)

• 16736 Hwy 8 W P.O. Box 1070 Grenada MS 38901 (dual address: both P.O. Box and street)

• UNIT 2134 APO AP 96214 (military address)

Using Address Range Geocoding

Some business locations are identified by address ranges. For example, a shopping plaza could be addressed as 10-12 Front St. This is how business mail would typically be addressed to such a business location. These address ranges can be geocoded to the interpolated mid-point of the range.

L

Address ranges are different than hyphenated (dashed) addresses that occur in some metropolitan areas. For example, a hyphenated address in Queens County (New York City) could be 243-20 147 Ave. This represents a single residence (rather than an address range) and is geocoded as a single address. If a hyphenated address similar to this example is returned as a close match candidate, address range geocoding will not be attempted.

Address ranges cannot be geocoded in CASS™ mode, since the range is not an actual USPS

® address. Also, the following fields are not returned by address range geocoding:

• ZIP + 4

®

(in multiple segment cases)

• Delivery Point

• Check Digit

• Carrier Route

• Record Type

• Multi-Unit

• Default flag

See the following topics:

Address Range Geocoding Capabilities and Guidelines on page 78

Examples of Address Ranges on page 79

Address Range Geocoding Capabilities and Guidelines

Address Range geocoding works within the following guidelines:

• There must be two numbers separated by a hyphen.

• The first number must be lower than the second number.

• Both numbers must be of the same parity (odd or even) unless the address segment itself has mixed odd and even addresses.

• Numbers can be on the same street segment or can be on two different segments. The segments do not have to be contiguous.

MapMarker 23

78

User Guide

Chapter 3:

Postal Geocoding

• If both numbers are on the same street segment, the geocoded point is interpolated to the approximate mid-point of the range.

• If the numbers are on two different segments, the geocoded point is based on the last valid house number of the first segment. The ZIP Code™ and FIPS Code are based on the first segment.

• In all cases, odd/even parity is evaluated to place the point on the correct side of the street.

Address range geocoding will not be attempted in the following cases:

• If a valid hyphenated address is recognized as a close match (similar to the Queens, NY address described in the preceding

i

)

• If removing the hyphen produces a close match. For example: an address like 1-5 Hoosick St,

Troy, NY produces a valid address of 15 Hoosick St if the hyphen is removed. So 15 Hoosick St. is returned as a close match and address geocoding is not attempted.

Examples of Address Ranges

Following are examples of address ranges that can be successfully geocoded:

• 212-216 Red Apple Court, Central Valley, NY

• 212-266 Red Apple Court, Central Valley, NY – can geocode even though 212 and 266 are located on different segments.

• 2702-2730 Pine Hills Road, Orlando, FL

The following addresses would not be geocoded to address range for the given reasons:

• 212-215 Red Apple Court, Central Valley, NY – invalid address range because 212 and 215 have different parity numbers (even and odd) and the segment does not allow this.

• 10-212 Red Apple Court, Central Valley, NY – invalid address range because 10 does not exist

• 2730-2702 Pine Hills Road, Orlando, FL – invalid address range because the first number is greater than the second number.

• 10-14 Columbia Avenue, Lancaster, PA – address range geocoding is not attempted because removing the hyphen produces a close match on 1014 Columbia Avenue.

Postal Geocoding

As an alternative to street-level geocoding, you can specify for MapMarker to geocode your records to the appropriate ZIP Code™ centroid. This is called Postal geocoding. This is a fast method of geocoding because it eliminates the need to match based on street address. This method matches the ZIP Code in your table with the ZIP Code in the Address Dictionary. MapMarker geocodes to the most precise ZIP Code level contained in your table.

Use ZIP Code centroid matching when you have a large database that you want to geocode quickly and you are less concerned with spotting the points to street level.

To geocode to ZIP Code™ centroids:

1. In the Geocode dialog, select To ZIP Centroid under Geocode Precision.

2. Choose the range and type of rows you want to geocode.

MapMarker 23

79

User Guide

Chapter 3:

Geographic Geocoding

3. Click Geocode. MapMarker updates the Automatic Geocode dialog every 25 records.

4. When through, click Done to view the log file or return to the MapMarker menu.

Geographic Geocoding

Geocoding to geographic centroids provides another fast alternative to street-level geocoding that you can use when you do not need an exact match on the street address. Geographic geocoding is less precise than street or postal geocoding, but may be suitable for certain applications. You can

also use geographic geocoding as a fallback option (see

Fallback Dialog on page 93

) if MapMarker cannot match a record to the level or precision you originally requested (such as street level).

For geographic geocoding, MapMarker returns the most precise geographic centroid that it can, based on the user input.

To geocode to geographic centroids:

1. At the Geocode dialog in the Geocode Precision group, choose To Geographic Centroid.

2. Choose the range and type of rows you want to geocode.

3. Click Geocode.

MapMarker 23

80

User Guide

Chapter 3:

Geographic Geocoding

MapMarker 23

81

User Guide

Chapter 3:

Displaying Geocoded Records in MapInfo Professional

Displaying Geocoded Records in MapInfo Professional

After MapMarker geocodes your records, you can display them in MapInfo Professional or MapX to analyze them geographically.

1. Close your table in MapMarker and open it in MapInfo Professional or add it to your MapX geoset.

The points are displayed with color-coded symbols that represent the level of geocoding precision for the record, as described below.

• Magenta stars: all records matched to a single address point. No interpolation is required

(S8 result code)

• Orange stars: all records geocoded an interpolated point along the candidate’s street segment (S7 result code)

• Purple stars: all records geocoded to point ZIP

®

locations (S6, M6 and Z6 result codes)

• Maroon stars: records offset a specified distance along the perpendicular between the original parcel/point to the associated street segment. (SC result code).

• Green stars: all records geocoded to a street address (S5 and M5 result codes)

• Blue stars: all records geocoded to a shape path centroid (S4, M4 result codes)

• Yellow stars: all records geocoded to a ZIP + 4

®

centroid (S3, M3 and Z3 result codes)

• Cyan stars: all records geocoded to a ZIP + 2 centroid (S2, M2 and Z2 result codes)

• Red stars: all records geocoded to a ZIP Code™ centroid, including highway exits (S1, M1 and Z1 result codes)

• Black stars: all records geocoded to intersections (Mx and Sx result codes)

• Black circles: all records geocoded to a state geographic centroid (G1 result code)

• Red circles: all records geocoded to a county geographic centroid (G2 result code)

• Blue circles: all records geocoded to a city/town geographic centroid (G3 result code)

See

Result Codes

for an explanation of the types of result codes.

2. Add other map layers such as MapMarker Streets or ZIP Code boundaries to give your points a geographic reference.

You are now ready to analyze your data geographically. using Pitney Bowes Software Inc. mapping software.

When displaying your geocoded points over street data, use MapMarker Streets, StreetInfo, or

StreetPro display (products that use TIGER 2000 street geometry). When geocoding with

MapMarker, be sure to display over enhanced TIGER 2000 street geometry, such as MapMarker

Streets or StreetPro Enhanced or Display. This preserves the positional accuracy of the points with respect to the street geometry.

MapMarker 23

82

User Guide

Chapter 3:

Re-Geocoding a Table

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 rematched, 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 matching options that are available from the tabs in the Geocode dialog. These preferences affect the conditions under which MapMarker attempts to match a record.

This includes automatic or interactive geocoding, exact matching settings, fallback options, how to handle multiple matches, log file setup, table attribution, and CASS settings

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

• 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.

To set geocoding preferences for a table:

1. On the Table menu, click Geocode. The Geocode dialog appears.

MapMarker 23

83

User Guide

Chapter 3:

Using Geocoding Options

2. Choose the settings you want from any of the geocoding preferences tabs: Geocode, Log File,

Match Settings, Fallback, or Multiple Match.

3. Click Apply to set the changes or Geocode to geocode immediately.

For information on each of the tabs, see:

Geocode Dialog on page 84

Log File Dialog on page 86

Match Settings Dialog on page 88

Fallback Dialog on page 93

Multiple Match Dialog on page 94

Geocode Dialog

The Geocode dialog allows you to select a variety of preferences that control the method, precision, range, and levels of geocoding.

Geocode Precision

Geocoding precision is a measure of how close a match is to the true location of the record you want to geocode. MapMarker has Street Level, ZIP

® centroid, and Geographic precision.

Street Level precision means that MapMarker attempts to geocode all records to street address, but some matches may end up at a less precise location such as a ZIP centroid (ZIP + 4

®

, ZIP + 2, or

ZIP Code™) or shape path.

ZIP Centroid precision means that MapMarker attempts to match a record to the most precise ZIP

Code it finds. Keep in mind that a match to a ZIP + 4 centroid is nearly as precise as a match to a street address. The added bonus of ZIP Centroid matching is the speed of the operation;

MapMarker processes records faster if it only has to match on the ZIP Code.

MapMarker 23

84

User Guide

Chapter 3:

Using Geocoding Options

The disadvantage of ZIP Code matching is that MapMarker only examines the ZIP Code field. If your records only contain 5-digit ZIP Codes, MapMarker can do no better than match to 5-digit ZIP Code centroids. If you use street level precision, MapMarker looks at both the street name and ZIP Code fields and attempts to return street level coordinates and falls back to ZIP Code coordinates, optionally to ZIP + 4 centroid.

Geographic precision is to the city, county, or state geographic centroid. See

Geographic

Geocoding on page 80

for details.

Street Level Geocoding Method Preference

The geocoding Method list allows you to select the geocoding method for Street Level geocoding.

MapMarker processes records automatically or interactively.

For automatic geocoding, the operation continues until all records are processed or the operation is cancelled. For interactive geocoding, MapMarker geocodes records automatically, but stops on each record for which it cannot make a single match. You can then choose the best match from a list of candidates.

Type of Rows to Geocode

The Unmatched Rows selection means that MapMarker attempts to geocode addresses in your input table only if those addresses have not previously been matched (rows for which the GeoResult field: blank or N). Addresses that already have been geocoded are not re-geocoded. Unmatched

Rows is the default selection.

You can click All Types to geocode all rows, regardless of whether they have been previously geocoded. You can also click Georesult less than and select a level of geocoding from the drop-down list. This re-geocodes addresses that were originally matched below the given level of precision. Use Georesult less than only with a table that has already been geocoded. If you use this option with a table that has not been geocoded, MapMarker geocodes all of the rows regardless of this selection.

Range to Geocode

The All Rows selection means that MapMarker attempts to geocode all rows in your input table. You can also select Row Numbers and select a range of row numbers for geocoding.

Matched Case Preference

Use Return Street Output in Mixed Letter Case to write matched output street addresses in mixed-case (for example, 12 Front St). The input street column remains unchanged.

An output address without a house number remains in uppercase. This is to accommodate cases such as PO BOX 233.

In mixed case output, streets such as McFly are handled so that the letter following Mc is capitalized.

However, words like MacIntosh are not handled because it cannot be differentiated from cases like

Macoun.

MapMarker 23

85

User Guide

Chapter 3:

Using Geocoding Options

Attribution Bindings

MapMarker has the ability to add information from one table to another, either before, during, or after the geocoding process. This ability is called attribution binding.

To begin the process of attribution binding (or simply to display or modify existing attribute bindings), click Configure Attribution. This displays the Bind Attribute Table Columns to Output Columns dialog.

Table attribution described fully in the topic

Table Attribution with MapMarker

.

For related information, see:

Using Geocoding Options on page 83

Log File Dialog on page 86

Match Settings Dialog on page 88

Fallback Dialog on page 93

Multiple Match Dialog on page 94

Log File Dialog

The log file is a text file that MapMarker generates during geocoding that contains setup and processing information about the geocoding session. If you do not specify another name, the log file is named mapmarkr.log

and contains the results of the session, including number of matches, non-matches, previously matched records, and the number of matched records by result code.

MapMarker appends new information to the top of the log file after each geocoding pass.

By default, the log file is written to the My Documents\MapMarker USA folder. CASS reports and

MapMarker batch files are also written to this area by default.

The maximum file size for the log file is 1 MB.

L

By default, the error files IgnoredErrors.txt and ODBCErr.log are created in:

Documents and Settings\All Users\Application

Data\MapInfo\MapMarker\USA\14.0.

MapMarker 23

86

User Guide

Select the Log File tab to control log file options.

Chapter 3:

Using Geocoding Options

To specify a different log file name, select the Specify Log File Name check box in the Log File tab of the Geocode dialog. You may enter a path as well as a name for the log file (for example, c:\temp\Us_addr.log). If the path specified is invalid, MapMarker creates MapMarker.log in the My

Documents\MapMarker USA folder.

In Windows 2003/XP, you must close the log file from a previous session before you can open the table it refers to in MapMarker. If you do not, a message that the table may not have read/write access is displayed. Close the table in the text editor to proceed.

In addition to creating a log file with the results of the geocoding operation, you can generate a table summary that shows the results of the geocoding. To do so, select Table > Table Summary and specify the column in your table that contains the georesults of the active table. The Save As dialog appears allowing you to save this information as a text file.

For related information, see:

Using Geocoding Options on page 83

Geocode Dialog on page 84)

Match Settings Dialog on page 88)

Fallback Dialog on page 93

Multiple Match Dialog on page 94)

MapMarker 23

87

User Guide

Chapter 3:

Using Geocoding Options

Match Settings Dialog

The Match Settings tab lets you specify how precisely MapMarker matches input addresses against the Address Dictionary. By adjusting match settings, you can control whether MapMarker requires a very precise match, an looser match, or an intermediate level of matching. The best choice for you depends on the nature of your data and the requirements of your application.

Match Modes

You can select one of the match modes to control the variance allowed between an input address and the matched address. Less variance ensures the highest quality matches. More variance can provide high quality matches on badly formatted or incomplete input addresses, but requires additional processing time.

The Standard, Tight, and Relaxed

Match Modes

use internal algorithms to achieve matching

results.

CASS

Mode allows you to produce a CASS report (assuming that CASS data is available).

You can also select Custom (

Exact Match On

) to achieve more precise control over your matching results.

MapMarker 23

88

User Guide

.

Match Mode

Standard

Chapter 3:

Using Geocoding Options

Match Modes

Description

This is the default mode and generally provides the best combination of accurate geocoding, few false matches, and high performance.

L

Standard mode is not equivalent to what was previously called

Default mode.

Tight

Relaxed

This provides strict matching rules. This restrictive mode generates the most precise matching. In general, this returns fewer non-close matches than are returned in Standard mode.

L

Tight mode is not equivalent to selecting Custom matching with all

Exact Match criteria checked (House Number, Street Name, City

Name, and ZIP Code).

This provides less strict matching rules. In general, this increases your chances of getting a close match. You may wish to use wide search in combination with Relaxed Mode as part of a two-pass geocoding strategy.

For information on this strategy, see

Using Wide Search on page 73

.

L

Relaxed mode is not equivalent to selecting Custom matching with all Exact Match criteria unchecked.

CASS When CASS mode is enabled, MapMarker will perform address standardization under strict matching conditions set by the USPS

®

.

Geocoding in CASS mode matches records to the exact house number, street name, and ZIP Code™. Other geocoding preferences are overridden.

CASS Mode also enables the option to Produce a CASS Report

See

CASS Options on page 90

.

Custom (Exact Match

On)

See

Exact Match On

for a description of all the Exact Match settings.

MapMarker 23

89

User Guide

Chapter 3:

Using Geocoding Options

Exact Match On

Use the Require Exact Match On criteria to fine-tune your control over geocoding matching preferences. You can specify precise matching criteria based on house number, street name, city name, and ZIP Code. If all specified criteria are not met, then the geocoded candidate is not considered a close match.

Exact Match

House number

Street name

Exact Match Settings

Description

When the House Number box is checked, candidate house numbers must be exactly matched to return a close match. When the House

Number box is unchecked, MapMarker can make a close match even if the house number match is not exact.

When the Street Name box is checked, candidate street names but be exactly matched to get a geocoding match. When the street name box is unchecked, MapMarker will accept similar street names as a match.

This requires an exact match on all elements of the street name. Also, blank input values for these elements will not match non-blank values in the candidate records.

L

Street name exact match also requires an exact match on street

type. That is, 147 Rd. must be matched exactly; 147 Ave does not match.

City Name

ZIP Code

When the City Name box is checked, MapMarker requires a city name match. When this box in unchecked, the city name does not have to match.

When ZIP Code™ is checked, ZIP Code must be exactly matched to get a geocoding match. When ZIP Code is unchecked, surrounding

ZIP Codes are considered for matching purposes and records with missing ZIP Codes are also considered.

CASS Options

Select CASS match mode to implement CASS™ matching rules for geocoding. MapMarker can standardize your mailing addresses and print a report describing the success of the operation. This is required if you plan to qualify your table for bulk mailing discounts from the U.S. Postal Service

®

.

This certification process is known as CASS.

Because the address standardization requirements for CASS are very rigid, you cannot control the geocoding settings you normally have when geocoding with the MapMarker Desktop application.

For example, you cannot geocode to a user dictionary when you are CASS geocoding.

MapMarker 23

90

User Guide

The CASS related options are:

Chapter 3:

Using Geocoding Options

CASS Options

Produce a CASS Report

Use DPV

Use LACSLink

Use SuiteLink

Return Short Address

MapMarker 23

CASS Related Options

Description

If you wish to qualify your table for CASS, you must print a report USPS Form 3553. If you choose to Produce a

CASS Report, the Use DPV and Use LACSLink check boxes are automatically checked. DPV validation is required for CASS reports. See

DPV

.

Check this box to specify DPV

®

geocoding. The DPV files must be installed and unlocked in order to access this feature. If you choose to Produce a CASS Report, the

Use DPV mode check box is automatically checked. This is because DPV validation is required for CASS™ reports.

Check this box to specify LACS

Link®

geocoding. The

LACS

Link

files must be installed and unlocked in order to

access this feature. See

LACSLink

.

Check this box to return Suite

Link

™ addresses. See

SuiteLink

.

Check this box to return CASS abbreviated addresses.

See

Returning Abbreviated Addresses

91

User Guide

Chapter 3:

Using Geocoding Options

CASS Options

CASS Related Options (continued)

Description

Return Short City Name

Use EWS file

Check this box to return CASS short city names.

Returning Abbreviated City Names

.

Check this box to include the USPS

®

-supplied EWS file when geocode. The EWS file is a file produced by the

USPS to report addresses that did not make it into the current update. The use of this file is optional

Additional Match Settings

The other selections on the Match Settings tab are controlled with the following check boxes in the

Additional Settings group.

Option

Use Wide Search

Additional Matching Preferences

Description

If checked, the wide search is used. Wide search considers all streets that begin with the first letter of the input street name, and therefore can identify many more potential candidates. Wide search is most often used in combination with Relaxed mode as part of a

two-pass geocoding strategy. See

Using Wide Search on page 73

.

Accept S5 or Better Street

Address Matches

Accept S5 Street Address

Matches Only

Check this box if you only want street address matches of S5 or higher accuracy.

Check this box if you want S5 street address matches only.

Match to Street Intersections If checked, MapMarker can read input street addresses that contain two street names separated by any of the following intersection tokens: “and”, “at”, “&”, “&&”. For example:

Main Street & Washington Avenue

This type of matching affects the MapMarker geocoding speed since it requires additional processing.

Clear Output Columns if No

Match

If checked, clears existing output values for a record if a match cannot be made. For example, your table may contain longitude and latitude values obtained from another source, and you want to maintain that information if MapMarker cannot match the record. If not checked, the output information is kept intact even if a geocoding match is not made.

MapMarker 23

92

User Guide

Chapter 3:

Using Geocoding Options

Option

Prefer User Dictionary

Matches

Additional Matching Preferences (continued)

Description

Prefer Matching ZIP Over

Matching City

If checked, user dictionary close match candidates take precedence over the MapMarker Address Dictionary. See

Preferring User

Dictionary Matches

for information on selecting a user dictionary. If not checked, the Address Dictionary takes precedence.

If checked, ZIP Code™ matches take precedence over city matches when determining a close match candidate. If not checked, a city match is favored over ZIP Code match.

For related information, see:

Using Geocoding Options on page 83

Geocode Dialog on page 84

Log File Dialog on page 86

Fallback Dialog on page 93

Multiple Match Dialog on page 94

Fallback Dialog

If MapMarker cannot match a record to the level or precision that you have requested (such as street level), it can fall back to use less precise matching criteria. Select the Fallback tab to control these fallback options.

MapMarker 23

93

User Guide

Chapter 3:

Using Geocoding Options

For example, you can fall back to match to the ZIP Code™ centroid, if you have selected the

Fallback to ZIP Code Centroid check box in the Fallback tab. You can also define the fallback to a particular level of ZIP Code. For example, if you only want to accept a ZIP + 4

®

centroid as a fallback match, select ZIP + 4 Centroid Only. By default, MapMarker does not fallback to ZIP centroid.

You can also select Fallback to Geographic Centroid. If MapMarker cannot return a close match based on the Geocode Precision and Must Match criteria, this option falls back to match on a geographic (state, county, or city) centroid.

For related information, see:

Using Geocoding Options on page 83

Geocode Dialog on page 84

Log File Dialog on page 86

Match Settings Dialog on page 88

Multiple Match Dialog on page 94

Multiple Match Dialog

If MapMarker determines that more than one match candidate exists for a record, it follows the instructions in the Multiple Match tab. Multiple match candidates are potentially strong matches, but none of them stands out enough from the others to be considered the definitive match.

Select the Multiple Match tab to control the multiple match options.

MapMarker 23

94

User Guide

Chapter 3:

Saving TAB Files

The

Multiple Match Options

table describes multiple match preferences and how they are used to filter multiple match results. See also,

A Closer Look at Multiple Matches

.

Multiple Match Option

Do Not Match

Accept First

Pick Street Address over ZIP + 4

Pick ZIP + 4 over Street Address

Multiple Match Options

Description

Click this option to disallow any matches for the record if multiple matches occur.

Click this option to accept the first candidate for the match.

Click this option to accept the candidate with the most accurate street level match.

Click this option to accept the candidate with the most accurate ZIP + 4

®

level match.

For related information, see:

Using Geocoding Options on page 83

Geocode Dialog on page 84

Log File Dialog on page 86

Match Settings Dialog on page 88

Fallback Dialog on page 93

Saving TAB Files

When you save a TAB file, MapMarker saves your geocoding settings and stores them as metadata in your table. These settings include columns mappings and geocoding preferences (such as match settings, fallback settings, and CASS™ options). The next time you open the TAB file in MapMarker, you can proceed directly to geocoding. You can view the settings by opening the TAB file in a text editor and examining the section called Metadata.

You can save a TAB file and its associated metadata as a MapMarker project. A project preserves additional settings and preferences and supersedes any settings in the associated TAB file. See

Creating and Saving a Project

.

You can also save a delimited text file and its associated metadata as a MapMarker project.

L

You must use a project to perform batch geocoding of a delimited text file. For more

information on batch geocoding, see

Batch Geocoding

.

MapMarker 23

95

User Guide

Chapter 3:

Creating and Saving a Project

Creating and Saving a Project

After you open an input file and perform column mappings, you can save the file as a project (PROJ file extension). A project preserves the settings used for geocoding a table, including column mappings and geocoding preferences. When you use a project, the project information supersedes the information stored in the table’s metadata.

You can also create a project based on an ODBC input. However, there are limitations on running an

ODBC-based project from a batch file. See the discussion of

Batch Geocoding

.

When you open a project, settings and preferences are restored, including:

• column mappings

• settings on the Geocode dialog (Geocode, Log File, Match Settings, Fallback, and Multiple

Match tabs)

• table attribution settings, if any

• System Preferences on the Dictionary and Offset tabs.

• relevant ODBC file names, locations, and settings

To save a project, first open the input file, perform column mappings, and set geocoding preferences

as you normally would. See

Opening a Table or Text File on page 58

and subsequent topics. Then

follow these steps:

1. From the MapMarker menu, Select File > Projects > Create/Save Project.

2. In the Save Project File As dialog box, type a project name. A PROJ file extension is used.

When you subsequently open the project, settings and preferences are restored. For example, if you had created a project with changes to the default geocode, match settings, fallback, and user dictionary preferences, all of these settings are restored when you open the project.

You can create multiple projects based on the same TAB or text input file. By creating unique projects based on the same input data, you can design, preserve, and manage multiple geocoding strategies customized to suit your needs. For example, you could create a project named

MapMarker 23

96

User Guide

Chapter 3:

Creating and Saving a Project

CustomerStats_Exact.proj that performs geocoding based on the rules and preferences that you specify. You could create another project named CustomerStats_RelaxedMode.proj that geocodes the same TAB file using the Relaxed Mode matching criteria.

L

If you created a project in an earlier version of MapMarker, the project will still be using the older Address Dictionary. If you re-save the project using the same name (overwriting the original project name), the project will then point to the new MapMarker 23 Address

Dictionary. Alternatively, you can edit the DataBasePath entry in the PROJ file to point to the location of the Address Dictionary (by default, <install>\MapMarker_USA_23_Data).

To open and run a previously saved project, see

Opening and Running a Project on page 57

.

You can also run a project from the command line using a project-based batch file. See the following topics:

Creating a Project-Based Batch File on page 97

Creating a Batch Geocoding File from a TAB File

Creating a Project-Based Batch File

After creating a MapMarker project, you can create a batch file to execute the project. Using a project-based batch file is the only way to perform batch geocoding of a CSV or TXT file.

L

For TAB files, you can create a batch file without creating a project. This procedure is

described in

Creating a Batch Geocoding File from a TAB File

. However you can also use

the project-based batch file approach for TAB files.

First create the MapMarker project, as described in

Creating and Saving a Project on page 96

. To create a batch file that executes a MapMarker project, follow these steps:

1. From the MapMarker menu, select File > Create Project-based Batch File.

2. In the Select Project Files dialog, navigate to the directory that contains the project file. Select the project file that you want to run in batch and click Add to move it into the Selected Projects column. You can run multiple projects from the same batch file. See

Multiple Pass Batch

Geocoding Strategy on page 98

.

MapMarker 23

97

User Guide

Chapter 3:

Creating and Saving a Project

3. Click OK to open the Save Batch File As dialog. Use the Save in drop-down selection to navigate to the directory where you want to save the batch file. Accept the default file name or change the name of the BAT file. Click Save.

A project-based batch file points to the MapMarker executable and runs the project file. The location of the input file, names of columns, and geocoding preferences are encapsulated in the project

(PROJ) file itself. A project-based batch file might appear as follows:

"C:\Program Files\MapInfo\MapMarker_USA_v23\desktop\mapmarkr.exe"

/Proj=C:\Documents and Settings\Administrator\My Documents\MapMarker

USA\Projects\1k_out_spat_ExactMatch.proj

Multiple Pass Batch Geocoding Strategy

You can run multiple projects from the same batch file. The projects listed in the batch file are executed in succession. These projects could be based on different input files. For example, the batch file could perform a geocoding pass on California-based addresses then run subsequent passes on Arizona-based addresses, etc.

For a project based on TAB file, a batch file can also run multiple geocoding passes on the same

TAB file. For example, the batch file could run the "Exact" match project on a Quebec addresses

TAB file followed by a "Relaxed" match project on the same Quebec addresses TAB file. This strategy allows you to perform batch geocoding based on precise Must Match criteria, then perform a less restrictive second pass on addresses that did not geocode during the first pass.

There is one important guideline for using this strategy on TAB files. While the Exact match project would typically geocode all records (All Types in the Geocode dialog), the Relaxed match project should geocode Unmatched Rows only. This ensures that the output from the Relaxed match geocoding pass does not overwrite the output from the initial Exact match pass.

For a project based on a delimited or text file (CSV or TXT), you cannot do multiple batch geocoding passes of the same address file because the initial output file will be overwritten. That is, a

Quebec_Address_out.csv file created by the Relaxed match batch geocoding pass will overwrite the identically named output file created by the Exact match pass. Therefore, project-based batch files that use CSV or TXT files should specify different input files (for example, address files from different provinces).

MapMarker 23

98

User Guide

MapMarker System

Preferences

This chapter discusses the system preferences that allow you to customize

MapMarker.

In this chapter:

Š

Setting System Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Š

Startup Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Š

Dictionary Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Š

Offset System Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Š

Maps System Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

4

Chapter 4:

Setting System Preferences

Setting System Preferences

The System Preferences dialog is displayed when you click System Preferences on the Options menu. Click , or click the right mouse button to display a shortcut menu and then click System

Preferences. The System Preferences dialog contains the tabs: Startup, Dictionary, Offset, and

Maps.

Any changes you make in these tabs are written to the Windows Registry at

HKEY_LOCAL_MACHINE\SOFTWARE\MAPINFO\MAPMARKER\USA\<version number>\SYSTEM

These changes are also saved for future geocoding sessions.

L

In the MapMarker registry keys, <version number> indicates the major-release version of

MapMarker, for example, 23.0, even if you are running one of the point releases of that version.

Startup Preferences

The Startup tab identifies the settings MapMarker uses when you start the application. You can select any and all check boxes in the tab. If you select either Show MapInfo or dBASE files or

Show for ODBC tables, the Open dialog is displayed automatically when you start MapMarker. If you check both boxes, MapMarker prompts you with another dialog at startup to choose which type of table you want to open.

MapMarker 23

100

User Guide

The Startup System Preferences appear as follows:

Chapter 4:

Dictionary Preferences

You can also control which of the System Preference dialogs, if any, display on startup.

Choose from:

• Show Select Column Dialog On Open (selected by default)

• Select Attribute Files After Selecting Columns

• Show Geocode Dialog After Selecting Columns (selected by default)

• Show Add Georesult, Longitude/Latitude Columns Dialog (selected by default)

The settings are saved to the table as metadata and used as new defaults when you open the table again.

Dictionary Preferences

The Address Dictionary group identifies the path(s) of all installed address dictionaries. The Address

Dictionary covers all of USA or individual provinces, depending on what you purchased and installed. You can add additional paths to the list at any time by separating each path with a semicolon. You do not need to specify the file name.

A user dictionary is a custom dictionary that you have created from your own data or data that you purchased from a third party. A custom user dictionary can contain address point data for the area that you are geocoding, and this can give you more accurate results than the standard address dictionary. In order to geocode with a user dictionary, you must specify the path. For complete

information on user dictionaries, see

Custom User Dictionaries

.

MapMarker 23

101

User Guide

The Dictionary Preferences appear as follows:

Chapter 4:

Offset System Preferences

You can also specify customized dictionaries that contain street addresses that are not included in the purchased Address Dictionary. To use a customized dictionary, select the check box marked Use

User Dictionary and type the path or browse to its location. You can geocode using both the

MapMarker Address Dictionary and a customized dictionary.

To use a customized dictionary, select the check box marked Use User Dictionary and type the path or browse to its location. Check both boxes if you want to geocode using both the MapMarker

Address Dictionary and a customized dictionary.

When both the Address and the user dictionaries return a close match, the Address dictionary takes precedence by default. To give precedence to user dictionary, see

Preferring User Dictionary

Matches

.

The Use Address Point Interpolation check box enables address point interpolation during geocoding. This technique allows MapMarker to accurately interpolate points along a street segment in relation to address point candidates that are found on that segment. This process increases the positional accuracy of the geocoded points.

Offset System Preferences

These Street Offset values specify the distance that geocoded points are offset from the original interpolated points.

MapMarker 23

102

User Guide

Chapter 4:

Offset System Preferences

When changing the units of the offset distance, be sure to also type the appropriate offset distance values, since changing the units does not automatically recalculate the offset values.

The Offset Preferences dialog allows you to control the offset preferences.

Street Offsets In the Street Offsets group, the Offset From Road and Offset From Corner selections specify the distance that interpolated points are offset from the street corner and from the street segment, respectively. You can specify the offset in feet, meters, or other common units. The default is 25 feet.

Center Line Offset The Use Center Line Offset selection specifies the distance that geocoded points are offset from the associated street segment (rather than being placed exactly at the original point). Center Line Offset is available if you are geocoding with a point-based Address Dictionary.

Where possible, the coordinates are offset perpendicularly from the segment. Center Line Offset is disabled by default but you can enable it and specify the offset distance and units. The default is 25 feet.

When changing any of the offset units (for example, from feet to meters), be sure to also enter the appropriate offset distance values, since changing the units does not automatically recalculate the offset values.

MapMarker 23

103

User Guide

Chapter 4:

Maps System Preferences

Maps System Preferences

In order to display match candidates in a Map window from the Interactive or Quick Find dialog boxes, MapMarker must know where the street data is located on your system. The Maps tab on the

System Preferences dialog allows you to set the directory path to the street data.

L

If you do not specify a valid location of the street data, the Map and Range buttons on the

Interactive or Quick Find dialog boxes will be disabled.

The Map System Preferences are displayed and selected as follows:

This also enables you to set an initial display radius for the Candidate Visualization Map window.

The radius is the distance in miles around the first match candidate that MapMarker finds among multiple matches when you geocode interactively. Set this distance in the Maximum Candidate Map

Zoom Distance field. The default value is five miles. You can set the distance from 1–99 miles. Use the zoom in and zoom out tools in the Candidate Visualization Map window to control the view of the map, and choose how much data you want to view in the Map window.

For best results when geocoding with MapMarker, use MapMarker Streets or StreetPro Enhanced as the background street map. These street packages are geographically consistent with the street data in the MapMarker Address Dictionary.

For information on how to quickly visualize candidates on a map, see

Viewing Match Candidates on a Map

. For information on visualizing candidates from the Quick Find dialog box, see

Finding

Candidates Using Quick Find

MapMarker 23

104

User Guide

Match Settings and

Strategies

In this chapter:

Š

Using Match Settings to Control Geocoding Precision . . . . . . .106

Š

Choosing Match Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Š

Picking Your Strategy: An Example . . . . . . . . . . . . . . . . . . . . . . .108

Š

Impact of Relaxing Match Conditions . . . . . . . . . . . . . . . . . . . . .109

Š

Viewing Match Candidates on a Map . . . . . . . . . . . . . . . . . . . . . . 111

5

Chapter 5:

Using Match Settings to Control Geocoding Precision

Using Match Settings to Control Geocoding Precision

The Geocode dialog includes tabs that allow you to control the Match Settings, Fallback, and

Multiple Match settings for a geocoding pass. This is where you set MapMarker to be as strict or relaxed as you need by selecting or clearing the appropriate check boxes.

Each of the settings affect the match rate, performance, and the positional accuracy of the geocoded

point. You must decide the settings that best fit you strategy and needs. See

Choosing Match

Strategies

.

Default Settings The default settings, which generally give you the best compromise among match rate, accuracy, and performance, are:

•

Require an exact match for house number only. See

Match Settings Dialog

.

• Do not fall back to ZIP Code centroid matching. Uncheck the setting in the Fallback dialog. See

Fallback Dialog

.

• Do not match if there are multiple match candidates. Uncheck the setting in Multiple Match dialog. See

Multiple Match Dialog

.

Choosing Match Strategies

You can use several matching strategies, including:

•

Maximizing the Match Rate on page 106

•

Maximizing Geographic Accuracy on page 107

•

Balancing Match Rate and False Positives on page 107

You can choose one method or use them in combination.

Maximizing the Match Rate

To generate the highest match rate possible, relax the match restrictions on house number, ZIP

Code, and street names in the Match Settings tab by unchecking those boxes. In addition, select

Accept First (Multiple Match tab) and Fallback to ZIP Centroid (Fallback tab). Relaxing the matching conditions tells MapMarker to broaden the area in which it searches for a match. For example, by relaxing the ZIP Code, MapMarker searches for candidates outside the ZIP Code but within the city of your input address.

To maximize the potential for a match, tell MapMarker what to do if it does not find a match. These settings include Fallback to ZIP Code matching and match to the first of multiple matches. See

Fallback Dialog

and

Multiple Match Dialog

.

MapMarker 23

106

User Guide

Chapter 5:

Choosing Match Strategies

While this strategy likely yields false positives, this may be the best match solution when you have large databases that need to be geocoded. You must decide if the percentage of false positives affects your analysis.

L

You can evaluate false positives if you have MapMarker use output columns to store the

returned street, city, state, and ZIP Code values. See

Selecting Input and Output Address

Columns

. Look for false positives by comparing the input address with the output address.

To further reduce the number of false positives without sacrificing hit rate, analyze the result codes after a geocoding session and re-geocode interactively. See

Result Codes

for more information on result codes.

Maximizing Geographic Accuracy

If positional accuracy of the geocoded records is the most important aspect for you, choose a strategy in which MapMarker returns the lowest number of erroneous matches. To do this, you must require MapMarker to find exact matches for all portions of the address—house number, street name, city, and ZIP Code™. Also, do not accept the first of multiple matches or fall back to ZIP

® centroid. These records remain ungeocoded.

The strictest matching conditions require an exact match on house number, street name, city name, and ZIP Code. In that case, MapMarker is looking for an exact street address match within the city and ZIP Code named in your input address.

Choose this scenario when your analysis requires precise locations for your records. To increase the number of matches, your next step might be to use interactive geocoding. Interactive geocoding is explained in

Making the Most of Interactive Geocoding

.

Balancing Match Rate and False Positives

You may want to use a balanced strategy between match rate and geographic accuracy. That is, you may want to geocode as many records as possible automatically, but at the same time want to minimize the number of erroneous matches (false positives). Rather than generate false positives, you could leave those records ungeocoded so that you can geocode them interactively later. You may want to analyze your data at a local level where the location of each record on a map is important.

MapMarker returns false positives when it

• Finds a street that sounds like the input street.

• Finds the same street in another town (if ZIP Code is relaxed).

• Finds the street but with a different house number (if House Number is relaxed).

MapMarker, however, contains a sophisticated matcher that usually finds the correct address.

MapMarker 23

107

User Guide

Chapter 5:

Picking Your Strategy: An Example

MapMarker default settings reflect this balanced strategy—exact match is required for house number, but is relaxed for street name and ZIP Code.

L

P.O Box and rural route addresses are automatically geocoded to the ZIP Code centroid. You do not need to set any conditions specific to these addresses.

Picking Your Strategy: An Example

The following scenario outlines a three-pass geocoding session based on the strategy of maximizing

the match rate. See

Maximizing the Match Rate on page 106

for an overview of that strategy. You

want to generate the highest match rate for a large database while minimizing false positives. The goal during the session is to set the conditions for that strategy in the first pass, then follow with an interactive session to pick up additional matches, and finally, a third pass to ZIP Code centroids to geocode any remaining records.

First Pass on page 108

Second Pass on page 108

Third Pass on page 109

One Pass Settings on page 109

First Pass

Geocode the table automatically with the settings that generate the highest match rate with the fewest false positives:

• Require exact match on House Number, relax Street Name, and ZIP Code (default settings).

For even stricter matching, also require exact match on street name and ZIP Code™.

• Do not accept first of multiple matches.

• Do not fallback to ZIP Code centroid matching.

All records geocoded during this pass are exact or close matches that geocode to the street level.

Depending on the cleanliness of your data, the majority of your table is processed during this pass.

This pass generates the least number of false positive matches.

Second Pass

For this pass, geocode all unmatched rows interactively with the following settings:

• Relax the settings for house number, street name, and ZIP Code.

• Do not accept first of multiple matches.

• Do not fallback to ZIP Code centroid matching.

• Edit the input address where necessary to increase the likelihood of a match.

Each match in this pass is still at street level accuracy. Since you are in interactive mode, you control every match, thus, minimizing the number of false positives.

MapMarker 23

108

User Guide

Chapter 5:

Impact of Relaxing Match Conditions

You can also change the match settings, expand the Search, map the match candidates, and edit the record to find additional matches.

Third Pass

Do a final geocoding pass on unmatched rows by geocoding to ZIP Centroid. Set the geocoding precision in the Geocode dialog to To ZIP Centroid.

This pass picks up virtually all remaining records and geocodes them to ZIP Code centroid accuracy.

If your data includes ZIP + 4

® information, some of these ZIP Code centroid matches could geocode to the street level in as nearly the same location as unique and close street matches from the first pass.

One Pass Settings

If you do not want to geocode your table interactively, combine the first and third passes using the following settings in the Options dialog:

• Require exact match on House Number, relax Street Name, and ZIP Code.

• Do not accept first of multiple matches.

• Select Fallback to ZIP Centroids.

Impact of Relaxing Match Conditions

Consider the following when you change the Match Settings in the Geocode dialog.

See

Match Settings Dialog

for a detailed description of the choices in this dialog.

See the following topics:

Relaxing ZIP Codes on page 109

Relaxing City Name on page 110

Relaxing Street Name on page 110

Relaxing House Number on page 110

Matching to Street Intersections on page 1107

Geocoding to ZIP Centroids versus Falling Back to ZIP Centroid on page 110

Preferring User Dictionary Matches on page 110

Relaxing ZIP Codes

When ZIP Codes are relaxed, MapMarker searches a wider area for a match. While this causes slower performance, the match rate is higher because MapMarker does not need to match exactly when it compares match candidates.

MapMarker 23

109

User Guide

Chapter 5:

Impact of Relaxing Match Conditions

Relaxing City Name

When city names are relaxed, MapMarker searches on the street address matched to the particular

ZIP Code, and considers other cities that do not match the city name, but do match the ZIP Code.

Relaxing Street Name

MapMarker looks at all candidates with names that sound like the input address. This slows down performance. However, since more candidates are examined, the match rate increases. If your table is indexed, the time difference between performance and match rate is reduced.

Relaxing House Number

Performance is not significantly affected when the house number setting is relaxed. It does, however, affect the type of match if the candidate address corresponds to a TIGER segment that does not contain any ranges. The type of match can also be affected when the house number range for a candidate does not contain the input house number.

Matching to Street Intersections

For MapMarker to recognize street intersections, your table must be set up in either of the following ways:

• Address1 and Address2 must be contained in the same field separated by any of the following intersection tokens: “and”, “at”, “&”, “&&”.

• Address1 and Address2 are in separate fields, but the Use Address2 as Intersection Cross

Street check box must be selected in the Select input columns from your table dialog.

L

Intersection matching does require increased processing time.

Geocoding to ZIP Centroids versus Falling Back to ZIP Centroid

When MapMarker matches to ZIP centroid it looks only at the ZIP Code™ in the input address. If your data has a 5-digit ZIP Code, MapMarker can only match to the 5-digit ZIP centroid.

If, on the other hand, you geocoded the same record at street level with a fallback to ZIP centroid,

MapMarker takes into account both the 5-digit ZIP Code and street name and is more likely to match it to a more precise location than the 5-digit ZIP centroid.

Preferring User Dictionary Matches

If you select Prefer User Dictionary Matches on the Match Settings tab, candidates from the User

Dictionary are given a higher score than a similar candidate from the Address Dictionary. This preference is designed for situations where you feel your User Dictionary is superior to the

MapMarker Address Dictionary. This selection is available only if a User Dictionary has been specified. See

Dictionary Preferences

.

MapMarker 23

110

User Guide

Chapter 5:

Viewing Match Candidates on a Map

Viewing Match Candidates on a Map

Candidate visualization allows you to see where potential matches fall on a map to help you determine the best match for your address. You can display match candidates in relation to a street network, using the appropriate Pitney Bowes Business Insight products. If you geocode your table with MapMarker 23, you can display the records with MapMarker Streets or StreetPro Enhanced products.

Candidate visualization is accessible via the Map button in the Interactive Geocode and Quick Find dialog boxes.

Setting the Street Data Path

Before mapping your candidates, specify the location of your street data in the Map tab of the

System Preferences dialog (Options > System Preferences). You can also control which layers you want displayed in the map. See

Maps System Preferences

.

L

If you did not previously specify a valid location of the street data, the Map button on the

Interactive or Quick Find dialog boxes will be disabled.

Viewing Match Candidates With Interactive Geocoding

Use candidate visualization with interactive geocoding to select the point on the map that represents your match choice. MapMarker geocodes to that record.

To view potential matches on a map during interactive geocoding:

1. From the Interactive dialog box, proceed through the table until you reach a record with a list of match candidates that you want to view on a map.

2. Click Map. MapMarker creates a map view of all match candidates in the list. Each candidate is displayed with the color representing match type.

For example, green stars are candidates that match to the street address (S5) and yellow stars are those that match to the ZIP + 4

®

centroid (S3 or Z3). See

Displaying Geocoded Records in MapInfo Professional

for more information on these symbols.

3. Use the tools provided to pan, zoom, and label the map to help you decide the best match candidate for the address. The label tool allows you to label nearby streets and features to provide a geographic reference for the candidates.

4. When you decide the best match, click the candidate symbol with the Select tool and click OK.

You are returned to the Interactive dialog box. Your choice is highlighted in the candidate list.

5. Click Geocode if you want to geocode the selected candidate.

L

You can also use candidate visualization as part of the Quick Find feature. See

Finding

Candidates Using Quick Find

for a description of this.

MapMarker 23

111

User Guide

Chapter 5:

A Closer Look at Multiple Matches

A Closer Look at Multiple Matches

A multiple match is when MapMarker finds more than one record in the Address Dictionary that covers the same address range. Multiple match candidates are potentially strong matches, but none of them stands out enough from the others to be considered the definitive match. You can control how you want MapMarker to respond when it encounters a multiple match.

Select the Multiple Match tab to control the multiple match options.

The

Multiple Match Options

table describes multiple match preferences and how they are used to filter multiple match results.

Multiple Match Option

Do Not Match

Accept First

Multiple Match Options

Description

Click this option to disallow any matches for the record if multiple matches occur. During interactive geocoding,

MapMarker stops at that record and waits for your response. Sometimes it finds multiple matches, even though there is a candidate that appears to be an exact match. In this situation, it is important to examine the ranges associated with the candidate to make the best judgement about whether to match to the candidate.

Click this option to accept the first candidate for the match.

MapMarker 23

112

User Guide

Chapter 5:

A Closer Look at Multiple Matches

Multiple Match Option

Pick Street Address over Postal

Multiple Match Options

Description

Pick Postal over Street Address

Click this option to accept the candidate with the most accurate street level match.

Click this option to accept the candidate with the most accurate postal code level match.

Consider the following example.

MapMarker determined that there are multiple matches for 981 Howard St. in San Francisco, even though it appears one candidate matches the record. By clicking Ranges and scrolling through the list of ranges, you see that there are four address ranges shown that cover 981

Howard St.

Because the multiple match setting is set to Do Not Match, MapMarker stops geocoding at this point and waits for you to choose the match or ignore it. By clicking Geocode in this example,

MapMarker generates an S result code, which means a single close match was made.

If the restriction had been set to one of the other choices in the Multiple Match tab, this record would not appear in the Interactive dialog because MapMarker would geocode it automatically. If the setting was Accept First, Pick Street Address over ZIP + 4, or Pick ZIP + 4 over Street

Address, the result code would be an M result. For more on result codes, see

Understanding

Result Codes

.

MapMarker 23

113

User Guide

Result Codes

In this chapter:

Š

Understanding Result Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Š

Single Match (S category) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Š

Best Match From Multiple Candidates (M category). . . . . . . . . .119

Š

Postal Centroid Matches (Z category) . . . . . . . . . . . . . . . . . . . . .120

Š

Geographic Matches (G category) . . . . . . . . . . . . . . . . . . . . . . . .120

Š

Non-match Codes (N category). . . . . . . . . . . . . . . . . . . . . . . . . . .120

Š

Using the Georesult Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

6

Chapter 6: Result Codes

Understanding Result Codes

Understanding Result Codes

As an output option, MapMarker returns a georesult code for every record it attempts to match. The code indicates the success or failure of the geocoding operation and conveys information about the quality of the match. Each character of the code indicates the level of precision of each address component matched.

The result codes are written to a result column specified in the Select Output Columns dialog at the beginning of the geocoding process. You can either create this column before geocoding or have

MapMarker create it automatically (default name Georesult) when you open your table.

The result code is an alphanumeric code of 1–10 characters. The codes fall into the following categories:

• Single unique match

• Best match from multiple candidates

• ZIP Code centroid match

• Geographic match

• Non-match

The match precision depends on the match settings that you choose. See

Match Settings and

Strategies in Chapter 5 on page 105

. Match precision also depends on the quality of the input

address data and on the quality of the Address or User Dictionary.

Each category is explained in the following topics.

Single Match (S category) on page 116

Best Match From Multiple Candidates (M category) on page 119

Postal Centroid Matches (Z category) on page 120

Geographic Matches (G category) on page 120

Non-match Codes (N category) on page 120

Using the Georesult Dialog on page 121

MapMarker 23

115

User Guide

Chapter 6: Result Codes

Single Match (S category)

Single Match (S category)

Matches in the S category indicate that the record was matched to a single address candidate. The first character (S) reflects that MapMarker found a street address that matches your record.

Within this category, a number of precision levels have been defined. The precision affects the location of the geocoded point on the map. An address matched to a street address position has greater positional accuracy than one matched to a ZIP Code™ centroid.

Matches in the S category can have the following types of precision:

• Address point – Using address point interpolation, address is matched to an address point position, or match is interpolated against a nearby address point candidate to arrive at a position along the street segment. Address point interpolation places geocoded points more accurately along the street segment and can prevent the “bunching” of points that can occur at either end of

a street segment. See

Dictionary Preferences

for information on address point interpolation.

• Street – Address is matched to a street address position.

• ZIP– Address is matched to a ZIP Code centroid or point ZIP centroid position.

Each of the S codes is defined below. The second position in the code reflects the positional accuracy of the resulting point for the geocoded record, as indicated below.

• S1 – single match, point located at ZIP Code centroid. This is the same quality match as a Z1 result.

• S2 – single match, point located at ZIP + 2 centroid. This is the same quality match as a Z2 result.

• S3 – single match, point located at ZIP + 4

®

. This is the same quality match as a Z3 result.

• S4 – single match, point located at a street centroid.

• S5 – single match, point located at a street address position. Because only street segment data is available, the interpolation is not as accurate as an S7 return. See also

Interpreting S5

Result Codes on page 118

.

• S6 – single match, point located at point ZIP centroid. See also

Interpreting S6 Result Codes on page 118

. This is the same quality match as a Z6 result.

• S7 – single match, located at an interpolated point along a street segment. Both a point/parcel dictionary and a street segment dictionary must be available. Because known point data is available, the S7 interpolation is more accurate than an S5 result. See

Interpreting S7 Result

Codes on page 118

.

• S8 – single match, point located at either the single point associated with an address point candidate or at an address point candidate that shares the same house number. No interpolation

is required. See also

Interpreting S8 Result Codes on page 117

.

• SX – single match, point located at street intersection.

• S0 – single match, no coordinates available (very rare occurrence).

• SC – Single close match where the original point has been moved a specified distance (usually along a perpendicular line) toward or away from the associated street segment. This result code can be returned only when both a point/parcel dictionary and a street segment dictionary are available and when the centerline offset feature is used.

See the table of

Geocoding Result Codes Related to Census Block Information

for more information on the S Return Codes.

For more information on how a close match is determined, see

Match Settings and Strategies

.

MapMarker 23

116

User Guide

Chapter 6: Result Codes

Single Match (S category)

See the following topics:

Interpreting Complete S and M Result Codes on page 117

Interpreting S8 Result Codes on page 117

Interpreting S7 Result Codes on page 118

Interpreting S6 Result Codes on page 118

Interpreting S5 Result Codes on page 118

S and Z Result Codes: What is the Difference? on page 119

Interpreting Complete S and M Result Codes

For S category result codes, eight additional characters describe how closely the address in your table matches an address in the Address Dictionary. The characters appear in the order listed in the following table. Any non-matched components are represented by a dash.

T

S

P

N

C

Z

H

Result Code

Component

A or U

House Number

Description

Street Prefix

Street Name

Street Type

Street Suffix

City Name

ZIP Code

Address Dictionary or User Dictionary

Example

110

North

Fletcher

Place

SE

Boulder

80303

A

For example, the result code S5- -N-SCZA is for a single close match that matched the street name, street suffix direction, city and ZIP Code™ exactly, but could not match the house number, street prefix direction, or the street type. The match came from the MapMarker Address Dictionary. This record would be geocoded to the street address position of the match candidate.

M category result codes follow the same pattern, and are described in

Best Match From Multiple

Candidates (M category) on page 119

.

Interpreting S8 Result Codes

S8 results are matched to either the single point associated with an address point candidate, or to an address point candidate that shares the same house number. An S8 result can return a complete

15-character Census Block ID.

MapMarker 23

117

User Guide

Chapter 6: Result Codes

Single Match (S category)

An S8 georesult indicates that the address candidate is a point. No interpolation is required, so S8 result codes are returned regardless of whether address point interpolation is enabled.

Interpreting S7 Result Codes

S7 results are matched to an interpolated point along the candidate’s street segment. An S7 result can return a complete 15-character Census Block ID. You must enable address point interpolation to generate S7 result codes.

Both a point/parcel dictionary and a street segment dictionary must be available. An S7 candidate is not located exactly at a known point (that is, there is no exact house number match). However, because both point and segment data is available, the interpolation along the street segment can be very accurate.

The geocoded candidate location is interpolated based on the nearest point candidates on the street segment. By using known address reference points on the street segment, the S7 interpolated point can be more accurate than an S5 result.

Interpreting S6 Result Codes

An S6 code is returned from geocoding when the candidate is matched to a point ZIP centroid. A point ZIP is a 5-digit ZIP Code that represents unique ZIPs such as a single site, building, or organization. Point ZIPs do not cover an area, so they are shown as dots on a map rather than polygons, and have no geographic extent defined in terms of street segments. Because these points show actual locations, a different result code is used to distinguish them from other ZIP Centroid matches.

Interpreting S5 Result Codes

S5 results are matched to an interpolated point along a street segment. This can return a complete

15-character Census Block ID.

An S5 result is based on a street segment dictionary only. This interpolation is not a accurate as an

S7 result, which can use point data to interpolate more accurately.

If you receive an S5 match for a record that was geocoded to an unexpected place, analyze the result code to determine why. This situation can occur during a geocoding pass where the match conditions are relaxed; that is, you did not require an exact match on house number, street name, and/or ZIP Code. When MapMarker attempts to geocode the record with those settings, it searches larger areas than it would if the conditions were stricter. Under those conditions, it is possible to match the record to a distant address that has a similar name.

For example, a typical result might look like this: S5-P--S--A. The missing components in the result code are represented by dashes. Even though MapMarker returned an S5 (it found a single match to a street address), it did not match the house number (H), street name (N), street type (T), city (C), or

ZIP Code (Z). To minimize the matches that geocode to incorrect locations, geocode your table with stricter matching conditions.

MapMarker 23

118

User Guide

Chapter 6: Result Codes

Best Match From Multiple Candidates (M category)

For the greatest matching accuracy, you can use CASS™ geocoding as explained in

CASS

Geocoding

. Alternatively, you can use a parcel level dictionary to generate highly-accurate S8 single-point geocode matches.

L

You cannot use ParcelPrecision dictionaries (or any user dictionary) in combination with

CASS geocoding.

S and Z Result Codes: What is the Difference?

An S3 match is defined as a single close match with the point located at the ZIP + 4

®

centroid. The

Z3 match is also geocoded to the ZIP + 4 centroid. The S3 and Z3 result codes indicate the identical postal centroid. There is no difference in the accuracy of S3 and Z3 matches. The only difference is how MapMarker arrives at the results.

For the S3 record, MapMarker found a street address that matches, but the match record did not contain any street geometry information. MapMarker is, therefore, unable to interpolate where along the segment to place the record. The best it can do is to geocode to the ZIP + 4 centroid.

A Z3 match is a direct match to the ZIP + 4 centroid. MapMarker could not find a street address match for one of several reasons: 1) you chose to geocode to the postal level; 2) there was no close street level match and you chose postal fallback; or 3) the address is a P.O. Box or rural route.

Similarly, S2/Z2 (ZIP + 2 matches) and S1/Z1 (5-digit ZIP Code matches) indicate the identical postal centroids. There is no difference in the accuracy of these S and Z matches.

Best Match From Multiple Candidates (M category)

Matches in the M category indicate that there is more than one match candidate for the record and

MapMarker has chosen the best one of those candidates. This category is used when you select

Accept First, Pick Street Address over ZIP + 4, or Pick ZIP + 4 over Street Address in the

Multiple Match tab and MapMarker finds more than one strong match candidate. As in the S category, the second position in the code of M category matches the positional accuracy of the resulting point object.

L

M category matches can be returned for the Desktop Application only.

• M1 – multiple matches, point located at ZIP Code centroid

• M2 – multiple matches, point located at ZIP + 2 centroid

• M3 – multiple matches, point located at ZIP + 4

®

centroid

• M4 – multiple matches, point located at the center of a shape point path (shape points define the shape of the street polyline)

• M5 – multiple matches, point located at a street address position (highest accuracy available)

• M6 – multiple matches, point located at point ZIP location

• MX – multiple matches, point located at street intersection

MapMarker 23

119

User Guide

• M0 – multiple matches, no coordinates available

See

A Closer Look at Multiple Matches on page 112

.

Chapter 6: Result Codes

Postal Centroid Matches (Z category)

Postal Centroid Matches (Z category)

Matches in the Z category indicate that no street match was made, either: 1) because there is no close match and you allowed MapMarker to fall back to ZIP

®

Centroid; 2) the address is a P.O. Box or rural address; or 3) you set MapMarker to match to ZIP Centroids. The resulting point is located at the ZIP Code™ centroid with five possible accuracy levels.

• Z1 – ZIP Code (5-digit) centroid match

• Z2 – ZIP + 2 centroid match

• Z3 – ZIP + 4 centroid match (highest accuracy available for Z matches)

• Z0 – ZIP Code match, no coordinates available (very rare)

• Z6 – ZIP Code centroid match for point ZIP

A Z6 code is returned when the candidate is matched to a point ZIP centroid. Point ZIPs are 5-digit

ZIP Codes that are points on a map rather than a polygon. Point ZIPs include unique ZIPs (single site, building, or organization). Instead of returning a Z1 result code, the Z6 code indicates that these special ZIPs are actual point locations, not an area.

Geographic Matches (G category)

Matches in the G category indicate that a match was made at the state, county, or city level.

• G1 – State match, point located at the state centroid.

• G2 – County match, point located at the county centroid.

• G3 – City match, point located at the city centroid. A number of prominent U.S cities can be matched even if no other information is provided. For example, if you provide Chicago (city) but no state, the record is matched to Chicago, IL.

Non-match Codes (N category)

The following result codes indicate no match was made:

• N – No close match. These records can be re-geocoded interactively or during subsequent automatic passes under different matching conditions.

• NX – No close match for street intersections.

• ND – MapMarker could not find the Address Dictionary for the given ZIP Code or city/state.

These records can be re-generated once the Address Dictionary is available. An ND code can also appear in the fields of Zip + 4

®

output columns. For example, MapMarker can return

12180-23ND. In this case, the ND code is ZIP + 4 Codes associated with nondelivery areas such as vacant lots or other areas to which the US Postal Service does not deliver mail.

MapMarker 23

120

User Guide

Chapter 6: Result Codes

Using the Georesult Dialog

• NG – The user marks these records during interactive geocoding as non-geocodable.

MapMarker does not attempt to match these records again until the code is removed.

Using the Georesult Dialog

Successfully geocoded addresses will have a have a code in the Georesult column of the geocoded

table. See

Understanding Result Codes on page 115

for an example.

To view details of the result codes for each record, double-click the code in the Georesult column.

The Georesult dialog provides detailed information on the selected record, including the address,

ZIP Code, result code, match type, and match details for each address component.

If you leave the Georesult dialog open, you can continue to double-click on result codes in your table and the detailed result code information for that record appears.

MapMarker 23

121

User Guide

Specialized Geocoding

Features

This chapter covers a number of specialized MapMarker features, including

CASS™ processing, DPV

®

, LACS

Link®

, ZIP

®

centroid geocoding, Quick

Geocoding, Quick Find, Locate Airport, Locate Highway Exit, batch geocoding, and table attribution.

In this chapter:

Š

CASS Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Š

LACSLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Š

DPV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129

Š

SuiteLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

Š

Returning Abbreviated Addresses . . . . . . . . . . . . . . . . . . . . . . . .138

Š

Returning Abbreviated City Names . . . . . . . . . . . . . . . . . . . . . . .139

Š

Geocoding Dual Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

Š

Geocoding dBASE Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Š

Using Quick Geocode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Š

Finding Address with Quick Find . . . . . . . . . . . . . . . . . . . . . . . . .143

Š

Finding Airports with Locate Airport . . . . . . . . . . . . . . . . . . . . . .151

Š

Finding Highway Exits with Locate Highway Exit . . . . . . . . . . . .152

Š

Batch Geocoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Š

Table Attribution with MapMarker. . . . . . . . . . . . . . . . . . . . . . . . .157

7

Chapter 7:

CASS Geocoding

CASS Geocoding

The Coding Accuracy Support System (CASS™) is the USPS

®

certification process for ZIP + 4

® matching software by which a table of mailing addresses is standardized to meet USPS requirements for bulk mailing discounts. MapMarker standardizes addresses under strict matching conditions set by the USPS

®

while it geocodes your records.

L

You cannot geocode your records with a user dictionary during CASS geocoding. This also means that the ParcelPrecision dictionary cannot be used during CASS geocoding.

To geocode your data to CASS standards and obtain the bulk mailing discount, a number of output columns are required, and you must produce a CASS report. You must also have the current revision of the MapMarker Address Dictionary available to comply with CASS address standardization.

MapMarker ships regular data updates to comply with CASS™ requirements and DPV

®

. The CASS expiration dates for your version of MapMarker USA are covered in your product Release Notes.

DPV is closely tied to the currentness of the CASS data. The CASS ZIP + 4

®

data is synchronized with DPV updates to ensure that both are valid for the full 105-day period of the quarter.

MapMarker 23

123

User Guide

Chapter 7:

CASS Geocoding

The following columns are required for generating CASS report. For a complete list of output columns (including type and width requirements) see

Output Column Type/Width Requirements

.

CASS Report Required Fields

• Firm

• Address

• Address2

• City

• State

• ZIP

• ZIP + 4

• URB – (This field is used to store urbanization codes for Puerto Rican addresses. You must have this field even if you do not have Puerto Rican addresses.)

• Delivery Point

• Check Digit

• LACS

• Carr. Route

• DefaultFlag

• PMB

• PMB Range

• EWS Flag

• RecordType

• DPV ConfCode

• DPV Cmra

• DPV falsePos

• DPV FtNote1

• DPV FtNote2

• DPV FtNote3

• DPV Vacant

• DPV NoStat

• LACS Indicator

• LACS

Link

Code

MapMarker 23

124

User Guide

Chapter 7:

CASS Geocoding

CASS Report Optional Fields

• Latitude – Float or Decimal (10,6)

• Longitude – Float or Decimal (11,6)

• Census – Character(15)

• EWS Flag – Character(1)

• County

• SuiteLink Code

Geocoding in CASS Mode

To geocode in CASS™ mode, do the following:

1. Start MapMarker.

2. Open the table you want to geocode. Proceed through the Select Column dialogs.

3. On the Geocode dialog box, select the Match Settings tab.

4. In the Match Settings group, select the CASS Match Mode.

5. Select the CASS option that you want to use.

6. To produce a U.S. Postal Service

®

Form 3553 CASS Report, select the Produce a CASS

Report check box. You are prompted for a name and location for the report at the Save CASS

Report As dialog.

MapMarker 23

125

User Guide

Chapter 7:

LACS

Link

7. Click Geocode to begin geocoding.

MapMarker geocodes your data while CASS processing and provides a printed report of the address standardization operation.

You can geocode using the CASS standards for any table, local or remote, without producing a report or conforming closely to the output columns. In this case, you do not qualify for the bulk mailing discount, but you are still geocoding your records to stricter matching standards.

LACS

Link

LACS

Link®

is a data product provided by the USPS

®

that enables addresses that have been converted because of municipality changes or 911 emergency systems to be linked with their updated addresses. The LACS

Link

database provided by the USPS contains a nationwide list of converted addresses.

The LACS

Link

technology and data have been added into MapMarker for use when you geocode in

CASS mode. LACS

Link

processing enables you to check your addresses against the LACS

Link database, and receive the converted address for any input address that has been converted. Most address conversions are the result of changes by the local governments that convert rural style addresses to street-style addresses for 911 conversions. Other addresses are converted because of changes to street names or P.O. Box™ renumbering.

Although you run LACS

Link

when you do CASS™ mode geocoding, it is a separate process from geocoding. LACS

Link

is an address standardization tool only. Records that undergo LACS

Link processing are not geocoded. The converted address is returned in the candidate list, but no coordinates are returned with it. These records have an S0 result code. To geocode the converted addresses, you must do a second geocode pass on the table.

LACS

Link

processing for an input address takes place under these circumstances:

• Input address is matched to a record in the Address Dictionary that has a LACS indicator set to

“L.”

• Input address is matched to a record in the Address Dictionary that is a Rural Route default.

• Input address does not match a record in the Address Dictionary.

Using LACS

Link

To use LACS

Link®

, do the following:

1. If you have not done so already, add the required CASS columns to the table that you want to geocode. See

CASS Geocoding on page 123

for information on the columns.

2. Start MapMarker.

MapMarker 23

126

User Guide

Chapter 7:

LACS

Link

3. Open the table you want to geocode. Proceed through the Select Column dialogs. When selecting output columns, make sure that you click Show DPV and LACSLink Columns. This displays the CASS-related columns.

For details of the LACS

Link

Indicator and LACS

Link

Code columns, see

LACSLink Output

Columns

.

4. Once you have provided all the information in the Select output columns from your table, click

Finish. You are then returned to the Geocode dialog box.

5. Select the Match Settings tab. In that dialog click Use CASS Mode and in the CASS options group click Use LACSLink.

6. Click Geocode to begin geocoding.

L

LACS

Link

processing does not require the creation of a CASS report. Output addresses are still provided without a report being created.

LACS

Link

Output Columns

There are two LACS

Link output columns that you can add to your table before you geocode, although

LACS

Link

processing still continues if you do not have the columns. These columns contain information about the LACS

Link

output.

MapMarker 23

127

User Guide

Chapter 7:

LACS

Link

The LACS

Link indicator column (char 1) shows whether the input address was converted. The

LACS

Link

Code column (char 2) includes information about the output. These two columns are read as a pair.

The paired LACS

Link

output columns and their possible values are described in the following

LACSLink Output Columns

table.

Y

LACS

Link

Indicator char(1)

A

LACS

Link

Output Columns

LACS

Link

Code char(2) Description

Y

S

09

92

Indicates that the input address was a converted address, and the converted address was returned as output.

Indicates that the input address was a converted address, but that the address was too imprecise for the

LACS

Link

converted address to be returned. The rest of the candidate information is returned as if LACS

Link was not used.

Indicates that the input address failed initially, but that a converted address was returned when secondary address information, such as the unit, was dropped.

F null

N

N

00

14

Indicates a false positive. When a false positive occurs,

LACS

Link

processing is disabled. No further LACS

Link processing is allowed until it is re-enabled. No CASS output information is returned (that is, ZIP + 4

®

, carrier route, delivery point). The input address is returned as if there was no match to the LACS

Link

database.

Indicates that no converted address was found for the input address. The input address is processed normally, but there is no converted output address.

Indicates that LACS

Link

processing proceeded as if a converted address would be returned, but that an output address could not be built.

L

To protect the security of the LACS

Link®

data, the U.S. Postal Service

®

requires that Pitney

Bowes Business Insight (PBBI) implement a stop processing sequence to shut off LACS

Link

if a possible misuse of the LACS

Link geocoding with LACS

Link

data is detected. If you incur a usage violation while

processing turned on, LACS

Link

is automatically shut off.

MapMarker 23

128

User Guide

Chapter 7:

DPV

For more information on LACS

Link

security guidelines and re-enabling LACS

Link

after a

usage violation, see

DPV and LACSLink Usage Guidelines and Requirements on page 135

DPV

The DPV

®

Product technology available from the USPS

®

provides the highest level of identifying known address records. When used in conjunction with CASS™ geocoding in MapMarker, DPV enables you to identify whether an address is a known USPS delivery point before your mailing leaves the premises. Conversely, you are also able to identify those addresses that are potentially undeliverable-as-addressed because of faulty address information.

When you geocode in DPV mode, MapMarker checks each geocoded address against the DPV database to identify whether the address is a known delivery point. The DPV database consists of over 165 million USPS delivery points, and is made available by the USPS for this specific use as part of the DPV option.

L

MapMarker installations shipped outside of the U.S. do not include DPV data. If the installer does not find the DPV data, it can not be chosen for installation.

Using DPV

DPV is used as part of the CASS process to ensure that geocoded addresses are identified as known USPS delivery points. Geocoding with DPV is available only when you are running in CASS mode, and requires extra columns in your table to hold the DPV output.

To use DPV, do the following:

1. If you have not done so already, add the required CASS columns to the table that you want to geocode. See

CASS Geocoding on page 123

for information on the columns.

2. Start MapMarker.

MapMarker 23

129

User Guide

Chapter 7:

DPV

3. Open the table you want to geocode. Proceed through the Select Column dialogs. When selecting output columns, make sure that you click Show DPV and LACSLink Columns. This displays the CASS-related columns

For details of the DPV

®

-related output columns, see

DPV Output Columns on page 131

.

4. Once you have provided all the information in the Select output columns from your table, click

Finish. You are then returned to the Geocode dialog box.

5. Select the Match Settings tab. In that dialog click Use CASS Mode to activate the

CASS-related check boxes. In the CASS options group click Use DPV mode.

6. Click Geocode to begin geocoding.

Street Directionals with DPV

CASS rules mandate that street directionals are handled differently when geocoding with DPV.

When a candidate is the only DPV-confirmed candidate and it matches the input address except for the directional, MapMarker makes this candidate a close match. Candidates that previously did not match return as the single close match because of this change. For example, when the following address is geocoded using DPV:

969 16th Ave S, Nashville TN 37208, the address is confirmed and matched to the following output address:

969 16th Ave N (DPV confirmed) Nashville TN 37208-3368.

MapMarker 23

130

User Guide

Chapter 7:

DPV

This change does not apply when there is more than one DPV-confirmed candidate in the output, or if the output contains no DPV-confirmed candidates.

Enhanced ZIP + 4 and DPV Requirement

If you are using DPV mode, and the primary number of the address does not DPV confirm (with Y,

S, or D confirmation code as described in

DPV Column Values on page 132

), then the USPS

® requires that MapMarker returns a ZIP Code™ and carrier route only for mailing-related information.

That is, if there is no DPV confirmation, MapMarker will not return the ZIP + 4

®

, Delivery Point,

Check Digit, RecordType, or DefaultFlag.

DPV Data and CASS

MapMarker ships regular data updates to comply with CASS requirements. Because the operation of DPV is closely tied to the currentness of the CASS data, the ZIP + 4 data is synchronized with

DPV updates to ensure that both are valid for the full 105-day period of the quarter.

If DPV expired on your system, MapMarker still functions normally except that you cannot use DPV and cannot create a CASS report. However, you can still geocode with CASS rules. To determine the DPV expiration on your installation, select Help > About from the MapMarker desktop application.

DPV Output Columns

DPV generates information for each geocoded address during the geocoding process. Your output table must include several columns to hold this information. These columns contain information specific to DPV, as well as a number of USPS

®

footnote codes that give more information about how the address was identified.

MapMarker 23

131

User Guide

Chapter 7:

DPV

The DPV

®

output columns and possible values are described in the following

DPV Column Values

table.

DPV Column Values

Column Name type (width) Description

DPV ConfCode char (1)

The DPV confirmation code for the geocoded address. The value of ConfCode determines the value of Cmra and falsePos.

Values:

N – Delivery Point not valid.

Y– Delivery Point valid for primary and valid for secondary, if secondary input is present.

S – Valid primary. Secondary (such as unit number) is present but not confirmed.

For rural route, primary is present but not confirmed.

D – Address is incomplete (highrise with no unit number, or rural route with no box number).

empty – No value returned. This happens when the ZIP + 4

®

code generates an

ND non-match code, for example, 91352-41ND. The Commercial Mail Receiving

Agency (CMRA) is also empty in this case. In CASS™ processing, ZIP + 4 codes that are NDs are not returned. For details on non-match codes, see

Non-match

Codes (N category) on page 120

.

DPV Cmra char (1)

Indicates whether the geocoded address belongs to a (Commercial Mail

Receiving Agencies (CMRA).

Values:

Y – CMRA was found.

N – CMRA was not found.

blank – Blank character (a space) returned as the value. If the ConfCode returns an ‘N’, the CMRA property returns a blank character as the value. Since the address does not exist in the DPV database, there is no reason to check for a

CMRA. This occurs in general delivery matches.

empty – No value returned. This happens in the following cases:

• If the ConfCode does not return a value, the CMRA does not return a value. This occurs when the ZIP + 4 code is an ND.

• Military matches.

• Unique ZIP Code™ matches.

MapMarker 23

132

User Guide

Chapter 7:

DPV

DPV Column Values

Column Name type (width)

DPV falsePos char (1)

Description

If true, DPV has detected a condition in which the geocoded address appears to be artificially generated and not a legitimately obtained address. DPV shuts down immediately in this instance.

Values:

Y – DPV has detected that an artificially generated address was geocoded. DPV shuts down immediately.

N – The address is not an artificially generated address.

blank – Blank character (a space) returned as the value. If the ConfCode returns a ‘Y’, ‘S’, or ‘D’, the falsePos property returns a blank character as the value.

Since the address exists in the DPV database, there is no reason to check for a false positive.

DPV Vacant

DPV NoStat

Indicates if a location is vacant.

Values:

Y – The address is vacant.

N –The address is not vacant.

Blank – DPV is not loaded or DPV did not confirm (so vacancy is irrelevant).

Indicates that the address is not receiving delivery and the address is not counted as a possible delivery. These addresses are not receiving delivery for one or more of the following reasons:

• Delivery has not been established.

• The customer receives mail as part of a drop.

• The address is no longer a possible delivery because the carrier destroys or returns all of the mail.

Values:

Y – The address was valid for computerized delivery sequence (CDS) pre-processing.

N – The address not valid for CDS.

Blank – The address is not presented to No Stat table or DPV data is not loaded.

LACSLink

Indicator

Indicates whether the input address was converted. This and the LACSLink

Code information are read as a pair.

LACSLink Code Includes information about the output.

MapMarker 23

133

User Guide

DPV Column Values

Column Name type (width)

DPV FtNote1 char (2)

Description

SuiteLink Code Indicates whether a Suite

Link

lookup or match was made.

Values:

A – SuiteLink match. Secondary information exists and was assigned to this record as a result of SuiteLink processing.

00 – SuiteLink no match. Lookup was attempted but no matching record could be found.

blank – A SuiteLink lookup was not attempted because one of the following was true:

• The address was not a highrise default according to CASS.

• The address did not contain a firm.

Field that may be populated with a standard USPS the codes follow this table.

® footnote code. Description of

DPV FtNote2 char (2)

DPV FtNote3 char (2)

Chapter 7:

DPV

Field that may be populated with a standard USPS footnote code. Description of the codes follow this table.

Field that may be populated with a standard USPS footnote code. Description of the codes follow this table.

Footnote Codes

The following DPV footnote codes may be output for match candidates:

• AA – Input address matched to the ZIP + 4

® file.

• A1– Input address not matched to the ZIP + 4 file.

• BB – Input address matched to DPV (all components).

• CC – Input address primary number matched to DPV but secondary number not matched

(present but invalid).

• F1 – Input address matched to a military address.

• G1 – Input address matched to a general delivery address.

• N1 – Input address primary number matched to DPV but highrise address missing secondary number.

• M1 – Input address primary number missing.

• M3 – Input address primary number invalid.

• P1 – Input address missing PO, RR, or HC box number.

• P3 – Input address PO, RR, or HC Box number invalid.

• RR – Input address matched to CMRA and PMB designator present (PMB123 or #123).

• R1 – Input address matched to CMRA but PMB designator not present (PMB 123 or #123).

MapMarker 23

134

User Guide

Chapter 7:

DPV and LACS

Link

Usage Guidelines and Requirements

• U1 – Input address matched to a unique ZIP Code™.

DPV and LACS

Link

Usage Guidelines and Requirements

The DPV

®

feature has specific requirements related to the CASS™ process to ensure the validity of the data, its security, and to guard against improper use of the feature. This section explains the mechanisms MapMarker has in place to meet these requirements.

False-positive addresses, are addressees the USPS

®

monitors to ensure users are not attempting to create a mailing list from the DPV or LACS

Link

data. To protect the security of the DPV

®

data, the

U.S. Postal Service

®

requires that PBBI implement a stop processing sequence to shut off DPV if a possible misuse of the DPV data is detected. This is designed to guard against users who are attempting to create address lists with the data, rather than do true address validation.

L

Per the USPS regulations, PBBI must contact the USPS with the organization’s name and address for every false-positive address encountered. If multiple incidents of artificial address detection occurs, the USPS may ask PBBI to suspend a customer’s DPV or

LACS

Link

processing capability.

If you encounter a false-positive, you will receive a message. Processing continues to the end of your job, but DPV or LACSLink processing is not available. DPV or LACS

Link

processing is not available for subsequent jobs until you have reported the false-positive address encounter to PBBI and have received a new security key.

Messages similar to the following appears when you encounter a false-positive address:

For DPV

DPV usage has been disabled because of a hit to a DPV false positive seed record. Please contact

Pitney Bowes Business Insight Technical Support to re-enable the DPV feature.

For LACS

Link

LACS

Link

feature has been disabled because of a hit to a LACS

Link

false positive seed record.

Creating the False Positive Report for DPV or LACSLink

If you generated a false positive record for DPV or LACS

Link

you must create a false-positive file that contains the Header Record and Detail Record information. You must provide this file to obtain a new security file from the PBBI Web site or from technical support.

The following tables contain the layout of the header and detail records of the false-positive files for

DPV and LACS

Link

. The header record contains the mailer information from the Mailer Parameter

Record and statistics gathered by the application. The detail record contains false-positive record information.

MapMarker 23

135

User Guide

Chapter 7:

DPV and LACS

Link

Usage Guidelines and Requirements

Position

1-40

41-98

99-126

127-128

129-137

138-146

147-155

156-164

165-173

174-178

179-180

9

9

9

9

40

58

28

2

Length

False Positive Table Header Records

Company Name

Address line

City name

Description

State abbreviation

9-Digit ZIP Code

Total records DPV LACSLInk processed

Format

alphanumeric alphanumeric alphanumeric alphabetic numeric numeric

Total records DPV LACSLInk matched numeric percent match rate to DPV

Found in DPV false positive header records only.

numeric

9

5

2 percent match rate to ZIP +4

Found in DPV false positive header records only.

numeric number of ZIP Codes on file

Found in DPV false positive header records only.

numeric

Number of false positives

Found in DPV false positive header records only.

numeric

Position

1-2

3-30

31-34

35-36

37-46

4

2

2

28

10

Length

False Positive Detail Records

Description

Street directional

Street name

Street suffix abbreviation

Street postdirectional

Address primary number

MapMarker 23

136

Format

alphanumeric alphanumeric alphanumeric alphanumeric alphanumeric

User Guide

Position

47-50

51-58

59-63

64-65

68-180

5

4

113

Chapter 7:

Suite

Link

4

8

False Positive Detail Records (continued)

Length Description

Address secondary abbreviation

Address secondary number

Format

alphanumeric numeric

Matched ZIP Code

Matched ZIP Plus 4

Filler numeric numeric

Submitting a False Positive Report and Obtaining New Security Key

Use the same procedure to report false-positive address matches and obtain a new security key for both DPV and LACS

Link

. You must provide the false-positive report file to PBBI to obtain a replacement security key.

If you do generate a DPV and LACS

Link

false positive address, contact Pitney Bowes Business

Insight Technical Support. Have your original DPV and LACS security keys ready when you contact

Technical Support.

Suite

Link

Suite

Link

™ is he USPS® business name database that provides suite numbers for businesses located in high-rise buildings. This allows delivery sequencing where it would not otherwise be available.

Suite

Link

is an optional add-on, and is installed from separate media. No additional licensing is required.

Using Suite

Link

Suite

Link

is used as part of the CASS process to return suite numbers for businesses even if the input address did not provide this information. Suite

Link

results are available as a user-selected option on the Match Settings dialog. Suite information is returned as part of the output Address field.

Suite

Link

data is an optional dataset. This dataset is provided on a separate DVD and is copied from the media by the user. There is no licensing required, but you must contact your sales representative to acquire Suite

Link

. Copy the Suite

Link

data into the Data directory (typically

<install>/MapMarker_USA_v23_Data).

MapMarker 23

137

User Guide

Chapter 7:

Returning Abbreviated Addresses

To use Suite

Link

, do the following:

1. If you have not done so already, add the required output columns to the table that you want to geocode. See

CASS Geocoding on page 123

for information on the columns.

2. Open the table you want to geocode. Proceed through the Select Column dialogs.

3. Once you have provided all the information in the Select output columns from your table, click

Finish. You are then returned to the Geocode dialog box.

4. In the Geocode dialog box, make selections for the Geocode Precision, Types of Rows to

Geocode, and Range to Geocode.

5. Select the Match Settings tab. In that dialog click Use SuiteLink. Note that this option is available even if Use CASS Mode is not selected. Make your other selections in the Match

Settings dialog.

6. Click Geocode to begin geocoding.

The following table shows examples of input addresses and the Suite

Link

returns:

Input Firmname

Chrtr Home Mrtg

Rockaway Bldg

SuiteLink Examples

Input Address

171 Park Ave #3

1578 Sussex Tpke #1

Capital EAP Limited 650 Warren St #4

Amercn Inst 80 Maiden Ln #221

Joliet Medical Limited 2100 Glenwood Ave

Suite

Link

Output Address

171 Park Ave Ste 2

1578 Susses Tpke Bldg 1

650 Warren St Ste 4

80 Maiden Ln Rm 221

2100 Glenwood Ave Ste 100

If the input address has incorrect suite/location information, Suite

Link

will return the corrected information. For example, input of #3 can be corrected to Ste 2. If the input address does not specify a street but the Suite

Link

dataset includes suite information for the business, then the suite is added to the output address.

Returning Abbreviated Addresses

MapMarker 23 can return an abbreviated alias address (maximum of 30 characters) if the standardized base input address exceeds 30 characters. Abbreviated address returns are available as a user-selected option on the Match Settings dialog. This information is returned in the standard

Address1 output field.

You do not have to be currently licensed for CASS to take advantage of the Abbreviated Address option.

MapMarker 23

138

User Guide

Chapter 7:

Returning Abbreviated City Names

To get abbreviated address on output, do the following:

1. If you have not done so already, add the required output columns to the table that you want to geocode. See

CASS Geocoding on page 123

for information on the columns.

2. Open the table you want to geocode. Proceed through the Select Column dialogs.

3. Once you have provided all the information in the Select output columns from your table, click

Finish. You are then returned to the Geocode dialog box.

4. In the Geocode dialog box, make selections for the Geocode Precision, Types of Rows to

Geocode, and Range to Geocode.

5. Select the Match Settings tab. In that dialog click Return Short Address. Note that this option is available even if Use CASS Mode is not selected. Make your other selections in the Match

Settings dialog.

6. Click Geocode to begin geocoding.

The following examples illustrate several standardized base addresses that exceed 30 characters and the corresponding abbreviated returned address. The bold text shows the standardized base address and the corresponding abbreviated address.

Abbreviated Addresses

Standardized Base Address Input Abbreviated Address Output

100 Tyngsborough Business Pk Dr

Unit Tyngsboro MA 01879

100 Business Park Dr Unit 1 Tyngsboro MA 01879-

00171

108 Woodsville Marshall Corner Rd

APT A Hopewell NJ 08525

108 Mrshl Crnr Wods Rd Apt A Hopewell NJ 08525-

2800

700 Rev S Howard Woodson Jr Way

31 Trenton NJ 08618-3802

700 Howard Woodson Way Trenton NJ 08618-3802

Returning Abbreviated City Names

MapMarker 23 can return an abbreviated city name (maximum of 13 characters) for any valid city name (regardless of length). Abbreviated city name returned are available as a user-selected option on the Match Settings dialog. This information is returned in the standard City output field.

You do not have to be licensed for CASS to take advantage of the Abbreviated Address option.

To get abbreviated city names on output, do the following:

1. If you have not done so already, add the required output columns to the table that you want to geocode. See

CASS Geocoding on page 123

for information on the columns.

1. Open the table you want to geocode. Proceed through the Select Column dialogs.

2. Once you have provided all the information in the Select output columns from your table, click

Finish. You are then returned to the Geocode dialog box.

MapMarker 23

139

User Guide

Chapter 7:

Geocoding Dual Addresses

3. In the Geocode dialog box, make selections for the Geocode Precision, Types of Rows to

Geocode, and Range to Geocode.

4. Select the Match Settings tab. In that dialog click Return Short City Name. Note that this option is available even if Use CASS Mode is not selected. Make your other selections in the

Match Settings dialog.

5. Click Geocode to begin geocoding.

The following examples illustrate several long input city names (exceeding 13 characters) and the corresponding abbreviated city name returned. The bold text shows the long city name (or non-mailing city name) and the corresponding abbreviated city name.

City Name Input

Abbreviated City Name

Abbreviated City Name Output

7311 Black Oak Ln Yosemite

National Park CA 95389

1202 Pioneer Rd Mangonia

Park FL 33407

(non-recognized city name)

7311 Black Oak Ln Yosemite Ntpk CA 95389-9102

1202 PIONEER RD West Palm Bch FL 33407-2241

(abbreviated name associated with the valid city name

West Palm Beach)

252 N Wickiup Rd Apache

Junction, AZ 85219

252 N Wickiup Rd Apache JCT, AZ 85219

7575 Rancho Cucamonga, CA

91730

7575 Rch Cucamonga, CA 91730

40 Smithwheel Rd, Old Orchard

Beach, ME 04064

40 Smithwheel Rd, Old Orchd Bch, ME 04064

Geocoding Dual Addresses

A dual address is an address that contains both a street address, and a P.O. Box or General

Delivery. These parts may appear on two lines, or on one line.

Two-Line Dual Addresses

A two-line dual address might appear like this on an envelope:

1 MAIN STREET

PO BOX 123

In a two-line dual address, the line that appears directly above the last-line information in the address is the intended delivery address. In the two-line address example above, PO BOX 123 is the intended delivery address.

MapMarker 23

140

User Guide

Chapter 7:

Geocoding Remote Tables

For MapMarker input purposes, PO BOX 123 is the Address1 input field and 1 MAIN STREET is the

Address2 input field.

When you geocode the table, a two-line dual address is matched to the address in the Address1 field if both addresses produce a close match.

One-Line Dual Addresses

A one-line dual address might appear like this:

1 MAIN STREET PO BOX 123

In CASS mode, for one-line dual addresses, MapMarker chooses a single close match based on the following priority, if both addresses produce a close match:

• P.O. Box

• Street

• Rural Route

• General Delivery

When you geocode a table in CASS™ mode, the address that is not used for the single close match is output to the Address2 field for both types of dual addresses.

In non-CASS geocoding, the street address is always preferred if both addresses produce close matches.

Geocoding Remote Tables

MapMarker supports ODBC tables in Microsoft Access, Oracle, and SQL Server formats. See your

MapMarker release notes for version-specific support information.

If you are geocoding your ODBC table, you or your database administrator must first add the fields for GeoResult, Latitude, and Longitude. A georesult column is highly recommended and coordinate columns are recommended. If you plan for MapMarker to write additional address information to your table, prepare columns for them as well.

To access your remote database:

1. Choose File > Open ODBC Table to display the Select Data Source dialog. (If you set File >

Open Startup Options for ODBC Tables from the System Preferences dialog, the Select Data

Source dialog appears automatically when you start MapMarker.

2. From the Select Data Source dialog, click the Machine Data Source tab.

3. Choose your data source. Your data source is the location of the specified database. For example, CUSTOMER could be the name of the data source that provides access to one or more Oracle tables located in a specified directory. Once connected to the CUSTOMER data source, you could access information from any Oracle table associated with that data source.

4. Sign on to your data source in the usual way. This procedure differs depending on what type of

ODBC table you are using.

MapMarker 23

141

User Guide

Chapter 7:

Geocoding dBASE Files

5. From the Select Table dialog, choose the table you want to access. Each of the tables owned by you or accessible to you are displayed. Keep in mind that you cannot open any other tables while you have an ODBC table open.

6. Proceed with geocoding as you would with any other MapMarker table.

Geocoding dBASE Files

MapMarker reads dBASE format (DBF) as well as MapInfo native format (TAB) files, enabling you to turn any table of records into geographic objects. This section explains some things to keep in mind when geocoding DBF files.

MapMarker creates a TAB file automatically when you open a DBF file. If you open the DBF file a second time, a dialog appears stating that a TAB file already exists. Select Yes to replace it.

Since MapMarker automatically creates a TAB file for any DBF file you open, all of the options available to TAB files apply to DBF files. Among them, MapMarker adds coordinate and result columns and creates points for your table automatically.

MapMarker does not display memo fields included with DBF files. The fields are not changed in any way by MapMarker.

MapMarker does not maintain indexes for DBF files. If you write to an indexed field during geocoding, the table must be re-indexed outside of MapMarker if you wish to maintain the index.

Geocoding Delimited, CSV, and SHP Files

MapMarker reads and writes delimited text files, CSV, TXT, and DBF files. After opening these files, you can use a Text File wizard to set properties for the input file.

MapMarker can also export files to ESRI Shapefile (SHP) format.

See the following topics in

Chapter 3: Geocoding with MapMarker

:

Opening a Table or Text File

.

Defining Properties of Delimited Text Files

Exporting to Shapefiles

Using Quick Geocode

Quick Geocode is a shortcut to geocoding your table with MapMarker. Use it to geocode previously opened tables with a single click. For example, use Quick Geocode on tables that you update frequently and need to geocode new records. Quick Geocode follows the geocoding preferences and system preferences settings you specify to carry out the geocoding operation.

MapMarker 23

142

User Guide

Chapter 7:

Finding Address with Quick Find

Quick Geocode is available after you open a table in MapMarker and set the input and output columns, geocoding, and system preferences. You can geocode the entire table or a portion of the table. When you close the table, the settings are written to the table’s metadata and the system registry, preserving your preferences for the next time you need to geocode the table.

L

MapMarker attempts to geocode all records in the table during a Quick Geocode pass, regardless of their previous geocoding status.

Finding Address with Quick Find

The MapMarker Quick Find feature provides a fast way to determine the correct address for a single record. If there are several match candidates to choose from, you can view them on a map to help determine the best choice. Quick Find does not geocode the record. It simply attempts to match the address to the Address Dictionary and return potential matches to help you confirm or correct the address.

Quick Find can generate the following kinds of results.

• street geocoding

• street intersection geocoding

• postal fallBack

• geographic fallback

• street browse

• place browse

Quick Find can also be used as a method to browse the Address Dictionary for the correct spelling of a street name. Provide the postal code and at least the first letter of the street and click the

Browse button. The city and state fields are optional. MapMarker returns a list of streets that meet your criteria.

Finding Candidates Using Quick Find

To view potential matches on a map from Quick Find:

1. Select Search > Quick Find to display the Quick Find dialog box.

MapMarker 23

143

User Guide

2. Type the address you wish to find and click Search.

Chapter 7:

Finding Address with Quick Find

Candidates are displayed in the Match Candidate List. The number and type of candidates returned by Quick Find depends on the criteria set in

Quick Find Settings on page 148

. Use

those settings to select street level, postal fallback, or geographic fallback options.

The specific column headings in the Match Candidate List depend on the type of geocoding. All street level, postal, or geographic results include a ResultCode column.

L

A green check mark in the Num column indicates a close match. Street browse or place browse candidates do not have a ResultCode or close match indicator.

Viewing Quick Find Candidates on a Map

To visualize Quick Find candidates on a map, you must first specify a valid location of the street data. This activates the Map button on the Interactive or Quick Find dialog box. See

Maps System

Preferences

for more information.

1. After pointing to a valid location for your street data, follow these steps:

2. Select the candidate that you want to display on a map and click Map. Use Ctrl-Click to select multiple candidates. The Candidate Map window appears and selected candidates are

MapMarker 23

144

User Guide

Chapter 7:

Finding Address with Quick Find

displayed. The color-coded symbols (stars or circles) represent the level of geocoding precision for each record. See

Displaying Geocoded Records in MapInfo Professional

.

3. Use the Pan, Zoom, and Label tools to help you identify the best match for your address. Use the Label tool to identify surrounding streets and features for additional information about the area.

4. With the Select tool, click the candidate symbol for your match and click OK. You are returned to the Quick Find dialog box. The candidate is highlighted in the list. Make a note of the corrected

MapMarker 23

145

User Guide

Chapter 7:

Finding Address with Quick Find

address and click Close. You can also copy selected candidate information to the clipboard. See

Copying Information from the Quick Find Candidate List on page 146

.

Quick Find also supports single line address searching in the Address field. A single line address has all address components on a single line rather than in separate fields. For example, in the

Address/Single Line Address field of the Quick Find dialog, you can enter an address such as:

One Global View, Troy NY, 12180

5. When you click Search, candidates are listed in the Match Candidate List. In this example,

MapMarker makes a close match. For a more complete explanation of single line address

searching, see

Using Single Line Addresses in Geocoding

.

L

Candidates from a Quick Find Browse cannot be displayed on a map. See

Browsing

Candidates Using Quick Find on page 147

for more information.

Displaying Address Ranges

After selecting a street level, postal, or geographic candidate from the list, you can display the address ranges associated with a candidate. To display address ranges, do either of the following:

• Select a candidate and click Range, or

• Double-click the candidate

The ZIP + 4

®

is also displayed immediately to the right of each street range.

The Range feature is available with candidates from a Quick Find search. You cannot display address ranges from a Quick Find Browse. See

Browsing Candidates Using Quick Find on page 147

.

Copying Information from the Quick Find Candidate List

Each Quick Find geocode candidate in the Match Candidate List includes the result code, address components, and latitude / longitude coordinates. Browse candidates will have street name or place name only.

You can copy the appropriate information to the clipboard and paste it into another application. For example, you can copy the address or coordinates into MapInfo Professional so that you can display the location on a map using al the features of MapInfo Professional.

MapMarker 23

146

User Guide

Chapter 7:

Finding Address with Quick Find

To copy Quick Find candidate information, right-click on one or more candidates in the Match

Candidate List. You will see the following choices in the pop-up menu, depending on whether the list contains street geocoded, postal fallback, or geographic fallback candidates.

Menu Selection

Copy Selected

Copy Address

Copy from Quick Find List

Action Available for

Copies all information for selected candidates, except the candidate number.

Copies street addresses for selected candidates.

street geocoding candidates postal or geographic fallback candidates street geocoding candidates

Copy Coordinate Copies coordinates for selected candidates.

street geocoding candidates postal or geographic fallback candidates

L

You cannot copy information from Quick Find browse candidates.

Browsing Candidates Using Quick Find

You can also use the Quick Find dialog to browse the Address Dictionary for the correct spelling of a street name or business.

Enter the ZIP Code™ and at least the first letter of the street or business and click Browse. The city and state fields are optional. MapMarker returns a list of streets or businesses that meet your criteria.

Browsing does not geocode the record, but you can use the browse results to confirm your address and then geocode based on this information. To maximize the ability of MapMarker to return a list of browsed candidates, it is best to provide only a partial street or business name.

L

The Map and Ranges buttons are unavailable when you Browse from the Quick Find dialog box.

MapMarker 23

147

User Guide

Chapter 7:

Finding Address with Quick Find

For example, after browsing on the street "Broad" in ZIP Code 12180, the Browsed Results list box displays street names and address ranges for Broadview Ct, Broadview Terrace, Broadway, and similarly named streets.

Quick Find Settings

You can change the criteria used for generating your Quick Find search results. In the Quick Find

Settings dialog, you can choose to:

• select one of the match modes (including CASS™ mode)

• select address components that must match exactly (house number, street name, city name,

ZIP Code™

• prefer a ZIP Code match over a City Name match

• choose fallback options

• list all candidates or list close candidates only

MapMarker 23

148

User Guide

Chapter 7:

Finding Address with Quick Find

To change the Quick Find settings:

1. Open the Quick Find dialog (see

Finding Address with Quick Find on page 143

.

2. Click Quick Find Settings.

The Quick Find Settings dialog appears.

3. Select the settings you wish to use and then click OK.

Quick Find Settings

Description Quick Find Setting

Match Modes

Standard Mode

Tight Mode

Relaxed Mode

CASS

Check this box to implement Standard Mode matching. See

Match

Modes

.

Check this box to implement Tight Mode. See

Match Modes

.

Check this box to implement Relaxed Mode. See

Match Modes

.

Check this box to use CASS™ mode in finding addresses.

L

When this check box is selected, the other settings options on this dialog are disabled and their values are overwritten by CASS rules. List Candidates options (All Candidates and Close Candidates Only) are available for selection.

MapMarker 23

149

User Guide

Quick Find Setting

Custom Selections (Exact Match Required)

House Number

Check this box to require the use of house number in determining an exact match.

Street Name

City Name

Quick Find Settings (continued)

Description

Check this box to require the use of street name in determining an exact match.

Check this box to require the use of city name in determining an exact match.

ZIP Code

Chapter 7:

Finding Address with Quick Find

Check this box to require the use of ZIP Code in determining an exact match.

Other Settings

Prefer Matching ZIP over

Matching City

Use Wide Search

Check this box to prefer an internal close candidate on postal code over a match on city.

Use wide search to consider all streets that begin with the first letter of the input street name, and therefore can identify many more potential candidates. Wide search is most often used in combination with Relaxed mode as part of a two-pass geocoding strategy. See

Using Wide Search

.

Fallback

Fallback to ZIP Centroid

Fallback to Geographic

Centroid

Click this option to allow fallback to ZIP Code™ Centroids. If a close match was not found using the Require Exact Match criteria, you can still geocode based on ZIP Code centroids.

Click this option to allow fallback to geographic centroids. If a close match was not found using the Require Exact Match criteria, you still can geocode based on state, county, or city centroids. These are not very specific geocoding options, but may be suitable for certain applications.

Candidates to Return

All Candidates

Close Candidates Only

Click this option to return all candidates matching the search criteria you specify.

Click this option to return only the candidates that closely match the search criteria you specify.

MapMarker 23

150

User Guide

Chapter 7:

Finding Airports with Locate Airport

Finding Airports with Locate Airport

The MapMarker Locate Airport feature allows you to locate an airport using a state abbreviation or a specific airport code. Enter an airport code or two-letter state abbreviation in the text field of the

Search frame. The Search Results box returns the number of successful matches for a state, match found for an airport code, or no matching records found. After a successful match, the Airport List field displays the airport code, airport name, state, and latitude/longitude coordinates.

To locate an airport:

1. On the Search menu, click Locate Airport.

The Locate Airport dialog appears.

2. Type the airport code or the state abbreviation in the Airport Code or State Abbreviation field

(for example, ALB for Albany International Airport or NY for all airports in New York).

3. Click Search. MapMarker returns all matching airports in the Airport List box, sorted by airport code.

MapMarker 23

In this example, the airports for Arizona are displayed in alphabetical order by airport code.

If a match cannot be made, the Search Results box displays one of three messages depending on your search criteria:

151

User Guide

Chapter 7:

Finding Highway Exits with Locate Highway Exit

Result Messages for Airport Search

Search Results Message Description

Invalid state or location code.

Invalid state code.

No matching records found.

The airport or state code you searched for did not contain at least two alphanumeric characters. Re-type the airport or state code, using two characters if searching by state, or three to four characters if searching by airport code.

The two-character code you searched for did not match a valid state code. Type the correct state code to search for all airports in the state or type the complete three- or four-character airport code to search for a specific airport.

The three- or four-character code you searched for did not match a valid airport code. Type the correct airport code to search for the airport or type a state code to search for all airports in the indicated state.

Finding Highway Exits with Locate Highway Exit

The MapMarker Locate Highway Exit feature allows you to locate a highway exit using the highway name, exit number, and state. You must enter a highway name, an exit number or exit name, and a state in order for the search to return a result. Search results include the highway name, full exit name, city, state, ZIP Code™, and X and Y coordinates for the exit.

You can select a search result and click Map to view the candidate’s location on a map to determine which candidate is the exact one you are looking for.

To locate a highway exit:

1. On the Search menu, click Locate Highway Exit.

The Locate Highway Exit dialog appears.

2. Type a highway name in the Highway field (for example, I-90 East or Interstate 90 East).

3. In the Exit field, type either an:

• exit number (for example, 2 or Exit 2).

• exit name (for example, Fuller Rd). Do not add a period or other punctuation after the street type (specify the street type as Rd or Ave).

4. Type a state abbreviation in the State field (for example, NY for New York).

5. Click Search.

MapMarker 23

152

User Guide

Chapter 7:

Batch Geocoding

MapMarker returns all matching highway exits in the Search Results box.

Batch Geocoding

MapMarker supports batch geocoding for geocoding one or more files without user interaction. You create a batch file containing the path and file names of the tables to geocode and specify the geocoding preferences you want applied to the session.

Batch geocoding is useful for overnight processing of large databases or when a table is updated regularly via a scheduling program.

CASS™ geocoding can also be set up as a batch process.

L

You can batch geocode MapInfo TAB files, comma-delimited (CSV), text files (TXT), and project files (PROJ). However, you usually cannot batch geocode ODBC database files, since a password is typically required and that requires user intervention.

The procedure for creating a batch file varies depending on whether the input file is a TAB file or other file type. See the following topics:

Creating a Project-Based Batch File

Creating a Batch Geocoding File from a TAB File on page 153

Creating a Batch Geocoding File from a TAB File

To create a batch geocoding file from a TAB file, follow these steps:

1. Open a table in MapMarker and proceed through the select column dialogs to confirm the input and output columns. See

Selecting Input and Output Address Columns

.

MapMarker 23

153

User Guide

Chapter 7:

Batch Geocoding

2. When you have finished specifying input and output columns, use the tabs in the Geocode dialog to select your geocoding settings. After selecting the settings, click Apply. Click the dialog Help buttons to learn more about each geocoding option.

3. When done with the settings, click Cancel in the Geocode dialog then choose Table > Create

Batch File. The Save Batch File As dialog appears.

4. Specify the path and filename for the batch file. By default the batch file uses the root file name of the table with the extension *.bat. Click Save.

5. Repeat

step 1

through

step 4

for each additional table you want to include in the batch file.

When saving to an existing batch file, such as the one initially created in

step 4

, the name of the table is appended to the end of the batch file. To create a new batch file, use a new filename.

L

If you want to batch geocode CSV or TXT files, you must create a project (PROJ file) to

accomplish this. For information on creating a project, see

Creating and Saving a Project

.

To run a project from a batch file, see

Creating a Project-Based Batch File

.

To run a batch file, double-click on the filename in Windows Explorer. MapMarker starts running and opens each table listed in the batch file in turn and then geocodes it to the specified settings. If

MapMarker encounters an error, it stops.

Manually Creating a Batch File from a TAB File

For TAB files, you can create a batch geocoding file without using a project. To do this, create a BAT file in a text editor and indicate the following:

• the path and filename of the MapMarker executable program

• the path and filename of the TAB file

• any geocoding preferences that you want MapMarker to follow

The parameters can be listed in any order and can use uppercase, lowercase, or mixed case text.

You must also open the table in MapMarker at least once and set the preferences. Otherwise

MapMarker will geocode using the default settings for that table as found in the metadata.

MapMarker 23

154

User Guide

Chapter 7:

Batch Geocoding

The batch geocoding parameters for a TAB file are described in following table:

Batch Geocoding

Parameters for TAB File

. These parameters are only used for batch files based on TAB files. For

project-based batch files, the preferences and parameters are encapsulated in the project file itself.

Parameter

Batch Geocoding Parameters for TAB File

Description

/TABLE=c:\sample\table

/LOG=<logfile name>

/STREET or /ZIP

/START=<number>

/END=<number>

/ALL or /UNMATCHED

Path and filename of table to geocode.

Name of log file. MapMarker writes the geocoding results to this file. If a log file is not specified, MapMarker creates a default Mapmarkr.log file.

Specify geocode precision to street level or to ZIP Code™ centroids.

Specify the starting row number to geocode. If omitted,

MapMarker begins with row 1.

Specify the ending row number to geocode. If omitted,

MapMarker ends at the end of the table.

Specify whether to geocode all records or only unmatched records.

Specify Y to geocode to the exact house number.

Specify Y to geocode to the exact street name.

Specify Y to geocode to the exact city name.

Specify Y to geocode to the exact ZIP Code.

/EXACT_HOUSE=Y,N

/EXACT_STREET=Y,N

/EXACT_CITY=Y,N

/EXACT_ZIP=Y,N

/STREET_ONLY=Y,N

/STREET_PTZIP_ONLY=Y,N.

Specify Y geocode only to street addresses, not to ZIP codes.

Specify Y to geocode to exact street address and point ZIP

Codes.

/FALLBACK=NO,ZIP4,ZIP2,ZIP Specify whether MapMarker falls back to a ZIP Code™, and if so, to which precision: ZIP + 4

®

, ZIP + 2, or ZIP Code™

/MATCH_MODE=STANDARD,

TIGHT, RELAXED, CUSTOM

Specify STANDARD to implement the Standard Match Mode.

TIGHT implements Tight match mode, RELAXED implements

Relaxed match mode. CUSTOM mode allows for exact match

criteria. Match Modes are set in the

Match Settings Dialog

.

See the topic

Match Modes

for a specific discussion of match

modes.

MapMarker 23

155

User Guide

Batch Geocoding Parameters for TAB File (continued)

Parameter Description

Chapter 7:

Batch Geocoding

/MULTI=NO,FIRST,STREET,ZIP Specify how MapMarker handles multiple matches:

• No = do not geocode

• First = geocode to the first candidate from a multiple match

• Street = choose a street match over a ZIP Code match

• ZIP = choose a ZIP Code match over a street match.

/PREFER_UD=Y,N Specify User Dictionary match over the MapMarker Address

Dictionary.

L

The user must have a user dictionary path already set up to use this setting.

/MIXED_CASE=Y,N

/CASS

/PREF_ZIP_OVER_CITY=Y,N

/WIDE_SEARCH

Specify output street addresses to have mixed-case.

Add this parameter to do CASS™ geocoding; omit parameter to do non-CASS geocoding.

Specify Y to prefer ZIP Code match over city match.

Add this parameter to enable wide search; omit parameter to disable wide search.

Following is a sample geocoding batch file. This same batch file could be created manually or through the MapMarker interface.

"C:\Program Files\MapInfo\MapMarker_USA_v23\desktop\mapmarkr.exe"

/TABLE=C:\Program Files\MapInfo\MapMarker_USA_v23\desktop\sampdata\

US_ADDR.TAB /LOG=mapmarkr.log /UNMATCHED /START=1 /END=20 /PREFER_UD=N

/MIXED_CASE=N /STREET /EXACT_HOUSE=Y /EXACT_STREET=N /EXACT_CITY=N

/EXACT_ZIP=N /STREET_ONLY=N /STREET_PTZIP_ONLY=N /FALLBACK=NO /MULTI=NO

Batch Geocoding Considerations

This section describes how batch geocoding handles information in your table.

Batch geocoding is available only for MapInfo TAB files. Batch geocoding of delimited text files and remote database (ODBC) files is not supported.

Batch File Contents for TAB and Other File Types

A batch files based on TAB files can contain the parameters listed in the table:

Batch Geocoding

Parameters for TAB File

. However, a project-based batch file (used for Delimited and Text files),

simply identifies and runs the project file, and does not use any other parameters. For project-based batch files, the preferences and parameters are encapsulated in the project file itself.

MapMarker 23

156

User Guide

Chapter 7:

Table Attribution with MapMarker

Running the Batch File

MapMarker should not be running when you run the batch file. The batch file will start MapMarker, execute the instructions, then exit.

Table Settings and Preferences

If you list a table in the batch file without parameters, MapMarker geocodes to the default settings for the table (whatever the settings were the last time the table was opened in MapMarker).

The batch geocoder uses the system preferences that are set at the time of geocoding. To ensure that a particular system setting is used, such as the location of the Address Dictionary, choose the setting in the System Preferences dialog, apply it, make the batch file, and run the batch file during the same MapMarker session.

CASS Geocoding in a Batch Process

When you do CASS™ geocoding on a table in a batch geocoding process, some of the command line parameters are overridden to the CASS settings. The CASS settings for these parameters are as follows:

Input and Output Columns

MapMarker uses the input and output columns it finds in the table’s metadata. Columns cannot be changed for batch geocoding.

Table Attribution with MapMarker

With MapMarker, you can add information from one table to another, either before, during, or after the geocoding process. This ability is called attribution.

Any table in MapInfo format (TAB file) can be a candidate for attribution. This includes boundary and point files, demographic tables, or non-geographic tables. The table to which the attributes are being applied must be local, since it is the table you are geocoding. The table containing the source attributes can be local or remote.

L

You cannot use table attribution with a text file. Attribution works with TAB files only.

There are two ways to do attribution in MapMarker. They are defined by the type of link required to connect the two tables:

• Output Point attribution – links the geocoded table to the attribution table by geography, specifically by matching latitude and longitude point coordinates within the geocoded table to a geographic boundary defined within the attribution table. For output point attribution, the attribution table must include a map object table (MAP).

• Column Value attribution – matches (joins) a column in the geocoded table to an equivalent column in the attribution table. The column in the attribute table must be indexed.

MapMarker 23

157

User Guide

Chapter 7:

Table Attribution with MapMarker

Attribution can operate either during a geocoding pass or as a separate batch process. Only successfully geocoded or matched records receive attribute data. Batch attribution is generally faster than geocoding with attribution enabled. Column value attribution is faster than output point attribution.

The general process for Output Point attribution in MapMarker is as follows:

1. Open the table that you want to geocode. This is the table into which you import attributes.

2. Select the attribution table.

3. Create a column to receive attribution data.

4. Bind the attribute column in your geocoding table to attribution table column. either by Output

Point or Column Value.

5. Geocode the table to add the attributes or run the batch attribution process.

Each of these steps is described more fully in the following topics:

Opening the Table for Attribution on page 158

Selecting an Attribution Table on page 159

Creating a Column to Receive Attribution Data on page 160

Binding Attributes – Output Point Attribution on page 162

Binding Attributes – Column Value Attribution on page 163

Adding Attributes to Your Table on page 164

Stopping Attribution on page 165

Clearing Attribute File Selections on page 166

Tips for Using Attributions on page 166

Opening the Table for Attribution

First you must open the geocoding table into which you want to add attributes. Follow these steps:

1. Open the MapInfo table. Select File > Open Table, navigate to the table you want to open and click Open. For example, open the US_ADDR.TAB file, which contains sample addresses from the U.S.

2. Click Next, then Finish. At the Geocode dialog, the click Cancel. Do not geocode at this point.

You are now ready to select an attribution table from which you want to pull attributes into your

geocoding table. See

Selecting an Attribution Table on page 159

.

MapMarker 23

158

User Guide

Chapter 7:

Table Attribution with MapMarker

Selecting an Attribution Table

To select an attribution table that you want to pull attributes from, follow these steps.

1. Open the Select Attribute Tables dialog by doing one of the following:

• On the Table menu, select Geocode and on the Geocode tab click Configure Attribution.

• On the Table menu, select Add Attributes and click Select Attribute Files. The Select

Attribute Tables dialog appears.

2. Navigate to the location of the attribute table that you wish to pull attributes from. Use the Drives list to select the drive containing the attribute table, and then navigate that drive.

MapMarker provides a sample attribution table in the <install>\desktop\MapMarker\sampdata directory called CNTYDEMO.TAB. You can use this table to try out the attribution feature using

Output Point attribution.

3. When you locate the attribute table you wish to use, click it and then click Add. The full path to the table appears in the Selected Tables box. Repeat to add additional tables.

When finished selecting attribution tables, click Next.

4. The Bind Attribute Table Columns to Output Columns dialog box appears. In the Join Using group, select Output Point (this example describes output point attribution).

MapMarker 23

159

User Guide

Chapter 7:

Table Attribution with MapMarker

You must now create a new column to contain the attribution data. Do not click OK at this point, but continue to

Creating a Column to Receive Attribution Data on page 160

.

Creating a Column to Receive Attribution Data

After you have selected an attribution table (

Selecting an Attribution Table on page 159

), the Bind

Attribute Table Columns to Output Columns dialog box appears. You must create a new column to contain the attribution data and define the properties of this new column. Follow these steps:

1. Click Modify/Add Columns to access the Modify Table Structure dialog.

2. Click Add Column to add a new column to the table. The Columns list box displays a new default 10-character column named Field# (where # is the column number in the table).

MapMarker 23

160

User Guide

Chapter 7:

Table Attribution with MapMarker

3. In the Column Information group, define the Name, Type, and Width of the new column containing the attributes. This column must have the same type and width as the attribution table column that you are pulling attributes from. Click OK when done editing the new column information. In this example, you have added a 25-character column named Attrib_Cnty

Add any additional output columns if necessary. Then click OK.

4. A prompt appears, informing you that the table must be closed and reopened to complete the update. Click Yes. The table is updated with the new column. This may take some time, depending on the size of the table. When the update is complete, the revised Bind Attribute

Table Columns to Output Columns dialog appears. This shows that the required output column has been added.

5. Click OK.

MapMarker 23

161

User Guide

Chapter 7:

Table Attribution with MapMarker

Your original geocoding table (US_ADDR.TAB in this example) now contains a blank Attrib_Cnty column that can store the attributes from your attribution table. You can view the added column using the table browser.

You are now ready to bind the attribute columns in your geocoding table to attribution table columns.

If you want to add attributes based on common geography, see

Binding Attributes – Output Point

Attribution on page 162

. If you want to add attributes using joined columns, see

Binding

Attributes – Column Value Attribution on page 163

.

You can do both types of attribution at the same time, provided you have selected the appropriate types of tables to use. Each attribution table you select can only be used for one type of attribution – either output point or column value.

Binding Attributes – Output Point Attribution

Output point attribution links the geocoded table to the attribution table by geography, specifically by matching latitude and longitude point coordinates within the geocoded table to a geographic boundary defined within the attribution table. For output point attribution, the attribution table must include a map object file (MAP).

1. To set up output point attribution:

2. After completing the procedure for

Creating a Column to Receive Attribution Data

), you will see the Bind Attribute Table Columns to Output Columns dialog.

If this dialog is not already open, select Table > Add Attributes > Select Attribute Files and click Next at the Select Attribute tables dialog. This will return you to the Bind Attribute Table

Columns to Output Columns dialog box.

From this dialog, use the Attribute Table Name drop-down list and select the table from which you want to copy attributes.

3. If necessary, click Output Point in the Join Information group.

4. From the list at the left, select the column in your table from which you want to pull attributes. For example, select the Ctyname column.

5. From the list at the right, select the output column into which you want to add attributes. For example, select the Attrib_Cnty column.

6. Click Bind to Column. The input column list box indicates the output column number to which the input column is bound.

MapMarker 23

162

User Guide

Chapter 7:

Table Attribution with MapMarker

Repeat this process for each output point attribution you wish to do. For each table you select, you can choose whether to do output point or column value attribution.

L

The Modify/Add Columns button may be disabled. If so, this is because the input and output columns have already been mapped. You cannot add or modify columns at this time. You can change the type of attribution (Output Point or Column Value) and change column bindings.

7. When finished, click OK.

You are now ready to add the bound attributes to your table. See

Adding Attributes to Your Table on page 164

.

Binding Attributes – Column Value Attribution

Column value attribution matches (joins) a column in the geocoded table to an equivalent column in the attribution table. The column in the attribution table must be indexed. (That is, there must be an

IND file to accompany the DAT file.)

To set up column value attribution:

1. After completing the procedure for

Creating a Column to Receive Attribution Data

), you will see the Bind Attribute Table Columns to Output Columns dialog. From this dialog, use the

Attribute Table Name drop-down list and select the table from which you want to copy attributes.

2. Click Column Value in the Join Information group.

3. In the Attribute Table Column drop-down list, select the column in the attribution table that you want to join to the output table.

4. In the Output Table Column drop-down list, click the column in the output table that you want to join to the attribution table.

MapMarker 23

163

User Guide

Chapter 7:

Adding Attributes to Your Table

5. In the Characters used in comparison box, type the number of characters you want MapMarker to use in determining a match between the joined attribute and output columns.

6. In the input table list box at the bottom left of the dialog, select the column in the attribute table from which you want to pull attributes. For example, select the PostCode column.

7. In the output table list box at the bottom right of the dialog, select the column in your geocoded table into which you want to add attributes. For example, select the ZIPCode column. (You may need to add this column if it does not already exist.)

8. Click Bind to Column. The input column list box indicates the output column number to which the input column is bound.

Repeat this process for each column value attribution you wish to do. For each table you select, you can choose whether to do output point or column value attribution.

9. When finished, click OK.

You are now ready to add the bound attributes to your table. You can do this by geocoding the table or by adding attributes via a batch process. See

Adding Attributes to Your Table

.

Adding Attributes to Your Table

Once you have bound your attribute and output table columns (see

Binding Attributes – Output

Point Attribution on page 162

) or

Binding Attributes – Column Value Attribution on page 163

), you are ready to add attributes to your table. One means of doing attribution is by geocoding your table (see

Adding Attributes By Geocoding

). You can also add attributes using a batch process

(see

Adding Attributes Using Batch Process

), which is done without geocoding the table.

Output point attribution must be done on a table either during a geocoding run or by a batch process using a table that has already been geocoded. Column value attribution can be done prior to, during, or after geocoding.

MapMarker 23

164

User Guide

Chapter 7:

Adding Attributes to Your Table

Adding Attributes By Geocoding

When you geocode the table, each record in your table is opened and processed. At this time,

MapMarker also pulls the attributes defined from the attribution table columns you specified when setting up attribution, and inputs those attributes into your table’s target column(s).

For information on geocoding your table, see

Geocoding with MapMarker in Chapter 3 on page 42

.

Adding Attributes Using Batch Process

You can use a batch process to add attributes to your table any time after setting up attribution.

When you batch add attributes, MapMarker uses the table joins and bindings that you defined when setting up attribution, copies the matched attributes from the attribution table(s), and adds them to your table in the column(s) you specified.

Batch attribution is generally faster than geocoding with attribution enabled.

To batch add attributes:

1. If it is not already open, open the MapInfo table.

2. Select Table > Add Attributes > Batch Add Attributes.

The Updating Table process indicator appears and automatically closes once attribution is complete.

Stopping Attribution

Once attribution is set up for your table, MapMarker does attribution on your table every time you geocode until you instruct it to stop. Attribution is enabled every subsequent time you open the table as well, until you manually stop attribution for the table. Stopping attribution does not remove the attribution information for the table, rather, it stops any further attribution for the table while it is open in MapMarker. To completely remove all attribution information for the table, see

Clearing Attribute

File Selections

.

To stop table attribution:

1. If it is not already open, open the MapInfo table.

2. Select Table > Add Attributes > Stop Attribution.

When you stop attribution, MapMarker no longer does attribution on the table while the table is open, but the attribution settings are still defined within your table’s metadata. You can view the metadata by opening the a TAB file in a text editor.

The attribution information is located at the bottom of the metadata, and resembles the following:

"\MapMarker\AddAttributes" = ""

"\MapMarker\AddAttributes\InputTables" = "1"

"\MapMarker\AddAttributes\Layer0" = "c:\program files\mapinfo\mapmarker\sampdata\cntydemo.tab"

"\MapMarker\AddAttributes\Layer0\BindOnPoint" = "1"

"\MapMarker\AddAttributes\Layer0\Attribute0" = "Ctyname County_nam"

MapMarker 23

165

User Guide

Chapter 7:

Adding Attributes to Your Table

"\MapMarker\AddAttributes\Layer0\AttributeCount" = "1"

Clearing Attribute File Selections

If you decide that you do not want to perform attribution for your table, you can clear the attribute file selections for your table. The table is no longer set up for attribution. When you clear attribute file selections, all attribution information in your table’s metadata is removed permanently. If you want to do attribution on your table in the future, you must configure new attribution settings for your table

(See

Table Attribution with MapMarker on page 157

for the basic steps to setting up and doing attribution.)

To clear attribute file selections:

1. If it is not already open, open the MapInfo table.

2. Select Table > Add Attributes > Clear File Selections.

If you want to stop the attribution process without removing the attribution metadata from your table, see

Stopping Attribution on page 165

.

Tips for Using Attributions

Consider the following when using attributes:

• The Add Attributes feature is available only after you have selected the input and output columns for your geocoding table.

• Do not open the attribution table in MapMarker. As long as you provide the path in the Select

Attribute Tables dialog, MapMarker is able to retrieve information from it.

• Attribution can be done on any local table that MapMarker can geocode. Attribution can also be

used in a batch geocoding session, for example, for overnight processing. See

Batch

Geocoding on page 153

, for instructions on setting up a batch operation.

• MapMarker does not output attributes to columns that have already been selected as input columns or output columns. Generally, you should create a new column to receive attribution

data. See

Creating a Column to Receive Attribution Data on page 160

.

• For a column value match, the matching column in the attribute table must be indexed. In addition, the values in the columns must be an exact match. This can be controlled by defining the number of characters required for an exact match in the Bind Attribute Table Columns to

Output Columns dialog. See

Binding Attributes – Column Value Attribution on page 163

for

more information.

• For output point attribution, the attribution table must include a map object file (MAP). The table you are geocoding must contain longitude and latitude values, not just the point object. The

coordinates can be obtained during the same geocoding/attribution pass. See

Binding

Attributes – Output Point Attribution on page 162

for more information.

• For proper storage of attributes, consider the type and length of attribute fields you are working with. The column type/length for the attribute and output columns display in the Bind Attribute

Table Columns to Output Columns dialog. For example, a 15-character value in the attribution table is truncated if the output column can only accept 10 characters. Character values stored as numerics in the attribute table may not display as expected in the output table.

• If MapMarker finds a duplicate match in the attribution table, it takes the attributes from the first record it finds.

MapMarker 23

166

User Guide

Geocoding Remote

Tables

In addition to geocoding MapInfo native format (TAB) and other supported table

formats as described in

Supported File Formats

, MapMarker can geocode tables that are stored on remote database systems. MapMarker geocodes remote relational databases via ODBC, an open database connectivity standard. MapMarker uses ODBC to access the data and store the resulting geocoding data and spatial object remotely. This ensures that data integrity and security are maintained.

The general process of geocoding these databases is the same as for local tables, but this chapter covers the information specific to remote table geocoding.

In this chapter

Š

Supported Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

Š

Remote Tables and Spatial Objects . . . . . . . . . . . . . . . . . . . . . . .168

Š

Preparing to Geocode Remote Databases. . . . . . . . . . . . . . . . . .169

Š

Accessing a Remote Table for Geocoding . . . . . . . . . . . . . . . . .170

Š

Writing Geocoding Output to Another Table . . . . . . . . . . . . . . . .172

Š

Additional Considerations for Remote Table Geocoding. . . . . .177

8

Chapter 8:

Supported Databases

Supported Databases

MapMarker 23 supports the following ODBC databases and drivers.

• SQL Server

• Microsoft Access

• Oracle

For a list of ODBC databases supported by MapMarker (including Microsoft Access, Oracle, and

SQL Server) see your product-specific MapMarker Release Notes.

The SQL Server and MS Access drivers are installed with MDAC 2.8.

You must install the Oracle driver separately. To use the driver, you must have the Oracle client installed.

Remote Tables and Spatial Objects

MapMarker supports remote database geocoding via ODBC for relational database management systems (RDBMS). The RDBMS stores coordinates in X,Y columns. The RDBMS stores the geocoded spatial object directly.

See the following topics:

Mappable Tables and the MapInfo Map Catalog on page 168

Supported Spatial Index Types on page 168

Mappable Tables and the MapInfo Map Catalog

This section describes the mappable tables and the MapInfo Map Catalog, features that are an integral part of remote geocoding with MapMarker.

A mappable table is a table of data that has its spatial information recorded in the MapInfo Map

Catalog. Mappable tables are managed by the MapInfo Map Catalog. MapMarker reads the Map

Catalog each time you geocode a remote mappable table to know how to handle the spatial object.

A Map Catalog is optional for X,Y databases. The MapInfo Map Catalog must have an entry for each table in the database that you wish to geocode.

We recommend that you create your Map Catalog and make a table mappable within MapInfo

Professional. Specific tools and commands are provided there for this purpose.

If, however, you do not have access to MapInfo Professional, you can do these procedures

manually. See

Creating a Map Catalog Manually

.

Supported Spatial Index Types

MapMarker supports X,Y (for Oracle, SQL Server, and Microsoft Access). This is shown in the Map

Catalog under the column SPATIALTYPE for X,Y.

MapMarker 23

168

User Guide

Chapter 8:

Preparing to Geocode Remote Databases

Preparing to Geocode Remote Databases

Before you can geocode your remote table with MapMarker, you (or the database administrator) must set up MapMarker and your database to handle the geocoding operation. In general, the process follows these steps:

1. Create a data source for the RDBMS (see

Creating a Data Source on page 169

).

2. Prepare the remote table with the appropriate columns and spatial handling requirements (see

Preparing the Remote Table on page 169

).

3. Create a Map Catalog for each remote database (see

Creating a Map Catalog on page 170

).

4. Make the remote table mappable (see

Making a Remote Table Mappable on page 170

).

See the following topics:

Creating a Data Source on page 169

Preparing the Remote Table on page 169

Creating a Map Catalog on page 170

Making a Remote Table Mappable on page 170

Creating a Data Source

After the drivers are installed, create a data source for your database. Use the ODBC Administrative

Tools in the Control Panel for this purpose.

L

Under Microsoft VISTA Ultimate Edition, you must have Administrator privileges to create an

ODBC data source.

To create an ODBC data source, follow these steps:

1. From Control Panel > Administrative Tools, double-click Data Sources (ODBC) to display the

ODBC Data Source Administrator dialog. Under the User DSN tab, click Add.

2. At the Create New Data Source dialog, choose the appropriate driver. Click Finish. The ODBC

Setup dialog is displayed. The dialog differs depending on your database.

3. Fill out the dialog per your needs and click OK. Select allows you to associate a specific database with the data source.

4. Return to the ODBC Data Source Administrator dialog and click OK.

Preparing the Remote Table

You or your database administrator must add columns to the table to store the results of the geocoding operation. For the X,Y spatial index type, there must be one column for longitude values and another column for latitude values. The longitude and latitude columns should be decimal type

(11,6 or larger) or float. See

Output Column Type/Width Requirements

.

MapMarker 23

169

User Guide

Chapter 8:

Accessing a Remote Table for Geocoding

In addition, you may wish to add a column to your table for storing the result code that MapMarker generates. The result code describes the type of geocoding match that was attempted.

If you plan to write geocoding output to another table, provide those columns as well. See

Writing

Geocoding Output to Another Table

for more information.

Creating a Map Catalog

Create a Map Catalog for each remote database you want to access in MapMarker. In MapInfo

Professional, run the utility MIODBCAT.MBX from the Run MapBasic Program command. For complete details see the topic on Accessing Remote Data in the MapInfo Professional Help System.

If you are not using MapInfo Professional, you must create the Map Catalog manually, as described

in

Creating a Map Catalog Manually

. This process only needs to be done once for each database.

Making a Remote Table Mappable

For each spatial table in the remote database that you want to access in MapMarker, you must include it as a row in the MAPINFO_MAPCATALOG table. This is carried out in MapInfo

Professional when you select Table > Maintenance > Make ODBC Table Mappable. For details, see the appropriate topic in the MapInfo Professional User Guide.

If you do not use MapInfo Professional to manage the Map Catalog, you must manually add rows to the MAPINFO_MAPCATALOG table for each spatial table in the database that you want to geocode.

See

Creating a Map Catalog Manually

for further instructions.

Accessing a Remote Table for Geocoding

1. After your remote database is prepared for geocoding, you are ready to open it in MapMarker and begin geocoding. Follow these steps.

2. If you have specified that the File Open dialog display at startup for ODBC tables (set in System

Preferences), the Select Data Source dialog is displayed automatically when you start

MapMarker.

Otherwise, select File > Open ODBC Table or click to display the Select Data Source dialog.

3. Click the Machine Data Source tab.

MapMarker 23

170

User Guide

Chapter 8:

Accessing a Remote Table for Geocoding

4. Choose your data source. Your data source is the location of the specified database. For example, Access Files could be the name of the data source for one or more Microsoft Access tables located in a specified directory. Once connected to the Access Files data source, you can get information from any Access table.

5. Sign on to your data source in the usual way. This procedure differs depending on what type of

ODBC table you are using.

6. Choose the table you want to access from the Select Table dialog. Each of the tables owned by you or accessible to you is listed.

L

Remember that you cannot open any other tables while you have an ODBC table open.

7. Proceed with geocoding as you would with any other MapInfo table (see

Geocoding Your Table

Automatically

and

Geocoding Your Table Interactively

). The procedure is the same as geocoding local tables, with the exceptions explained in the following topics.

Editing Records Interactively

Editing Records Interactively

In interactive geocoding, you can edit the information in the Input Address fields of the source table, as long as the table is a local table. This enables you to improve the possibility of a match. If you choose, you can also write these edits to the table using the options in the Interactive Geocode dialog.

However, when you geocode a remote table interactively, MapMarker cannot overwrite the Input

Address fields of the source table. So when you are geocoding a remote table, the Write modified

address above to Input Fields on Geocode check box in the Interactive Geocode dialog is unavailable.

MapMarker 23

171

User Guide

Chapter 8:

Writing Geocoding Output to Another Table

Writing Geocoding Output to Another Table

MapMarker can geocode a remote database table and write the results to a table. Often database administrators do not want users to modify or write back to the source table, because of the potential of introducing errors into the database. In that case the database administrator can set up a related table to store the geocoding results and other output information. During geocoding MapMarker reads the input addresses from the source table and writes the results of the operation to the related results table.

L

To avoid overwriting your input data, use output columns that have different names than the corresponding input columns. If your output columns and input columns have the same name, you receive a Warning message telling you that your input data will be modified when geocoding. You can then click Yes to Continue and overwrite your input data or click No if you want to change your output column selections.

See the following topics:

Relationship Between Source and Results Tables on page 173

Setting Up for Related Table Geocoding on page 173

Remote Table-to-Table Geocoding on page 173

Optimizing MapMarker for Related Table Geocoding on page 176

MapMarker 23

172

User Guide

Chapter 8:

Writing Geocoding Output to Another Table

Remote Database Views on page 176

Related Table Considerations on page 176

Relationship Between Source and Results Tables

The source and results tables must be linked by a common key. In the source table, the values of the primary key must match the values in the unique key of the results table. We recommend relating the tables in a one-to-one relationship. Each address record in the source table has a corresponding record in the related results table connected by the key values.

Where there is more than one record with the same address (a multiple-to-one relationship), these records may produce georesults that are written to one record. Each time MapMarker geocodes another address with the same value, it updates the output record in the results table. As long as each address record with the same key contains the same address, the output is identical. However, if two source records with the same key contain different address information, MapMarker geocodes the first record, writes its results, geocodes the second record, and updates the results with different information based on the different, and possibly incorrect, input address.

If your source table contains multiple unique keys, MapMarker prompts you to choose which keys are linked to the keys in the results table.

Setting Up for Related Table Geocoding

Prior to geocoding, the database administrator creates a table for geocoding results that is related to the source table. The table structure includes at least one key that uniquely identifies an address in the source table. In addition it contains fields for the geocoding results, and longitude and latitude coordinates. Other optional output fields include firm, street, city, ZIP Code, ZIP + 4, Carrier Route,

Delivery Point, Check Digit, and Census Block ID. See

Specify Output Address Columns

, for details on column type and width. Consult your database documentation for information on creating relational tables and primary keys.

The database administrator must also create a data source for the remote source/results tables. The data source must include information that enables MapMarker to determine which data to access and how to access it. See

Preparing to Geocode Remote Databases on page 169

for the instructions for setting up a data source.

Remote Table-to-Table Geocoding

1. Use this procedure to geocode a remote table and write the results to a related table:

2. In MapMarker, select File > Open ODBC Table.

3. In the Select Data Source dialog box, choose either the File Data Source or Machine Data

Source tab. Enter your user name and password if necessary. Click OK.

MapMarker 23

173

User Guide

Chapter 8:

Writing Geocoding Output to Another Table

4. In the Select Database dialog box, navigate to the source table that contains the addresses you want to geocode. Enter the password if your data source requires it. For example, an MS Access database selection might appear as:

For example, if you selected Machine Data Source and MS Access Database, you could navigate to the folder that contained your addresses.

Click OK.

5. In the Select Table dialog box, select the specific table that contains the addresses you want to geocode, then click OK. For example, an MS Access table selection might appear as follows:

6. You may be asked if you want to use a different table for output. Answer Yes if you want to write the geocoded results to a different table.

7. To write results to a different table, choose the data source for the output table. For example, you might select Add_Table_Out as the results table to contain the geocoding output. Click OK.

8. If your source table has multiple unique keys, the Describe Table Relationship dialog appears.

Proceed to

step 9

. If your table has only one key, the Select Input Column dialog appears. Skip

to

step 10

.

9. In the Describe Table Relationship dialog, select the address source columns and the corresponding columns with unique keys in the results table. In the Input Table list, select the input column and drag it to the Selected Input Columns box for Key 1. In the Output Table list, select the input column/key that is linked to the input column and drag it to the Selected Output

MapMarker 23

174

User Guide

Chapter 8:

Writing Geocoding Output to Another Table

Keys box for Key 1. Repeat for additional columns and keys. To remove a column name, drag the <Clear> item on top of them.

.

Click OK. The Select Input Column dialog appears.

10. In the Select Input Columns dialog, select the columns that contain the appropriate address components. Click Next. The Select Output Columns dialog is appears.

11. In the Select Output Columns dialog, identify the columns in the results table where MapMarker stores the result codes, coordinates, and output addresses.

12. Click Finish to close this dialog. The Geocode dialog appears if it is set to appear automatically in System Preferences. If the Geocode dialog does not appear, select Table > Geocode.

13. Select the Related Table tab and click either Optimize for insertion or Optimize for update.

Choose Optimize for insertion if your results table is new or contains few records. Choose

Optimize for update if your results table contains many records are likely to be updated.

14. Continue with the normal geocoding process by choosing options on the other dialog tabs

(Geocode, Match Settings, Fallback, etc.) See

Geocoding with MapMarker in Chapter 3 on page 42

.

L

When geocoding using multiple tables, the options, "Georesult less than" and "Unmatched rows" are not available on the Geocode tab. The option, "All types" is the only choice.

MapMarker 23

175

User Guide

Chapter 8:

Writing Geocoding Output to Another Table

Optimizing MapMarker for Related Table Geocoding

You may be writing the geocoding results to a new output table or may be updating previously geocoded records in an existing related table. To get the best performance from MapMarker, you can optimize for one situation over the other. In the Geocode dialog, choose from two settings in the

Related Table tab: Optimize for Insertion or Optimize for Update.

As a general rule, select Optimize for Insertion when the results table is empty or nearly so. Select

Optimize for Update when the results table already contains many records that are likely to be updated. The default setting is Insertion.

L

This feature does not apply to geocoding to a table in a remote database where the input and the output results are stored in the same table. In these instances, the Related Table tab is not visible in the Geocode dialog.

Remote Database Views

MapMarker enables you to geocode views of remote tables if you are writing the geocoding output to another table. A view is a subset of a table that is typically the result of a select statement. For example, you may create a view of a nationwide table that includes only records for California. Refer to your database documentation when creating views.

Once your view is created and you are ready to geocode, follow these steps: This example uses a machine data source

1. Select File > Open ODBC Table. The Data Source dialog is displayed.

2. From the Machine Data Source tab, choose the data source (such as DBF files or Excel files).

Click OK.

3. From the Select Table dialog, click Filter. Select the Views check box and click OK. The Select

Table dialog is displayed again with a list of views for the data source.

4. Choose the view that shows the input table and click OK.

5. Answer Yes to using a different table for the outputs from geocoding.

6. From the Select Table dialog, choose the view for the output table and click OK.

7. At the Select Input and Output Column dialogs, choose your columns and click OK.

8. Select Table > Geocode and proceed with the normal geocoding process. See

Geocoding with

MapMarker in Chapter 3 on page 42

, for complete information on the geocoding process.

Related Table Considerations

MapMarker can write geocoding results to remote related tables using MapMarker ODBC support.

All addresses must be contained in the source table, while all results must be written to a related results table.

MapMarker 23

176

User Guide

Chapter 8:

Additional Considerations for Remote Table Geocoding

You or your database administrator must be familiar with how the two tables are related. If the tables use multiple keys, you must set the relationship before starting any geocoding. Be familiar with your data and table structure to ensure the geocoding output results are valid.

Additional Considerations for Remote Table Geocoding

Consider the following when doing any type of remote table geocoding:

Sort by ZIP Code™ for Faster Geocoding on page 177

Geocoding Unmatched Records on page 177

Transaction Control with ODBC Tables on page 177

Remote Database Views on page 178

Rollback Segment Limit on page 178

Supported Unique Index and Primary Key Data Types by Database on page 178

Sort by ZIP Code™ for Faster Geocoding

MapMarker performance is best when it can access records sorted by ZIP Code. For local tables, therefore, we recommend that all tables for geocoding are sorted by ZIP Code prior to geocoding.

For remote tables, we recommend that the ZIP Code column be indexed for faster accessing. To add an index to a remote table, follow the instructions for your database.

Geocoding Unmatched Records

MapMarker can geocode unmatched records in previously geocoded remote tables instead of geocoding the entire table with every pass. After you select the input and output columns, go to the

Geocode dialog and set the types of rows to geocode to Unmatched Rows. MapMarker attempts to find a match for all records in your table that have a georesult of N or blank. MapMarker updates the log file to reflect the total number of records it attempted to geocode during the pass, not the total number of records in the table.

L

Geocoding unmatched records is not available for multi-table geocoding.

Transaction Control with ODBC Tables

MapMarker uses as non-obtrusive locking mechanism as possible when geocoding your ODBC table. It attempts to use the lowest level of locking available (for example, row, page or, at worst case, table locking). Locks are not placed until the row is geocoded. MapMarker issues a commit after each update so that each lock is held for an extremely short time (the time it takes to lock a row, update it, and commit it).

MapMarker 23

177

User Guide

Chapter 8:

Additional Considerations for Remote Table Geocoding

If MapMarker attempts to lock a row that is already locked, MapMarker follows the default behavior of the database. Usually this means waiting until that row is released. MapMarker does not use any deadlock detection beyond that provided by the database.

L

You are responsible for maintaining the relationship of the street address and the latitude/longitude for that address. For example, whenever you change any street address information, you must re-geocode that record.

If rows are deleted from your table after MapMarker opens the table, MapMarker reports an error when it tries to geocode that deleted row.

Remote Database Views

You may only geocode views of a remote table when you are doing a table-to-table geocode. See

Writing Geocoding Output to Another Table on page 172

, for more information.

Rollback Segment Limit

Be sure that you set your database rollback segment or temp space to be sufficiently large enough to accommodate the size of your database.

Supported Unique Index and Primary Key Data Types by Database

The following table identifies the supported data types by RDBMS. A Primary Key must also be defined for your table.

Char

Microsoft SQLServer

Float

Integer

SmallInt

Tinyint

Real

Varchar

Microsoft Access

Character

Number (double)

Number (Long Integer)

Number (Integer)

Number (Single)

N/A

N/A

Character

Number

Varchar

Varchar2

N/A

N/A

N/A

Oracle

If MapMarker encounters a mappable table with a spatial type it does not support, an error message is displayed and the table is not geocoded.

For a list of ODBC databases supported by MapMarker (including Microsoft Access, Oracle, and

SQL Server) see your product-specific MapMarker Release Notes.

MapMarker 23

178

User Guide

Custom User

Dictionaries

MapMarker supports the creation and use of custom User Dictionaries based on your own source data. A User Dictionary can be used independently or as a supplement to the supplied Address Dictionary.

This chapter includes information on creating User Dictionaries, source data requirements and required fields, and other information specific to working with

User Dictionaries.

As part of the Desktop Application, MapMarker provides a User Dictionary wizard to simplify user dictionary creation in the desktop application.

In this chapter

Š

What Is a Custom User Dictionary? . . . . . . . . . . . . . . . . . . . . . . .180

Š

User Dictionary Capabilities and Requirements . . . . . . . . . . . . .180

Š

User Dictionary File Names and Formats . . . . . . . . . . . . . . . . . .183

Š

Additional User Dictionary Considerations . . . . . . . . . . . . . . . . .183

Š

Creating a Custom User Dictionary . . . . . . . . . . . . . . . . . . . . . . .185

Š

Preferring User Dictionary Matches . . . . . . . . . . . . . . . . . . . . . . .188

9

Chapter 9:

What Is a Custom User Dictionary?

What Is a Custom User Dictionary?

A custom User Dictionary is a table of streets and address ranges that you use as a source for geocoding. If you have newer or more precise data than what is available in the MapMarker Address

Dictionary, creating a dictionary with this data can help you get more accurate geocoding results. For example, if you have address point data you can create a User Dictionary that enables you to take advantage of the MapMarker address point interpolation capabilities.

A User Dictionary can be used by itself to geocode records, or can be used in combination with the supplied Address Dictionary.

User Dictionary Capabilities and Requirements

The capabilities of User Dictionaries and the basic requirements for creating them are as follows.

• All fields supported by normal street geocoding can be included in User Dictionaries.

• Points Of Interest (POI) geocoding is supported in User Dictionaries. Postal or geographic centroid geocoding are not supported in User Dictionaries.

• User Dictionaries support address browsing using partial street names or Points of Interest.

• An Address Dictionary is required to create the User Dictionary. This is because the MapMarker

Address Dictionary has some internal structure that must be available when you are creating a

User Dictionary.

The results from a User Dictionary are similar to that from the MapMarker Address Dictionary. The only difference appears in the georesult code. A candidate from a User Dictionary has a ‘U’ at the end of the georesult code. A candidate that comes from the MapMarker Address Dictionary has an

‘A’ at the end of the georesult code.

For example: S5HPNTSCZA is a result code that comes from an Address Dictionary, while

S5HPNTSCZU comes from a User Dictionary. See

Chapter 6: Result Codes

for a complete description of result codes.

User Dictionary Only Requirements

If you are using a User Dictionary exclusively (without an accompanying standard Address

Dictionary), several supporting files are required in the UD directory. For example, if you created a

User Dictionary in:

C:\Program Files\MapInfo\MapMarker_USA_v23\MapMarker_USA_v23_data\MYUD and you are using the User Dictionary exclusively, then either you must still provide the Address

Dictionary path or add the following files to the User Dictionary directory.

ctyst.dir (USPS City State table) parse.dir

us.z9 file (required if you want to do ZIP centroid geocoding)

These files are installed in your data directory (MapMarker_USA_v23_data). Copy them to the appropriate User Dictionary directory.

MapMarker 23

180

User Guide

Chapter 9:

User Dictionary Capabilities and Requirements

Source Data Requirements

The source data for User dictionaries includes street data but can also include place names and intersections.

To create a User Dictionary, your source data must conform to the following requirements:

• Source records must include required fields, and these fields are mapped during the User

Dictionary creation process. If a value of a required field is empty for a particular record, then that record will not be imported into the User Dictionary. Required fields may vary for different countries. The MapInfo table must contain specific fields, which MapMarker then uses to convert

the table into the dictionary format. These input fields are described in

Required Input Fields on page 181

.

• Source records must be in a MapInfo table (TAB file). The TAB file requirements will vary for different countries.

• Segments that make up intersections must have one or more endpoints in the intersection for

MapMarker to recognize it as an intersection.

• Source records can be either point objects or segments.

• Each row in the table is equivalent to a street segment.

Required Input Fields

You must specify the field names in the MapInfo table (TAB file) in order for the table to be translated into a User Dictionary. Certain fields are required and must be present in the MapInfo table. Other fields are optional, but are strongly recommended because there may be negative consequences if

they are omitted. This is described in

Optional (Recommended) Input Fields on page 182

. If any of the required fields are missing, a missing field error code is returned.

The following table describes the required input fields.

Required Fields

Left Start Address

Right Start Address

Left End Address

Right End Address

Street Name

State Abbreviation

Left ZIP Code

Right ZIP Code

Description

Start of address range on left side of street

Start of address range on right side of street

End of address range on left side of street

End of address range on right side of street

Name of street

Two-character state abbreviation

ZIP Code for left side of street

ZIP Code for right side of the street

2

5

5

10

10

10

30

Maximum

Field Length

10

MapMarker 23

181

User Guide

Chapter 9:

User Dictionary Capabilities and Requirements

Optional (Recommended) Input Fields

The Left and Right Odd/Even Indicator fields are used to specify whether the sides of the street segment contain odd or even address ranges. Although these indicators are not required for creating a User Dictionary, it is important to use the Odd/Even Indicators when your data contains odd/even address numbers.

When the Odd/Even Indicator is specified, but is inconsistent with address numbers, the indicator is set to Both.

When the Odd/Even Indicator is not specified and both Start Address and End Address have values, the indicator is set to Both, unless the start and end address numbers are the same number. In that case, the indicator is set to Odd if the address numbers are odd, and set to Even if the address numbers are even.

When the Odd/Even Indicator is not specified and both Start Address and End Address have values, the indicator is set to Both (odd and even).

L

If your table contains odd/even indicator information, we strongly recommend that you use the Odd/Even indicator fields. These fields ensure that your geocoded addresses are located on the correct side of the street. Omitting the fields when your data contains odd/even information may produce incorrect results.

The following table describes the optional input fields.

Optional Fields Description

Left Odd/Even indicator * Left side of the street contains only odd or even address ranges (O=odd, E=even, B=both)

1

Maximum

Field Length

Right Odd/Even indicator

*

Right side of the street contains only odd or even address ranges (O=odd, E=even, B=both)

1

City

*

City name 28

4-digit ZIP + 4 add-on for left side of street 4

Left ZIP + 4

®

Code

Right ZIP + 4 Code

Left Census Block

4-digit ZIP + 4 add-on for right side of street

Census Block ID for left side of street

Right Census Block

Place Name

Census Block ID for right side of street

Place name

* These fields are highly recommended.

4

15

15

40

MapMarker 23

182

User Guide

Chapter 9:

User Dictionary File Names and Formats

User Dictionary File Names and Formats

MapMarker has some requirements for User Dictionary files that you must be aware of before you create a User Dictionary:

• Each User Dictionary has a base name of eight characters or fewer.

• Each User Dictionary must reside in its own directory.

• The maximum length of a path to a User Dictionary is 1024 characters.

• The maximum length of the paths to multiple User dictionaries is 1024 characters.

• The ZIP Code™ range in the MapInfo table for a User Dictionary is unlimited.

Because each User Dictionary resides in its own directory, User dictionaries may share the same name. However, it is generally good practice to use a unique name for each User Dictionary.

Some of the output files are tied to the base name. The other output files have constant names. For example, the output files for a dictionary called ud1 are the following: postinfo.jdr

postinfo.jdx

lastline.jdr

post2sac.mmj

geo2sac.mmj

sac2fn_ud.mmj

ud1.jdr

ud1.jdx

ud1.bdx

If your data includes placenames, the dictionary contains the following files: ud1.pdx

ud1.pbx

The dictionary also contains these log files: ud1.log

ud1.err

Additional User Dictionary Considerations

Consider the following when working with custom User dictionaries.

Data Access License on page 184

CASS Standards on page 184

Address Range Order on page 184

Street Intersections and Customized User Dictionaries on page 184

MapMarker 23

183

User Guide

Chapter 9:

Additional User Dictionary Considerations

Data Access License

You must still have a valid access license to the data contained in the MapMarker Address

Dictionary when you are geocoding against your custom User Dictionary. For example, if you create a dictionary of New York streets and addresses, you must purchase the New York or entire U.S.

MapMarker Address Dictionary.

CASS Standards

You cannot geocode to CASS standards using a custom User Dictionary. This also means that the

ParcelPrecision Dictionary cannot be used during CASS geocoding. Other available point address dictionaries (such as Centrus

®

Points and Tele Atlas

®

Points) can be geocoded using CASS.

Address Range Order

MapMarker determines the order of the address range based on a comparison of the start and end addresses. The comparison produces the following results:

• If the end is greater than the start, the range is ascending

• If the start is greater than the end, the range is descending

• If the start is equal to the end, the range is ascending

Street Intersections and Customized User Dictionaries

When geocoding to street intersections with a custom User Dictionary, MapMarker cannot recognize the intersections if one or more of the segments that make up the intersection does not have an endpoint at the intersection. This can happen when you create the User Dictionary from a customized street table in which some segments that terminate at intersections do not have endpoints (Example 1).

MapMarker 23

184

User Guide

Chapter 9:

Creating a Custom User Dictionary

Example 1: Intersection in custom User Dictionary does not have endpoints for all segments.

MapMarker does not recognize this as an intersection.

Example 2: Intersection in TIGER-based Address Dictionary includes endpoints for all segments.

MapMarker geocodes to this intersection.

Creating a Custom User Dictionary

In the MapMarker Desktop Application, use the User Dictionary Wizard to create a User Dictionary.

L

If you installed the MapMarker Developer Edition, you can also use the MapInfo User

Dictionary Utility that is provided with the Server product. See the MapMarker 23 Developer

Guide for detailed information and instructions on using this Utility.

Using the MapMarker User Dictionary Wizard

The Desktop Application includes a wizard to walk you through the user dictionary creation process.

To create a user dictionary:

1. Choose File > Create User Dictionary. The User Dictionary Wizard (Step 1 of 3) dialog appears.

2. Specify the path and filename of the MapInfo table from which address information is to be derived. Alternatively, click the Browse button to reach the desired location of the table.

3. Specify how much of the table you wish to include in the dictionary by specifying the row numbers or leave All Rows selected.

4. Click Next to continue. The User Dictionary Wizard (Step 2 of 3) dialog appears.

MapMarker 23

185

User Guide

Chapter 9:

Creating a Custom User Dictionary

5. Specify the required fields in the street table by highlighting a field name in the list box and dragging it to the appropriate box in the address groups. Note that you must fill in all the fields in the dialog.

When selecting the state field choose the field that contains the two-letter state abbreviation. Do not use the 2-digit FIPS code field as the state field.

6. To clear any box, highlight <CLEAR> in the list and drag it over the column name you wish to delete.

7. Click Next to continue. The User Dictionary Wizard (Step 3 of 3) dialog appears.

8. Specify any optional fields for City, ZIP + 4

®

, Census Block, Odd/Even Indicator, or place name columns you wish to include in the dictionary. Including the Odd/Even Indicator allows for better

MapMarker 23

186

User Guide

Chapter 9:

Creating a Custom User Dictionary

placement of address points when geocoding. A place name is a point object, rather that a street segment. Examples include Sears Tower, Wrigley Field, or City Hall.

9. Click Finish to proceed or Back to revisit the previous dialogs. When you click Finish the Save

User Dictionary As dialog appears.

10. Specify the name and location of the User Dictionary. and save in its own folder. For example, you could create a UD folder under

C:\Program Files\MapInfo\MapMarker_USA_v23\data\TroyUD

Save the newly created User Dictionary in this folder. This folder must be initially be empty.

11. Click Save. When the progress bar indicates that the User Dictionary is created, click Done.

Adding the User Dictionary to the Desktop Application

After creating a User Dictionary, you must add the dictionary so that it can be used by the Desktop

Application.

You can also specify system preferences for:

• User Dictionary (or multiple User Dictionaries) alone

• Standard MapMarker Address Dictionary

• A combination of Address Dictionary and User Dictionaries

In the Desktop Application, these preferences are found in the Dictionary tab of the System

Preferences dialog. If you select the User Dictionary, you can also control the search priority of User

Dictionaries (if dictionaries overlap in their coverage.)

1. Choose Options > System Preferences and select the Dictionary tab. Select the Use User

Dictionary check box and Browse for the directory in which you created the User Dictionary.

Add this directory to the Selected Directories column and click OK,

MapMarker 23

187

User Guide

Chapter 9:

Preferring User Dictionary Matches

2. Check Use User Defined Dictionary to enable the User Dictionary.

3. Click the Browse button associated with the User Dictionary and in the Choose Directories dialog, use the Up and Down arrow keys to adjust the search order of User Dictionaries. User dictionaries at the top of the list are given higher priority. This is important if two or more User

Dictionaries overlap in coverage. For example, you may have two User Dictionaries that provide coverage of the same city, but one dictionary provides point coverage and the other dictionary offers address coverage only. In the following example, there is only one User Dictionary, so no change is required.

4. Click OK in the Choose Directories dialog.

5. Click OK in the System Preferences dialog.

Preferring User Dictionary Matches

You can geocode using:

• User Dictionary (or multiple User Dictionaries) alone

• Standard MapMarker Address Dictionary

• A combination of Address Dictionary and User Dictionaries

The results from a User Dictionary are similar to that from the MapMarker Address Dictionary. The only difference appears in the georesult code. A candidate from a User Dictionary has a ‘U’ at the end of the georesult code. A candidate that comes from the MapMarker Address Dictionary has an

‘A’ at the end of the georesult code.

MapMarker 23

188

User Guide

Chapter 9:

Preferring User Dictionary Matches

For example: S5HPNTSCZA is a result code that comes from an Address Dictionary, while

S5HPNTSCZU comes from a User Dictionary. See

Chapter 6: Result Codes

for a complete description of result codes.

In the Desktop Application, use the Match Settings tab of the Geocode dialog to specify whether you prefer User Dictionary matches (or Address Dictionary matches.) If you check Prefer User Dictionary

Matches, the User Dictionary will be used in preference to the Address Dictionary. Otherwise, the

Address Dictionary is preferred.

If Prefer User Dictionary Matches is selected, the User Dictionary is used in preference to the

Address Dictionary for geocoding.

If more than one User Dictionary can be used, the priority is determined in the Desktop Application

by the order listed in the Dictionary tab of the System Preferences dialog. See

step 3

in the topic

Adding the User Dictionary to the Desktop Application

.

MapMarker 23

189

User Guide

MapMarker User

Interface Reference

This appendix has reference information for the various dialogs, buttons, and menu commands in the MapMarker user interface.

In this appendix:

Š

MapMarker Menu Commands and Toolbar Buttons . . . . . . . . . .191

Š

MapMarker Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

A

Appendix A:

MapMarker Menu Commands and Toolbar Buttons

MapMarker Menu Commands and Toolbar Buttons

This section describes the various buttons and menu commands in MapMarker and what they are used for. The topics are organized in alphabetical order by button/command name. Use the list below to locate the description of the button or menu command you wish to learn about.

•

About MapMarker command on page 192

•

Arrange Icons command on page 192

•

Batch Add Attributes command on page 192

•

Cascade command on page 192

•

Choose Font command on page 192

•

Clear File Selections command on page 193

•

Close command on page 193

•

Close Project command on page 193

•

Create Batch File command on page 193

•

Create Project-based Batch File on page 193

•

Create/Save Project command on page 194

•

Create User Dictionary command on page 194

•

Exit command on page 194

•

Export to ESRI Shapefile on page 194

•

Geocode command on page 195

•

Help Topics command on page 195

•

Locate Airport command on page 195

•

Locate Highway Exit command on page 195

•

Logfile command on page 195

•

MapMarker on the World Wide Web command on page 196

•

Open Browser List command on page 196

•

Open ODBC Table command on page 196

•

Open Project command on page 196

•

Open Table command on page 197

•

Quick Find command on page 197

•

Quick Geocode command on page 197

•

Recent File List command on page 198

•

Select Attribute Files command on page 198

•

Select Columns command on page 198

•

Status Bar command on page 198

•

Stop Attribution command on page 198

•

Submit Problem Report to Technical Support command on page 199

•

Summary command on page 199

•

System Preferences command on page 199

•

Table Summary command on page 199

•

Tile command on page 200

•

Toolbar command on page 200

MapMarker 23

191

User Guide

Appendix A:

MapMarker Menu Commands and Toolbar Buttons

About MapMarker command

About MapMarker displays the About MapMarker message box. This message box has information about your copy of MapMarker, including the product version number, data vintage, copyright, legal, and licensing information and the serial number for the licensed user of the product. About

MapMarker is available when MapMarker is running.

To view your MapMarker information:

• On the Help menu, click About MapMarker.

Arrange Icons command

Arrange Icons arranges all minimized browser windows into rows along the bottom of the

MapMarker workspace. Arrange Icons is always available when MapMarker is running and there is at least one table open.

To arrange your minimized windows:

• On the Window menu, click Arrange Icons.

Batch Add Attributes command

Batch Add Attributes allows you to add attributes from one table to another without geocoding the table at the same time. Batch Add Attributes is available when a table is open, input and output columns for geocoding have been selected, and the attribute table(s) have been identified.

To use Batch Add Attributes:

• On the Table menu, point to Add Attributes, and then click Batch Add Attributes.

Cascade command

Cascade arranges open windows in an overlapping pattern so that the title bar of each window is visible. Cascade is always available when MapMarker is running and there is at least one table open.

To cascade your open windows:

• On the Window menu, click Cascade.

Choose Font command

Choose Font allows you to select a font, font style and font size for the text in the Browser window.

Choose Font is always active when MapMarker is running.

To choose font settings:

• In the Options menu, click Choose Font.

MapMarker 23

192

User Guide

Appendix A:

MapMarker Menu Commands and Toolbar Buttons

Clear File Selections command

Clear File Selections deletes the attribute settings stored in a table’s metadata. Clear File Selections is available when a table is open and attribute settings exist.

To delete a table’s attribute settings:

• In the Table menu, point to Add Attributes, and then click Clear File Selections.

Close command

Close allows you to close a table. Close is available when at least one table is open.

To close a table, do one of the following:

• In the File menu, click Close.

• Click in the table window.

Close Project command

To close a project, do the following:

• In the File menu, click Projects, then Open Projects.

Create Batch File command

Create Batch File allows you to save a text file containing instructions for MapMarker to carry out a batch geocoding session. Create Batch File is available when at least one table is open.

To create a batch file, do one of the following:

• In the Table menu, click Create Batch File.

• Click the right mouse button to display a shortcut menu, then click Create Batch File.

Create Project-based Batch File

Create Project-based Batch File allows you to create MapMarker projects (PROJ) files and to batch geocode TXT files (delimited or fixed-width). Batch geocoding of a TXT file can only be done by done through a project.

To create a project-based batch file, do one of the following:

• On the File menu, click Create/Project-based Batch File.

• Click the right mouse button to display a shortcut menu, then click Create/Project-based Batch

File.

MapMarker 23

193

User Guide

Appendix A:

MapMarker Menu Commands and Toolbar Buttons

Create/Save Project command

Create/Save Project allows you to save a MapMarker project file with all saved geocoding settings, column mappings, table attributes settings, and some system preferences. These project file

settings will be used when the project is re-opened with the

Open Project command

. The project file settings override any of the existing metadata settings in the TAB file.

To save a project file, do the following:

1. In the File menu, click Projects, then Create/Save Project.

2. In the Save Project File As dialog box, type a name for the project. A PROJ file extension is used.

Create User Dictionary command

Create User Dictionary allows you to create a customized user address dictionary from a MapInfo street table using the User Dictionary Wizard. This dictionary can be used in place of, or along with, the purchased MapMarker Address Dictionary when geocoding your records. Create User

Dictionary is available when MapMarker is running and no tables are open.

To start the User Dictionary Wizard:

• In the File menu, click Create User Dictionary.

Exit command

Exit allows you to quit MapMarker. Exit is active when MapMarker is running.

To exit MapMarker, do one of the following:

• In the File menu, click Exit.

• Click in the MapMarker window.

Export to ESRI Shapefile

The Export to ESRI Shapefile command allows you to export TAB, DBF, CSV, and TXT files to ESRI

Shapefile (SHP) format.

To export to ESRI Shapefile, do the following:

1. In the Table Menu, click Export to ESRI Shapefile. (A table must already be open.)

2. In the Export To dialog, select a file name for export. The SHP file extension is automatically selected for ESRI Shapefiles.

3. In the Export to ESRI Shape dialog, select the columns or points that contain the geometry information and click Export.

MapMarker 23

194

User Guide

Appendix A:

MapMarker Menu Commands and Toolbar Buttons

Geocode command

Use Geocode to specify the geocoding settings you want to use, including run type (automatic or interactive geocoding), street-level or ZIP Code™ centroid match, match settings, fallback settings, and CASS geocoding setup. Geocode is available when a table is open and you have selected the input and output columns for that table.

To specify your geocoding settings, do one of the following:

• In the Table menu, click Geocode.

• Click In the MapMarker toolbar.

• Click the right mouse button to display a shortcut menu, then click Geocode.

Help Topics command

Help Topics displays the main entry topic for the MapMarker Online Help system. Help Topics is always available when MapMarker is running.

To display the online Help, do one of the following:

• In the Help menu, click Help Topics.

• Press the F1 key for a command or dialog for which you need more information.

• Click in a dialog.

• Click and then click a toolbar button or menu command in the MapMarker window.

Locate Airport command

Airport Locator is a search tool you can use when you need to find one airport or all airports within one state. Airport Locator is available when MapMarker is running.

To use Airport Locator:

• In the Search menu, click Locate Airport.

• Click the right mouse button to display a shortcut menu, then click Locate Airport.

Locate Highway Exit command

Locate Highway Exit is a search tool you can use when you need to find the location of an exit ramp for a specified highway. Locate Highway Exit is available when MapMarker is running.

To use Locate Highway Exit:

• In the Search menu, click Locate Highway Exit.

• Click the right mouse button to display a shortcut menu, then click Locate Highway Exit.

Logfile command

Logfile displays the log file in a text editor where you can view the results and chosen settings of the current geocoding session. Logfile is available after geocoding a table.

MapMarker 23

195

User Guide

Appendix A:

MapMarker Menu Commands and Toolbar Buttons

To view the log file, do one of the following:

• In the View menu, click Logfile.

• Select Automatically open log file after geocoding in the Log File tab of the Geocode dialog.

MapMarker on the World Wide Web command

MapMarker on the World Wide Web opens your default Web browser and displays the MapMarker home page on the World Wide Web. Once there, you can access the latest information about

MapMarker, download related files, and search the MapMarker Knowledge Base for helpful information. MapMarker on the World Wide Web is available in the Help menu when MapMarker is running.

To visit the MapMarker home page:

• In the Help menu, click MapMarker on the World Wide Web.

L

You must have a Web browser installed on your system and have access to the Internet to use this feature.

Open Browser List command

The Open Browser List shows a list of filenames for all open tables within MapMarker. The Open

Browser List is active when at least one table is open in MapMarker.

To use the Open Browser List:

• In the Window menu, click the filename of the table to view.

Open ODBC Table command

Open ODBC Table allows you to specify which remote table you want to open in MapMarker.

MapMarker supports remote tables in MS Access, Oracle, and SQL Server formats. Open ODBC

Table is available when MapMarker is running, and is unavailable if there is already a local table open.

To open a remote table, do one of the following:

• In the File menu, click Open ODBC Table.

• Click on the MapMarker toolbar.

Open Project command

Open Project allows you to open a MapMarker project file with all saved geocoding settings, column mappings, table attributes settings, and some system preferences. These project file settings override any of the existing metadata settings in the TAB file. To open a project file, do the following:

1. In the File menu, click Projects, then Open Projects.

MapMarker 23

196

User Guide

Appendix A:

MapMarker Menu Commands and Toolbar Buttons

2. Navigate to the folder that contains projects (PROJ file extension), select the project file and click

Open.

The project file is created with the

Create/Save Project command

.

Open Table command

Open Table allows you to open a local MapInfo table (TAB file), dBase (DBF). comma-delimited

(CSV), or text (TXT) file. table in preparation for geocoding. Open Table is available when

MapMarker is running.

To open a table, do one of the following:

• In the File menu, click Open Table.

• Click on the MapMarker toolbar.

• Click the right mouse button to display a shortcut menu, then click Open Table.

Quick Find command

Quick Find is a search tool you can use to find or confirm one address at a time. Quick Find is active when MapMarker is running.

To use Quick Find, do one of the following:

• In the Search menu, click Quick Find.

• Click on the MapMarker toolbar.

• Click the right mouse button to display a shortcut menu, then click Quick Find.

Quick Geocode command

Quick Geocode allows you to immediately proceed to geocoding when you open a table in

MapMarker. MapMarker uses the system and table settings from the table's metadata as its matching criteria. The type of geocoding pass done (automatic or interactive) is the same as the last geocoding pass made In the table. For example, if you previously geocoded in interactive mode,

Quick Geocode then geocodes in interactive mode until you change the geocode preference to automatic. Quick Geocode is available when at least one table is open and that table has previously been geocoded.

To use Quick Geocode, do one of the following:

• In the Table menu, click Quick Geocode.

• Click on the MapMarker toolbar.

• Click the right mouse button to display a shortcut menu, then click Quick Geocode.

MapMarker 23

197

User Guide

Appendix A:

MapMarker Menu Commands and Toolbar Buttons

Recent File List command

The Recent File List is a shortcut method you can use to access tables you have previously opened in MapMarker. The names of up to the last four opened tables are listed toward the bottom of the

File menu. The Recent File List is available when at least one table has been opened and closed in the current MapMarker session.

To use the Recent File List:

• In the File menu, click the filename of the table you want to open.

Select Attribute Files command

Select Attribute Files allows you to specify the table of attributes you want to connect to your geocoding table. The attribute table can be local or remote. The table you are geocoding, however, must be local, unless that table uses a different table for output. Select Attribute Tables is available when at least one table is open.

To select attribute files:

• In the Table menu, point to Add Attributes, and then click Select Attribute Files.

Select Columns command

Select Columns allows you to specify the input address columns that MapMarker uses to match your records against its Address Dictionary when geocoding your table. Select Columns is available when a table is open.

To use Select Columns, do one of the following:

• In the Table menu, click Select Columns.

• Click on the MapMarker toolbar.

• Click the right mouse button to display a shortcut menu, then click Select Columns.

Status Bar command

Status Bar shows or hides the status bar at the bottom of the MapMarker window. The status bar is visible when the Status Bar command is checked.

To show or hide the MapMarker status bar:

• In the View menu, click Status Bar.

Stop Attribution command

Stop Attribution stops the addition of attributes from another table. It instructs MapMarker to do the next geocoding pass in the normal way. It does not stop attribution during a geocoding or batch attribution operation. Stop Attribution is available when a table is open and attribute settings exist.

To stop attribution:

• In the Table menu, point to Add Attributes, and then click Stop Attribution.

MapMarker 23

198

User Guide

Appendix A:

MapMarker Menu Commands and Toolbar Buttons

Submit Problem Report to Technical Support command

Submit Problem Report to Technical Support opens your default Web browser and displays a problem report form on the World Wide Web. Once there, you can submit your MapMarker problem report. You can submit a problem report to Technical Support from the Help menu when MapMarker is running.

To submit a problem report:

• In the Help menu, click Submit Problem Report to Pitney Bowes Business Insight Technical

Support. This link submits a report to:

https://community.mapinfo.com/mmdata

.

L

You must have a Web browser installed on your system and have access to the Internet to use this feature.

Summary command

Summary displays the results of the previous geocoding pass. Summary is available after geocoding a table.

To view a geocoding summary:

• In the View menu, click Summary.

System Preferences command

System Preferences allows you to set system-wide preferences that relate to starting MapMarker, setting the Address Dictionary path(s), offset distances for geocoded points, and location of the street maps for candidate mapping. System Preferences is always active when MapMarker is running.

To change system preferences, do one of the following:

• In the Options menu, click System Preferences.

• Click on the MapMarker toolbar.

• Click the right mouse button to display a shortcut menu, then click System Preferences.

Table Summary command

Table Summary generates a report providing statistics about the number and type of geocodes for a table, provided the table contains a georesult column. Table Summary is available when a table is open that contains a georesult column.

To create a table summary:

• In the Table menu, click Table Summary.

MapMarker 23

199

User Guide

Appendix A:

MapMarker Dialogs

Tile command

Tile arranges open windows side by side so that all windows are visible. Tile is always active when

MapMarker is running and there is at least one table open.

To tile your open windows:

• In the Window menu, click Tile.

Toolbar command

Toolbar shows or hides the MapMarker toolbar. The MapMarker toolbar is visible when the Toolbar command is checked.

To show or hide the MapMarker toolbar:

• In the View menu, click Toolbar.

MapMarker Dialogs

This section describes the dialogs in MapMarker and what they are used for. The topics are organized in alphabetical order by dialog name. Use the list below to locate the description of the dialog you wish to learn about.

•

About MapMarker dialog on page 201

•

Add Columns dialog on page 202

•

Automatic Geocode dialog on page 203

•

Bind Attribute Table Columns to Output Columns dialog on page 204

•

Candidate Map dialog on page 205

•

Describe Table Relationships dialog on page 208

•

Dictionary Preferences dialog on page 209

•

Export to dialog on page 210

•

Export to ESRI Shapefile on page 194

•

Fallback dialog on page 212

•

Filter Tables dialog on page 213

•

Font dialog on page 214

•

Geocode dialog on page 215

•

Geocoding Summary dialog on page 216

•

GeoResult dialog on page 217

•

Interactive Geocode dialog on page 218

•

Locate Airport dialog on page 220

•

Locate Highway Exit dialog on page 222

•

Log File dialog on page 223

•

Maps Preferences dialog on page 224

•

Match Settings dialog on page 225

•

Modify Table Structure dialog on page 228

•

Multiple Match dialog on page 230

MapMarker 23

200

User Guide

•

Offset Preferences dialog on page 231

•

Open Project command on page 196

•

Open Table dialog on page 233

•

Quick Find dialog on page 234

•

Quick Find Settings dialog on page 236

•

Related Table dialog on page 239

•

Save As dialog on page 240

•

Save Table Summary As dialog on page 241

•

Select Attribute Tables dialog on page 242

•

Select input columns from your table dialog on page 244

•

Select output columns from your table dialog on page 246

•

Select Project Files dialog on page 247

•

Select Table dialog on page 248

•

Select Table Type dialog on page 249

•

Startup Preferences dialog on page 250

•

Table Georesult Summary dialog on page 251

•

Text File Wizard (Step 1 of 3) on page 252

•

Text File Wizard (Step 2 of 3) on page 253

•

Text File Wizard (Step 3 of 3) on page 254

•

User Dictionary Wizard (Step 1 of 3) on page 254

•

User Dictionary Wizard (Step 2 of 3) dialog on page 256

•

User Dictionary Wizard (Step 3 of 3) dialog on page 257

About MapMarker dialog

Appendix A:

MapMarker Dialogs

The About MapMarker message box displays information about your copy of MapMarker, including the version number, data vintages, and legal and licensing notices.

MapMarker 23

201

User Guide

Tech

Support

Click to view technical support information.

Copyright

Click to view the product copyright information.

Close

Click OK to close the dialog.

Add Columns dialog

Appendix A:

MapMarker Dialogs

The Add Columns dialog appears when you open a table within MapMarker that does not contain one or more of the following columns: Latitude, Longitude, and GeoResult. This dialog prompts you to select which columns to add to your table. Columns you select are added to your table when it opens within MapMarker.

Add Latitude and

Longitude columns

(optional)

Add Latitude column

Click this check box to add a latitude column to your table.

Add Longitude column Click this check box to add a longitude column to your table.

Add GeoResult column

(recommended)

Click this check box to add a georesult column to your table.

OK

Cancel

Help

Click this check box to add latitude and longitude columns to your table.

Invokes the settings and closes the dialog. The settings are saved in the table’s metadata until you clear them.

Cancels the operation and closes the dialog.

Displays help for this dialog.

MapMarker 23

202

User Guide

Appendix A:

MapMarker Dialogs

Automatic Geocode dialog

The Automatic Geocode dialog appears during an automatic geocoding pass. Within this dialog you can monitor the progress of your geocoding pass, noting the following types of information:

Match Type

Matched

No Match

Previous Match

Rows Percent

Indicates number of rows successfully matched.

Indicates percent of rows successfully matched.

Indicates number of rows not matched.

Indicates percent of rows not matched.

Indicates number of rows geocoded in previous geocoding sessions.

Indicates percent of rows geocoded in previous geocoding sessions.

Percent Complete

Stop

Done

Indicates the percentage of the geocoding process completed, based on how much of the table is being geocoded.

Click Stop to interrupt the geocoding process.

When MapMarker completes the geocoding pass on the table, Stop changes to Done. Click Done to return to the MapMarker workspace.

MapMarker 23

203

User Guide

Bind Attribute Table Columns to Output Columns dialog

Appendix A:

MapMarker Dialogs

The Bind Attribute Table Columns to Output Columns dialog allows you to control the attribution operation, including how the attribution table and geocoding tables are related and where

MapMarker stores the attributes in the output table.

Attribute Table Name

Lists the attribute table(s) you set in the Select Attribute Tables dialog.

Join Information Group

This portion of the dialog tells MapMarker how the geocoding and attribute tables are related.

Join Using

Output Point

Use the options in this group to specify how to join attribute and output tables.

Tells MapMarker to make the connection between the attribute and output tables by geography. The geocoded point in your table is compared with the geography in the attribute table. Requires the attribute table to have a MAP component file. Also requires the geocoding table to store the longitude and latitude values.

Column Value

This type of link between attribute and output tables is based on matching columns. When this option is chosen the attribute table and output table columns lists become available.

Attribute Table Column

Lists the indexed columns in the attribute table available for matching against the output columns in your geocoding table.

Output Table Column

Lists the output columns available for matching to an indexed attribute column.

MapMarker 23

204

User Guide

Appendix A:

MapMarker Dialogs

Characters used in comparison

The number of characters that MapMarker uses to compare attribute and output columns to make an exact match.

Bind Information Group

The lower half of the dialog is where you identify the attributes you want added to your geocoding table and which columns to place them in.

Type/Attribute List Box

Lists the type and names of attribute fields contained in the attribute table.

Type/Output Column List

Box

Lists the type and column name of the output column where you want the attribute information stored.

Modify/Add Columns

Click to access the Modify Table Structure dialog and add a new column to the table or modify an existing column.

Bind to Column

Unbind Column

OK

Back

Cancel

Help

Links to the highlighted attribute column and the output column.

Uncouples the highlighted attribute column and the output column.

Invokes the settings and closes the dialog. The settings are saved in the table’s metadata until you clear them.

Returns you to the Select Attribute Tables dialog.

Cancels the operation and closes the dialog.

Displays help on this dialog.

Candidate Map dialog

MapMarker 23

205

User Guide

Appendix A:

MapMarker Dialogs

The Candidate Map dialog appears when you click Map in the Interactive Geocode, Quick Find, or

Locate Highway Exit dialogs. Candidate Map displays a street map for the vicinity of the match candidates MapMarker has returned for a record. Use the Candidate map to help you decide the best match for your record. You can view match candidates for street addresses, ZIP Code™ centroids and street intersections.

Map

Tools

Select

Pan

The map window shows the match candidates and the underlying street layers that you set in Map Preferences dialog. Each candidate is identified by a color-coded star and address label. The star represents the type of geocoding accuracy you would get if you selected that candidate as a match.

• Magenta stars: all records matched to a single address point. No interpolation is required (S8 result code)

• Orange stars: all records geocoded an interpolated point along the candidate’s street segment (S7 result code)

• Green stars: all records geocoded to a street address (S5 and M5 result codes)

• Blue stars: All records geocoded to a shape path centroid (S4, M4 result codes)

• Yellow stars: All records geocoded to a ZIP + 4

®

centroid (S3, M3 and Z3 result codes)

• Cyan stars: All records geocoded to a ZIP + 2 centroid (S2, M2 and

Z2 result codes)

• Red stars: All records geocoded to a ZIP Code™ centroid, including highway exits (S1, M1 and Z1 result codes)

• Purple stars: All records geocoded to point ZIP

®

locations (S6, M6 and Z6 result codes)

• Maroon stars: records offset a specified distance along the perpendicular between the original parcel/point to the associated street segment. (SC result code).

• Black stars: All records geocoded to intersections (Mx and Sx result codes)

• Black circles: all records geocoded to a city geographic centroid (G1 result code)

• Red circles: all records geocoded to a county geographic centroid

(G2 result code)

• Blue circles: all records geocoded to a state geographic centroid (G3 result code)

Lists the tools available to assist in displaying and navigating the candidate map.

An arrow cursor that allows you to select a candidate that you determine is the best match for your input address.

A hand cursor that allows you to move the map for a different view.

MapMarker 23

206

User Guide

Appendix A:

MapMarker Dialogs

Label

Zoom In

A crosshair cursor that allows to label any map feature, such as streets and highways, to help you identify the surrounding area and choose the appropriate match. The candidates display in the map with labels by default.

A plus-sign cursor that allows you to change the map display to a more local view. To zoom-in, click on the map.

A minus-sign cursor that expands the viewable area of the map.

Zoom Out

Default View

Returns the map to the original view of all match candidates visible on the map.

Zoom Level (miles)

Indicates the zoom level the map is displayed at, measured in miles.

X,Y Coordinates

Shows the longitude and latitude coordinates, respectively, for the location under the cursor. As you move the cursor around the map the coordinates change appropriately.

Carries out the selection operation, if any, and closes the dialog.

OK

Cancel

Help

Cancels the operation and closes the dialog.

Displays help on this dialog.

MapMarker 23

207

User Guide

Describe Table Relationships dialog

Appendix A:

MapMarker Dialogs

The Describe Table Relationships dialog allows you to create links between a remote source table and a local results table. This is part of the procedure for geocoding a remote table and writing the results to a related table.

Input Table Columns

Output Table Keys

Selected Input Keys

Lists the input keys that correspond to a specific output key.

Selected Output Keys

Lists the output keys that correspond to a specific input key. Up to six key combinations can be listed for a table.

OK

Lists the columns in the source table.

Lists the columns in the results table.

Cancel

Help

Invokes the settings and closes the dialog. The settings are saved in the table’s metadata until you clear them.

Cancels the operation and closes the dialog.

Displays help on this dialog.

MapMarker 23

208

User Guide

Dictionary Preferences dialog

Appendix A:

MapMarker Dialogs

The Dictionary Preferences dialog allows you to specify the type of data dictionary you want

MapMarker to use, and to specify the location of that data dictionary.

Use MapMarker

Address Dictionary

Path

Use User Defined

Dictionary

Click this check box to use the Address Dictionary. These can include the standard street address MapMarker 23 address dictionary that covers the entire U.S. or a point level dataset (such as Tele Atlas

®

Points, or Centrus

®

Points).

Specify the path for the MapMarker Address Dictionary. Click Browse to identify the current Address Dictionary path and other Address

Dictionary paths you want MapMarker to search. The path(s) reflects all address dictionaries included with your installation. When adding additional paths to the list, separate each by a semicolon.

Click this check box to use a User Dictionary. This is a customized dictionary that contains additional street address information that is not included in the MapMarker Address Dictionary. If you wish to use a customized dictionary, check this box and type in the name of the file.

Alternatively, click Browse to browse to the location.

MapMarker 23

209

User Guide

Path

Use Address Point

Interpolation

OK

Cancel

Apply

Help

Appendix A:

MapMarker Dialogs

Specify the path for the User Dictionary(s). These user-defined databases contain the address information MapMarker will use to set the x and y coordinates for your records. Click Browse to identify the current User Dictionary path and other User Dictionary paths you wish

MapMarker to search.

Select this check box to use address point interpolation when you geocode. Address point interpolation enables records to be geocoded in relation to any address point candidates that are available in the output.

Using a customized dictionary that contains address point data gives the best results.

Closes the dialog and saves the changes that you have made.

Cancels the operation and closes the dialog.

Applies the settings that you specified.

Displays help on the dialog.

Export to dialog

The Save As dialog appears when you select after you open a TAB, CSV, delimited text (TXT), or

DBF file and select Table > Export to ESRI Shapefile. Use it to name a SHP file when you are exporting to Shapefile format.

MapMarker 23

210

User Guide

Appendix A:

MapMarker Dialogs

Export to ESRI Shapefile dialog

The Export to ESRI Shapefile dialog allows you to export TAB, DBF, CSV, and TXT files to ESRI

Shapefile (SHP) format.

Use Point Geometry

Use X/Y Coordinate

Columns

Long (X)

Lat (Y)

Export

Cancel

Help

Specify that the geometry information will come from points on a mappable table.

Specify that the geometry information will come from Longitude /

Latitude columns.

Use the drop-down list to choose the column that contains the

Longitude geometry.

Use the drop-down list to choose the column that contains the

Latitude geometry.

Click Export to begin the export to SHP format.

Cancels the operation and closes the dialog.

Displays online help for this dialog.

MapMarker 23

211

User Guide

Fallback dialog

Appendix A:

MapMarker Dialogs

The Fallback dialog allows you to specify if you want MapMarker to geocode to a ZIP Code™ centroid or to a Geographic centroid it no close match is found at street level.

Fallback to ZIP Centroid

Click this check box when you want to fall back to ZIP Code centroid matching.

ZIP, ZIP + 2 or ZIP + 4

Centroid

ZIP + 2 or ZIP + 4

Centroid Only

Click this option if you want to fall back to either the ZIP

®

centroid, the

ZIP + 2 centroid, or the ZIP + 4

® centroid. This option geocodes to a less specific point than other ZIP fallback options, and is also less specific than geocoding to street level.

Click this option if you want to fall back to either the ZIP + 2 centroid or the ZIP + 4 centroid. This option can potentially geocode to a less specific point than the ZIP + 4 Centroid Only fallback option, and is also less specific than geocoding to street level.

ZIP + 4 Centroid Only

Click this option if you want to fall back to the ZIP + 4

®

centroid only.

This option geocodes to a more specific point than other ZIP fallback options, but is less specific than geocoding to street level.

Fallback to Geographic

Centroid

Click this option if you want to fall back to a state, county, or city centroid. These are not very specific geocoding options, but may be suitable for certain applications.

MapMarker 23

212

User Guide

Geocode

Cancel

Apply

Help

Filter Tables dialog

Begins the geocoding operation.

Cancels the operation and closes the dialog.

Applies the settings that you specified.

Displays online help for this dialog.

Appendix A:

MapMarker Dialogs

Use the options in this dialog to control what types of tables to display in the

Select Table dialog

.

Show

Tables

System Tables

Views

Shows which types of tables to display in the Select Table dialog.

Click this check box to display non-system tables in the Select Table dialog.

Click this check box to display system tables in the Select Table dialog.

Click this check box to display view tables in the Select Table dialog.

L

MapMarker supports Views only if you are geocoding a table and writing the outputs to another table.

Synonyms/Aliases

OK

Cancel

Help

Click this check box to display synonym/alias tables in the Select Table dialog.

Carries out the operation and closes the dialog.

Cancels the settings and closes the dialog.

Displays help on using this dialog.

MapMarker 23

213

User Guide

Appendix A:

MapMarker Dialogs

Font dialog

The Font dialog appears when you click Options > Choose Font. Use the Font dialog to set fonts for your table in the Browser window.

Font

Font Style

Size

Sample

Script

OK

Cancel

Help

In the Font list, click the font type from the scroll list.

Choose the font style from the scroll list.

Choose the font size from the scroll list.

Displays a sample of the font using the selected font style and size.

In the Script list, click the font script that is appropriate for the font you want to use based on your computer’s default language setting.

Click OK to apply the font changes you specify and closes the dialog.

Click Cancel to close the dialog without saving or applying your font changes.

Click Help to display online help for this dialog.

MapMarker 23

214

User Guide

Geocode dialog

Appendix A:

MapMarker Dialogs

The Geocode dialog allows you to select a variety of preferences that control the method, precision, range, and levels of geocoding. Use this dialog to set options for the current geocoding operation.

Table

Geocode Precision

Street Level

Method

To ZIP Centroid

To Geographic

Centroid

Range to Geocode

All Rows

Displays the name of the table to be geocoded.

Geocode to the specified level of precision (street level, ZIP

® centroid or

Geographic Centroid).

Geocode to street level.

Choose from automatic (default) or interactive.

Geocode to the centroid of a ZIP Code™. This is faster than street level geocoding.

Geocode to the centroid of the geography (state, county, or city). These are not very specific geocoding options, but may be suitable for certain applications.

Use the options in this group to specify which rows in your table to geocode.

Geocode the entire table.

MapMarker 23

215

User Guide

Appendix A:

MapMarker Dialogs

Row Numbers

Types of Rows to

Geocode

Unmatched

Geocode a specific block of rows in your table. Enter the row number range in the text boxes below this option. Type the starting row number for the range in the first text box and the end row number for the range in the second text box.

Use the options in this group to specify which table rows within the range you specified in Range to Geocode you want to geocode.

Geocode all unmatched rows (rows for which the GeoResult field: blank or N).

All Types

Geocode all rows.

GeoResult less than

Geocode rows by match precision.

Use the drop-down list to choose the georesult code with the highest precision for which you want to geocode. Only use this option with a table that has already been geocoded. If you use this selection with a table that has not been geocoded, MapMarker geocodes all of the rows regardless of this selection.

Matched OutStreet

Case

Use the option in this group to specify the character case of the street output.

Return Street Output in Mixed Letter Case

Click this check box to have MapMarker write the output street in mixed case (for example, 12 Front St.).

Configure

Attribution

Geocode

Displays the Bind Attribute Table Columns to Output Columns dialog.

This begin the process of attribution binding.

Begins the geocoding operation.

Cancel

Apply

Help

Cancels the operation and closes the dialog.

Applies the settings that you specified.

Displays help on this dialog.

Geocoding Summary dialog

MapMarker 23

216

User Guide

Appendix A:

MapMarker Dialogs

The Geocoding Summary dialog appears at the end of a geocoding session. The Geocoding

Summary dialog lists the results of the latest geocoding pass, including the number of new matches, unmatched records and previously matched records.

Matched

No Match

Previous Match

Total

Rows Percent

Indicates number of rows successfully matched.

Indicates percent of rows successfully matched.

Indicates number of rows not matched.

Indicates percent of rows not matched.

Indicates number of rows geocoded in previous geocoding sessions.

Indicates total number of unmatched rows, entire table or block of rows examined.

Indicates percent of rows geocoded in previous geocoding sessions.

Indicates total percent of rows examined.

GeoResult dialog

The Georesult dialog shows a breakdown of the result code for each record. To display this dialog, double-click on the code in your table’s result column in the Browser. This behavior is available after you have completed a geocoding pass or set the columns for a previously geocoded table. It is not available at the initial opening of the table.

Street Address

Zip Code

Displays the street address for the record you are viewing georesult information.

Displays the ZIP Code™ for the record you are viewing georesult information for

MapMarker 23

217

User Guide

Result code

Match type

Match details

Close

Help

Appendix A:

MapMarker Dialogs

Displays the result code for the record you are viewing georesult information

Describes the type of match made while geocoding the record and to what level the record was geocoded.

Indicates the criteria used in determining the match.

Click to close this dialog.

Contains help on this dialog.

Interactive Geocode dialog

The Interactive Geocode dialog appears when the Interactive option is selected in the Geocode dialog. This dialog displays unmatched records one at a time and a list of suggested matches (if any). Click Geocode to accept the match or click Ignore to move to the next ungeocoded record.

Summary

Matched

No match

Previous match

Percent complete

The summary reflects the percentage of new matches, unmatched and previously matched records.

Indicates percent of rows successfully matched.

Indicates percent of rows not matched.

Indicates percent of rows geocoded in previous geocoding sessions.

A progress bar that updates the match count after each record.

MapMarker 23

218

User Guide

Geocoding result

Input Address

Row indicator

Firm

Street

Street2

City

State

ZIP Code

Plus 4

Write indicated address to Input

Fields on Geocode

Appendix A:

MapMarker Dialogs

Displays the results of geocoding for that record (for example no matches found, unknown address).

This group displays (for viewing and editing) the address to be geocoded.

This drop-down list displays the name of the column that contains the row numbers for the table. Row numbers are shown to the right of this list during interactive geocoding, provided there are valid row numbers to display.

The name of the business residing at the address.

The primary street address.

The secondary street address (for example, an apartment or post office box number).

The full city name.

The abbreviated state code (for example, NY for New York).

The five-digit ZIP Code™.

The four digit extension to the ZIP Code.

After editing a record, check this box to add the changes you made to the record’s address information into your table upon clicking Geocode.

L

The existing input address is overwritten with your changes.

Expand Search

Distance in miles

Check this box to increase the probability of a match by expanding the search area in which MapMarker checks for a match. This helps to find a match when the input address contains limited or inaccurate city or ZIP

Code information.

If you checked Expand Search, you can specify in miles (up to 99) for the search radius.

Limit to current state

If you checked Expand Search, you can limit the expanded search to the same state indicated in the input address.

Select best match from candidate list

Displays suggested alternatives from the Address Dictionary, indicating the result code followed by the address. The top candidate is highlighted by default.

Search

Options

Click to re-geocode a record after you have changed a constraint or option or after you have edited the input address.

Click to change the matching conditions for the displayed record.

MapMarker 23

219

User Guide

Ranges

Map

Close

Help

Back

Next

Geocode

Locate Airport dialog

Appendix A:

MapMarker Dialogs

Click to display a detailed list of address ranges for the highlighted street. The records are geocoded to the selected range. By default,

MapMarker displays the range that most closely matches the input address.

Displays a map showing all match candidates for the input address. This button is active when you have previously set the location of your street data in the Maps Preferences dialog.

Stops the interactive geocoding session and closes the dialog.

Displays help on this dialog.

Click to go back to previous records to re-geocode. This is helpful to re-check previous geocoding decisions or to redo previous interactive geocodes.

Click to leave the record ungeocoded and skip to next unmatched record.

Click to geocode the specified match candidate if you agree that it is the correct match for your record. MapMarker assigns the coordinates from that record and moves on to display the next unmatched record in your file.

Use the Locate Airport dialog to search for location information for a specified airport, using the airport code or state abbreviation as your search criteria.

MapMarker 23

220

User Guide

Appendix A:

MapMarker Dialogs

Airport Code or State

Abbreviation

Type the airport code or abbreviated state code in which you want to search for airports.

Search

Clear Field

Search Results

Click to search for airports matching your input criteria.

Click to clear the Airport Code of State Abbreviation text box.

Airport List

Displays the number of records matching your search criteria. In the event of an unsuccessful search, one of three messages appears:

Invalid state or location code. The airport or state code you searched on did not contain at least two alpha-numeric characters. Re-type the airport or state code, using two characters if searching by state, or three to four characters if searching by airport code.

Invalid state code. The two-character code you searched on did not match a valid state code. Type the correct state code to search for all airports in the state or type the complete three- or four-character airport code to search for a specific airport.

No matching records found. The three- or four-character code you searched on did not match a valid airport code. Type the correct airport code to search for the airport or type a state code to search for all airports in the indicated state.

Displays a list of all airport candidates matching your search criteria, organized alphabetically by airport code.

Close

Help

Click to close this dialog.

Displays online help for this dialog.

MapMarker 23

221

User Guide

Locate Highway Exit dialog

Appendix A:

MapMarker Dialogs

Use the Locate Highway Exit dialog to search for location information for a specified highway exit, using the highway name, exit, and state as your search criteria.

Highway

Search

Results

Map

Type the highway name and direction (for example, I-90 E or Interstate 90 East) for which you want to search for an exit location.

Exit

Type the exit number and/or the exit name (for example, Exit 2 to Washington

Ave) for which you want to find location information.

State

Search

Type the state in which the exit exits (for example, NY for New York).

Click to search for highway exits matching your input criteria.

Clear Fields

Click to clear the Highway, Exit, and State text boxes.

Displays the records matching your search criteria.

Close

Help

Displays a map showing all match candidates for the input address. This button is active when you have previously set the location of your street data in the

Maps

Preferences dialog

. This button is active only when you look for a match via

Search.

Click to close this dialog.

Displays online help for this dialog.

MapMarker 23

222

User Guide

Log File dialog

Appendix A:

MapMarker Dialogs

The Log File dialog allows you to set up a log file to track your matching conditions, geocoding results and other settings.

Update Log File

Check to have MapMarker update the log file for each geocoding session. Information about the session appears at the top of the file.

Automatically open log file after geocoding

Check the box to view the log file after MapMarker completes a geocoding run.

Specify Log File Name

Check the box and specify the name of the log file. The default is

table.log, where table is the root name of the topmost opened table. If you do not specify a file name, the geocoding information is written to a file named Mapmarkr.log that is found in the MapMarker program directory after the geocoding pass.

Geocode

Cancel

Apply

Help

Begins the geocoding operation.

Cancels the operation and closes the dialog.

Applies the settings that you specified.

Displays help on this dialog.

MapMarker 23

223

User Guide

Maps Preferences dialog

Appendix A:

MapMarker Dialogs

To see the Maps Preferences dialog, select Options > System Preferences and select the Maps tab. Use this dialog to set the location and layer choices of the street data to display in the Candidate

Map.

Street Table Data

Location

Street Table Layer

Configuration

Add

Remove

Add All

Remove All

Candidate

Visualization

OK

Specify the path for the MapMarker Streets, StreetInfo or StreetPro data set. Click Browse to navigate to the location instead of typing it in. You do not need to specify particular files to be opened.

Choose the layers you want to see in the candidate map from the Available

Layers list.

Adds any highlighted layer in the Available Layers list to the Layers to Use list.

Removes any highlighted layer from the Layers to Use list.

Adds all layers from the Available Layers list to the Layers to Use list.

Removes all items in the Layers to Use list.

Sets the maximum zoom distance for the candidate map. Default setting is

5 miles.

Invokes and saves the settings.

MapMarker 23

224

User Guide

Cancel

Apply

Help

Match Settings dialog

Cancels the operation and closes the dialog.

Applies the settings that you specified.

Displays help on this dialog.

Appendix A:

MapMarker Dialogs

The Match Settings dialog allows you to adjust the match settings you require for your geocoding session.

Standard

Tight

Relaxed

Enables Standard match mode. This is the default mode an generally provides the best combination of accurate geocoding, few false matches, and high performance.

Enables Tight match mode. This provides strict matching rules. In general, this returns fewer non-close matches than are returned in Standard mode.

Enables Relaxed match mode. This provides less strict matching rules. In general, this increases your chances of getting a close match. This is the only mode that does not respect the street parity when making an address match.

MapMarker 23

225

User Guide

CASS

Custom (Exact

Match On)

House number

Street name

City Name

ZIP Code

Appendix A:

MapMarker Dialogs

When CASS mode is enabled, MapMarker will perform address standardization under strict matching conditions set by the USPS

®

.

Geocoding in CASS mode matches records to the exact house number, street name, and ZIP Code™. Other geocoding preferences are overridden.

CASS Mode also enables the option to Produce a CASS Report

See

CASS Options

.

If you wish to specify exact match conditions, select Custom (Exact

Match On) to activate these choices. Clear or check the appropriate check box in the group. For example, clearing the House Number box and checking Street Name and ZIP Code means that MapMarker matches your record to the closest house number for the exact street in that

ZIP Code it finds in the Address Dictionary.

When the House Number box is checked, candidate house numbers must be exactly matched to return a close match. When the House Number box is unchecked, MapMarker can make a close match even if the house number match is not exact.

L

Street name exact match also requires an exact match on street

type. That is, 147 Rd. must be matched exactly; 147 Ave does not match.

When the Street Name box is checked, candidate street names must be exactly matched to get a geocoding match. When the street name box is unchecked, MapMarker will accept similar street names as a match.

This requires an exact match on all elements of the street name. Also, blank input values for these elements will not match non-blank values in the candidate records.

Street name exact match also requires an exact match on street type.

That is, 147 Rd. must be matched exactly; 147 Ave does not match.

When the City Name box is checked, MapMarker requires a city name match. When this box in unchecked, the city name does not have to match.

When ZIP Code™ is checked, ZIP Code must be exactly matched to get a geocoding match. When ZIP Code is unchecked, surrounding ZIP Codes are considered for matching purposes and records with missing

ZIP Codes are also considered.

MapMarker 23

226

User Guide

Appendix A:

MapMarker Dialogs

Produce a CASS

Report

If you wish to qualify your table for CASS, you must print a report USPS

Form 3553. If you choose to Produce a CASS Report, the Use DPV and

Use LACSLink check boxes are automatically checked. DPV validation is

required for CASS reports. See

DPV

.

Use DPV

Use LACSLink

Use SuiteLink

Return Short

Address

Return Short City

Name

Use EWS file

Check this box to specify DPV

®

geocoding. The DPV files must be installed and unlocked in order to access this feature. If you choose to

Produce a CASS Report, the Use DPV mode check box is automatically checked. This is because DPV validation is required for CASS™ reports.

Check this box to specify LACS

Link®

processing to return addresses that have been converted because of E911 or USPS changes. The LACS

Link files must be installed and unlocked in order to access this feature. See

LACSLink

.

Check this box to return Suite

Link

™ addresses. See

SuiteLink

.

Check this box to return CASS abbreviated addresses. See

Returning

Abbreviated Addresses

Check this box to return CASS short city names.

Returning Abbreviated

City Names

.

Check this box if you want to use the Early Warning System (EWS) feature. The EWS file contains addresses that did not make it into the current USPS

®

update, and therefore do not match. For example 100 S

Bonnie Ct would not match 100 S Bonnie Ave if 100 S Bonnie Ct was not in the current USPS

®

database. Using EWS ensures that this address does not match. Records that have no match because they are in the

EWS file can be flagged in the EWS output column. EWS usage is not required for CASS™ discounts.

Use Wide Search

Use wide search to consider all streets that begin with the first letter of the input street name, and therefore can identify many more potential candidates. Wide search is most often used in combination with Relaxed mode as part of a two-pass geocoding strategy. See

Using Wide Search

.

Accept S5 or Better

Street Address

Matches

Check this box if you only want street address matches of S5 or higher accuracy.

Accept S5 Street

Address Matches

Only

Check this box if you want S5 street address matches only.

MapMarker 23

227

User Guide

Appendix A:

MapMarker Dialogs

Clear Output

Columns If No

Match

If this box is checked, MapMarker removes existing output values for a record that it cannot match. If you want to preserve this data, such as longitude/latitude coordinates obtained from another source, clear the check box before geocoding the table.

Prefer User

Dictionary Matches

Check this box to select User Dictionary candidates over Address

Dictionary candidates, regardless of match scores.

Prefer Matching ZIP

Over Matching City

When multiple potential close matches are identified, MapMarker selects a City candidate over a ZIP Code candidate by default. However, you can check Prefer Matching ZIP over Matching City to generate close matches based on ZIP Code rather than based on city.

Geocode

Cancel

Apply

Help

Begins the geocoding operation.

Cancels the operation and closes the dialog.

Applies the settings that you specified.

Displays help on this dialog.

Modify Table Structure dialog

The Modify Table Structure dialog allows you to change the structure of your geocoding table by adding, removing or changing information about the table’s columns. This is useful for creating columns “on the fly” when you want MapMarker to return additional data from the Address Dictionary for which you had not provided a column. This eliminates the time-consuming step of going outside of MapMarker to make these changes.

MapMarker 23

228

User Guide

Appendix A:

MapMarker Dialogs

Columns

Column Name

Type

Shows the existing columns for the table.

Indicates the type of column with the number of characters listed in parentheses.

Add Column

Adds a new column to the table at the bottom of the list with the default name Field1, Field2 etc.

Removes an existing column from the table.

Remove Column

Column Information

Area where you can rename the column and change its type and width.

Name

The name of the column.

Type

Width

OK

Cancel

Help

The type of data the column contains.

The character width of the column.

Click to save your new column settings and close the dialog. The settings are saved in the table’s metadata until you clear them.

Cancels the operation and closes the dialog.

Displays help on this dialog.

MapMarker 23

229

User Guide

Multiple Match dialog

Appendix A:

MapMarker Dialogs

The Multiple Match dialog allows you to instruct MapMarker on how to handle multiple candidate matches with the same candidate score for a record while geocoding.

Do Not Match

Accept First

Pick Street Address over ZIP + 4

Click this option to accept the first candidate for the match.

Click this option to accept the candidate with the most accurate street level match.

Pick ZIP + 4 over

Street Address

Geocode

Cancel

Apply

Help

Click this option to not allow a match to be made for the record if multiple matches occur.

Click this option to accept the candidate with the most accurate ZIP + 4 level match.

Begins the geocoding operation.

Cancels the operation and closes the dialog.

Applies the settings that you specified.

Displays help on this dialog.

®

MapMarker 23

230

User Guide

Offset Preferences dialog

Appendix A:

MapMarker Dialogs

Offset Preferences allow you to specify the distance the geocoded point spots from the corner and center line of the road. For more information on using offsets. see

Offset System Preferences

.

Field

Offset from Road

Description

Specify that the interpolated point is offset from the street using the measurement set in the Units drop-down list.

Offset from Corner

Specify that the interpolated point is offset from the street corner using the measurement set in the Units drop-down list.

Units

Specify the units used for the street (road) or street corner offset. When changing the units, be sure to also specify the appropriate offset distance values, because changing the units does not automatically recalculate the offset values.

Use Center Line

Offset

Specify that the point is offset from the associated street segment (rather than placed at the original point). Where possible, the coordinates are offset perpendicularly from the segment.

Center Line Offset is available only if you are using a point-based Address

Dictionary. A street segment dictionary must also be available.

MapMarker 23

231

User Guide

Units

Field

OK

Cancel

Apply

Help

Open Project dialog

Appendix A:

MapMarker Dialogs

Description

Specify the units used for the center line offset. When changing the units, be sure to also specify the appropriate offset distance values, because changing the units does not automatically recalculate the offset values.

Closes the dialog and saves the changes that you have made.

Cancels the operation and closes the dialog.

Applies the settings that you specified.

Provides help on the dialog.

Use the Open Project dialog to open a MapMarker project. A project will preserve MapMarker preferences and table settings so that they can be easily restored when you open the project.

Look in:

Lists the available folders and files. To see how the current folder fits in the hierarchy on your computer, click the down arrow. To see what is inside a folder, click it.

The box below shows the folders and files in the selected location. You can also double-click a folder or file in that box to open it.

File name:

Has a space for you to type the name of the file. If you select a project, the project name is populated in this box

Files of type:

MapMarker projects have a PROJ file extension,

Open

Cancel

Help

Opens the selected project.

Cancels the operation and closes the dialog.

Displays help on this dialog.

MapMarker 23

232

User Guide

Appendix A:

MapMarker Dialogs

Open Table dialog

Use the Open dialog to open a street file for creating a User Dictionary. Use the Open Table dialog to open a MapInfo table to geocode.

Look in:

Lists the available folders and files. To see how the current folder fits in the hierarchy on your computer, click the down arrow. To see what is inside a folder, click it.

The box below shows the folders and files in the selected location. You can also double-click a folder or file in that box to open it.

File name:

Has a space for you to type the name of the file.

You can use * as a wildcard. For example, you can type *.* to see a list of all files.

You can also type the full path of a file. For example, you can type c:\mymaps\States.tab.

Files of type:

This is useful for narrowing the list of files displayed to only those files you are interested in.

The tables displayed are tables in MapInfo format (TAB) or any other supported

file format. See

Supported File Formats

. Select the file format of the file you

want to open.

Open

Cancel

Help

Opens the file with the name, file type, and location you specified.

Cancels the operation and closes the dialog.

Displays help on this dialog.

MapMarker 23

233

User Guide

Quick Find dialog

Appendix A:

MapMarker Dialogs

The Quick Find dialog appears when you click Quick Find on the Search menu. Use this dialog to search for a single address match or to browse the Address Dictionary for a listing of street names or firms for a ZIP Code™. Quick Find does not geocode the address.

You can also right-click on a candidate to display the context menu. From that menu, you can copy selected information to the clipboard. See

Copying Information from the Quick Find Candidate

List

.

Input Address

Firm

Fields for holding parts of the address including Firm, Address, City,

State, ZIP Code and ZIP + 4

®

fields.

The name of the business residing at the address.

MapMarker 23

234

User Guide

Appendix A:

MapMarker Dialogs

Address/Single Line

Address

Address2

The primary street address. This can also include the, one-line single line address with address components in the order: <street address>

<city> <state> <ZIP> <country>.

Not all address components are required. You can use delimiters

(comma, semicolon, colon, or tab) between each component of the single line address. If no delimiters are present, MapMarker recognizes spaces as separators, but non-delimited addresses may take longer to geocode.

The Browse selection in the Quick Find dialog does not support the single line address format. That is, the ZIP Code™ (and City/State information if provided) must be entered in separate input fields, not in single line format.

The secondary street address (for example, an apartment or post office box number).

The full city name.

City

State

ZIP Code

Plus 4

Quick Find Settings

Clear Fields

Geocoding Result

The abbreviated state code (for example, NY for New York).

The five-digit ZIP Code™.

The four digit extension to the ZIP Code.

Changes the criteria used in producing your Quick Find search results.

Clears the address fields and items in the candidates list.

After MapMarker searches for a match, it returns a message here describing the type of match.

Match Candidate List

The list box contains either the message “no suggestions available” or at least one candidate that MapMarker deems a suitable match for the input information provided. The candidates include the result code followed by the street address.

A green check mark in the Num column indicates a close match. See

Finding Candidates Using Quick Find

for details of the match candidate list for the Quick Find dialog.

Ranges

Displays a detailed list of address ranges for the highlighted street. The

ZIP + 4

®

is displayed for each street range. By default, MapMarker displays the range that most closely matches the input address. This button is active only when you look for a match via Search. You cannot display address ranges from a Quick Find Browse.

MapMarker 23

235

User Guide

Map

Search

Browse

Close

Help

Appendix A:

MapMarker Dialogs

Displays a map showing all match candidates for the input address. You must previously set the location of your street data in Options >

System Preferences > Maps tab. This button is active only when you look for a match via Search. You cannot map any results of a Quick

Find Browse.

Allows you to search the Address Dictionary after you have entered the input address.

Allows you to see a listing of streets or firms in the Address Dictionary.

Requires that you enter the ZIP Code™ and either the partial or full street name or firm. ZIP Code (and City/State information if provided) must be entered in separate input fields, not in single line format.

Stops the search for a match and closes the dialog.

Displays help on this dialog.

Quick Find Settings dialog

Use the Quick Find Settings dialog to change the criteria used in producing your Quick Find search results.

Match Modes

Standard Mode

You can select one of the match modes to control the geocoding precision and number of returned candidates. You can also select

Custom (

Exact Match On

) to achieve more precise control over

your geocoding results.

Check this box to implement Standard Mode matching. This typically provides the best balance among hit rate, performance,

and minimizing extraneous matches. See

Match Modes

.

MapMarker 23

236

User Guide

Tight Mode

Relaxed Mode

CASS

Appendix A:

MapMarker Dialogs

Check this box to implement Tight Mode. This restrictive mode generates the most precise matching. In general, this returns fewer non-close matches than are returned in Standard mode.

See

Match Modes

.

Check this box to implement Relaxed Mode. This provides less strict matching rules. In general, this increases your chances of getting a close match. This is the only mode that does not respect the street parity when making an address match. See

Match

Modes

.

Check this box to use CASS™ mode in finding addresses.

L

When this check box is selected, the other settings options on this dialog are disabled and their values are overwritten by CASS rules. List Candidates options (All Candidates and Close Candidates Only) are available for selection.

Custom Selections (Exact

Match On)

House Number

Street Name

City Name

ZIP Code

Use Exact Match selections to fine-tune your control over geocoding matching preferences. You can specify precise matching criteria based on house number, street name, city name, and ZIP Code. If all specified criteria are not met, then the geocoded candidate is not considered a close match.

When the House Number box is checked, candidate house numbers must be exactly matched to return a close match. When the House Number box is unchecked, MapMarker can make a close match even if the house number match is not exact.

When the Street Name box is checked, candidate street names must be exactly matched to get a geocoding match. When the street name box is unchecked, MapMarker will accept similar street names as a match.

This requires an exact match on all elements of the street name.

Also, blank input values for these elements will not match nonblank values in the candidate records.

When the City Name box is checked, MapMarker requires a city name match. When this box in unchecked, the city name does not have to match.

When ZIP Code™ is checked, ZIP Code must be exactly matched to get a geocoding match. When ZIP Code is unchecked, surrounding ZIP Codes are considered for matching purposes and records with missing ZIP Codes are also considered.

MapMarker 23

237

User Guide

Appendix A:

MapMarker Dialogs

Other Settings

Use Wide Search

Prefer Matching ZIP over

Matching City

Fallback

Fallback to ZIP Centroid

Fallback to Geographic

Centroid

Candidates to Return

All Candidates

Close Candidates Only

OK

Cancel

Help

Use wide search to consider all streets that begin with the first letter of the input street name, and therefore can identify many more potential candidates. Wide search is most often used in combination with Relaxed mode as part of a two-pass geocoding

strategy. See

Using Wide Search

.

Check this box to prefer an internal close candidate on postal code over a match on city.

If MapMarker cannot match a record to the level or precision that you have requested (such as street level), it can fall back to use less precise matching criteria. You can select one or both of the fallback options.

Click this option to allow fallback to ZIP Code™ Centroids. If a close match was not found using the Require Exact Match criteria, you can still geocode based on ZIP Code centroids.

Click this option to allow fallback to geographic centroids. If a close match was not found using the Require Exact Match criteria, you still can geocode based on state, county, or city centroids.

These are not very specific geocoding options, but may be suitable for certain applications.

You can specify the number of candidates you want Quick Find to return.

Click this option to return all candidates matching the search criteria you specify.

Click this option to return only the candidates that closely match the search criteria you specify.

Saves your Quick Find settings and return to the Quick Find dialog.

Closes the Quick Find Settings dialog without saving your changes.

Displays help on this dialog.

MapMarker 23

238

User Guide

Related Table dialog

Appendix A:

MapMarker Dialogs

This dialog only appears if you are geocoding a remote table and want to write the results to a related table. It tells MapMarker whether you want to optimize the geocoding operation for inserting new records or for updating existing records.

L

This feature is not available for single remote table geocoding.

Optimize for Insertion

Optimize for Update

Geocode

Cancel

Apply

Help

Choose this option if your results table is new or contains few records.

Choose this option if your results table contains many records are likely to be updated.

Begins the geocoding operation.

Cancels the operation and closes the dialog.

Applies the settings that you specified.

Displays help on this dialog.

MapMarker 23

239

User Guide

Appendix A:

MapMarker Dialogs

Save As dialog

The basic "Save As" dialog is used in several contexts.

Save Batch File

Save Project File

Export to Shapefile

Save Table Summary As dialog

Save Batch File

The Save As dialog appears when you select Create Batch File from the Table menu. Use it to navigate to a folder in which to save your batch file.

Save Project File

The Save As dialog appears when you select File > Projects > Create/Save Project. Use it to name a project with a PROJ file extension. See

Creating and Saving a Project

.

MapMarker 23

240

User Guide

Appendix A:

MapMarker Dialogs

Export to Shapefile

The Save As dialog appears after you open a TAB, CSV, delimited text (TXT), or DBF file and select

Table > Export to ESRI Shapefile. Use it to name a SHP file when you are exporting to Shapefile format.

Save Table Summary As dialog

The Save Table Summary As dialog appears when you click OK on the

Table Georesult Summary dialog

. This allows you to specify the name and location of the logfile.

MapMarker 23

241

User Guide

Appendix A:

MapMarker Dialogs

Select Attribute Tables dialog

The Select Attribute Tables dialog allows you to choose the attribute tables MapMarker accesses during the attribution process.

Available Tables

Displays the directory structure of the chosen drive that contains the table you want MapMarker to use for tagging.

Selected Tables

Displays the table(s) you have chosen for the attribution process.

Add

Adds the highlighted table in the Available Tables list to the Selected Tables list.

Removes the highlighted table(s) from the Selected Tables list.

Remove

Remove All

Drives

Removes all items from the Selected Tables list.

Lists the drives on the system. The chosen drive displays the directory structure in the Available Tables list.

OK

Cancel

Help

Invokes the settings and closes the dialog.

Cancels the operation and closes the dialog.

Displays help on this dialog.

Select Data Source

When using a remote table as a geocoding source, you can select either a file data source or a machine-specific data source.

MapMarker 23

242

User Guide

Appendix A:

MapMarker Dialogs

File Data Source

Data source can potentially be shared over network by authorized users. You can use any file data source that refers to an ODBC driver that is installed on your system.

Machine Data Source

Data source is specific to a machine. User data sources are specific to a user on this machine. System data sources can be used by all users on this machine.

MapMarker 23

243

User Guide

Select input columns from your table dialog

Appendix A:

MapMarker Dialogs

Use this dialog to choose the fields from your table that contain the address information to be matched against the Address Dictionary during the geocoding operation.

Table

Firm

Address

Identifies the name of the table and lists all columns in the table that can be selected. Highlight an address column name and drag it to the appropriate address component box. If the table has been previously geocoded,

MapMarker remembers the fields from the table’s metadata. If this is the first time you have geocoded this table, MapMarker attempts to guess at the correct fields by examining their field names. To view the complete name of a field that extends beyond the box provided, hold the cursor over the field name and MapMarker displays a popup box with the full name of the field.

Specify the field that contains the name of the organization associated with the record, if any.

Select the column from your table that contains the primary address data.

Single line address input is recognized in the ADDRESS column. single line addresses appear on a single line. You can use delimiters (comma, semicolon, colon, or tab) between each component of the single line address. If no delimiters are present in the address, MapMarker recognizes spaces as separators, but non-delimited addresses may take longer to geocode.

MapMarker 23

244

User Guide

Appendix A:

MapMarker Dialogs

Address2

City

State

ZIP Code

Select the secondary address column. The secondary address is usually used for apartment numbers or post office box numbers. This optional information is appended to the end of the street to form the complete address to be parsed.

Select the column containing the town or city name.

Select the column containing the two-letter state name.

ZIP + 4

Urb

Modify/Add

Columns

County

Select the column containing the ZIP Code™ or ZIP + 4

®

if contained in one column.

Select the column containing additional ZIP + 4 information if it is contained in a separate column from ZIP Code; this information is optional.

This field holds the urbanization code, an address component for addresses in

Puerto Rico. If you are trying to qualify your table for CASS, you must provide this field, even if you do not have Puerto Rican addresses.

Leads to the Modify Table Structure dialog where you can add, remove or change information about the columns in the open table.

Choose the column containing the county name. Specify this column only if you want to geocode to the county centroid.

Enables you to specify the Address2 column as the intersection cross street to

Address1.

Use Address2 as Intersection

Cross Street

Next

Cancel

Help

Moves to the Select Output Columns dialog.

Cancels the settings and closes the dialog.

Displays help on this dialog.

MapMarker 23

245

User Guide

Select output columns from your table dialog

Appendix A:

MapMarker Dialogs

In this dialog, you specify the columns to contain the results of the geocoding operation, such as: result code, longitude, latitude, and CASS required information. This dialog appears when you click

Next in the Select Input Columns dialog after selecting your input address column choices.

Table

Status Column

Coordinate

Columns

MapMarker 23

Identifies the name of the table and lists all columns in the table that can be selected. Highlight an address column name and drag to the appropriate address component box. If the table has been previously geocoded,

MapMarker remembers the fields from the table’s metadata. If this is the first time you have geocoded this table, MapMarker attempts to guess at the correct fields by examining their field names. To view the complete name of a field that extends beyond the box provided, hold the cursor over the field name and MapMarker displays a popup box with the full name of the field.

Select the column where MapMarker stores the result code after it attempts to geocode. MapMarker generates a code for each record. The code indicates how the record was matched and whether the match is exact. Use the code to diagnose MapMarker performance, to identify false positives, and analyze ungeocoded records. This column is optional, but highly recommended.

For local tables, choose the columns where longitude (x coordinate) and latitude (y coordinate) information is written when a record is geocoded.

These columns are optional when “Create Points” is selected.

246

User Guide

Appendix A:

MapMarker Dialogs

Create points in

MapInfo Table

For local tables check this box if you want MapMarker to automatically create points for your MapInfo table. Creating points is optional if you have specified coordinate columns. For SpatialWare tables, MapMarker automatically creates points for the table. The option box is then checked and grayed out.

Output Address

Columns

Modify/Add

Columns button

Specify the columns for these components if you want MapMarker to return the address information from the Address Dictionary. To avoid overwriting your data, be sure to identify columns other than the address columns you chose in the Select Input Columns dialog. These columns are optional unless you are geocoding your table to meet CASS. The Census and Carrier Route fields are optional in all situations.

See

Specify Output Address Columns

for

When you click Show DPV and LACSLink Columns, the view switches to the DPV and LACS

Link

output columns that are required for generating a

CASS report. See

DPV Output Columns

and

LACSLink Output Columns

for detailed information.

Leads to the Modify Table Structure dialog where you can add, remove, or change information about the columns in the open table.

Show/Hide DPV and LACSLink

Columns button

Back

Finish

Cancel

Help

Click Show DPV and LACSLink Columns to view the output columns for

DPV and LACS

Link

. Click Hide DPV and LACSLink Columns to go back and view the first set of address output columns.

Returns to the Select Input Columns dialog.

Completes the columns selection process and closes the dialog.

Cancels the settings and closes the dialog.

Displays help on this dialog.

Select Project Files dialog

MapMarker 23

247

User Guide

Appendix A:

MapMarker Dialogs

This dialog appears when you create a batch file to run a project that was created using a delimited file or fixed-width TXT file. After you complete this dialog, you will see the

Save As dialog

.

Field Description

Available Projects Displays the available projects that you can add to a project-based batch file.

Selected Projects

Displays the project(s) you have chosen for the batch file.

Add

Remove

Adds the highlighted table in the Available Projects list to the Selected

Projects list.

Removes the highlighted Project(s) from the Selected Projects list.

Remove All

Drives

OK

Cancel

Help

Removes all items from the Selected Projects list.

Use the drop-down arrow to select from the available drives on the system.

Invokes the settings and closes the dialog.

Cancels the operation and closes the dialog.

Provides help on this dialog.

Select Table dialog

This dialog appears after selecting a data source when opening an ODBC table. Use this dialog to select the table you wish to open within the data source you specified.

Owner

Filter list of tables

MapMarker 23

Specify the owner of the table.

Click to set filters on the types of tables you want to select from.

List of all tables in the database that are owned by you or accessible to you, constrained by the filters you set. Choose which table you want to geocode.

248

User Guide

OK

Cancel

Help

Carries out the operation and closes the dialog.

Cancels the settings and closes the dialog.

Displays help on this dialog.

Select Table Type dialog

Appendix A:

MapMarker Dialogs

This dialog prompts you to choose between opening a MapInfo TAB or other supported file format or an ODBC table. This dialog appears if you have set startup preferences to open both local and remote (ODBC) tables when you start MapMarker. See

Startup Preferences dialog

Open MapInfo table, or .dbf file

Click this option if you want to open a MapInfo TAB, DBF, or other supported file format. This includes CSV or other delimited files. See

Supported File Formats

.

Open ODBC table

Click this option if you want to open an ODBC table.

OK

Carries out the operation and closes the dialog.

Cancel

Help

Cancels the settings and closes the dialog.

Displays help on this dialog.

MapMarker 23

249

User Guide

Startup Preferences dialog

Appendix A:

MapMarker Dialogs

The Startup tab identifies the settings MapMarker uses when you start the application. You can select any or all check boxes. If you select either Show MapInfo/dBASE files or Show for ODBC

tables, the Open dialog will be displayed automatically when you start MapMarker. If you check both boxes, MapMarker prompts you with another dialog at startup to choose which type of table you want to open.

File Open Startup

Options

Show Select Column

Dialog On Open

Select Attribute Files

After Selecting

Columns

Show Geocode Dialog

After Selecting

Columns

Check either or both boxes in this group:

• Show for MapInfo TAB, DBF, or delimited text files

• Show for ODBC Tables

If you check both items, MapMarker prompts you to choose which table type you want to open when you start MapMarker.

The Select Input Columns dialog automatically appears when you open a table. This is the default setting.

The Select Attribute Tables dialog appears after you choose input and output columns for the open table. The default setting is not to display this dialog.

The Geocode dialog appears automatically once you have opened your table and identified the address columns for geocoding. This is the default setting.

MapMarker 23

250

User Guide

Appendix A:

MapMarker Dialogs

Show Add Georesult,

Longitude/Latitude

Columns Dialog

When this check box is selected, the Add Columns dialog appears upon opening a table without a latitude, longitude, or georesult column. This check box is selected by default.

Write modified address on geocode in interactive dialog

When this check box is selected, any address you modify during an interactive geocoding run is updated in your table by default.

Log file Viewer

Identify a viewer for MapMarker to display a message log file at the conclusion of the geocoding pass. Provide the viewer name in the box or click Browse to find its location. Windows Notepad is the default viewer.

OK

Cancel

Apply

Help

Closes the dialog and saves the changes that you have made.

Closes the dialog and cancels the changes that you have made.

Applies the settings that you specified.

Displays help on this dialog.

Table Georesult Summary dialog

The table Georesult Summary Dialog appears when you click Table > Table Summary. The Table

Summary option is available only after MapMarker has opened a table. If a table has a georesult column, this dialog generates a report providing statistics about the number and type of geocodes.

MapMarker 23

251

User Guide

Appendix A:

MapMarker Dialogs

Select the georesult column

This list contains an alphabetical list of the column headings in your table.

Choose a column that contains georesult codes and click OK. A report is generated with statistics based off the georesult codes in the specified column.

OK

Cancel

Help

Invokes the settings and closes the dialog. The settings are saved in the table’s metadata until you clear them.

Cancels the operation and closes the dialog.

Displays help on this dialog.

Text File Wizard (Step 1 of 3)

This is the first dialog box in the Text File Wizard.

Text File Type

Delimiter Type

Delimited is the only supported text file type.

If MapMarker can determine the delimiter type (comma, semicolon, tab, slash, or other), the delimiter will be preselected. Otherwise, you can specify the delimiter type (comma, semicolon, tab, slash, or other).

MapMarker 23

252

User Guide

Appendix A:

MapMarker Dialogs

First Line Used for

Column Titles

Next

Cancel

Help

Specifies that the first line of the input file is used for column titles rather than data.

Go to the next dialog in the Text File Wizard.

Cancels the operation and closes the dialog.

Displays help on this dialog.

Text File Wizard (Step 2 of 3)

This is the second dialog box in the Text File Wizard. Click a field name to see all the relevant the

Information for that field. You can view this information and may be able to change some fields.

Fields

Name

Width

List Box

Back

MapMarker 23

Click a field name to see all the relevant the Information for that field. You can use the following fields to view and possibly change any of this information.

Displays the name of the selected field.

Displays the width of the selected field. This cannot be changed in this dialog.

The list box area at the bottom of the dialog will display up to the first 20 records of the opened file.

Returns to

Text File Wizard (Step 1 of 3)

.

253

User Guide

Appendix A:

MapMarker Dialogs

Next

Cancel

Help

Go to the next dialog in the Text File Wizard.

Cancels the operation and closes the dialog.

Displays help on this dialog.

Text File Wizard (Step 3 of 3)

This is the final step of the Text File Wizard.

Input Path

Output Path

Back

OK

Cancel

Help

This shows the data input path. This is for display only and cannot be changes at this point.

Specify the full path of the output file. If the file already exists, data will be overwritten.

Returns to

Text File Wizard (Step 2 of 3)

.

Completes the Text File Wizard.

Cancels the operation and closes the dialog.

Displays help on this dialog.

User Dictionary Wizard (Step 1 of 3)

MapMarker 23

254

User Guide

Appendix A:

MapMarker Dialogs

The User Dictionary Wizard allows you to create a custom address dictionary from a MapInfo table.

This first step in the User Dictionary Wizard requires that you select a MapInfo table and specify the rows within it to use in creating the User Dictionary.

Table Name

All Rows

Row Numbers

Specify the path of the MapInfo table you wish to use as the source table for the user dictionary.

Browse

Navigate to the location of the MapInfo table. You cannot proceed with using the User Dictionary Wizard without specifying a MapInfo table.

Rows to Process

Use the options in this group to specify what part of the table you want to use to create the user dictionary.

Process all table rows in creating the User Dictionary.

Process a defined range of table rows when creating the User Dictionary.

Provide the row number range in the text boxes below this option, typing the starting row number for the range in the first text box and the ending row number for the range in the second text box.

Back

Next

Cancel

Help

Click Back to return to the previous step in the User Dictionary Wizard. This button is disabled in this first step.

Click Next to continue to the next step in the User Dictionary Wizard. This button is available after a table is selected.

Click Cancel to close the User Dictionary Wizard and return to the

MapMarker workspace.

Displays help on this dialog.

MapMarker 23

255

User Guide

User Dictionary Wizard (Step 2 of 3) dialog

Appendix A:

MapMarker Dialogs

The User Dictionary Wizard allows you to create a custom address dictionary from a MapInfo table.

This first step in the User Dictionary Wizard requires that you select a MapInfo table and specify the rows within it to use in creating the User Dictionary.

Click and drag a column name from this list into the Required Columns group. To remove a column name from a box, highlight <CLEAR> and with the mouse button still depressed, drag <CLEAR> over the contents of a box and release the mouse button.

If you do not specify a column for each field, the Wizard prompts you to do so.

Table

Required Columns

Lists all columns for the table specified in Step 1.

Select the appropriate columns from the list that have these required address components.

Left Starting Address

Number

The column containing the beginning number of an address range for the left side of a street segment.

Right Starting Address

Number

The column containing the beginning number of an address range for the right side of a street segment.

Left Ending Address

Number

The column containing the ending number of an address range for the left side of a street segment.

Right Ending Address

Number

The column containing the ending number of an address range for the right side of a street segment.

Street Name

The column containing the street names.

MapMarker 23

256

User Guide

State

Left ZIP Code

Right ZIP Code

Back

Next

Cancel

Help

Appendix A:

MapMarker Dialogs

The column containing the state names.

The column containing the 5 or 9-digit ZIP Code™ for the left side of a street segment.

The column containing the 5 or 9-digit ZIP Code for the right side of a street segment.

Click Back to return to the previous step in the User Dictionary Wizard.

Click Next to continue to the next step in the User Dictionary Wizard.

This is available after Required Columns are specified.

Click Cancel to close the User Dictionary Wizard and return to the

MapMarker workspace.

Displays help on this dialog.

User Dictionary Wizard (Step 3 of 3) dialog

This is the final step of the User Dictionary Wizard.

Table

Optional Columns

Left ZIP + 4

MapMarker 23

Lists all columns for the table specified in Step 1.

Select the appropriate columns from the list that have these optional address components.

The column containing the ZIP + 4

®

(4-digit ZIP Code™ expansion) for the left side of a street segment.

257

User Guide

Appendix A:

MapMarker Dialogs

Right ZIP + 4

The column containing the ZIP + 4 (4-digit ZIP Code expansion) for the right side of a street segment.

Left Census Block

The column containing the Census Block ID for the left side of a street segment.

Right Census Block

The column containing the Census Block ID for the right side of a street segment.

Left Odd/Even

Indicator

Right Odd/Even

Indicator

Place Name

City Name

Back

Finish

Cancel

Help

The column containing the odd/even street number indicator for the left side of a street segment.

The column containing the odd/even street number indicator for the right side of a street segment.

The column containing the name of the company residing at an address.

The column containing the city name.

Click Back to return to the previous step in the User Dictionary Wizard.

Click Finish to complete the User Dictionary Setup.

Click Cancel to close the User Dictionary Wizard and return to the

MapMarker workspace.

Displays help on this dialog.

MapMarker 23

258

User Guide

Creating a Map Catalog

Manually

This appendix includes instructions for creating a MapInfo Map Catalog manually and making a remote table mappable, two procedures that are necessary for geocoding remote tables.

This information is designed for users who do not have access to MapInfo

Professional. If you have MapInfo Professional, see the MapInfo Professional

User’s Guide for instructions on carrying out these procedures automatically.

The MapInfo Professional online help system includes topics on Creating a

MapInfo_MapCatalog and Making a Remote Table Mappable.

For more complete details on remote table geocoding see

Geocoding Remote

Tables in Chapter 8 on page 167

.

In this appendix:

Š

Manually Creating a MapInfo Map Catalog . . . . . . . . . . . . . . . . .260

Š

Adding Rows to the MapInfo_MapCatalog. . . . . . . . . . . . . . . . . .261

B

Appendix B:

Manually Creating a MapInfo Map Catalog

Manually Creating a MapInfo Map Catalog

If you are not a MapInfo Professional or EasyLoader user, you or your database administrator will need to create the Map Catalog manually, as described below. You only have to create the Map

Catalog once per server/database.

1. Create the user MAPINFO in the specific database where the mappable tables are located.

2. Create the table MAPINFO_MAPCATALOG in the database.

The Create Table statement needs to be equivalent to the following SQL Create Table statement:

Create Table MAPINFO_MAPCATALOG (

SPATIALTYPE Float,

TABLENAME Char(32),

OWNERNAME Char(32),

SPATIALCOLUMN Char(32),

DB_X_LL Float,

DB_Y_LL Float,

DB_X_UR Float,

DB_Y_UR Float,

VIEW_X_LL Float,

VIEW_Y_LL Float,

VIEW_X_UR Float,

VIEW_Y_UR Float,

COORDINATESYSTEM Char(254),

SYMBOL Char(254),

XCOLUMNNAME Char(32),

YCOLUMNNAME Char(32),

RENDITIONTYPE INTEGER,

RENDITIONCOLUMN CHAR(32),

RENDITIONTABLE CHAR(32)

NUMBER_ROWS INTEGER

)

L

It is important that the structure of the table looks exactly like this statement. The only substitution that can be made is for databases that support varchar or text data types; these data types can be substituted for the Char data type.

3. Create a unique index on the TABLENAME and the OWNERNAME, so only one table for each owner can be made mappable. create unique index mapcat_i1 on mapinfo.mapinfo_catalog (OwnerName,TableName)

4. Grant Select, Update, Insert, and Delete privileges on the MAPINFO_MAPCATALOG. This allows users to make tables mappable. The delete privilege should be reserved for database administrators.

grant select, insert, update, delete on mapinfo.mapinfo_mapcatalog to public

MapMarker 23

260

User Guide

Appendix B:

Adding Rows to the MapInfo_MapCatalog

Adding Rows to the MapInfo_MapCatalog

For each spatial table that you want to access from your application, you need to add a row to the

MAPINFO_MAPCATALOG table. If you do not use MapInfo Professional to manage the

MapInfo_MapCatalog, you will have to add rows to the MAPINFO_MAPCATALOG table manually.

The following describes the syntax and meaning of each column in the

Map Catalog Table

.

Column Name

SPATIALTYPE

TABLENAME

OWNERNAME

SPATIALCOLUMN

DB_X_LL

DB_Y_LL

DB_X_UR

Map Catalog Table

Values to Assign Examples

MapInfo Spatial Object Format

See

Spatial Index Types for SPATIALTYPE

Spatial Object Type

x.0: Points only x.1: Lines only x.2: Regions only x.3: All types supported

This column describes the Spatial Object Format of how the data is stored and indexed and the Spatial Object type(s) supported and not supported in the column. The digits to the left of the decimal point are the Spatial

Object Format. The digits to the right represent the type of Spatial Object Type that can be stored in the column

23.0 = SQL Server

The name of the table.

The owner name of the table.

The name of the column, if any, containing spatial features:

SW_GEOMETRY

(mappable using SpatialWare Type/IDS/UDO)

NO_COLUMN (mappable using X–Y)

MI_SQL_MICODE (mappable using MI Code) Or the name of the IDS/UDO, or Oracle column that is

ST_SPATIAL datatype.

Name of the Oracle SDO_GEOMETRY column.

The X coordinate of the lower left corner of the layer’s bounding rectangle, in units that are indicated by the

COORDINATESYSTEM (see below).

The lower left bounding Y value.

The upper right bounding X value.

STATES

BOB

SW_GEOMETRY

–360

–90

360

MapMarker 23

261

User Guide

Appendix B:

Adding Rows to the MapInfo_MapCatalog

Column Name

DB_Y_UR

VIEW_X_LL

Map Catalog Table (continued)

Values to Assign

The upper right bounding Y value.

90

The X coordinate of the lower left corner of the default view.

The default view only applies if this is the first table to be opened.

-180

Examples

VIEW_Y_LL

VIEW_X_UR

The lower left bounding Y value of the default view.

-45

The upper right bounding X value of the default view.

180

VIEW_Y_UR The upper right bounding Y value of the default view.

45

COORDINATESYSTEM A string representing a MapInfo CoordSys clause (but without the keyword CoordSys at the very start), which specifies a map projection, coordinate units, etc. For simple Lon/Lat maps, specify Earth Projection

1, 0.

Earth Projection

1, 0

SYMBOL A MapInfo Symbol clause (if the layer contains only points); or a Symbol clause followed by a Pen clause

(indicating styles for linear features) followed by another

Pen clause (indicating styles for the borders of regions) followed by a Brush clause.

Symbol(35,0,12)

Pen(1,2,0)

Pen(1,2,0)

Brush(2,255,255)

XCOLUMNNAME

YCOLUMNNAME

For the X/Y mappable tables, specify the name of the column containing X-coordinates. If there is no such column (i.e., if this table uses a single spatial column instead of a pair of X-Y columns) then specify

NO_COLUMN or leave empty.

For the X/Y mappable tables, specify the name of the column containing Y–coordinates, or specify

NO_COLUMN

NO_COLUMN

NO_COLUMN

MapMarker 23

262

User Guide

Appendix B:

Adding Rows to the MapInfo_MapCatalog

Map Catalog Table (continued)

Values to Assign Examples Column Name

RENDITIONTYPE

NUMBER_ROWS

This indicates how the object style information is applied.

0 – Indicates that all the objects in the table will have the style specified in the symbol field of the MapCatalog applied to them. No per-record styles are in effect.

Objects will be read/updated using the default style for the table.

0 or 1

1 – Indicates that the table uses per-record styles. The table has a separate column that contains a MapBasic string representation of the style information for each object in the table (the same format that is currently used in the MapCatalog SYMBOL column). The style column in the table is recorded in

RENDITIONCOLUMN.

RENDITIONCOLUMN If RENDITIONTYPE is 1, this field stores the name of the column in the spatial table that contains style information. This column is automatically added to any query against the table and is maintained (updated) as the object is updated. Users should NOT specify this column in their queries as problems can occur with intersect or update statements. Queries which include this column in the select clause (excluding the wildcard character “

*

”) may access the values through the

Dataset object. Rows with a NULL value in their style column will have the style from the SYMBOL field of the

MapCatalog applied to the object.

MI_SYMBOLOGY

Creates a MapInfo.Column.DataType with

MIDBType.Style

RENDITIONTABLE Currently not used, but reserved for future use.

NULL

Currently used by MapInfo Professional.

NULL

MapMarker 23

263

User Guide

Appendix B:

Adding Rows to the MapInfo_MapCatalog

Spatial Index Types for SPATIALTYPE

This table lists the supported Spatial Index types for SPATIALTYPE.

.

Spatial Index Types

Spatial Index Type Type Number

1 MapInfo MICODE schema (any database) — Point layer in X/Y columns indexed with micode (a serialized quadtree key)

XY schema (any database) — Point layer in X/Y columns

Oracle Spatial Geometry

SpatialWare for Microsoft SQL Server

Oracle Spatial Annotation Text

SQL Server Spatial (for geometry)

SQL Server Spatial (for geography)

PostGIS for PostgreSQL

SQL Server Spatial with M and Z values (for geometry)

SQL Server Spatial with M and Z values (for geography)

4

13.x

14.x

16.x

17.x

18.x

19.x

20.x

21.x

Per-Record Styles

Per-record style allows geometry in a single table to have its own style. For example, a single 'public institution' table in Oracle Spatial can have schools, town halls, libraries, and police departments and each point type would be represented with its own symbol (i.e., a school symbol for all the schools).

Similarly, a single road table in SpatialWare SQL Server may have different road types such that streets are shown as a single pixel black line, secondary roads as a double pixel red line and interstates as parallel red lines.

To use per-record styles, your table must be represented with an entry in the MapInfo Map Catalog with appropriate settings for RENDITIONTYPE, RENDITIONCOLUMN, and RENDITIONTABLE.

L

If these columns are not present, the table’s default style will be applied to all objects.

Symbol, Pen, Brush Clause Syntax

If you are manually creating a MAPINFO_MAPCATALOG table to provide support for a remote spatial database, you will need to specify a symbol style, and possibly line and fill styles as well.

MapMarker 23

264

User Guide

Appendix B:

Adding Rows to the MapInfo_MapCatalog

Specifying Point Styles

Use a Symbol clause to specify point styles. There are three types of Symbol clauses: one for specifying MapInfo 3.0-style symbols; one for specifying TrueType font symbols; and one for specifying bitmap symbols.

Point Styles

Symbol Syntax

Symbol(shape, color, size) or

Symbol(shape,color,size,font,fontstyle,rotation) or

Symbol(bitmapname,color,size,customstyle)

Example

Symbol(35,0,12)

Symbol(64,255,12,"MapInfo

Weather",17,0)

Symbol("sign.bmp", 255, 18, 0)

Specifying Line Styles

Use a Pen clause to specify line styles. In a MAPINFO_MAPCATALOG table, you may need to specify two pen clauses: one to specify the appearance of linear features, and another to specify the appearance of region borders.

Line Styles

Pen Syntax

Pen(thickness, pattern, color)

Pen(1, 2, 0)

Example

Specifying Fill Styles

Use a Brush clause to specify the style for closed features (regions).

Brush Syntax

Brush(pattern,color,backgroundcolor)

Fill Styles

Example

Brush(2, 255, 65535)

MapMarker 23

265

User Guide

Frequently Asked

Questions

In this FAQ:

Š

Q: I have a table that I cannot geocode because I get the error

“Unable to update row.” What does this mean and how can I fix it?

Š

Q: I open a table in MapInfo Professional and I am able to open that same table in MapMarker. Is this safe?

Š

Q: How can I improve MapMarker’s performance?

Š

Q: What determines if a row is unmatched?

Š

Q: After geocoding, some of my records have a result code of

“ND.” What does this mean?

Š

Q: What is the breakdown of the Census Block code?

Š

Q: What is the MapMarker Geoengine API and how can I use it?

Š

Q: When geocoding, how can I prevent firm names from matching to street names?

Š

Q: What is the difference between the Desktop product and the

Developer Product?

Š

Q: Why am I generating different results from the GeoEngine APIs vs. the MapMarker Desktop (UI)?

C

Appendix C:

Frequently Asked Questions

Frequently Asked Questions

Q: I have a table that I cannot geocode because I get the error “Unable to update row.” What does this mean and how can I fix it?

A: This error occurs when MapMarker attempts to create the point object for a given row and is unable to do so. To fix this problem, remove the map from the table, and use either MapMarker or

MapInfo Professional to re-create the map file associated with the table.

To use MapInfo Professional to remove the map file association, select Table > Maintenance >

Table Structure from the menu, and clear the “Table is Mappable” check box. This causes the map to be dropped from the table and all the objects associated with the table to be removed. Alternatively, you can delete the MAP file associated with the table manually.

After dropping the map, simply open the table with MapMarker and re-geocode the table.

MapMarker automatically makes any table that you open mappable, and you are able to geocode the table without getting the error.

Note that this error may also result from running out of disk space while geocoding with MapMarker.

Q: I open a table in MapInfo Professional and I am able to open that same table in MapMarker. Is this safe?

A:

No. Avoid opening tables with MapMarker that are already open in MapInfo Professional.

Because of limitations on the number of files that a Windows application can open at one time,

MapInfo Professional closes files that are not actively being used. Once MapInfo Professional has closed all the files associated with a table, MapMarker is able to open that same table, potentially causing a conflict between the two applications.

Q: How can I improve MapMarker’s performance?

A:

Performance is improved by sorting the table to geocode by ZIP Codes™. You can also improve performance by requiring an exact match on street names and/or ZIP Codes. Other things you can do are the following:

• Use the fastest processor available to you.

• Have enough memory so that the operating system can allocate some memory to your disk cache.

• Copy the Address Dictionary to your hard drive.

• Do not create points automatically.

MapMarker 23

267

User Guide

Appendix C:

Frequently Asked Questions

Q: What determines if a row is unmatched?

A:

Unmatched rows are those rows in your table that have a result code that is either blank or contains an “N”. These are the only rows that MapMarker attempts to match when you choose to geocode unmatched rows. It is important to note that unlike the MapInfo Professional geocoder,

MapMarker does not use the existence of a point object to determine if a row has been previously matched.

Note that MapMarker does not remove points from table rows that it does not match. If a table contains pre-existing point objects, delete these objects before geocoding to ensure that your results accurately reflect your current geocoding session.

If you have records for which you want to preserve pre-existing points, mark them as non-geocodable by putting the result code “NG” into the result code column. MapMarker does not attempt to match records with a result code of “NG” even if you choose to match all rows in a table.

Q: After geocoding, some of my records have a result code of “ND.”

What does this mean?

A:

ND stands for “No Data:” This means that the file containing the address matching data needed for that record was not found in your data path or that the area is not licensed. You get this result if you copy a subset of the MapMarker address dictionary to your hard disk and attempt to geocode addresses that are outside of that area.

Remember, you can include more than one directory in your MapMarker data path, and the path is searched in the order in which it appears. This means that you can move the two-digit ZIP Code™ files for New England to your hard drive and leave the complete U.S. Address Dictionary on

DVD-ROM. For example, your data path could be: c:\mapinfo\mapmarkr\nedata;d:\data where c:\mapinfo\mapmarkr\nedata is the hard drive location of your New England data subset and d:\data is the Address Dictionary DVD-ROM. The path components are separated by a semicolon.

Q: What is the breakdown of the Census Block code?

A:

MapMarker can return the full 15-digit Census Block ID only for a successfully geocoded record with an S8, S7, S5 result code. An S4 can return a complete 15-character Census Block ID, but only if the block groups on each side of the street are the same and if a house number is provided. An S3 result can return no more than a 12-digit Census Block Group number.

The complete Census Block ID code is as follows:

SSCCCTTTTTTGBB(B) where

S = State FIPS (Federal Information Processing Standard) code (2 characters)

C = County FIPS code (3 characters)

T = Census Tract (6 characters)

G = Census Block Group (1 character)

B = Census Block (typically 2 characters, sometimes 3).

MapMarker 23

268

User Guide

Appendix C:

Frequently Asked Questions

Q: What is the MapMarker Geoengine API and how can I use it?

A:

The MapMarker Geoengine API is a programmatic interface to the 32 bit Windows DLLs that contains the code that MapMarker uses to match addresses and return the lat/long coordinates of those addresses (UNIX libraries are also available). We provide this API and the header files that allow you to use it so that you can add geocoding capabilities to your own programs.

Included are C header files, definition files for MapBasic and Visual Basic, and several sample programs that show how to use the geocoding libraries. Note that use of the MapMarker API is not limited to these development environments only. The API can be used with any environment that provides a way to call routines in an external DLL.

Q: When geocoding, how can I prevent firm names from matching to street names?

A:

One way to keep firm names from matching to street names is to require exact match on the house number. MapMarker does not match an input without a house number to an address with a house number. Since a firm name never has a house number, you never get a firm name matching to a street range.

Data often has the firm names and street names in the same columns or swapped. Therefore,

MapMarker looks at both the firm name and the street address fields to try to determine the address.

Firm names can be very close to a street names. For example, "Little Johns", "Albany NY 12203" could match to "Little Johns Pizza" or "1 Little John Rd" which are both in that ZIP Code™. Neither one is an exact match to the input. In this case it would return a multiple match.

In general, requiring an exact match on the house number produces more accurate geocoding. Not requiring this introduces a significant chance of positioning the point a distance from the real point. If

MapMarker does not find the house number in a range for a street, it matches it to the closest one.

Q: What is the difference between the Desktop product and the

Developer Product?

MapMarker can be licensed as a Desktop edition or Developer edition. The Desktop Edition includes the Desktop Application which includes the graphical user interface for geocoding addresses and the MapMarker Address Dictionary. You can purchase data for all 50 states (plus D.C. and Puerto

Rico), regional state bundles, or individual state data. Related documentation is also provided.

L

The Desktop Application runs on Microsoft Windows only.

The Developer edition includes the MapMarker Desktop Application and the tools necessary for developing MapMarker solutions using the popular Java programming language. These tools include the MapMarker SDK, native code libraries, and examples. A preconfigured Apache Tomcat servlet is provided to run MapMarker as a geocoding server.

MapMarker 23

269

User Guide

Appendix C:

Frequently Asked Questions

Q: Why am I generating different results from the GeoEngine APIs vs. the

MapMarker Desktop (UI)?

A: When geocoding using the GeoEngine APIs and the MapMarker Desktop (UI) there are differences between both result codes and candidates.

ResultCode/GeoResult – If the GeoEngBuildResultCode() is used from the API, then result codes must be the same except that there is no ND result code. These are just N result codes.

Candidates – If comparing results from batch geocoding to geocode results generated by the API, the results should be the same (assuming that the same input table geocoding preferences were used). However, differences occur when handling Private Mailbox (PMB) addresses, since PMB handling exists in CASS™ mode. Therefore, do not compare PMB results to non-CASS™ mode results.

QuickFind/Interactive candidate lists can be different than candidate lists generated from the API.

Both methods relax street names, postcode, and house number. In addition, they both set the interactive flag (GeoEngSetInterActive()). This flag can dramatically affect the candidate list returned. Setting this flag allows the maximum number of candidates to be returned. Candidates that would ordinarily be discarded are returned in this mode.

MapMarker 23

270

User Guide

MapMarker Utility

Programs

This appendix describes utility programs that are installed with MapMarker: Find

Address and Append. Note that these are MBX programs that must be run from

MapInfo Professional.

In this appendix:

Š

FindAddress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272

Š

Append . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273

D

Appendix D:

FindAddress

FindAddress

FindAddress is a MapBasic application that allows you to find any address contained in the

MapMarker Address Dictionary or from a customized user dictionary and display the location in

MapInfo Professional. You can find street intersections as well. FindAddress is included on the

MapMarker DVD-ROM and installs in the MapMarker installation directory. FindAddress uses the

MapMarker geocoding engine and the Address Dictionary to match the U.S. address or street intersection you want to find and spot on the map.

FindAddress is run from within MapInfo Professional. It is installed on the Tools menu when you invoke the MapBasic application.

Running FindAddress

To run FindAddress:

1. From MapInfo Professional, select Run MapBasic Program. The Run MapBasic Program dialog is displayed.

2. Select findad32.mbx from the MapMarker directory. Click OK. FindAddress is added to the Tools menu.

3. With an active Map window displaying the general area of the address you wish to find, select

Tools > FindAddress > Locate Address. The Find Address dialog is displayed.

4. Type the address you want to find. You must enter the street name and either the city/state or the

ZIP Code™. Click FindAddress. MapInfo Professional locates the address and marks the location with a symbol. To match to ZIP Code centroids, enter at least a 5 or 9 digit ZIP Code and click Map Centroid.

To find a street intersection, in the Street Address text box enter the first street name followed by the ampersand (&) or the word and followed by the second street name. For example: East 37th

Street & Avenue P. Click FindAddress. MapInfo Professional locates the intersection.

5. If multiple address or intersection candidates are found, FindAddress appears them in the

Candidate Address dialog. Highlight the appropriate address or intersection. The ranges of that address are displayed in the Ranges dialog. To spot the location on the map, click Map

Candidate.

6. To find the ZIP Code centroid for your address, type in the ZIP Code and click Map Centroid.

MapInfo Professional spots a symbol at the ZIP Code centroid.

7. Close the FindAddress dialog by clicking Close Window. The Map window appears and the symbol for the located address is visible.

8. To change the default symbol, the zoom level for the Map window, or to relax address matching conditions, select Tools > FindAddress > Options. Note that changing the zoom level in the

Options dialog only takes effect after you have located another address in the FindAddress dialog. For the zoom level units, FindAddress uses the settings you set in Map > Map Options.

MapMarker 23

272

User Guide

Appendix D:

Address Dictionary

Address Dictionary

FindAddress needs to know the location of the MapMarker Address Dictionary to find your addresses. This information is contained in two places in the Windows Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\MAPINFO\MAPMARKER\USA\<version number>\

SYSTEM\DatabasePath

HKEY_CURRENT_USER\SOFTWARE\MAPINFO\MAPMARKER\USA<version number>\

SYSTEM\DatabasePath

L

In references to the MapMarker registry keys, <version number> shows the major-release version of MapMarker, for example, 23.0 even if you are running one of the point releases of that version, such as, 23.1

If you move the Address Dictionary at any time, be sure to update the new path information in either of these places so that FindAddress works properly.

You can find addresses or street intersections from a customized user dictionary as well as from the

MapMarker Address Dictionary. See

Custom User Dictionaries in Chapter 9 on page 179

for more information.

Append

Append is a utility program included in MapMarker that combines two or more MapInfo tables into a new table or adds them to an existing table. These tables must have the same number of columns and data types for each column. We recommend using Append for making one large MapInfo table when creating MapMarker User Dictionaries.

Append runs from within MapInfo Professional as an add-on application. A series of dialogs are displayed where you can specify the starting drive and directory of the search and select any available options. Append.mbx is located in the mbx directory after installing MapMarker.

Append.mbx and iputil32.dll must be in the same directory.

Running Append

To run the Append program from within MapInfo:

1. In MapInfo Professional, select File > Run MapBasic Program. The Run MapBasic Program dialog appears.

2. Select APPEND.MBX from the directory where MapMarker is installed.

3. Click OK. The DataKit menu is added to the menu bar.

4. Select DataKit > Append > Append Tables to display the Append Tables dialog.

MapMarker 23

273

User Guide

Appendix D:

Append

5. Choose a processing mode. Select Use Interactive Mode to choose individual groups of tables to append. The tables are placed in a queue for Append to concatenate. For more information on

Interactive Mode, see

Append Interactive Mode

.

If you want the Append program to use a text file to determine which tables to append and how to append them, select the Use Input File Mode check box. For more information on Input File

Mode see

Append Input File Mode

.

6. Click OK in the Append Tables dialog to start processing.

While Append runs, the program appends tables and writes out the new appended table with or without the table ID field, depending on the options you have chosen. When the program finishes, Append records a summary of the results in the message file and a dialog is displayed showing the elapsed processing time. You may open the message files in any text editor such as Notepad.

7. When you have finished, select DataKit > Append > Exit Append to close the program. If the

Append command is the last item left in the DataKit menu, exiting the program also removes the

DataKit menu.

Append Interactive Mode

Interactive Mode allows you to specify each process one at a time. This allows you to build an interactive list of tables that Append processes. Follow these guidelines to use Append in interactive mode. Follow these steps for each group of tables you wish to append.

1. Click on the tables you want to select in the Table Names list. You can change the directory and drive to display other tables. Keep the following in mind when choosing your tables:

• Append does not let you concatenate tables if the numbers of columns in all of the tables are not the same. The program returns you to the Append Tables dialog if you attempt to do this.

• If the number of columns in all of the tables is the same but they do not share the same data types between column numbers, Append tries to resolve the differences in the column types.

When this happens, Append may change some of the data types of your columns. If there are changes, Append records these changes in the message file. If Append cannot resolve the data type differences, the program returns you to the Append Tables dialog.

• If the number and types of columns in the appended tables are the same but the names are different, Append names the resulting columns according to the following rules. If you are appending tables to an existing table, the column names of the existing table does not change. If you are creating a new table with Append, the table has the same name as the first table that you selected in the Table Names list.

2. To insert a table identifier field into the output table, select the Insert Table ID field check box.

The table identifier field contains the source table name for each row.

3. Click on Add to List. Append prompts you for the output name of the appended table. Enter the table name and click OK.

4. Click on View/Save List to inspect or save the current interactive list. You may want to do this if you intend to process the same tables later in Input File Mode. To remove all the items in the current interactive list, click Clear List.

MapMarker 23

274

User Guide

Appendix D:

Append

Append Input File Mode

Input File Mode allows you to specify an input text file that Append uses to process many tables without having to add them into a list one at a time. The input file is a formatted file that contains command lines for Append. The command lines list the files that are joined and instruct the Append program which options to use when processing. This method is most convenient when you have a large number of tables that must be appended and you do not want to go through the process of selecting the tables through the graphical interface.

Below is the format of the command line that you must use and some examples that use the format.

append <input_table_name_list> [/table-id] /output <output_table_name> for example, append c:\data\test1.tab test2.tab /table-id /output newtest.tab append test1.tab test2.tab /output c:\data\newtest.tab

The first example creates a table called newtest that is a concatenation of two other tables: test1 and test2. This example also creates a new column in the newtest table (Table_ID) that holds the source table for each record.

The second example is similar to the first except that Append does not create a Table_ID column; the paths for the source and output tables are also different.

To use Append in Input File Mode, do the following:

1. Select the Use Input File Mode check box.

2. Click Set Input File Name to specify the name of the input file that Append must use.

APPEND.MSG File

Append produces a message file for each processing session that contains information about the tables that were appended. Append names the message file APPEND.MSG and places the file in the same directory as the output tables. If the file APPEND.MSG already exists, Append adds the new information to the end of the existing file.

Considerations when Running Append

If you append a file that is currently open, Append closes the table before the program processes it.

If the table has pending edits, Append displays a dialog that asks you whether you want to save or discard those edits before appending.

If you are using input file mode, be sure that none of your command lines conflict or overwrite files produced by a previous line in your input file.

MapMarker 23

275

User Guide

U.S. ZIP Code Ranges

This table identifies the range of ZIP Codes™ assigned to states and territories by the U.S. Postal Service

®

.

In this appendix:

Š

ZIP Code Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277

E

ZIP Code Ranges

State/Territory

Puerto Rico/Virgin Islands

Massachusetts

Rhode Island

New Hampshire

Maine

Vermont

Connecticut

New Jersey

New York

Pennsylvania

Delaware

District of Columbia

Maryland

Virginia

West Virginia

North Carolina

South Carolina

Georgia

Florida

Alabama

09000-14999

00400-06399

15000-19699

19700-19999

20000-20599

20600-21999

22000-24699

20100-20199

24700-26899

27000-28999

29000-29999

30000-31999

39900-39999

32000-34999

35000-36999

ZIP Code Range

00600-01000

01000-02799

05500-05599

02800-02999

03000-03899

00200-00299

03900-04999

05000-05999

06000-06999

07000-08999

MapMarker 23

277

Appendix E:

ZIP Code Ranges

User Guide

State/Territory

Tennessee

Mississippi

Kentucky

Missouri

Kansas

Nebraska

Louisiana

Arkansas

Oklahoma

Texas

Ohio

Indiana

Michigan

Iowa

Wisconsin

Minnesota

South Dakota

North Dakota

Montana

Illinois

Colorado

Wyoming

Idaho

MapMarker 23

66000-67999

68000-69399

70000-71499

71600-72999

73000-74999

75000-79999

73300-73399

88500-88599

80000-81699

82000-83199

83200-83899

ZIP Code Range

37000-38599

38600-39799

40000-42799

45200-45299

43000-45999

46000-47999

48000-49999

50000-52899

53000-54999

55000-56799

57000-57799

58000-58899

59000-59999

60000-62999

75500-75599

63000-65899

278

Appendix E:

ZIP Code Ranges

User Guide

Utah

Arizona

State/Territory

New Mexico

Nevada

California

Hawaii

Oregon

Washington

Alaska

Guam

ZIP Code Range

84000-84799

85000-86599

87000-88499

88900-89899

90000-96699

96700-96899

97000-97999

98000-99499

99500-99999

96900-96999

Appendix E:

ZIP Code Ranges

MapMarker 23

279

User Guide

Index

Index

A

abbreviated addresses

returning

138

abbreviated city names

returning

139

About MapMarker

dialog

201

About MapMarker menu command

192

accessing remote tables

MapInfo_MapCatalog

260

specifying styles

264

Add Columns

dialog

202

address dictionary

available

17

definition

43

FindAddress utility

272

–

273

installing

27

storing on hard drive

27

system preferences

101

–

102

address matching

73

geocoding

14

input columns

48

,

64

–

65

,

68

output columns

49

,

54

,

66

address point interpolation

102

,

116

address range

geocoding

78

airports

locating

151

append.mbx

273

,

275

Arrange Icons menu command

192

attribution

add output column

68

,

160

–

161

adding attributes

164

–

165

adding columns

158

,

162

attaching data to geocoded records

157

batch process

165

clearing file selections

166

column value

157

,

163

–

164

considerations

166

output point

157

,

162

–

163

selecting a table

159

selecting table

162

stopping

165

–

166

attribution table

selecting

159

automatic geocoding

69

,

203

MapMarker 23

280

B

batch add attributes

192

batch attribution

165

batch file

creating manually

154

batch geocoding

153

–

154

,

156

–

157

CASS settings

157

best match from multiple candidates

result codes

119

bind attribute table columns to output columns

204

binding

attribute columns to output

68

,

86

,

159

–

160

browsing

147

browsing address records

quick find

147

brush styles

in remote spatial tables

264

C

Candidate Map

dialog

205

candidate visualization

displaying your match on a map

73

interactive geocoding

111

street data path

104

,

111

candidates

definition

43

Cascade menu command

192

CASS

definition

43

geocoding

123

,

126

match settings

90

CASS match mode

89

,

226

CASS settings

batch geocoding

157

Census Block IDs

51

,

54

,

268

center line offset

103

,

231

centroid

definition

43

Choose Font menu command

192

clear file selections

193

client installation

40

close match

definition

43

Close menu command

193

CMRA

User Guide

definition

44

column value attribution

157

,

163

–

164

columns

input

48

,

64

–

65

,

68

output

49

–

50

,

54

,

66

commands

192

copy from quick find results

quick find

copy from

146

corner offset

103

county

geocoding

66

Create Batch File menu command

193

Create User Dictionary menu command

194

Create/Save Project menu command

194

creating

map catalogs

170

MapInfo_MapCatalog

260

standalone geocoding applications

269

user dictionary

181

,

186

–

187

user dictionary wizard

185

,

187

custom user dictionary

creating

186

D

data

installing

27

storing

27

databases

supported

168

dBASE files, geocoding

142

delimited text file

first line

60

output

61

delimiter type

60

Describe Table Relationships

dialog

208

dialogs

About MapMarker

201

Add Columns

202

Automatic Geocode

203

Bind Attribute Table Columns to Output

Columns

204

Candidate Map

205

Describe Table Relationships

208

Dictionary preferences

209

Export to

210

,

241

Export to ESRI Shapefile

211

Fallback preferences

212

Filter Tables

213

Font

214

Geocode preferences

215

Geocoding Summary

216

GeoResult

217

Interactive Geocode

218

Locate Airport

220

Locate Highway Exit

222

Log File preferences

223

Maps preferences

224

Match Settings

225

Modify Table Structure

228

Multiple Match preferences

230

Offset preferences

231

Open

233

Quick Find

234

Quick Find Settings

236

Related Table

239

Save Batch File As

240

Select Attribute Tables

242

Select input columns from your table

244

Select output columns from your table

246

Select Table

248

Select Table Type

249

Startup Preferences

250

Table Georesult Summary

251

Text File Wizard

253

Text File Wizard 1

252

Text File Wizard 3

254

User Dictionary Wizard

254

,

256

–

257

dictionary preferences

101

–

102

dialog

209

displaying geocoded records

82

distance units

102

DPV

129

,

131

,

135

adding columns

131

–

132

definition

44

re-enabling

135

street directionals

130

usage requirements

131

using

129

dual addresses

geocoding

140

E

editing records interactively

74

error files

location

86

EWS

definition

44

exact match

90

Exit menu command

194

Export to

dialog

210

,

241

Export to ESRI Shapefile

Index

MapMarker 23

281

User Guide

dialog

211

Export to Shapefile

menu command

194

export to Shapefile

62

,

211

F

fallback preference

to geographic centroid

94

to ZIP Code

94

fallback preferences

dialog

212

false positives

reducing

107

–

108

fill styles

in remote spatial tables

265

Filter Tables

dialog

213

FindAddress

272

–

273

Font

dialog

214

frequently asked questions

267

,

270

G

Geocode

menu command

195

toolbar button

195

geocoding

scoring model

46

geocoding matches

displaying on a map

73

,

111

positional accuracy

107

strategies

106

–

107

geocoding preferences

83

,

87

,

215

geocoding procedures

address columns

64

–

66

,

68

automatic

69

CASS

123

,

126

dBASE files

142

displaying geocoded records

82

interactive

70

,

74

one pass

109

quick geocode

142

re-geocoding a table

83

to ZIP Code centroids

79

–

80

using quick geocode

143

geocoding remote databases

accessing remote tables

170

preparation procedures

169

related table geocoding

172

,

177

remote mappable tables

168

,

170

rollback segment limit

178

supported data types

178

MapMarker 23

Index

282

transaction control

177

–

178

geocoding results

details

121

output columns

49

result codes

115

,

121

unmatched rows

268

Geocoding Summary

dialog

216

geocoding terms

43

geographic geocoding

definition

44

GeoResult

dialog

217

H

I

hardware requirements

27

Help Topics

menu command

195

toolbar button

195

highway exits

152

input column settings

saving to a table

95

installation

client

40

new installation

29

overview

26

removing MapMarker

39

shared

26

silent install

35

UNIX/Linux

29

upgrading

37

Windows procedure

29

Interactive Geocode

dialog

218

interactive geocoding

70

,

74

,

111

intersections

customized user dictionary

184

geocoding

75

matching to

110

L

LACSLink

126

–

127

,

135

adding columns

127

definition

44

re-enabling

135

using

126

line styles

in remote spatial tables

265

Locate Airport menu command

195

Locate Highway Exit menu command

195

User Guide

locating airports

151

–

152

,

220

locating highway exit

152

–

153

locating highway exits

152

,

222

log file preferences

86

–

87

,

223

Logfile menu command

195

longitude/latitude columns

49

–

50

,

54

M

map catalog

creating

170

remote mappable tables

168

MapInfo ftp site

24

MapInfo_MapCatalog

adding rows

261

,

263

,

265

creating

260

MapInfo_Mapcatalog

spatial index types

264

MapMarker

features

20

technical support

23

–

24

what’s new

21

MapMarker API

269

MapMarker dialogs

200

MapMarker on the World Wide Web menu

command

196

MapMarker Streets

using with MapMarker

23

mappable tables

adding rows to MapCatalog

261

,

263

Maps preferences

dialog

224

match mode

CASS

89

,

226

relaxed

89

,

225

standard

89

,

225

tight

89

,

225

use

88

Match Settings

dialog

225

match settings

106

CASS

90

exact match

90

specifying

88

match settings dialog

225

,

227

matching addresses

displaying match candidates on a map

104

expanding search area

73

input columns

48

,

64

–

65

,

68

output columns

49

–

50

,

54

,

66

with geographic data

14

matching conditions

changing interactively

73

MapMarker 23

283

Index

fallback settings

93

multiple matches

94

relaxing

109

–

110

matching strategies

106

–

107

menu command

Arrange Icons

192

Batch Add Attributes

192

Cascade

192

Choose Font

192

Clear File Selections

193

Close

193

Create Batch File

193

Create User Dictionary

194

Create/Save Project

194

Exit

194

Export to Shapefile

194

Geocode

195

Help Topics

195

Locate Airport

195

Locate Highway Exit

195

Logfile

195

MapMarker on the World Wide Web

196

Open Browser List

196

Open Project

196

Open Table

197

Quick Find

197

Quick Geocode

197

Recent File List

198

Select Attribute Files

198

Select Columns

198

Status Bar

198

Stop Attribution

198

Submit Problem Report to Technical Support

199

Summary

199

System Preferences

199

Table Summary

199

Tile

200

Toolbar

200

menu commands

191

About MapMarker

192

metadata

saving settings to a table

95

mixed case output

55

modify

installation

36

silent

37

modifying table structure

228

Multiple Match preferences

dialog

230

multiple matches

choice of actions

112

must match

User Guide

definition

44

N

network installation

26

new features and enhancements

21

non-match result codes

120

,

268

O

ODBC tables

geocoding

173

–

175

supported data types

178

transaction control

177

–

178

offset from center line

preference

103

offset from corner

231

preference

103

offset from road

231

preference

103

offset preferences

102

,

231

Open

dialog

233

Open Browser List

menu command

196

toolbar button

196

Open Browser List menu command

196

Open Project menu command

196

Open Table

menu command

197

toolbar button

197

output

mixed case

55

output columns

geocoding results

49

–

50

,

54

saving to a table

95

output point attribution

157

,

162

–

163

P

pen styles

in remote spatial tables

264

performance

increasing

267

per-record styles

263

–

264

PMB

definition

44

point styles

in remote spatial tables

265

positional accuracy

geocoded records

107

postal centroid match

result codes

120

postal geocoding

79

definition

45

MapMarker 23

Index

284

postcode

definition

45

postDirectional

definition

45

postType

definition

45

preDirectional

definition

45

preferences

dictionary

101

–

102

fallback settings

93

fallback to geographic centroid

94

fallback to ZIP Code

94

geocoding

83

,

87

log file

86

–

87

maps

104

match restrictions

88

multiple matches

94

offset

102

startup

56

,

100

–

101

system

100

,

103

–

104

project

opening

57

saving

96

using

57

Q

Quick Find

menu command

197

toolbar button

197

quick find

browsing

147

settings

148

single line address

146

viewing candidates

143

quick find command

dialog

234

finding a single address

143

seeing your match

143

settings

236

quick find settings

150

Quick Geocode

menu command

197

toolbar button

197

quick geocode button

142

–

143

R

RDBMS

168

Recent File List menu command

198

re-enabling DPV

135

re-enabling LACSLink

LACSLink

User Guide

re-enabling

135

re-geocoding

83

,

267

related table geocoding

172

–

173

,

177

,

239

relational database management systems

168

relative matching

46

relaxed match mode

89

,

225

relaxing match conditions

109

–

110

remote database geocoding

geocoding procedure

170

–

171

preparation

169

preparation procedures

170

remote mappable tables

168

,

170

rollback segment limit

178

supported data types

178

transaction control

177

–

178

remote database views

176

remote mappable tables

making a remote table mappable

170

MapInfo map catalog

168

supported data types

168

supported spatial index types

168

remote spatial tables

adding rows to MapCatalog

261

,

263

,

265

MapInfo_MapCatalog

260

per-record styles

263

–

264

specifying styles

264

styles

265

remote tables

additional considerations

177

–

178

removing MapMarker from your system

39

requirements

hardware and memory

27

system

27

result codes

address point interpolation

116

best match from multiple candidates

119

complete M code

117

complete S code

117

definition

45

G category

120

geographic matches

120

M category

119

N category

120

no data

268

non-match codes

120

output columns

49

–

50

,

54

postal centroid matches

120

S category

116

S3 and Z3 comparison

119

S5

118

S6

118

S7

118

S8

117

MapMarker 23

285

single close match

116

unmatched rows

268

viewing

121

Z category

120

road offset

103

rollback segment limit

remote databases

178

running MapMarker

57

S

S1 result

53

S2 result

53

S3 result

53

S4 result

53

S5 result

53

S6 result

53

S7 result

52

S8 result

52

Save Batch File As

dialog

240

saving settings to a table

95

SC result

53

Select Attribute Files menu command

198

select attribute tables

242

Select Columns

menu command

198

toolbar button

198

select input columns

48

Select input columns from your table

dialog

244

Select output columns from your table

dialog

246

Select Table

dialog

248

Select Table Type

dialog

249

settings and preferences

saved in project

96

Shapefile

export

62

,

211

silent install

35

silent modify

37

silent uninstall

40

silent upgrade

39

single line address

geocoding

76

–

79

input

66

quick find

146

single match result codes

116

spatial index types

168

,

264

standard match mode

89

,

225

starting MapMarker Desktop Application

41

Index

User Guide

Index

Startup Preferences

dialog

250

startup preferences

56

,

100

–

101

Status Bar menu command

198

Stop Attribution menu command

198

street directionals

DPV

130

street intersections

customized user dictionary

184

geocoding

75

matching to

110

street level geocoding

definition

45

street names

relaxing match conditions

110

styles

in remote spatial tables

264

Submit Problem Report to Technical Support

menu command

199

SuiteLink

using

137

SuiteLink

137

–

138

Summary menu command

199

support

technical support

23

–

24

supported databases

168

SX result

53

symbol styles

in remote spatial tables

264

system preferences

dictionary

101

–

102

maps

104

offset

102

setting

100

–

101

startup

100

,

104

System Preferences menu command

199

T

table attribution

add output column

68

,

160

–

161

adding attributes

164

–

165

adding columns

158

,

162

clearing file selections

166

column value

157

,

163

–

164

considerations

166

output point

157

,

162

–

163

selecting a table

159

selecting table

162

stopping

165

–

166

Table Georesult Summary

dialog

251

Table Summary menu command

199

tables

editing records while geocoding

74

ODBC

177

–

178

opening

58

opening in MapInfo

267

saving settings

95

technical support

23

–

24

text file

opening

58

type

60

Text File Wizard

dialog 1

252

dialog 3

254

Text File Wizard 2dialog 2

253

tight match mode

89

,

225

Tile menu command

200

Tips for Using Attribution

166

toolbar buttons

191

Geocode

195

Help Topics

195

Open Browser List

196

Open Table

197

Quick Find

197

Quick Geocode

197

Select Columns

198

Toolbar menu command

200

transaction control

178

ODBC tables

177

U

uninstall

39

silently

40

unmatched row result code

268

updated records

re-geocoding a table

83

,

267

upgrade

silently

39

using graphical interface

38

upgrading your installation

37

user dictionary

address point interpolation

102

considerations and restrictions

183

creating

186

data requirements

181

definition

46

description

180

FindAddress utility

273

format requirements

183

intersections

184

preferring

110

,

188

system preferences

101

–

102

User Dictionary Wizard

MapMarker 23

286

User Guide

dialog

254

,

256

–

257

utilities

append.mbx

273

,

275

FindAddress

272

V

viewing candidates

quick find

143

W

wide search

73

,

150

,

227

quick find settings dialog

238

Z

Z1 result

54

Z2 result

54

Z3 result

54

Z6 result

54

ZIP Codes

matching to centroids

80

,

110

ranged by state

276

relaxing match conditions

109

Index

MapMarker 23

287

User Guide