THE CALL COMES IN Continued from page 51 say, 1,000 feet or less). Click the Pick Address from Map button and use the crosshair tool to choose the best candidate, then click Match. Also check the Fixes1 spreadsheet to see if any ties show up there. After matching the last tied records, all tied records should show a 100 percent score. While matching ties, look for the reasons they occurred. Some are readily fixed by editing street address ranges, which will require that you rebuild the affected address locators before continuing. Other errors, such as those caused by looped streets and offset intersections, are hard to avoid. Finally, consider matched addresses that score less than 100. Show results for matched addresses and sort the Score field in ascending order. Only a few records will have scores less than 100. See if you can boost those scores to 100 by using observations, intuition, and the Fixes1 spreadsheet. After fixing all records, close the Interactive Rematch dialog box and save the map document. Task 5: Adding Detailed Information about Incidents The input data contains only incident numbers and addresses. With all these points properly placed on a map, joining or relating data from other tables will add more information on the incidents such as date and type of incident. The last step will symbolize incidents using a graduated color scheme that identifies incidents by type. 1. Navigate to \Lakewood\DBFFiles and add Inc_2008_Date_Type.dbf to the map document. Open Inc_2008_Date_Type and compare it to the attribute table for Geocoding Results: Inc_2008_GC1. Note that these tables share a common field, INC_NO, so there may be a one-to-one relationship between the tables. 2. Right-click Geocoding Results: Inc_ 2008_GC1 and choose Join. Create this join to Inc_2008_Date_Type.dbf using INC_NO as the common field. Inspect the results and verify that all records have joined. 3. The next step symbolizes incident points using a graduated color legend that corresponds to the National Fire Incident Reporting System (NFIRS). Open the Layer Properties dialog box for the incident layer (Geocoding Results: Inc_2008_GC1) and click the 52 ArcUser Spring 2010 Join the table Inc_2008_Date_Type to Geocoding Results: Inc_2008_ GC1 to symbolize the incidents. Load the ArcView 3.x legend to use the NFIRS color scheme. properties to learn more about NFIRS incident types. Incidents are coded thus: 100 series points are fire related; 200 series points are explosions or ruptures; 300 series points are rescues and EMS calls; 40 series points are hazardous conditions; and all points over 499 are service calls, false alarms, and special calls. Acknowledgments The author thanks all the people who helped provide mapping data and other information that was used in this tutorial. Because this data has been synthesized, those providers might not recognize their own data. Thanks also go to the author’s advanced GIS students at Bellingham Technical College in Washington who helped identify and resolve real-world training issues. Symbology tab. Click the Import button and choose ArcView 3 (*.avl) file and navigate to the \Lakewood\Utility folder. Select nfirs5_3. avl and set the Value field to NFIRS_TYPE. Click OK several times to apply the legend. 4. Save the finished project. Once the color scheme is applied, check the symbology Once the incidents are symbolized, check the symbology properties to learn more about the incidents. www.esri.com