CommunityViewer & Census 2010 LUCA Program

CommunityViewer & LUCA -- Local Address Files in Census Structure

This document summarizes the process of converting a local address file into the Census/LUCA 26-field parsed address list file structure. Once the local address file is in this format, the file may be used in combination with the Census supplied address list file to perform address list updates. While the example used here is an Enhanced 911 (E911) file, the same procedures can be applied to any local-sourced address data. This document assumes some familiarity with operation of the CommunityViewer (CV) software and that the reader has access to the CV User Guide.

With CV running, use File>Open to open the project c:\cv\gafiles\marion.gpr.
(if you do not have this project fileset, contact Proximity)

To preserve the original Marion E911 shapefile, use File>Copyshapefile:
-- copy c:\cv\gafiles\marion_911.shp to c:\cv\gafiles\marion_911_rev.shp

Modify c:\cv\gafiles\marion_911_rev.dbf to add fields listed below.
-- See CV Help>Applications>Census 2010 LUCA>Building Local Address File.

Use Excel to add fields and assign values:

• ID = col A
• ADDR1 = col B+&" "&+col D
• CITY = col F
• STATE = GA (constant -- not in file)
• ZIP5 -- leave blank for now -- not in file
• LAT = col R
• LON = col Q
• GEOID -- leave blank

These properties of the revised file are essential:

• key in header row field names (8 above listed fields)
• initially leave all new fields as 'general'
• set computational values in row 2
• copy row 2 new fields to all other rows (bulk copy)
• copy these columns and paste to replace with values (rather than computes)
• attribute each new field/column as set forth in user guide
• --> see CV Help>Applications>Census 2010 LUCA>Building Local Address File
• set full 'database' to include extended columns

Use CV AddLayer button to add the new shapefile: c:\cv\gafiles\marion_911_rev.shp.

Use CV File>Save ProjectAs to the new project file name c:\cv\gafiles\marion1.gpr.

Use CV Tools>Point in Polygon to code GEOID (numbers below refer to graphics in User Guide).

1 - TGR Blocks
1.3 TRACT='980200' (as one example -- there are 211 points in this tract)
2 - marion_911_rev.shp
4 - checked
4.1 GEOID
4.2 STFID
click Process

Use CV File>Close to close the project project.

Use CV Tools>AddressManager>LUCA Address Processing to parse the file and create a new file:
-- existing file: c:\cv\gafiles\marion_911_rev.dbf
-- new LUCA file: c:\cv\gafiles\marion_911_rev_luca.dbf dbf
-- entity id: co13197

The entire county file is built, but only 911 records in tract 980200 are coded (due to criteria setting).

Use CV File>Open and open project marion1.gpr.

Use CV AddLayer button to add c:\cv\gafiles\marion_911_rev_luca.shp. Resulting view:

In the above view, the two markers by the pointer both show (with identify tool) as in block 1018 whereas one should be in 1016. There are other such examples. This is the result of a) the TIGER/Line road remains incorrect after MTAIP and/or b) the lat-lon assigned to the 911 point is slightly off. This suggests that even though the 911 data are coded with lat-lon, they might have to be re-geocoded with the local geocoder running on the TIGER/Line sourced block shapefile. In non-MTAIP counties thus poses further problems of inaccuracy.

Finally, use CV File>Save to save the project as c:\cv\gafiles\marion2.gpr. The entire set of files, beginning through end, is contained in the marion.zip distribution file.

Following the development of this file, next steps would include analyzing these data in context of the Census supplied local address file. See CV User Guide for additional information.