Geographic Coding Plus - Pitney Bowes · 2019. 2. 9. · Chapter 3, Getting Started Walks you...

Location Intelligence

Geographic Coding Plus Version 5.2/5.3

User’s Guide for Open Systems July 2018

© 2018 Pitney Bowes Software Inc. All rights reserved.

Pitney Bowes Software Inc. is a wholly-owned subsidiary of Pitney Bowes Inc. Pitney Bowes, the Corporate logo, Centrus and “Every connection is a new opportunity” are trademarks of Pitney Bowes Inc. or a subsidiary. All other trademarks are the property of the respective owners.

The following trademarks are owned by the United States Postal Service®: CASS, CASS Certified, DPV, eLOT, FASTforward, First-Class Mail, Intelligent Mail, LACSLink, NCOALink, PAVE, PLANET Code, Postal Service, POSTNET, Post Office, RDI, SuiteLink, United States Postal Service, Standard Mail, United States Post Office, USPS, ZIP Code, and ZIP+4. This list is not exhaustive of the trademarks belonging to the Postal Service.

USPS Notice: Pitney Bowes Software Inc. holds a nonexclusive license to publish and sell ZIP+4 databases on optical and magnetic media. The price of the Pitney Bowes Software Inc product is neither established, controlled, nor approved by the U.S. Postal Service.

Pitney Bowes Software is a non-exclusive licensee of USPS® for NCOALink® processing. Prices for the Pitney Bowes Software products, options and services are not established, controlled or approved by USPS® or United States Government. When utilizing RDI™ data to determine parcel-shipping costs, the business decision on which parcel delivery company to use is not made by the USPS® or United States Government.

T A B L E O F C O N T E N T S

BEFORE YOU BEGIN

Welcome! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Finding the Information You Need. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 If You Need More Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

The Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 eService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

To Obtain Additional User's Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

CHAPTER 1. INTRODUCING GEOGRAPHIC CODING PLUS Why You Need Geographic Coding Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Street Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Auxiliary Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Mapping Product-Compatible Output File Formats . . . . . . . . . . . . . . 14 Multi-Locator Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Intelligent Call to CODE-1 Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Enhanced Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Database Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Geographic Coding Plus Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 The Batch System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 The Interactive System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Integrating Geographic Coding Plus into Your System . . . . . . . . . . . . 19 Geographic Coding Plus Environments . . . . . . . . . . . . . . . . . . . . . . . . 19

Geographic Coding Plus: The Big Picture. . . . . . . . . . . . . . . . . . . . . . . . . . 20 Batch Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Geographic Coding Plus Callables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

CHAPTER 2. AFTER INSTALLING THE SOFTWARE: WHAT’S NEXT? For New Geographic Coding Plus Users: First Things First . . . . . . . . . . . 22 Getting Started with Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

What are the Geographic Coding Data Files?. . . . . . . . . . . . . . . . . . . . 23 Modifying the Parameter Files for Your New Job . . . . . . . . . . . . . . . . 23

Getting Started with Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 What are the Geographic Coding Data Files?. . . . . . . . . . . . . . . . . . . . 23 Modifying the Parameter Files for Your New Job . . . . . . . . . . . . . . . . 24

Getting Started with MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 What are the Geographic Coding Data Files?. . . . . . . . . . . . . . . . . . . . 24 Tailoring IVPFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

CHAPTER 3. GETTING STARTED WITH YOUR BATCH JOB Using Geographic Coding Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Parameter Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Control Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Combining Parameter Records and Control Language . . . . . . . . . . . 27

Geographic Coding Plus Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Parameter Record Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Geographic Coding Plus 3

Step 1. Copying the IVP File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Step 2. Defining the Physical Attributes of Your Files. . . . . . . . . . . . . 29 Step 3. Defining the Layout of Input Record Elements . . . . . . . . . . . . 29 Step 4. Defining the Layout of Output Record Elements. . . . . . . . . . . 30 Step 5. Defining Processing Options. . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Step 6. Defining Reporting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Step 7. Writing Control Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

CHAPTER 4. GETTING STARTED WITH INTERACTIVE PROCESSING The Geographic Coding Plus Interactive Address Matcher. . . . . . . . . . . . 34

How to Use the Matcher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Database Inquiry Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Online Help Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 How to Use Geographic Coding Plus Inquiry . . . . . . . . . . . . . . . . . . . . 42 ZIP Code Information for a State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 County/MSA Information for a State . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 ZIP+4 Information for a ZIP Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 County/MSA Information for a ZIP Code. . . . . . . . . . . . . . . . . . . . . . . . 51

CHAPTER 5. WORKING WITH THE AUXILIARY FILE Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Step 1. Create the Auxiliary File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Use USPS Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Step 2. Use GCAUXBLD to Build the File . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Building Your Auxiliary File in MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Building Your Auxiliary File in Windows . . . . . . . . . . . . . . . . . . . . . . . . 60 Building Your Auxiliary File in Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Step 3. Tell Geographic Coding Plus to Match to the Auxiliary File . . . . . 61 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Step 4. Post Data from the Auxiliary File (optional) . . . . . . . . . . . . . . . . . . 62 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

CHAPTER 6. WORKING WITH THE CALLABLE FUNCTIONS Overview of the Callable Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

The Geographic Coding Plus Street Matcher (GCMATCH) . . . . . . . . . 64 The CBSA Function (GCCBSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 The Multi-Locator Function (GCSTLOC) . . . . . . . . . . . . . . . . . . . . . . . . 66 The Geographic Coding Function (GCP10) . . . . . . . . . . . . . . . . . . . . . . 67 The Distance Calculation Function (GCP20). . . . . . . . . . . . . . . . . . . . . 68

Invoking the Callable Functions — COBOL Example. . . . . . . . . . . . . . . . . 69 Calling GCMATCH for MVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Calling GCMATCH for Other Platforms. . . . . . . . . . . . . . . . . . . . . . . . . 70 Calling GCSTLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Calling GCP10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Calling GCP20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 If You Are Not Using Language Environment (LE)... . . . . . . . . . . . . . . 70

Calling the GCMATCH Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72


Matcher Control Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Matcher Input Address (MIA) Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Matcher Output Area (MOA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Street Matcher Audit Area (GCAADT) . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Calling the GCCBSA Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 The CBSA Control Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 The CBSA Input Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 The CBSA Output Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Calling the GCSTLOC Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Multiple Lat/Long Control Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Multiple Lat/Long Input Address (MLIA) Area . . . . . . . . . . . . . . . . . . . 89 Multiple Lat/Long Output Area (MOA). . . . . . . . . . . . . . . . . . . . . . . . . . 89

Calling the GCP10 Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 The GCIIN Input Parameter Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 The GCOOUT Output Parameter Area. . . . . . . . . . . . . . . . . . . . . . . . . . 93 The GCAADT Audit Parameter Area . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Calling the GCP20 Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 The DSIIN Input Parameter Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 The DSOOUT Output Parameter Area. . . . . . . . . . . . . . . . . . . . . . . . . . 98

Calling the MFDIST Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 The DSIIN Input Parameter Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 The DSOOUT Output Parameter Area. . . . . . . . . . . . . . . . . . . . . . . . . 100

Calling Geographic Coding Plus Under CICS . . . . . . . . . . . . . . . . . . . . . . 100 Example Procedure Division for CICS. . . . . . . . . . . . . . . . . . . . . . . . . 101

CHAPTER 7. WORKING WITH THE MULTI-LOCATOR FUNCTION Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Step 1. Create the SEQLOC File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Step 2. Use GCLOCBLD to Convert the File . . . . . . . . . . . . . . . . . . . . . . . 103

Building the G1GCLOC File in MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Building the G1GCLOC File in Windows . . . . . . . . . . . . . . . . . . . . . . . 104 Building the G1GCLOC File in Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Step 3. Use the Multi-Locator Function . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Step 4. Limit Distance (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

CHAPTER 8. PERFORMING DATABASE REDUCTION Database Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Using G1DBLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

PRODCD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 FILESL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 HEADER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 REDUCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 PAGESZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 UFTxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 UHDxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115


Reports Produced by G1DBLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Executing G1DBLOAD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Unix Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

CHAPTER 9. EXITOP PARAMETER CODING FROM OTHER PITNEY BOWES APPLICATIONS

Parameter Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 The EXITOP Parameter Record for GCP65 . . . . . . . . . . . . . . . . . . . . . 119 The EXITOP Parameter Record for GCP60 . . . . . . . . . . . . . . . . . . . . . 121 The EXITOP Parameter Record for GCP70 . . . . . . . . . . . . . . . . . . . . . 124

CHAPTER 10. USING GEOGRAPHIC CODING PLUS IN DIFFERENT ENVIRONMENTS File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 The Unix Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Step 1. Source the setup Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Step 2. Modify the Unix Shell Script(s) . . . . . . . . . . . . . . . . . . . . . . . . 128 Step 3. Source the Job Shell Script(s) . . . . . . . . . . . . . . . . . . . . . . . . 129 Step 4. Submit Your Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Step 5. Invoke the Interactive System. . . . . . . . . . . . . . . . . . . . . . . . . 129

The Windows Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Customization Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Step 1. Edit/Save Job Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Step 2. Edit/Save Parameter Record Files . . . . . . . . . . . . . . . . . . . . . 131 Step 3. Run a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Step 4. Invoke the Interactive System. . . . . . . . . . . . . . . . . . . . . . . . . 132

MVS JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Invoking the Interactive System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

APPENDIX A. PARAMETER RECORD REFERENCE

ADDRDF Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

ARCOUT Parameter Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Field by Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

AUXOUT Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

CBSOUT Parameter Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

CONFIG Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

CONFRM Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142


Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 CONSxx Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

CS ZIP Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

DISTIT Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

EXITOP Parameter Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

EXITOP Parameter Record (GCP65) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

FILEDF Parameter Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Limiting Processing With FILEDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Specifying FILEDF Exit Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

FILESL Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

GEOOUT Parameter Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

HEADER Parameter Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Low/High Postal Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

LLOUT Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

MCDOUT Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

MOVE I Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

MOVE O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

MSAOUT Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

PAGESZ Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

PRODCD Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174


Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 REDUCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

REPORT Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

STLOCn Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

TESTIT Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

UFTxx Parameter Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

UHDxx Parameter Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

APPENDIX B. ERROR CONDITIONS

Parameter Record Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Condition Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

APPENDIX C. SAMPLE LIBRARY MEMBER REFERENCE

Sample Library Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

APPENDIX D. CALLING CODE-1 PLUS FROM GEOGRAPHIC CODING PLUS

Calling CODE-1 Plus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 What Is Corrected During a Call to CODE-1 Plus? . . . . . . . . . . . . . . 187 What About Auxiliary File Matching and Calling CODE-1 Plus? . . . . 188

APPENDIX E. CONCEPTS IN GEOGRAPHY

Overview of the Geographic Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Census Geography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Small-Area Geography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Counties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Metropolitan Statistical Areas (MSA) . . . . . . . . . . . . . . . . . . . . . . . . . 191 Census Tracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Block Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Minor Civil Divisions (MCDs)/Census County Divisions (CCDs) . . . . 193

Postal Geography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 ZIP Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 ZIP+4 Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Latitude and Longitude. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Latitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Longitude. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198


Block Group, Census Tract Area Centers and the Center of Population for ZIP Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Calculating Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204


B E F O R E Y O U B E G I N

Welcome!

Welcome to Geographic Coding Plus! Geographic Coding Plus helps you to concentrate and direct your marketing efforts by attaching U.S. Census data to your name-and-address records. Use Geographic Coding Plus to add geocodes, state and county codes, latitude and longitude, and other data to your records. The results you get from Geographic Coding Plus will help you to:

• Build accurate customer profiles at various data levels. • Pinpoint the consumers who are most likely to respond to your message. • Save marketing dollars by selling your products and/or services to a targeted group.

Finding the Information You Need

The following table summarizes the chapters in this guide.

Table 1: Chapter Summaries

Chapter Description Chapter 1, Introducing Describes Geographic Coding Plus and introduces you to the functions Geographic Coding Plus that it performs.

Chapter 2, After Installing Provides platform-specific information on copying the IVP job and scripts the Software: What’s to write your own batch jobs. Next?

Chapter 3, Getting Started Walks you through the basic tasks involved in creating a Geographic with Your Batch Job Coding Plus batch job: system requirements, defining input and output

files, steps in a job, parameter records used in a job, matcher programs, and reports.

Chapter 4, Getting Started Describes interactive address matching and database inquiry functions with Interactive that make up the Interactive Geographic Coding Plus System. Processing

Chapter 5, Working With Describes how to build and use an Auxiliary File in your batch job. the Auxiliary File

Chapter 6, Working With Explains how to call the coding and calculation modules from other the Callable Functions applications to apply geocodes and latitude/longitude information to your

input address records. Provides detailed descriptions of the parameter areas used to call these modules.

Chapter 7, Working With Describes how to build a Multi-Locator file and use it in your batch job. the Multi-Locator Function

Chapter 8, Performing Describes how to create a reduced database from delivery media or disk. Database Reduction


Table 1: Chapter Summaries

Chapter Description Chapter 9, EXITOP Explains how to code the EXITOP parameters from other Pitney Bowes Parameter Coding from applications to invoke the GCP60 and GCP70 programs. Provides detailed Other Pitney Bowes descriptions of the parameter fields used by these modules. Applications

Chapter 10, Using Provides platform-specific file names and basic instructions for running Geographic Coding Plus in jobs and invoking the Interactive System. Different Environments

If You Need More Help

If you are unable to resolve a problem, a Pitney Bowes Technical Support Representative can help guide you to a solution. When you call Pitney Bowes Technical Support, please have the following information ready:

• A description of the task you were performing • The resulting reports (specifically, the Execution Log and Parameter Record Listing)

Reporting complete details to Technical Support will help you and the technical support representative quickly resolve the problem.

The Technical Support Hotline number for customers in the United States and Canada is 800-367-6950.

The Web Site

You can also find out about Pitney Bowes software products and services through our Website at www.g1.com/Support/. Registered users may obtain electronic copies of product documentation, join online discussion forums, download software and databases, learn about our training classes, or sign up for the Pitney Bowes Software List Services. From the home page, click Support and log in to the Customer Support area.

NOTE: Registered users are those who have a maintenance agreement with Pitney Bowes. Contact Technical Support to obtain your user ID and password.

eService

eService, available through the Pitney Bowes Website, provides supported Pitney Bowes customers with direct access to Service Requests and the Pitney Bowes Software Solutions Knowledge Base. You can search for your own Service Requests, search the Knowledge Base, and access a variety of


www.g1.com/Support

other Technical Support services. You must be a registered user, with an ID and password, to access eService.

To Obtain Additional User's Guides

To obtain electronic copies of our product manuals, go to the Pitney Bowes Website at www.g1.com/Support/ and click on Customer Login in the upper right corner. Log in with your User ID and password. On the left side of the window under “Technical Services” click on Documentation to download copies (.pdf files) of available user guides.


www.g1.com/Support

C H A P T E R 1

Introducing Geographic Coding Plus This chapter provides an overview of Geographic Coding Plus, including its components, features, and capabilities. You will learn about the Geographic Coding Plus modules and database files, and how these relate to your geocoding efforts.

Why You Need Geographic Coding Plus

The world of business geographics is as diverse as the world we live in and Pitney Bowes’ Geographic Coding Plus is one of the mainstays in the industry. This product supports hundreds of customers in multiple verticals - banking, direct marketing, financial services, government (local, state, federal), health care, hospitality, logistics, manufacturing, publishing, retail, telecommunications, and utilities. These customers utilize Geographic Coding Plus for diverse internal needs. But they all share the need for geocoding accuracy and product reliability across the diverse computing platforms that they utilize.

Pitney Bowes is proud of its over twenty-year history in the business geographics market as a supplier of geocoding products and contributor to the industry. This product represents that commitment to the industry and to our customers to provide greater functionality, expanded data, and better accuracy than any previous version of this product. Over the next few pages, you'll get an overview of the new features.

Street Coding

Geographic Coding Plus provides street coding capability. Using data provider TomTom’s MultiNet® database of street segments and latitude/longitude coordinates, Pitney Bowes has devised a street address-based Geographic Coding Plus solution to supplement the current ZIP+4-based approach.

TomTom’s street segment database originated with the U.S. Census Bureau’s TIGER files, but has been continuously refined and updated with the latest digital satellite imagery, Global Positioning System (GPS) surveys, and local planning and zoning information to provide the most accurate street-based geographic data available. Pitney Bowes’ street coder takes a standardized address and matches it to an exact physical location, returning latitude/longitude coordinates with the correct census codes for the address. This solution, based on the actual physical location of the address, greatly reduces the inaccuracies associated with 9-digit and 5-digit ZIP Code-based matching.



How It Works

The Geographic Coding Plus street coder takes a house address and matches it to the correct street segment. Using the house number, it determines on which side of the street the house is located (usually based on an odd-even division). Once the correct street segment and street side is known, Geographic Coding Plus interpolates the house’s actual physical location based on known latitudes/ longitudes and other geographic data in the street segment database. Users have the option to offset the house’s location by 0, 20, 40, or 60 feet from the street center-line. Geographic Coding Plus then returns the coordinates of the house, along with the correct state, county, census block, and other geocode data.

The street coder also includes an algorithm known as “squeeze.” A squeeze value ensures that an endpoint address lat/long calculation is positionally adjusted in from a perpendicular cross street. This avoids placing the first and last addresses on each street segment in the middle of a cross street. Geographic Coding Plus provides a 2.5% squeeze percentage, representing a “shortening” on both ends of a street segment.

Auxiliary Matching

In some cases, you may have access to a portion of geocode/census data that has recently changed and is more current than that provided in the Geographic Coding Plus databases, which are updated quarterly. In these situations, you have the option to use the Geographic Coding Plus Auxiliary matcher. The Auxiliary matcher allows you to use your own custom coded records. Just “point” to the file location and let the Auxiliary matcher do the rest.

Your original files will need to be converted into a format that Geographic Coding Plus can read. Instructions on converting and using these files are provided in Chapter 5, “Working With the Auxiliary File.”.

Mapping Product-Compatible Output File Formats

You also have the option to format the matched-address output so it can be read into a mapping application, such as ESRI’s ArcView®. For users of GIS mapping systems such as ArcView® or MapInfo®, you can tell Geographic Coding Plus to produce a file called GCBMARC. This fixed-length output file contains comma-delimited data. By default, latitude and longitude are provided for each record. The remaining fields are user-defined. The GCBMARC file can then be imported to your mapping program so you can view geocoded records on a map.

NOTE: See Appendix A, "Parameter Record Reference"; specifically, the following parameters: ARCOUT, FILEDF, and LLOUT



Multi-Locator Function

The Multi-Locator function is a multi-point distance calculator that returns the closest one to nine distances (user-selectable) between a target lat/long (for example, a customer address) to a user-defined set of coordinate points (for example, store locations). This function allows you to create a file of up to 10,000 coordinate points representing store locations, sales agents, and other points of interest. Instructions for building and using the multi-locator file are provided in Chapter 7, “Working With the Multi-Locator Function.”.

Intelligent Call to CODE-1 Plus

In order to achieve a higher percentage of street matches, you can task CODE-1 Plus to normalize bad address records in the event that an input address fails the first match attempt. Based on parameters you provide, CODE-1 Plus will be called in order to either normalize the address, or in some cases, standardize the address correcting minor address flaws. This feature can be used on every address, only on addresses not matched by Geographic Coding Plus, or not used at all.

Enhanced Geographic Data

Enhanced geographic data includes Census Block IDs, which can be returned from either a postal match or a street match, as well as the new Core Based Statistical Areas (CBSAs), which are replacing traditional Metropolitan Statistical Areas (MSAs).

Database Options

The Geographic Coding Plus database files contain the information against which input addresses are matched. There are four database installation options:

• The “Heavy” Street Segment option — installs the Street database, the Base postal file, and the Advanced postal file. Provides street matching.

• The “Lite” Postal option — installs both the Base and Advanced postal databases from the complete set of media files, which can provide up to ZIP+4-based matching.

• The “Advanced” option — installs just the Advanced file, which can provide ZIP+2 or ZIP+4 latitude and longitude coordinates.

• The “Base” option — installs just the Base file, which can provide ZIP+4 Code-level geocode information.

At over 2 gigabytes of data, the “Heavy” Street Segment file is significantly larger than the Postal files, but provides the greatest coding accuracy. In addition, you have the option of using your own



address data as a database via Auxiliary File matching. All of the database files provided with Geographic Coding Plus contain the following information that you may post to your records:

• 2010 Census geographical codes • Latitude and longitude information • Core Based Statistical Areas (CBSAs) codes and names • Census Block codes and Census Block IDs • Minor Civil Divisions (MCDs)/Census County Division (CCDs) codes and names.

“Heavy” Street Segment Database

The Street Segment database is used in street coding, and actually consists of five separate files (G1GCGTD, G1GCRSN, G1GCDTL, G1GCLL1, G1GCLL2). When accessed by Geographic Coding Plus, it identifies all geographic components associated with a street address, including its latitude/longitude, state, county, census tract, block group, MSA, and MCD/CCD. The Street Level databases contain detailed street segment information (based on data provider TomTom’s MultiNet®), along with known latitude/longitude coordinates. Geographic Coding Plus matches the input address to a street segment and interpolates the address’ actual physical location on the correct side of the street, based on these known latitude/longitude coordinates. You can choose the address to be offset by 0, 20, 40, or 60 feet from the street. Thus, the level of accuracy as to an address’ location within a place or tax jurisdictions is at the “street” level — the finest level of accuracy available in Geographic Coding Plus.

“Lite” Postal Database

The Postal databases (GCMASTR and GCZ4MST), used in postal address matching allows Geographic Coding Plus to assign census geocodes, including latitude and longitude. File GCMASTR returns geocoding information at the nine-digit ZIP+4 level of accuracy. File GCZ4MST provides finer levels of latitude and longitude information available at the ZIP+2 and ZIP+4 levels.

Advanced Database

By itself, the Advanced database (GCZ4MST) does not include census geocodes. It does, however, provide a finer level of latitude/longitude coordinates, at the ZIP+2 and ZIP+4 levels.


Geographic Coding Plus Components

Base Database

By itself, the Base database (GCMASTR) contains census geocodes and latitude/longitudes. It can return geocoding information at the ZIP+4 level of accuracy. However, the latitude/longitude data is only at the 5-digit ZIP Code level.

These database options are summarized in the following table.

Database Option Files Highest Level of Accuracy / Data Options

“Heavy” Street Files: Street level - most accurate

• G1GCGTD

• G1GCRSN

• G1GCDTL

• G1GCLL1

Input address matched to street segment. Includes use of interpolation, offset, and squeeze.

Also includes option to use your own street segment data via Auxiliary File matching.

• G1GCLL2

Postal Files:

• GCZ4MST

• GCMASTR

“Lite” Postal Files:

• GCZ4MST

• GCMASTR

Up to ZIP+4 centroid level of accuracy.

Advanced - ZIP+4, ZIP+2

Base - Block Group, Census Tract.

Advanced GCZ4MST Up to ZIP+4 centroid level of accuracy. Returns latitude and longitudes at finer levels than the base file.

Base GCMASTR Up to ZIP+4 centroid level of accuracy.


The Geographic Coding Plus batch product comprises the programs for batch processing, as well as programs for the Interactive System and callable programs that can be integrated into your own system.

The Batch System

The batch system, governed by program GCBM00, appends census and geographic code information to your input name-and-address records based on parameter records you enter. You use the parameter records to:



NOTE: See Chapter 3, "Getting Started with Your Batch Job" for a tutorial on creating a batch job.

• Specify information about the layout of the data in the name-and-address records. • Define the content and layout of your output records. • Specify headers and footers for Geographic Coding Plus reports, as well as define the data and

the number of lines to be printed on each page of the reports. • Specify what census and/or geographic code data should be applied.

NOTE: See Appendix A, "Parameter Record Reference" for complete details about Geographic Coding Plus parameter records.

When you submit the parameter records and input file for processing, Geographic Coding Plus:

• Verifies the input address against the Geographic Coding Plus databases • Appends the requested census and/or geographic code data for matched records • Generates a non-coded records file, if asked for, and processing reports.

The batch processing environment is made up of the following components:

• Batch Driver (GCBM00) — Acts as the “engine,” coordinates the matching output processes.

• Matching Program (GCMATCH) — Calls the matching programs GTSTMAT and GCP10, depending on the level of matching available. If an address cannot be matched at the street level (i.e., GCSTMAT cannot find an answer), then postal matching is used (i.e., GCP10 is used instead).

• Street-Level Matcher (GCSTMAT) — Matches the input address, based on its physical location on a street segment, to Geographic Coding Plus or Auxiliary databases.

• ZIP+4 Matcher (GCP10) — Matches the input ZIP and/or ZIP+4 Code to the geographic database.

• Distance Calculator (GCP20) — Calculates the distance between two sets of latitude and longitude coordinates.

NOTE: MFDIST is another distance calculator that is available for the MVS platform. • Multi-Locator File Build Program (GCLOCBLD) — Indexes the raw Multi-Locator file

so Geographic Coding Plus can use it in the Multi-Locator Function. • Multi-Locator Function (GCSTLOC) — Calculates the closest 1 to 9 distances to a target

address. • Auxiliary File Build Program (GCAUXBLD) — Indexes the raw Auxiliary file so

Geographic Coding Plus can use it for matching. • GCP60 Output exit program 1 — Calls GCP10 to post variable Geographic Coding Plus

data to a record passed to it. Generates statistics that report on the EXITOP processing results. Called from your applications or from other Pitney Bowes applications.

• GCP70 Output exit program 2 — Calls GCP10 and GCP20 to post latitude/longitude coordinates. Posts distance calculation from a fixed point on the EXITOP parameter record.



Generates statistics that report on the EXITOP operation. Called from your own application or from other Pitney Bowes applications.

• Parameter Validation (GCBMVP00) — Verifies that the parameter records are correct.

The Interactive System

The interactive system enables you to look up geocode data by state and by ZIP Code (Database Inquiry function), or lets you match a single input address against the database file (Address Match function).

NOTE: See Chapter 4, "Getting Started with Interactive Processing" for details on using the interactive screens.

The interactive Inquiry begins with a listing of states from which you can select. The resulting view lists all ZIP Codes for that state and includes ZIP Code-level census information. From the screen of all ZIP Codes for a state, you can list all counties and MSAs found within that state. You can also select a ZIP Code and list all ZIP+4 Codes found for that ZIP, plus related census information. In addition, you can view a list of all counties and MSAs found within a particular ZIP Code. In essence, the interactive system displays all data that would otherwise be displayed as a result of a match, but is organized by state and ZIP code.

Integrating Geographic Coding Plus into Your System

See Chapter 9, “EXITOP Parameter Coding from Other Pitney Bowes Applications” for information on using the EXITOPs.

Geographic Coding Plus provides two different options for integrating its batch functions into your own system. You can integrate Geographic Coding Plus functions by:

• Using EXITOP parameters from other Pitney Bowes applications

See Chapter 6, "Working With the Callable Functions" for information on the callable functions.

• Calling Geographic Coding Plus’s callable functions from your application.

Geographic Coding Plus Environments

The Geographic Coding Plus batch product operates on the following platforms:

• Unix • Windows • MVS


Geographic Coding Plus: The Big Picture

• iSeries platforms

It currently accepts fixed-field input address files in ASCII text, EBCDIC flat file, or delimited file format, based on the platform used.


Geographic Coding Plus is more than the base product you licensed when you received this user’s guide. To complement the base product’s functions, Pitney Bowes also offers Geographic Coding Plus callables, and Geographic Coding Plus Web on the Windows and Unix platforms. These products work together to offer you a complete geocoding system. The diagram below illustrates various areas in your organization where Geographic Coding Plus would fit to offer a complete geographic coding system.

Geographic Coding Plus Batch

Geographic Coding Plus

Callables

Geographic Coding Plus

Figure 1: Geographic Coding Plus: The Big Picture

Batch Processing

For example, you provide Geographic Coding Plus an input file of 1,000,000 customer names and addresses. The product will then attempt to verify each address and append the geocoding data you specify. It will provide the following separate output files:



• Coded output file • Not-coded output file • Mapping application output file.

NOTE: Please refer to Chapter 3, "Getting Started with Your Batch Job" for step-by-step instructions for processing your file.

Geographic Coding Plus Callables

Callable modules are those that Geographic Coding Plus uses to analyze your input addresses and attempt to match the address to the database. These modules are primarily designed so you can call them from your own COBOL or Assembler applications in a mainframe environment.

For example, your organization might have a COBOL-written data entry system application. You want to accurately assign county name and FIPS county codes as they are entered onto your mainframe system. Geographic Coding Plus provides a callable named GCMATCH to allow you to assign accurate county information as they are entered into your order entry system.


C H A P T E R 2

After Installing the Software: What’s Next? If you have never before defined and run a Geographic Coding Plus job “from scratch,” you will want to review this chapter. In this chapter, we review information about the files copied to your system during installation.

For New Geographic Coding Plus Users: First Things First

Okay, you’ve installed your software and loaded the database files. You’ve run the sample or IVP job and looked at the Execution Log to ensure that the job ran to completion...now what?

We admit that your first acquaintance with Geographic Coding Plus can leave you wondering, ”What do I do next?” Be assured that we are here to help! If you installed the product on a Windows operating system, you probably noticed that some icons were placed in the folder where you installed the software. If you installed the software on a mainframe or Unix platform, you probably see some new library members. What do these things do? What do they mean? How do you use them?

You may have noticed that Pitney Bowes supplied a sample or installation verification procedure (IVP) job. This is the template for your own jobs, but where do you get started?

This chapter removes the mystery surrounding the first steps in creating your Geographic Coding Plus jobs. Since Geographic Coding Plus installation differs by platform, we’ve separated this chapter into separate sections: one for each platform.

NOTE: Chapter 10, "Using Geographic Coding Plus in Different Environments" provides more details on platform-specific issues.

Getting Started with Windows

After you’ve completed your Windows installation and run your IVP job, take a look at the Pitney Bowes folder. If this is the first time you’ve installed a Pitney Bowes product, you’ll find that this is the folder that the installation program creates to contain the Pitney Bowes applications and their associated files.


Getting Started with Unix

What are the Geographic Coding Data Files?

Double-click the DB folder icon to view the items in it. This folder contains the Geographic Coding Data Files. Note that there are pairs of files: one file with the .vix extension, and an accompanying file with no extension. The GCDBLOAD.XLG file is the Execution Log file resulting from the last time you loaded a Geographic Coding Data File.

NOTE: For a description of the database options, see “Database Options” on page 15.

Depending on which database installation option you’ve chosen, you could have the Street database (5 files in all), the Advanced Postal file, and/or the Base Postal file. Note that you will also have two files related to License Management: G1GCLIC and G1GCLIC.VIX.

We highly recommend that you update your \DB directory with the latest Geographic Coding Plus files as you receive them from Pitney Bowes.

Modifying the Parameter Files for Your New Job

Review the contents of this folder. The Sample.* files contain the various output files for the “stock” sample job. These files include reports, etc.

Typically, you will make parameter changes to the .prm file members.

Refer to Chapter 3, "Getting Started with Your Batch Job", to write your parameters and add them to your job script.

Getting Started with Unix

If this is the first time you’ve installed a Pitney Bowes product, read this section to learn about the folders and files Geographic Coding Plus has installed on your system.


Depending on which database option you’ve installed, you could have the Street database (5 files in all), the Advanced postal database, and/or the Base postal database. These files contain the geocoding data that you are trying to match to your input records.

NOTE: See Chapter 1, page 15, for a description of database install options.


Getting Started with MVS

Modifying the Parameter Files for Your New Job

In the pgms directory, the “sample” files contain the various output files for the “stock” sample job. These files include reports, etc.

Refer to Chapter 3, "Getting Started with Your Batch Job", to write your parameters and add them to your job script.


If this is the first time you’ve installed a Pitney Bowes Business Insight product, read this section to learn about the libraries and files Geographic Coding Plus has installed on your system. Once you have completed the install process, you will end up with these libraries:

• A Load library that will contain the actual Geographic Coding Plus (GCP) load members • An Object library that will contain the GCP Object members • An Install JCL library that will contain all required JCL for proper execution and subsequent

maintenance of GCP. • A Sample library that contains JCL, copybooks, and sample source code to illustrate how to

call the various Geographic Coding Plus functions.


Depending on which database option you’ve installed, you could have the Street database (5 files in all), the Advanced postal database, and/or the Base postal database. These files contain the geocoding data that you are trying to match to your input records.

NOTE: See Chapter 1, page 15, for a description of database install options.

Depending on which database install option you choose, you will select one of the following install jobs:

• GCPLDSTR — “Heavy” option • GCPLDLIT — “Lite” option • GCPLDADV — Advanced file only • GCPLDBAS — Base file only

Locate the member in the JCL library. Edit this member, replacing the lower-case variable names with your site-specific names. Run this JCL against your most current, uninstalled Geographic Coding Data Files. You should perform this operation each time you receive Geographic Coding Data File media.



Tailoring IVPFILE

After you've completed your MVS Geographic Coding Plus product installation, go to the JCL library created by the installation and locate the member IVPFILE. This is a sample installation verification job that you can use to verify that the installation was successful and that the “plumbing” works.

1 Locate member IVPFILE. Edit this member, replacing the lower-case variable names with your site-specific ones.

2 Submit the IVPFILE JCL for processing.

3 Once the IVP job runs, go to your SDSF (Systems Display and Search Facility), or IOF, or use the display tool of choice for viewing reports, logs, system messages, etc.

4 Select the jobid for the IVPFILE job that you just ran.

All steps should have completed with a return code of zero (RC=0). Among several other files created, each job produces a report and an Execution Log for each execution of the Geographic Coding Plus product. The following driver program makes up a Geographic Coding Plus job:

• GCBMVP00 — Parameter Check and Verification Program

The output report files that will most likely interest you are the PRNTPRT Report and PRNTXLG Execution Log that is created for every driver program.

Refer to Chapter 3, "Getting Started with Your Batch Job", to write your parameters and add them to your job.


C H A P T E R 3

Getting Started with Your Batch Job This chapter outlines the steps required for defining your job with parameter records. Each type of information you will define is provided, as is a list of the parameter records required for each step. For a complete reference of every field on each parameter record, please refer to Appendix A, "Parameter Record Reference".

Using Geographic Coding Plus

Geographic Coding Plus is manipulated by parameter records and control language. You can use them independently or combine them to work together.

Parameter Records

Parameter records contain your processing instructions to the Geographic Coding Plus program that tell the program what you want to accomplish. Through these parameter records, you will tell Geographic Coding Plus information such as:

• The format of your input file • The location, length, and format of each relevant data element in your input file • Which output files to create • The processing options that should be performed on each input record • The location, length, and format of additional output record data elements (such as latitude/

longitude, FIPS state and county codes, etc.) • Which reports to print at the end of the job • The headers, footers, and lines per page for your reports.


Geographic Coding Plus Tasks

Control Language

In addition to writing parameter records to control your job, you will have to write control language. Control language varies from processing platform to processing platform, but its purpose is always the same: to define the operating environment and execute the programs that will process your records. Pitney Bowes assumes that you are familiar with writing control language for your platform. The control language provided in this manual is example only, and must be modified to meet your site-specific needs. The following table shows the types of control language used by each of the platforms supported by Geographic Coding Plus.

Processing Platform Control Language

MVS MVS JCL

UNIX Shell Scripts

Windows/NT Scripts

Combining Parameter Records and Control Language

Parameter records and control language can be combined in two ways:

• Have a file that contains all of your parameter records and “point” to that file from your control language.

• Embed your parameter records directly into your control language file.

Either method is acceptable, and Geographic Coding Plus will run with the same efficiency regardless of the method you choose.


To create a Geographic Coding Plus job, you will perform seven tasks:

1 Copy the IVP file to use as a template.

2 Define the physical attributes of your input and output files.

3 Define the layout of your input records.

4 Define the layout of your output records.

5 Define your processing options.

6 Define your reporting options.



7 Write control language.

Parameter Record Reference

The table below shows which parameter records are associated with each step of a Geographic Coding Plus job. Please refer to Appendix A, "Parameter Record Reference" for complete details of each parameter record.

Table 2: Parameter Records By Job Step

Job Step Parameter Records Used

2. Defining the physical attributes of input and output files

FILEDF* *a separate FILEDF is required for each input and output file

3. Defining the layout of input records ADDRDF CS ZIP

4. Defining the layout of output records

ARCOUT AUXOUT CONSxx DISTIT GEOOUT LLOUT MCDOUT MOVE I MOVE O MSAOUT STLOC

5. Defining processing options CONFRM CONFIG TESTIT

6. Defining reporting options REPORT HEADER UHDxx UFTxx PAGESZ

Step 1. Copying the IVP File

The Geographic Coding Plus installation process copies an IVP (installation verification procedure) file to your system. This is a basic job that verifies the proper installation of the application files and programs. The IVP is useful as a template for new jobs because it contains the minimum required organization and content.

NOTE: See Chapter 2 of this guide for platform-specific instructions on copying the IVP files. Please refer to the installation instructions that came with Geographic Coding Plus for instructions on loading Geographic Coding Plus files and databases.



Step 2. Defining the Physical Attributes of Your Files

The first step to creating a Geographic Coding Plus job is to define the physical attributes of your input and output files. You will define some or all of the following files:

• GCBMNAM—This required file contains your input name-and-address records. • GCBMCOK—This required file will contain all of the records that were matched by

Geographic Coding Plus. • GCBMNCO—This optional file will contain all of the records that Geographic Coding Plus

could not match. • GCBMARC—This optional file will contain data you specify to be used as input to a

geographic mapping application, such as ESRI’s ArcView®. • GCBMPRM—This file will contain all the parameter records for your job.

Define each of these files by creating a FILEDF parameter record. Remember that each input and output file requires a separate FILEDF parameter record.

Step 3. Defining the Layout of Input Record Elements

To define the data elements that are contained in your input records, you will create parameter records to define the format of your address and the locations and lengths of the elements that make up the address, such as street address and ZIP Code.

You will define some or all of these parameter records, depending on your processing requirements:

• ADDRDF — Tells Geographic Coding Plus the format, location, and length of each address line or field. Required if doing a street match; optional if doing a postal match.

• CS ZIP — Tells Geographic Coding Plus the location, length, and format of city, state, and ZIP Code fields. Required.

• MOVE I — Allows you to rearrange pieces of the input records before they are processed. Optional.

• CONSxx — Allows you to define up to 99 constants to use with the MOVE I or MOVE O parameter records. Optional.



Step 4. Defining the Layout of Output Record Elements

The next type of information you will define is the layout and content of the records that Geographic Coding Plus will write to the output files you have defined. You will define locations, lengths, and sometimes formats for the following types of data elements:

• Latitude and longitude information • Metropolitan Statistical Area codes (MSAs) and names • Minor Civil Divisions (MCDs)/Census County Division (CCDs) and names • Census codes, such as state, county, Census Tract, Block Group, and Block ID • Auxiliary information stored in the Auxiliary File.


• ARCOUT — Tells Geographic Coding Plus what data elements should be posted in the GCBMARC file other than latitude and longitude coordinates (for import to a mapping application).

• AUXOUT — Tells Geographic Coding Plus the location and length of data to be posted (on the output record) from the user-defined Auxiliary file.

• DISTIT — Tells Geographic Coding Plus to post a distance calculation between two different latitude/longitudes.

• GEOOUT — Tells Geographic Coding Plus to post the matched geographic codes to your output records, including FIPS state and county codes, census tract, block group, block ID, state abbreviation, and county name.

• LLOUT — Tells Geographic Coding Plus to post the matched latitude/longitudes to your output records. Also allows you to set latitude/longitude formats and matching levels (e.g., street level or postal level).

• MCDOUT — Tells Geographic Coding Plus to post the MCD/CCD names and codes to your output records.

• MOVE O — Allows you to rearrange pieces of the output record before it is written to the output file.

• MSAOUT — Tells Geographic Coding Plus to post MSA names and codes to your output records.

• STLOC — Tells Geographic Coding Plus to use the optional Multi-Locator function to identify (up to) nine of the closest locations (e.g., stores) to each target address (e.g., a customer address).

NOTE: Geographic Coding Plus creates output records as follows: 1Geographic Coding Plus copies the input record to the output area. 2Geographic Coding Plus reads all output parameter records, writing the data elements they describe to the desired locations. For this reason, you must take care when defining output locations for your data elements. It is very easy to accidentally overwrite input data that you want to preserve with output data. Unless you intentionally want to overwrite input data, you should take care to define the locations for your output elements so that they are written beyond the input data.



Step 5. Defining Processing Options

To define the processing options that control your Geographic Coding Plus job, create parameter records for the following:

• To define the processing configuration used to process your input file. This configuration consists of matching preferences (street matching, postal matching, or Auxiliary file matching).

• To write records with a specific input field value directly to the GCBMCOK file without being processed. This procedure is called “automatic confirmation.”

• To indicate that the parameter records in your job should be checked for errors but that the job should not be executed at this time.


• CONFRM — Tells Geographic Coding Plus to write records to the output file that possess a certain input field value without going through the matching process.

• CONFIG — Tells Geographic Coding Plus what kind of matching to occur during processing.

• TESTIT — Run the job to check for parameter record errors.

Step 6. Defining Reporting Options

You can optionally print several reports within Geographic Coding Plus in addition to those that are printed automatically. You can also determine some of the format options for your reports.

Defining Which Reports to Print

Geographic Coding Plus has four reports that are printed automatically for every job; therefore, you cannot suppress them. These reports include:

• Parameter Record Listing • Execution Log • Control Totals • Address Match Execution Statistics.

You can, however, choose to print or suppress the following reports by using the REPORT parameter record:

• Coding Percentages per State/County • Coding Percentages per State.

NOTE: The default is to print each of these reports for your job. If you do not want to suppress any of them, you do not need to include a REPORT parameter record in your job.



Defining Report Formats

While the format for the body of all reports is internally set by Geographic Coding Plus, you can control the format and content of the reports' headers and footers as well as the number of lines that will be printed on each report page. You will write parameter records to accomplish the following report formatting:

• Control the main header • Control the additional header • Control the footer • Specify the number of lines per page.

Headers and Footers

There are three kinds of headers and two kinds of footers on all Geographic Coding Plus reports. The types of headers are:

• System Header—Generated by Geographic Coding Plus, the system header is a single line that prints at the very top of the report page and includes the name of the report and the page number.

• Main Header—Generated by the data you specify, this single-line includes a date (either the system date or another date you specify) and/or up to 40 characters of text. This header line is the last header line printed, and appears just above the main body of the report page.

• Additional Header—Generated by data you specify, this header can be up to 4 lines of text. Each line can contain up to 132 characters. These lines are printed below the system header but above the main header.

The types of footers are:

• System Footer—Generated by Geographic Coding Plus, the system footer is a single line that prints at the very top of the report page, and includes the name of the report and the page number exactly as it appears in the system header.

• Additional Footer — Generated by data you specify, this footer can be up to 4 lines of text. Each line can contain up to 132 characters. These lines are printed below the body of the report page, but above the system footer.



For example, a report with all lines of all headers and footers defined would be formatted as follows:

System Header

Additional Header Line 1 Additional Header Line 2 Additional Header Line 3 Additional Header Line 4

Main Header

.

.

. Body of Report . . .

Additional Footer Line 1 Additional Footer Line 2 Additional Footer Line 3 Additional Footer Line 4

System Footer

Step 7. Writing Control Language

Your software media came with a sample file that you should copy and edit as necessary to run your Geographic Coding Plus job. Chapter 10, "Using Geographic Coding Plus in Different Environments" provides additional information on file names and platform-specific functions.


C H A P T E R 4

Getting Started with Interactive Processing

This chapter describes the database matching and inquiry functions that make up the Interactive Geographic Coding Plus System. Screens, examples, and navigation techniques are presented.

The Geographic Coding Plus Interactive Address Matcher

The Geographic Coding Plus Interactive Matcher enables you to obtain census information and latitudes/longitudes for individual addresses via one easy-to-use screen. On this screen, you enter a single input address to match against the Geographic Coding Plus databases. For a matched address, Geographic Coding Plus shows you the:

• State and county FIPS codes • Census tract • MSA Code and name • MCD/CCD code and name • Block group and Block ID • Latitude/longitude.

Input Fields

Match Results

Function Keys

Figure 2: Components of the Address Matching Screen



Figure 2 shows the layout of the Address Matching screen. This screen includes:

• Input Fields — enter the address you want to match. • Match Results — Geographic Coding Plus returns the geographic and census information. • Function Keys — access other functions in the address matching component, including Help.

How to Use the Matcher

To match an address, launch Geographic Coding Plus Matcher and follow the steps below.

1 Move your cursor to the top of the screen using the TAB key, arrow keys, or Field Exit key.

2 Enter any firm name, primary and secondary address lines, city, state, and/or ZIP Code.

NOTE: The Primary Address and ZIP Code fields are both required fields — you must enter information into these fields for Geographic Coding Plus to find a match.

3 Press .

4 Geographic Coding Plus searches the database to find an address that matches the one you entered.

5 If a match is found, geographic and census information for that address appear on the bottom half of the screen.

Figure 3: Match Results Screen



Fields

The following table presents a description of, and acceptable values for, each field on the Address Match screen.

Field Name Description

Input Fields

Firm Name The name of the firm for the record you want to match — optional. Example: PITNEY BOWES

Primary Addr The primary address line for the record you want to match — required for Street match Example: 4200 PARLIAMENT PLACE

Secondary Addr The secondary address line for the record you want to match — optional. Example: SUITE 600

City, ST The city and state for the record you want to match. You can enter the state name or abbreviation — optional. Example: LANHAM, MD

ZIP Code The ZIP Code (or ZIP+4) for the record you want to match — required. Example: 20706

Command Input a command. Example: HELP

Match Results Fields

Match Level Indicates what level of match:

S Street level

9 ZIP+4 level

5 ZIP Code level

A Auxiliary file

State Code Two-digit FIPS state code and state name. Example: 24 MD

County Code Three-digit FIPS county code and name. Example: 033 PRINCE GEORGES

Census Tract Six-digit code representing a small statistical subdivision of a metropolitan county, with about 4000 residents. Example: 803510

MSA Code Old Definition: Four-digit code for the Metropolitan Statistical Area, which is a group of counties containing a central population nucleus of at least 50,000 inhabitants. Example: 8840

New Definition: see CBSA

MCD/CCD Code Five-digit code representing the Minor Civil Division or Census County Division, which is the primary political or administrative division of a county. Example: 91164




MCD/CCD Name Name of the Minor Civil Division or Census County Division, which is the primary political or administrative division of a county. Example: DISTRICT 13 KENT

NOTE: MCD/CCD names are provided as a result of a street match only (RC=S).

Block Group One-digit code for the collection of census blocks within a census tract or block numbering area sharing the same first digit. Example: 1

Block ID Three-digit code for the block ID (a unit of a block group). Example: 009

MSA Name MSA’s have a unique name including the name of the population nucleus and state abbreviations for all inclusive states. Example: WASHINGTON DC-MD-VA-WV

CBSA Code/Name Five-digit code for the Core Based Statistical Area, which is replacing MSA as a unit of statistical measure. CBSAs are county-based, have a core urbanized cluster, plus adjacent territory that has a high degree of social and economic integration with the core as measured by commuting ties. Are identified by a name that ends with “Metropolitan Statistical Area” or “Micropolitan Statistical Area” Example: 47900, WASHINGTON-ARLINGTON-ALEXANDRIA, DC-VA-MD-WV

CBSAD Code/ Name

Five-digit code for the Core Based Statistical Area Division, which is a subdivision of a Metropolitan Statistical Area that contains a single core of 2.5 million or more inhabitants and has been subdivided to form smaller groupings of counties. Example: 47894, WASHINGTON-ARLINGTON-ALEXANDRIA, DC-VA-MD-WV

CSA Code/Name Three-digit code for the Combined Statistical Area which is an area created from two or more CBSAs — a “super” CBSA. Example: 548, WASHINGTON-BALTIMORE-NORTHERN VIRGINIA, DC-MD-VA-WV

Lat/Long Level The level at which the lat/long was determined:

R “Rooftop” based on street address

4 ZIP+4 Code centroid

B Block group centroid

2 ZIP+2 Code centroid

T Census tract centroid

5 ZIP Code centroid

Z ZIP Code centroid

Blank No latitude/longitude could be determined


Database Inquiry Function


Latitude The address location’s distance north or south of the equator, measured in degrees. Example: 039.948634 N

Longitude The address location’s distance east or west of Greenwich, England, measures in degrees. Example: 076.837170 W

Function Keys

The following table describes the action taken by each function key on the Address Match screen.

Function Key Name Description

F1 HELP Obtain online help.

F3 QUIT Exit from the Interactive Geographic Coding Plus System.

F5 REFRESH Refresh the screen so you can enter another address for matching.

NOTE: Entering the name of a key in the Command field is the same as pressing the function key (for example, to access online help, you could either press F1 or, in the Command field, type HELP and press ENTER.)


The database inquiry function lets you browse the contents of the Geographic Coding Plus postal database. Using this feature, you can look up all counties and MSAs within a state; ZIP+4 Codes and census information within a ZIP Code; and counties and MSAs within a ZIP Code. The database inquiry function enables you to display and analyze the following information for each state in the Geographic Coding Plus database:

• ZIPs within a state • Counties and MSAs within a state • ZIP+4 Codes and related census information within a ZIP Code • Counties and MSAs within a ZIP Code.



The Geographic Coding Plus Inquiry function begins with a screen that lists all the states in the database. The different parts of the screen are shown in Figure 4.

Figure 4: Components of the Inquiry Screen

As shown in Figure 4, the Inquiry screen includes:

• Command Field — enter screen commands. • Database Inquiry — the first database inquiry screen shows you a list of states in the database

(sorted by the first three digits of the ZIP Code range) • Function Keys — access navigation functions available in the Inquiry component, and access

Help.

Online Help Facility

Geographic Coding Plus Inquiry also has an extensive help facility. Help is available on three levels:

• Context sensitive help • System Tutorial • List of Commands.

To access the online help facility, enter “HELP” in the Command field or press function key or the key. The online help facility displays a menu, and you can choose to see the tutorial, a list of all valid commands, or context sensitive help on the screen that was displayed when you accessed the online help facility.



To exit the help facility, press function key or enter X in the Selection field.

Figure 5: Interactive Geographic Coding Plus Main Help Screen

Navigation

From the main Inquiry screen, you can also access County/MSA information, ZIP information, and ZIP+4 information. In total, there are five screens that support database inquiry:

• Main inquiry screen (i.e., state listing) • ZIP Code information for a state • County/MSA information for a state • ZIP+4 information for a ZIP Code • County/MSA information for a ZIP Code.

Figure 6 on page 41 shows how all these inquiry screens are related.



Function Keys

You can move around the Inquiry screens by using the following navigation keys:

• F6 Back — Move back to the previous level • F7 Up — Move up to the previous screen of data • F8 Down — Move to the next screen of data • F9 Top — Move to the first screen of data • F10 Bottom — Move to the last screen of data.

From any screen in the inquiry function, press F3 to exit from Geographic Coding Plus Inquiry. For Help, press F1.

Select state, press

Press

Select ZIP, press

Press ZIP+4 Listing for a ZIP Code

County/MSA Listing for a State

County/MSA Listing for a ZIP Code

Main Inquiry Screen State Listing

ZIP Code Listing for a State

Figure 6: Hierarchy of Geographic Coding Plus Inquiry Screens



Inquiry Commands

Commands provide another way of moving around the Inquiry screens. The table below lists all the commands available in the Inquiry function.

Command What It Does Alternate Method

BACK Return to previous level F6

HELP Invoke Help F1

QUIT Exit Geographic Coding Plus Inquiry F3

CMsa Go to the County/MSA screen F2

ST Go to the State screen n/a

ZIP Go to the ZIP Code screen F4

ZIP4 Go to the ZIP+4 screen F4

Z4 Go to the ZIP+4 screen F4

ADVanced File Display Advanced File data (ZIP Code and ZIP+4 n/a screens only)

BASe Display Base File data (ZIP Code and ZIP+4 n/a screens only)

How to Use Geographic Coding Plus Inquiry

To use the inquiry function, launch Geographic Coding Plus Inquiry. You are presented with a list of all the states in the database, as shown in Figure 7. To select a state, use the right arrow key or TAB key to move the cursor to the state you want to select. To move up or down in the state listing:

• Type the 3-digit ZIP Code range in the Command field, or • Use the function keys (F7, F8, F9, and F10), or Page Up/Page Down keys.

NOTE: See Chapter 7 of the “Working With” guide for platform-specific instructions on launching the Interactive system.



Once you select a state, press F4 for a listing of ZIPs in that state.

Figure 7: The Main Inquiry Screen

Fields

The following table presents a description of each field on the Main Inquiry screen.


3D Range The first three digits of the ZIP Code (i.e., ZIP Code range) for that state.

State The FIPS state code.

Abbr The standard state abbreviation.

State Name The name of the state.



Function Keys

The following table describes the action taken by each function key on the Main Inquiry screen.

Function Key Name Description

F1 HELP Obtain online help.

F3 QUIT Exit from the Interactive Geographic Coding Plus System.

F4 ZIP Go to the ZIP Code Information for a State screen for the selected state.

F7 UP Go to the previous screen of state listings.

F8 DOWN Go to the next screen of state listings.

F9 TOP Go to the top of the state listing.

F10 BOTTOM Go to the bottom of the state listing.

ZIP Code Information for a State

When you select a state from the Main Inquiry Screen and press F4, you are presented with the ZIP Code listing for that state. The ZIP Code Listing for a state also lists the state code, county code, census tract, MSA code, MCD/CCD code, latitude, and longitude for each ZIP Code.

Figure 8: ZIP Code Information for a State



Fields

The following table presents a description of each field on the ZIP Code Information for a State screen.


ZIP The 5-digit ZIP Code. Example: 20113

St Two-digit FIPS state code. Example: 51

Geographic Coding Plus - Pitney Bowes · 2019. 2. 9. · Chapter 3, Getting Started Walks you...

Documents

Transcript of Geographic Coding Plus - Pitney Bowes · 2019. 2. 9. · Chapter 3, Getting Started Walks you...