THE CALL COMES IN Continued from page 47 Name: Description: Reference data: \GC1_Parcel.shp \GC2_City_Street.shp \GC3_TIGER_ Street.shp Store relative Fields path names Checked Checked Checked Key Field – SITE_FULL See Table 2 See Table 2 The field containing: KeyField Street Street Is recognized if it is named: Address2 Address2 Address2 Place Name Alias Table 1_Parcel_Single_Field Single Field 2_City_US_Streets 3_TIGER_US_Street US Streets US Streets Table 1: Parameters for creating individual address locators cator. Unfortunately, CAD data often does not include sufficient information to apply a U.S. Streets with Zone Locator. Typically this data lacks municipality or ZIP Code information. Each agency must decide how to clip streets to include unique names or process addresses in different communities that share similar street names. 3. Next, open the attribute table for the GC3 TIGER Street shapefile and inspect its fields. This dataset is adapted from 2009 Census TIGER street data, now in development by the U.S. Census Bureau. It includes a schema similar to the Lakewood Public Works data. Notice that field names and placement are different. This is the third addressing dataset, and it captures many road intersection addresses and the locations of incidents that might occur outside the extent of the Public Works dataset. The TIGER 2010 data, not yet released, will be different from TIGER 2000 data. 4. Now click the Add Data button, navigate to \Lakewood\DBFFiles and locate Inc_2008_ Address, and load this table containing incident data. Open this table and inspect it. This dataset contains nearly 7,000 incident records and has only a few fields. It has an index field (INDEX), an incident number field stored as an alpha string (INC_NO), and a standardized address field named (ADDRESS2). Notice that there is no field in this dataset to identify a geocoding zone. 5. Sort ADDRESS2 and notice it contains both numeric and street intersection addresses. These addresses were generated and posted using CAD software, then edited by the local jurisdiction to correct inconsistencies. This data is clean and contains only incident addresses. Other information will be joined to these geocoded points later using the INC_NO field. To review: In this task, the three reference datasets in the map document were reviewed, and one file containing incident data was added to the map document. The second geocoding data source, GC2 City Streets, supports a U.S. Streets Locator. It is maintained by the Lakewood Public Works Department and is current and complete. It will be used to build the 2_City_US_Streets address locator. The data source for the third address locator, the GC3 TIGER Street shapefile, was adapted from 2009 Census TIGER street data, now in development by the U.S. Census Bureau. 48 ArcUser Spring 2010 www.esri.com