+---------------------------------------------------------+------------+
| **2008 Census Dress Rehearsal**                         | **June     |
|                                                         | 2006**     |
| **Local Update of Census Addresses (LUCA) Program**     |            |
|                                                         |            |
| **User Guide**                                          |            |
+---------------------------------------------------------+------------+
| **Option 1 -- Title 13 Full Address List Review**       |            |
|                                                         |            |
| **Computer-Readable Format**                            |            |
|                                                         |            |
| ![](media/image1.wmf){width="2.7284722222222224in"      |            |
| height="2.7284722222222224in"}                          |            |
+---------------------------------------------------------+------------+
| ![](media/image2.png){width="2.751388888888889in"       |            |
| height="0.42291666666666666in"}                         |            |
+---------------------------------------------------------+------------+

Table of Contents

[**Chapter 1 Introduction to the 2008 Census Dress Rehearsal Local
Update of Census Addresses (LUCA) Program
1**](#chapter-1-introduction-to-the-2008-census-dress-rehearsal-local-update-of-census-addresses-luca-program)

[The 2008 Census Dress Rehearsal Local Update of Census Addresses (LUCA)
Program
1](#the-2008-census-dress-rehearsal-local-update-of-census-addresses-luca-program)

[Background 2](#background)

[The Census Address List Improvement Act
2](#the-census-address-list-improvement-act)

[The Census Bureau's Master Address File (MAF)
2](#the-census-bureaus-master-address-file-maf)

[The Topologically Integrated Geographic Encoding and Referencing
(TIGER^^) Database
2](#the-topologically-integrated-geographic-encoding-and-referencing-tiger-database)

[Census Bureau LUCA Responsibilities
3](#census-bureau-luca-responsibilities)

[LUCA Participant Responsibilities
3](#luca-participant-responsibilities)

[Training and Technical Support 4](#training-and-technical-support)

[Schedule 4](#schedule)

[The 2008 Census Dress Rehearsal LUCA User Guide Overview
4](#the-2008-census-dress-rehearsal-luca-user-guide-overview)

[Chapter 2 Before You Begin Your Review
7](#chapter-2-before-you-begin-your-review)

[What is a Housing Unit? 7](#what-is-a-housing-unit)

[What are Group Quarters? 7](#what-are-group-quarters)

[Unacceptable Types of Housing Units and Group Quarters
8](#unacceptable-types-of-housing-units-and-group-quarters)

[Census Bureau Addresses 8](#census-bureau-addresses)

[Residential and Nonresidential Addresses
8](#residential-and-nonresidential-addresses)

[Address Formats 8](#address-formats)

[City-style Address Format 8](#city-style-address-format)

[Noncity-Style Address Format 9](#noncity-style-address-format)

[Strategies for Reviewing the Census Bureau's Address List
9](#strategies-for-reviewing-the-census-bureaus-address-list)

[Local Address Sources 9](#local-address-sources)

[Chapter 3 The LUCA Program's Computer-Readable Adress List and Address
Count List
11](#chapter-3-the-luca-programs-computer-readable-adress-list-and-address-count-list)

[Introduction 11](#introduction)

[Protecting Census Bureau Address Information
11](#protecting-census-bureau-address-information)

[The File Names 13](#the-file-names)

[The File Format 14](#the-file-format)

[Example -- Computer-Readable Address List File Record Layout
15](#example-computer-readable-address-list-file-record-layout)

[Example -- Address Count List File Record Layout
16](#example-address-count-list-file-record-layout)

[Software Requirements 16](#software-requirements)

[Opening the Files 17](#opening-the-files)

[Example -- Pipe-delimited Address List File -- City-style Address
18](#example-pipe-delimited-address-list-file-city-style-address)

[Example -- Pipe-delimited Address List File -- Noncity-style Address
19](#example-pipe-delimited-address-list-file-noncity-style-address)

[Example -- Pipe-delimited Address Count List File
20](#example-pipe-delimited-address-count-list-file)

[Chapter 4 The Census Bureau Maps 21](#chapter-4-the-census-bureau-maps)

[Introduction 21](#introduction-1)

[Reading a Census Bureau Paper Map
21](#reading-a-census-bureau-paper-map)

[Examples 23](#examples)

##### [Map Example 1: Adding a New Street and Associated Address Ranges 23](#map-example-1-adding-a-new-street-and-associated-address-ranges) {#map-example-1-adding-a-new-street-and-associated-address-ranges-23 .TOC-5}

##### [Map Example 2: Correcting a Street Name 24](#map-example-2-correcting-a-street-name) {#map-example-2-correcting-a-street-name-24 .TOC-5}

##### [Map Example 3: Moving a Street 24](#map-example-3-moving-a-street) {#map-example-3-moving-a-street-24 .TOC-5}

##### [Map Example 4: Deleting a Street 25](#map-example-4-deleting-a-street) {#map-example-4-deleting-a-street-25 .TOC-5}

[The MAF/TIGER Accuracy Improvement Project: Digital Update of the
TIGER^^ Database
25](#the-maftiger-accuracy-improvement-project-digital-update-of-the-tiger-database)

[Shapefiles 25](#shapefiles)

[Submitting Shapefile Feature Information
26](#submitting-shapefile-feature-information)

[The Census Bureau's Shapefile Coordinate System and Projection
Information
26](#the-census-bureaus-shapefile-coordinate-system-and-projection-information)

[General File Setup Guidelines 26](#general-file-setup-guidelines)

[Changing Our Coordinate System to Match Yours
27](#changing-our-coordinate-system-to-match-yours)

[Feature Information 27](#feature-information)

[Updating the Feature Shapefile 28](#updating-the-feature-shapefile)

[Displaying Features Based on CFCC1
28](#displaying-features-based-on-cfcc1)

[Address Information 30](#address-information)

[Data Dictionary and Metadata 30](#data-dictionary-and-metadata)

[Data Dictionary 30](#data-dictionary)

[Metadata Requirements 32](#metadata-requirements)

[Digital File Submission 33](#digital-file-submission)

[Compressing the File 33](#compressing-the-file)

[Boundary and Annexation Survey (BAS)
34](#boundary-and-annexation-survey-bas)

[Chapter 5 Reviewing and Updating the Address List File
35](#chapter-5-reviewing-and-updating-the-address-list-file)

[Action Codes for Updating the Address List File
35](#action-codes-for-updating-the-address-list-file)

[A -- Adding Addresses 35](#a-adding-addresses)

[C -- Correcting Addresses 36](#c-correcting-addresses)

[D -- Deleting Addresses 38](#d-deleting-addresses)

[J -- Not in Jurisdiction Addresses
38](#j-not-in-jurisdiction-addresses)

[N -- Nonresidential Addresses 39](#n-nonresidential-addresses)

[Saving the File 39](#saving-the-file)

[Chapter 6 Reviewing and Updating the Address Count List File
40](#chapter-6-reviewing-and-updating-the-address-count-list-file)

[The Address Count List File 40](#__RefHeading___Toc137619543)

[Reviewing and Editing the Address Count List File
40](#reviewing-and-editing-the-address-count-list-file)

[Saving the File 40](#saving-the-file-1)

[Chapter 7 Submitting Your LUCA Program Updates
42](#chapter-7-submitting-your-luca-program-updates)

[Submitting LUCA Program Updates 42](#submitting-luca-program-updates)

[Files 42](#files)

[Census Bureau Paper Maps 42](#census-bureau-paper-maps)

[Shapefile 42](#shapefile)

[Shipping Census Bureau Title 13 Materials
43](#shipping-census-bureau-title-13-materials)

[Chapter 8 Returning Or Destroying Census Bureau Title 13 Materials
44](#chapter-8-returning-or-destroying-census-bureau-title-13-materials)

[Returning or Destroying Census Bureau Title 13 Materials
44](#returning-or-destroying-census-bureau-title-13-materials)

[Shipping Census Bureau Title 13 Materials
44](#shipping-census-bureau-title-13-materials-1)

[Methods for Destroying Census Bureau Title 13 Materials
44](#methods-for-destroying-census-bureau-title-13-materials)

[APPENDIXES](#__RefHeading___Toc137619556)

[Appendix A Confidentiality and Security Guidelines
46](#appendix-a-confidentiality-and-security-guidelines)

[Appendix B Confidentiality Agreement Form
52](#appendix-b-confidentiality-agreement-form)

[Appendix C Boundary and Annexation Survey (BAS) Paper Map
53](#appendix-c-boundary-and-annexation-survey-bas-paper-map)

[Appendix D Boundary and Annexation Survey (BAS) Digital File Submission
56](#appendix-d-boundary-and-annexation-survey-bas-digital-file-submission)

[Appendix E Annexations and Detachments Form
87](#appendix-e-annexations-and-detachments-form)

[Appendix F Contact Update Information Form
88](#appendix-f-contact-update-information-form)

[Appendix G Inventory Form 89](#appendix-g-inventory-form)

[Appendix H Special Disclosure Notice
90](#appendix-h-special-disclosure-notice)

[Appendix I Return/Destruction of Title 13, U.S.C. Materials Form
91](#appendix-i-returndestruction-of-title-13-u.s.c.-materials-form)

[Appendix J The Map Legend 92](#appendix-j-the-map-legend)

[Appendix K Physical Location Description and Street Type Abbreviation
Examples
97](#appendix-k-physical-location-description-and-street-type-abbreviation-examples)

[Appendix L Unit Designation Abbreviation Examples
98](#appendix-l-unit-designation-abbreviation-examples)

[Glossary 99](#glossary)

[Index 103](#index)

# 

Table of Figures

[Figure 3.1: Entity Identification Codes
13](#__RefHeading___Toc137619573)

[Figure 3.2: Computer-Readable Address List File Record Layout
15](#__RefHeading___Toc137619574)

[Figure 3.3: Address Count List File Record Layout
16](#__RefHeading___Toc137619575)

[Figure 3.3.1: Address Count List File "Total Row" Layout
16](#__RefHeading___Toc137619576)

[Figure 3.4: Pipe-delimited LUCA Program Address List File -- City-style
Address 18](#__RefHeading___Toc137619577)

[Figure 3.5: Pipe-delimited LUCA Program Address List File --
Noncity-style Address 19](#__RefHeading___Toc137619578)

[Figure 3.6: Pipe-delimited Address Count List File
20](#__RefHeading___Toc137619579)

[Figure 4.1: Sample of a Census Bureau Paper Map
22](#__RefHeading___Toc137619580)

[Figure 4.2: Adding a New Street and Associated Address Ranges
23](#__RefHeading___Toc137619581)

[Figure 4.3: Correcting a Street Name 24](#__RefHeading___Toc137619582)

[Figure 4.4: Moving a Street 24](#__RefHeading___Toc137619583)

[Figure 4.5: Deleting a Street 25](#__RefHeading___Toc137619584)

[Figure 4.6: Change Type Codes for Feature Corrections
28](#__RefHeading___Toc137619585)

[Figure 4.7: Digital Road Correction Example
29](#__RefHeading___Toc137619586)

[Figure 4.8: Table Extract for Figure 4.7
30](#__RefHeading___Toc137619587)

[Figure 4.9: Data Dictionary for all Line Shapefiles
31](#__RefHeading___Toc137619588)

[Figure 4.10: Data Dictionary for Census Tracts
31](#__RefHeading___Toc137619589)

[Figure 4.11: Data Dictionary for Census Blocks
32](#__RefHeading___Toc137619590)

[Figure C.1: Boundary Changes 54](#__RefHeading___Toc137619591)

[Figure C.2: Signature Box 54](#__RefHeading___Toc137619592)

[Figure C.3: Example of a Completed Annexations and Detachments Form
55](#__RefHeading___Toc137619593)

**Quick Reference**

**[How to:]{.mark}**

> Protect the Census Bureau's Address List 11
>
> Open files 17
>
> Save files 39, 40
>
> Read a Census Bureau Map 21
>
> Add a street 23
>
> Add address ranges on a new street 23
>
> Correct a street name 24
>
> Move a street 24
>
> Delete a street 25
>
> Update the feature shapefile 28
>
> Submit shapefile feature information 33
>
> Correct boundaries 53, 56
>
> Add an address 35
>
> Correct address information 36
>
> Update the conversion of a housing unit to a multi-unit structure 37
>
> Add apartment/unit numbers 37
>
> Update the conversion of a multi-unit structure to a housing unit 37
>
> Update the conversion of a group quarters to a housing unit 38
>
> Update the conversion of a housing unit to a group quarters 38
>
> Delete an address 38
>
> Identify an address not in my jurisdiction 38
>
> Identify a nonresidential address 8, 38
>
> Edit the Address Count List 40
>
> Submit updates 42
>
> Ship Census Bureau Title 13 materials 43, 44
>
> Return Census Bureau Title 13 materials 44
>
> Destroy Census Bureau Title 13 materials 44

# Chapter 1 Introduction to the 2008 Census Dress Rehearsal Local Update of Census Addresses (LUCA) Program  {#chapter-1-introduction-to-the-2008-census-dress-rehearsal-local-update-of-census-addresses-luca-program .Style-Heading-1-+-Centered}

> The 2008 Census Dress Rehearsal Local Update of Census Addresses
> (LUCA) Program
>
> Background
>
> The Census Address List Improvement Act
>
> The Census Bureau's Master Address File (MAF)
>
> The Topologically Integrated Geographic Encoding and Referencing
> (TIGER^^)
>
> Database
>
> Census Bureau Responsibilities
>
> Participant Responsibilities
>
> Training and Technical Support
>
> Schedule
>
> The 2008 Census Dress Rehearsal LUCA User Guide Overview

###  {#section-1 .Style-Heading-3-+-Dark-Teal}

### The 2008 Census Dress Rehearsal Local Update of Census Addresses (LUCA) Program {#the-2008-census-dress-rehearsal-local-update-of-census-addresses-luca-program .Style-Heading-3-+-Dark-Teal}

> In preparation for the 2010 Census, the U.S. Census Bureau is
> conducting the 2008 Census Dress Rehearsal for selected jurisdictions.
> The Local Update of Census Addresses (LUCA) Program is an integral
> part of the census dress rehearsal activities and utilizes the
> expertise of tribal, state, and local governments to improve the
> accuracy and completeness of the address list used to take the census.

The Census Bureau invited the highest elected official of your
jurisdiction to participate in this program. Your jurisdiction selected
Option 1, Title 13 Full Address List Review in computer-readable format.
This option allows you to:

-   Review the Census Bureau's address list (Address List) for your
    jurisdiction.

-   Comment on any **city-style**[^1] address in a census block on the
    Address List using add, delete, correction, not in jurisdiction, or
    nonresidential action codes and identify (flag) group quarters[^2]
    addresses.

-   Challenge the count of addresses for any census block. (For census
    blocks containing all noncity-style[^3] addresses, you can challenge
    only the count of addresses for census blocks; you cannot comment on
    individual noncity-style addresses.)

> **Note**: *For census blocks with a mix of city-style and
> noncity-style addresses, you may comment on individual city-style
> addresses **or** challenge the count of addresses for the census
> block, but you may not do both.*

-   Identify any additions, deletions, or corrections to boundaries,
    roads, or other physical features on the Census Bureau paper maps or
    submit an updated version of the digital map file (shapefile)
    provided by the Census Bureau.

###  {#section-2 .Style-Heading-3-+-Dark-Teal}

### Background {#background .Style-Heading-3-+-Dark-Teal}

####  {#section-3 .Style-Heading-4-+-Left:--0.75\"}

#### The Census Address List Improvement Act {#the-census-address-list-improvement-act .Style-Heading-4-+-Left:--0.75\"}

> The Census Address List Improvement Act of 1994 (Public Law 103-430)
> strengthened the Census Bureau's partnership capabilities with tribal,
> state, and local governments by expanding the methods the Census
> Bureau could use to exchange address information. Designed to improve
> the accuracy of the Census Bureau's address list, the Act authorized
> the Census Bureau to provide individual addresses to officials of
> tribal, state, local governments who agreed to conditions of
> confidentiality. Census 2000 marked the first decennial census for
> which the Census Bureau could provide its address list for review to
> governments that signed the required confidentiality agreement.

####  {#section-4 .Style-Heading-4-+-Left:--0.75\"}

#### The Census Bureau's Master Address File (MAF) {#the-census-bureaus-master-address-file-maf .Style-Heading-4-+-Left:--0.75\"}

> In preparation for Census 2000, the Census Bureau created the Master
> Address File (MAF) by merging the 1990 Address Control File[^4] with
> the latest version of the U.S. Postal Service's (USPS) Delivery
> Sequence File[^5] (DSF). The MAF is a nationwide list of all address
> records used to support many of the Census Bureau's operations.
> Besides containing mailing addresses and ZIP Codes, a MAF record also
> contains geographic information about the location of addresses. In
> areas where there are no noncity-style (e.g., rural route or post
> office box numbers) addresses the MAF record may contain additional
> information such as a location description (*See Appendix K*).

#### The Topologically Integrated Geographic Encoding and Referencing (TIGER^^) Database {#the-topologically-integrated-geographic-encoding-and-referencing-tiger-database .Style-Heading-4-+-Left:--0.75\"}

> The MAF address records are linked to feature segments in the
> Topologically Integrated Geographic Encoding and Referencing
> (TIGER^^) database. The TIGER^^ database includes the geographic
> coordinates and names of all streets, water features, and other linear
> features, and boundaries for all jurisdictions and statistical areas
> (census tracts[^6], census blocks[^7], etc.) used to tabulate
> decennial census data. The TIGER^^ database also includes address
> ranges along streets that have city-style addresses and the hierarchy
> of census geographic area codes from the state level down to
> individual census blocks
> (http://www.census.gov/geo/www/geodiagram.html). By linking the MAF
> address records to the TIGER^^ database, the Census Bureau is able to
> identify street segments along which an individual address exists and
> determine the geographic code that applies to that address.
>
> The Census Bureau's Geography Division regularly updates the MAF and
> TIGER^^ from various sources. In addition to the USPS DSF, other
> sources of updates include updates from current household surveys,
> special censuses, and local sources.

### Census Bureau LUCA Responsibilities {#census-bureau-luca-responsibilities .Style-Heading-3-+-Dark-Teal}

> The Census Bureau's LUCA responsibilities include:

-   Providing training to LUCA Program participants.

```{=html}
<!-- -->
```
-   Providing the necessary materials to participants.

    -   Providing technical assistance.

    -   Processing the updates submitted by LUCA participants.

    -   Conducting a 100% address canvassing (field check) operation to
        validate the content of the Address List.

    -   Providing feedback materials to participants.

### LUCA Participant Responsibilities {#luca-participant-responsibilities .Style-Heading-3-+-Dark-Teal}

> Your responsibilities include:

-   Selecting staff to perform the LUCA Program review. *(The Census
    Bureau suggests that individuals in your jurisdiction involved in
    zoning enforcement not work on this program since this may create a
    conflict of interest.)*

-   Ensuring that everyone accessing the Address List signed the
    Confidentiality Agreement and returned it to the Census Bureau.
    *(See Appendix A for the terms of the LUCA Program Confidentiality
    Agreement and the Security Guidelines.)*

-   Ensuring the receipt of all required materials for the LUCA Program
    review.

-   Ensuring that everyone working on the LUCA Program understands the
    procedures for participating in the program and Census Bureau
    terminology.

-   Keeping Census Bureau addresses and maps showing housing unit and
    group quarters location (structure points[^8]) confidential and
    ensuring their use only for census purposes.

-   Preparing a strategy to conduct the review of LUCA materials.

-   Conducting the review of LUCA materials.

-   Returning the updated materials to the appropriate Census Bureau
    regional office.

-   Reviewing the Census Bureau's detailed feedback report.

-   Relaying to the Census Bureau any questions regarding the feedback
    report.

-   Returning or destroying all Census Bureau Title 13 materials after
    the program is completed.

### Training and Technical Support {#training-and-technical-support .Style-Heading-3-+-Dark-Teal}

> Training workshops conducted by Census Bureau staff will provide you
> with "hands-on" experience in using the 2008 Census Dress Rehearsal
> LUCA Program materials. Should you need additional information, please
> contact your Census Bureau Regional Office listed on the back cover.

### Schedule {#schedule .Style-Heading-3-+-Dark-Teal}

###  {#section-5 .Style-Heading-3-+-Dark-Teal}

> January 2006 LUCA advance notification letters and materials mailed to
> highest elected officials
>
> March -- May 2006 Census Bureau invited local governments to
> participate in the LUCA Program
>
> May 2006 Census Bureau conducted training workshops for participants
>
> June 2006 Census Bureau mailed LUCA materials to participants

June -- October 2006 Participants conduct LUCA review

> **October 2006 Participants return annotated materials to the Census
> Bureau's regional offices**

November -- December 2006 Census Bureau processes submissions and
updates

> April -- May 2007 Census Bureau conducts address canvassing (field
> check) operation

December 2007 -- January 2008 Participants review feedback materials

### The 2008 Census Dress Rehearsal LUCA User Guide Overview {#the-2008-census-dress-rehearsal-luca-user-guide-overview .Style-Heading-3-+-Dark-Teal}

> *The 2008 Census Dress Rehearsal LUCA User Guide* provides
> instructions and examples for your review of the LUCA Program
> materials.
>
> Before you begin your review, read **Chapter 2**. This chapter
> discusses:

-   The Census Bureau's definitions of housing units and group quarters.

-   An explanation of the acceptable types of housing units and group
    quarters to include in your review of the Address List.

-   An explanation of the types of addresses classified by the Census
    Bureau

-   Strategies for reviewing and updating the Address List.

-   Sources for local address information.

> **Chapter 3** explains how to protect computer-readable Census Bureau
> Title 13 address information, describes the computer-readable Address
> List and Address Count List, software requirements, and how to open
> the files.
>
> **Chapter 4** describes the information contained on a Census Bureau
> paper map. Census Bureau paper maps or a digital file (shapefile) are
> available to all LUCA participants to use as a reference with the
> Address List and Address Count List and to make any necessary updates
> or corrections to features and boundaries. This chapter includes:

-   How to read a Census Bureau paper map.

-   An example of a portion of a Census Bureau paper map.

-   Examples of the most common paper map updates.

-   A brief outline of the MAF/TIGER Accuracy Improvement Project
    (MTAIP).

-   How to submit shapefile feature information.

-   An overview of the Boundary and Annexation Survey (BAS) Program.

> *Appendix J* provides detailed information about the map legend. If
> you need to make updates or corrections to your jurisdiction
> boundaries, the Census Bureau's BAS program is explained in *Appendix
> C*. *Appendix D* contains the [Digital BAS Guidelines Supplement,
> Boundary and Annexation Survey (BAS) User's Guide]{.underline} for
> submitting boundary shapefiles. A blank Annexations and Detachments
> Form is included for boundary documentation in *Appendix E*.
>
> **Chapter 5** provides instructions for adding, correcting, and
> deleting addresses, identifying nonresidential addresses and addresses
> not in your jurisdiction using various action codes, and how to
> identify (flag) group quarters addresses.
>
> **Chapter 6** provides instructions for updating census block address
> counts on the Address Count List.
>
> **Chapter 7** explains how to submit your completed LUCA materials to
> the Census Bureau.
>
> **Chapter 8** provides instructions for returning or destroying all
> Title 13, U.S.C. address lists (both computer-readable and any paper
> copies) and maps (including copies) containing structure points after
> you have reviewed your feedback materials.
>
> **After you have reviewed your feedback materials, you must return or
> destroy all Title 13, U.S.C. materials. A Return/Destruction of Title
> 13, U.S.C. Materials form is included in *Appendix I*. Your primary
> LUCA liaison must sign and return this form to the Census Bureau after
> destroying your Title 13 materials or include the form with your
> returned Title 13 materials. All LUCA Program reviewers are required
> to sign and date this form at the completion of the LUCA Program.
> Should any liaison or reviewer leave before the completion of the LUCA
> Program, they are required to "sign-out" of the program by signing and
> dating this form. If any liaison or reviewer fails to sign and date
> this form, the current liaison can "sign-out" on their behalf.**
>
> If you need to add additional LUCA reviewers, *Appendix B* provides a
> blank Confidentiality Agreement Form. Be sure additional reviewers
> have read and understand the Confidentiality and Security Guidelines
> included in *Appendix A* before signing the Confidentiality Agreement
> Form and returning it to the Census Bureau.
>
> Should you need to update your Census Bureau contact person(s),
> *Appendix F* provides a Contact Update Information Form.
>
> *Appendix G* provides an inventory form to enclose with your returned
> materials. In addition, *Appendix H* provides a special disclosure
> statement notice that must be included with the return of the Census
> Bureau's Title 13 information.
>
> *Appendix K* contains examples of the most common abbreviations for
> physical location descriptions (BRICK HSE w/ATTACHED GARAGE) and
> street types (ST, TWP RTE, etc.) used on the Address List. In
> addition, *Appendix L* contains examples of unit designation
> identifiers (APT, BSMT, etc) used by the Census Bureau.
>
> A glossary of Census Bureau terms related to the LUCA Program is
> included. For additional Census Bureau terms and information, please
> visit the Census Bureau Web site at <http://www.census.gov/>**.**
>
> The Census Bureau's regional office addresses, telephone numbers, and
> E-mail addresses are listed on the back cover.

# Chapter 2 Before You Begin Your Review {#chapter-2-before-you-begin-your-review .Style-Heading-1-+-Centered}

> What is a Housing Unit?
>
> What are Group Quarters?
>
> Unacceptable Types of Housing Units and Group Quarters
>
> Census Bureau Addresses
>
> Strategies for Reviewing the Census Bureau's Address List
>
> Local Address Sources
>
> Chapter 2 provides some terms and concepts used by the Census Bureau
> and strategies for your LUCA review. Refer to the *Glossary* or visit
> the Census Bureau's Web site at
> [http://www.census.gov](http://www.census.gov/) for additional terms
> and definitions.

###  {#section-6 .Style-Heading-3-+-Dark-Teal}

### What is a Housing Unit? {#what-is-a-housing-unit .Style-Heading-3-+-Dark-Teal}

###   {#section-7 .Style-Heading-3-+-Dark-Teal}

> *A single-family house, townhouse, mobile home, trailer, vacant
> trailer park pad, apartment, group of rooms, or a single room occupied
> as a separate living quarters or, if vacant, intended for occupancy as
> a separate living quarters. A separate living quarters is one in which
> one or more occupants (or intended occupants, if vacant) live separate
> from any other individual(s) in the building and have direct access to
> the living quarters without going through another living quarters,
> such as from outside the building or through a common hall.*
>
> The following types of housing units are acceptable and should be
> included on the Address List:

-   Houses, including townhouses and condominiums.

-   Apartments.

-   Living quarters within an otherwise nonresidential structure. For
    example, an apartment within a church, school, or business.

-   Mobile homes or trailers occupied as separate living quarters, or if
    vacant, intended for occupancy as separate living quarters.

-   Any units under construction that will be habitable (closed to the
    elements with final roof, windows, and doors) on Census Day, April
    1, 2008.

### What are Group Quarters? {#what-are-group-quarters .Style-Heading-3-+-Dark-Teal}

> *A place where people live or stay that is normally owned or managed
> by an entity or organization providing housing and/or services for the
> residents. These services may include custodial or medical care, as
> well as other types of assistance, and residency is commonly
> restricted to those receiving those services. People living in group
> quarters are usually not related to each other.*
>
> The following types of group quarters are acceptable and should be
> included on the Address List:

-   Correctional facilities.

-   Juvenile facilities.

-   Nursing homes.

-   Hospitals with long-term care facilities.

-   College or university dormitories, fraternities, sororities.

-   Dormitories for workers.

-   Religious group quarters.

-   Shelters.

-   Group homes.

-   Any group quarters under construction that will be habitable (closed
    to the elements with final roof, windows, and doors) on Census Day,
    April 1, 2008.

> **Note:** Housing units and group quarters can exist within the same
> structure.

### Unacceptable Types of Housing Units and Group Quarters {#unacceptable-types-of-housing-units-and-group-quarters .Style-Heading-3-+-Dark-Teal}

> Exclude the following unacceptable types of housing units and group
> quarters addresses from the Address List:

-   Used as nonresidential storage facilities or as offices or
    businesses in which no one is living.

-   Condemned or scheduled for demolition.

-   Being converted or remodeled for nonresidential purposes.

-   Used solely for nonresidential storage.

-   Used solely as offices or businesses in which no one is living.

-   Under construction, but will **not** be habitable (closed to the
    elements with final roof, windows, and doors) on Census Day, April
    1, 2008.

-   Used solely for ceremonial purposes.

### Census Bureau Addresses  {#census-bureau-addresses .Style-Heading-3-+-Dark-Teal}

####  {#section-8 .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

#### Residential and Nonresidential Addresses {#residential-and-nonresidential-addresses .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> The Census Bureau divides all addresses into two *use types*,
> residential and nonresidential. Residential addresses are addresses of
> housing units and group quarters. Nonresidential addresses are
> addresses of a structure or unit within a structure that do not serve
> as a residence, such as commercial establishments, schools, government
> offices, and churches.
>
> Some structures can contain both residential and nonresidential units,
> even though they have a single address.

###  {#section-9 .Style-Style-Heading-3-+-Dark-Teal1-+-Right:---0.5\"}

#### Address Formats

#### 

####### City-style Address Format {#city-style-address-format .Style3}

> The majority of housing units and group quarters in the United States
> have a house number and street name address; for example, 212 Elm
> Street or 137 Clark Ct., Apt. 316. The Census Bureau refers to these
> as city-style addresses. Addresses for housing units in multi-unit
> structures, such as apartment buildings, should contain a unit
> designator, for example, Apt 101 or Ste D (*See Appendix L, Unit
> Designation Abbreviation Examples*). The Census Bureau and the U.S.
> Postal Service treat these designators as part of the housing unit
> address, and they are included in each affected census address record.
> Some city-style addresses, referred to as E-911 addresses, are used
> only to provide location for emergency services, such as police, fire,
> and rescue.

####### Noncity-Style Address Format {#noncity-style-address-format .Style3}

> The Census Bureau classifies addresses that do not include a house
> number and street name as noncity-style addresses. The majority of
> noncity-style addresses are located in the more sparsely settled areas
> of the United States; however, they may exist in small or medium sized
> towns as well. Frequently used noncity-style mailing addresses
> include:

-   General delivery.

-   Rural route and box number.

-   Highway contract route and box number.

-   Post Office box only delivery.

> Noncity-style addresses often do not follow any numeric sequence, and
> may not be associated with the name of the street or highway on which
> they are located. For this reason, the Census Bureau uses different
> methods to compile the list of addresses for inclusion into the
> Address List, such as location descriptions (BRICK HSE w/ATTACHED
> GARAGE), structure points (geographic coordinates), and geographic
> codes. Census Bureau maps may show structure points in selected areas,
> generally those with sparse settlement.

### Strategies for Reviewing the Census Bureau's Address List {#strategies-for-reviewing-the-census-bureaus-address-list .Style-Heading-3-+-Dark-Teal}

> You must decide for yourself how to conduct the LUCA Program review.
> Consider your available time, the information you have readily
> available, and the staff and computer resources you have. If resources
> are limited, the Census Bureau recommends focusing on areas where
> addresses are more likely to be missed or incorrect. For example:

-   Areas of new construction.

-   E-911 address conversion areas.

-   Areas that have changed from single-family homes to multi-family
    homes and vice versa.

-   Warehouses converted to residential lofts.

-   New mobile home parks or new scattered mobile homes.

-   Apartment buildings with irregular or missing numbering schemes for
    the individual units.

-   Recently added territory.

-   Addresses near jurisdictional boundaries.

### Local Address Sources {#local-address-sources .Style-Heading-3-+-Dark-Teal}

> There are many possible sources of local address information. Some of
> these sources may not match the Census Bureau's address list exactly,
> but they are a good indication of where change is taking place and can
> help you identify addresses that need to be added to the Address List.
> The following list provides suggestions for local address source
> materials:

-   New housing construction or building permits (include units that are
    under construction only if final roof, doors, and windows will be in
    place on Census Day, April 1, 2008).

-   E-911 address files.

-   Housing occupancy permits.

-   Planning or zoning records.

-   Local utility records.

-   Drivers' license files.

-   Annexation records.

-   Assessment or taxation files.

-   Voter registration files.

# Chapter 3 The LUCA Program's Computer-Readable Adress List and Address Count List {#chapter-3-the-luca-programs-computer-readable-adress-list-and-address-count-list .Style-Heading-1-+-Centered}

> Introduction
>
> Protecting Electronic Census Bureau Address Information
>
> The File Names
>
> The File Format
>
> Software Requirements
>
> Opening the Files

### Introduction {#introduction .Style-Heading-3-+-Dark-Teal}

###  {#section-11 .Style-Heading-3-+-Dark-Teal}

> The Address List and Address Count List files for your entity are
> included on your CD-ROM. This chapter discusses how you must protect
> the Census Bureau's computer-readable address information and explains
> the:

-   File names and formats.

-   Software requirements.

-   How to open the files.

### Protecting Census Bureau Address Information  {#protecting-census-bureau-address-information .Style-Heading-3-+-Dark-Teal}

> The most efficient method to review and match your local address list
> to the Address List is to copy the address file onto a computer hard
> drive or a network server in a useable format. You must first ensure
> the protection of the Census Bureau's Title 13 address information
> including your Census Bureau computer-readable address file, all
> address list paper copies, and maps (including copies) containing
> structure points. For detailed information see *Appendix A,
> Confidentiality and Security Guidelines*.
>
> The Census Bureau addresses must be accessible only to the LUCA
> Program liaison and reviewers who signed the Confidentiality
> Agreement. The automated data processing (ADP) system should restrict
> the read, write, delete, and execute functions applicable to the
> Census Bureau's addresses.
>
> The ADP system must use log-on routines that require a user-ID and
> password that conform to the following guidelines:

-   **Assign** a unique user-ID and password for each LUCA Program
    liaison and reviewer.

-   Passwords **must consist** of at least eight (8) characters:

```{=html}
<!-- -->
```
-   Use at least one (1) alphabet character.

-   Use either one number or one special character (\$,\*, &).

-   No more than six (6) identical, consecutive characters (AAAAAA) may
    appear in the password, and then only once.

```{=html}
<!-- -->
```
-   **Reject** passwords that are the same as the user-ID or used within
    the last 6 months.

-   **Encrypt** passwords.

-   **Disable** passwords after three bad attempts.

-   **Do not display** passwords on terminals or printers.

-   **Change** passwords every 90 days (more frequent change is
    optional) or immediately, if compromised.

-   On new accounts, **change the assigned** password to a unique
    password the first time users log on.

> The ADP system **must display** a warning log-on feature. Computer
> screens must display a warning that states:
>
> **\*\*WARNING\*WARNING\*WARNING\*\***
>
> **YOU HAVE ACCESSED A COMPUTER SYSTEM CONTAINING UNITED STATES
> GOVERNMENT INFORMATION. USE OF THIS COMPUTER WITHOUT AUTHORIZATION OR
> FOR PURPOSES FOR WHICH AUTHORIZATION HAS NOT BEEN EXTENDED IS A
> VIOLATION OF FEDERAL LAW AND CAN BE PUNISHED BY FINE OR IMPRISONMENT
> (Public Law 99-474). ALL USE MAY BE INTERCEPTED, MONITORED, RECORDED,
> COPIED, AUDITED, INSPECTED AND DISCLOSED TO AUTHORIZED LAW ENFORCEMENT
> OFFICIALS. REPORT SUSPECTED VIOLATIONS TO YOUR AGENCY SECURITY
> OFFICER. USE OF THIS SYSTEM INDICATES YOU CONSENT TO THIS WARNING. LOG
> OFF IMMEDIATELY IF YOU DO NOT AGREE TO THE CONDITIONS OF THIS
> WARNING.**
>
> **\*\*WARNING\*WARNING\*WARNING\*\***

-   If you place Census Bureau address information on a shared computer
    system, **construct electronic security profiles** to allow only the
    LUCA liaison and reviewers access to the Census Bureau's address
    information. **Test your security** to ensure that only the LUCA
    liaison and reviewers are permitted access to the Census Bureau's
    address information.

```{=html}
<!-- -->
```
-   **Encrypt** all Title 13 Census address information transmitted via
    FTP to the Census Bureau's data site with an appropriate product.

-   **Lock all rooms** containing computers and all associated media
    during non-work hours.

-   **Do not leave** computers with Census Bureau address information
    unattended during work hours. **Log-off** the computer or **lock**
    the room whenever you leave.

-   **Label** any computer diskettes, CD-ROMs, DVDs, tapes, cartridges
    or other computer storage media containing Census Bureau address
    information with the following:

> ***"This document contains information the release of which is
> prohibited by Title 13 U.S.C. and is for Bureau of the Census official
> use only."***

-   If backup is necessary, **do not send** the tapes, cartridges, or
    disks off-site. **Store** them in a secured area. **Do not mix,
    store, or back-up LUCA data with other data.**

```{=html}
<!-- -->
```
-   **Clear** magnetic media (tapes, disks, hard drives) containing
    Census Bureau address information before reuse. To clear magnetic
    media, overwrite all Title 13 data three times at a minimum using a
    commercial disk utility program or degauss using a commercial
    degausser.

-   **Program** any software you develop for displaying the Census
    Bureau addresses to label each affected page of a printout
    containing Census Bureau address information with the following:

> ***"This document contains information, the release of which is
> prohibited by Title 13 U.S.C. and is for Bureau of the Census official
> use only."***

### The File Names {#the-file-names .Style-Heading-3-+-Dark-Teal}

> The Address List (AL) file contains all of the addresses currently
> recorded by the Census Bureau for your jurisdiction. The Address Count
> List (ACL) file contains the address counts for each census block
> within your jurisdiction. The name of each of the files is:
>
> 1\. Address List -- XXyyyyyyyy.8AL
>
> 2\. Address Count List -- XXyyyyyyyy_08.ACL
>
> Where:
>
> XX = 2 character, alpha entity type (ST for State, CO for County, PL
> for Place, and MC for Minor Civil Division), and
>
> yyyyyyyy = variable length, numeric entity ID code.
>
> The numeric portion of the entity identification code is of variable
> length, depending on the type of entity:

-   State: 2 digits

-   County: 3 digits

-   Minor Civil Division (MCD): 3 digits

-   Census Place: 4 digits

> []{#__RefHeading___Toc137619573 .anchor}Figure 3.1: Entity
> Identification Codes

  ---------------- ------------------------------------------ --------------
  **Entity**       **Entity Identification Code**             **Total
                                                              Characters**

  State            ST (2 alpha) + (2 numeric)                 4

  County           CO (2 alpha) + State (2 numeric) + County  7
                   (3 numeric)                                

  Minor Civil      MC(2 alpha) + State (2 numeric) + County   10
  Division (MCD)   (3 numeric) + MCD (3 numeric)              

  Census Place     PL (2 alpha) + State (2 numeric) + Place   8
                   (4)                                        
  ---------------- ------------------------------------------ --------------

> An example of an Address List 4-character state file name is ST36.8AL
> where "ST" is state and "36" is the state code for New York. An
> example of a 7-character county file name for Erie County, New York is
> CO36029.8AL, where "ST" is state, "36" is the state code for New York,
> and "029" is the county code for Erie County.
>
> The file name for a Minor Civil Division is 10-characters while the
> file name for a Census place is 8-characters. For example, the Address
> List file name for "My Township", Indiana County, Pennsylvania is
> MC42063985.8AL where:

-   "MC" is minor civil division.

-   "42" is the state code for Pennsylvania.

-   "063" is the county code for Indiana County.

-   "985", the minor civil division code for My Township.

> An example of the Address List file name for the place "Lake Zurich",
> Illinois, is PL173115.8AL, where "PL" is place, "17", the state code
> for Illinois, and "3115" is the Census place code for Lake Zurich.
>
> One example of an Address Count List 8-character file name for the
> place "Mitchell", Wyoming, is PL564578_08.ACL, where "PL" is place,
> "56" is the state code for Wyoming, and "4578" is the Census place
> code for Mitchell.

### The File Format {#the-file-format .Style-Heading-3-+-Dark-Teal}

> All of the files are formatted as pipe-delimited ASCII text files.

-   Each address record has a maximum length of 314 characters and
    contains 24 fields of information. The length for each record may
    vary. See Figure 3.2 for the Address List file record layout.

-   Each block record is at least 56 characters in length and contains
    nine (9) fields of information. The character length of each record
    may vary. See Figure 3.3 for the Address Count List file record
    layout.

#### Example -- Computer-Readable Address List File Record Layout

+--------+--------------------+----------------------------------------+
| >      | **Field Name**     | **Description/Notes**                  |
|  **Max |                    |                                        |
| imum** |                    |                                        |
| >      |                    |                                        |
| > *    |                    |                                        |
| *Chara |                    |                                        |
| cter** |                    |                                        |
| >      |                    |                                        |
| > **Le |                    |                                        |
| ngth** |                    |                                        |
+--------+--------------------+----------------------------------------+
| > 11   | Entity ID Code     | Unique number assigned by the Census   |
|        |                    | Bureau to each entity                  |
+--------+--------------------+----------------------------------------+
| > 7    | Line Number        | Unique number for each address record  |
|        |                    | in the file                            |
+--------+--------------------+----------------------------------------+
| > 13   | MAFID              | Unique number assigned to each MAF     |
|        |                    | address                                |
+--------+--------------------+----------------------------------------+
| > 2    | Action Code        | Valid codes: A, C, D, J, N, entered by |
|        |                    | participant                            |
+--------+--------------------+----------------------------------------+
| > 2    | State Code         | 2-digit Current State Code             |
+--------+--------------------+----------------------------------------+
| > 3    | County Code        | 3-digit Current County Code            |
+--------+--------------------+----------------------------------------+
| > 7    | Census Tract       | 4-digit Census Tract Number, plus      |
|        | Number             | 2-digit number suffix, if applicable,  |
|        |                    | includes a period for suffixed tracts  |
+--------+--------------------+----------------------------------------+
| > 5    | Census Block       | 4-digit Current Census Block Number,   |
|        | Number             | plus 1-digit alpha character suffix if |
|        |                    | applicable                             |
+--------+--------------------+----------------------------------------+
| > 1    | Group Quarters     | Display a 'Y' if the unit is a group   |
|        | Flag               | quarters                               |
+--------+--------------------+----------------------------------------+
| > 23   | House Number       | Housing unit's or group quarter's      |
|        |                    | assigned house number                  |
+--------+--------------------+----------------------------------------+
| > 2    | Street Name Prefix | e.g., N, W, SE                         |
|        | Direction          |                                        |
+--------+--------------------+----------------------------------------+
| > 4    | Street Name Prefix | e.g., HWY, RT, US                      |
|        | Type               |                                        |
+--------+--------------------+----------------------------------------+
| > 40   | Street Name        | Full street or road name               |
+--------+--------------------+----------------------------------------+
| > 4    | Street Name Suffix | e.g., ST, CT, AVE, DR                  |
|        | Type               |                                        |
+--------+--------------------+----------------------------------------+
| > 2    | Street Name Suffix | e.g., N,W, SE                          |
|        | Direction          |                                        |
+--------+--------------------+----------------------------------------+
| > 3    | Street Name Street | e.g. EXT, ALT, BUS                     |
|        | Extension          |                                        |
+--------+--------------------+----------------------------------------+
| > 100  | Location           | Description of living quarter (Red     |
|        | Description or GQ  | Rancher w/White Shutters) or name of   |
|        | Name               | group quarter (Dobbs Hall-University   |
|        |                    | of Dobbs)                              |
+--------+--------------------+----------------------------------------+
| > 27   | Apartment/Unit     | Within structure descriptor or         |
|        | Number             | identifier, such as APT 5 or 1^st^ FL  |
|        |                    | FRNT                                   |
+--------+--------------------+----------------------------------------+
| > 5    | City-Style Mailing | 5-digit ZIP Code for city-style        |
|        | ZIP Code           | mailing addresses                      |
+--------+--------------------+----------------------------------------+
| > 24   | Noncity-Style Mail | Rural Route and Box Number, Post       |
|        | Delivery Address   | Office Box Number, etc.                |
|        | (RR#, HCR#, or PO  |                                        |
|        | BOX#)              |                                        |
+--------+--------------------+----------------------------------------+
| > 5    | Noncity-Style      | 5-digit ZIP Code for the noncity-style |
|        | Mailing ZIP Code   | mailing address                        |
+--------+--------------------+----------------------------------------+
| > 5    | Structure Point    | 4-digit number plus 1-digit alpha      |
|        |                    | assigned by the Census Bureau to       |
|        |                    | structures in areas that contain       |
|        |                    | predominately noncity-style addresses  |
|        |                    | (RR, PO Box #, General Delivery, etc.) |
+--------+--------------------+----------------------------------------+
| > 9    | Structure Latitude | The latitude coordinate in degrees,    |
|        |                    | with 6 implied decimals                |
+--------+--------------------+----------------------------------------+
| > 10   | Structure          | The longitude coordinate in degrees,   |
|        | Longitude          | with 6 implied decimals                |
+--------+--------------------+----------------------------------------+

[]{#__RefHeading___Toc137619574 .anchor}Figure 3.2: Computer-Readable
Address List File Record Layout

#### Example -- Address Count List File Record Layout

> []{#__RefHeading___Toc137619575 .anchor}Figure 3.3: Address Count List
> File Record Layout

+-------+------------------+------------------------------------------+
| *     | **Field Name**   | **Description/Notes**                    |
| *Maxi |                  |                                          |
| mum** |                  |                                          |
|       |                  |                                          |
| *     |                  |                                          |
| *Char |                  |                                          |
| acter |                  |                                          |
| Len   |                  |                                          |
| gth** |                  |                                          |
+-------+------------------+------------------------------------------+
| 11    | Entity ID Code   | Unique number assigned by the Census     |
|       |                  | Bureau to each entity                    |
+-------+------------------+------------------------------------------+
| 2     | State Code       | 2-digit Current State Code               |
+-------+------------------+------------------------------------------+
| 3     | County Code      | 3-digit Current County Code              |
+-------+------------------+------------------------------------------+
| 7     | Census Tract and | 4-digit Census Tract Number, plus        |
|       | Suffix           | 2-digit number suffix, if applicable,    |
|       |                  | includes a period for suffixed tracts.   |
+-------+------------------+------------------------------------------+
| 5     | Census Block and | 4-digit Current Census Block Number,     |
|       | Suffix           | plus 1-digit alpha character suffix if   |
|       |                  | applicable                               |
+-------+------------------+------------------------------------------+
| 7     | Census Count of  | Census Bureau's most recent count of     |
|       | Housing Unit     | housing unit addresses                   |
|       | Addresses        |                                          |
+-------+------------------+------------------------------------------+
| 7     | Local Count of   | Most recent count of housing unit        |
|       | Housing Unit     | addresses recorded by participant        |
|       | Addresses        |                                          |
+-------+------------------+------------------------------------------+
| 7     | Census Count of  | Census Bureau's most recent count of     |
|       | Group Quarters   | group quarters addresses                 |
|       | Addresses        |                                          |
+-------+------------------+------------------------------------------+
| 7     | Local Count of   | Most recent count of group quarters      |
|       | Group Quarters   | addresses recorded by participant        |
|       | Addresses        |                                          |
+-------+------------------+------------------------------------------+

#### 

[]{#__RefHeading___Toc137619576 .anchor}Figure 3.3.1: Address Count List
File "Total Row" Layout

+-------+------------------+------------------------------------------+
| *     | **Field Name**   | **Description/Notes**                    |
| *Maxi |                  |                                          |
| mum** |                  |                                          |
|       |                  |                                          |
| *     |                  |                                          |
| *Char |                  |                                          |
| acter |                  |                                          |
| Len   |                  |                                          |
| gth** |                  |                                          |
+-------+------------------+------------------------------------------+
| 7     | Census Tract and | The word "Total" appears in this column  |
|       | Suffix           |                                          |
+-------+------------------+------------------------------------------+
| 5     | Census Block and | Total number of Census Blocks on the     |
|       | Suffix           | Address Count List                       |
+-------+------------------+------------------------------------------+
| 7     | Census Count of  | Total number of Census Bureau Housing    |
|       | Housing Unit     | Unit Addresses on the Address Count List |
|       | Addresses        |                                          |
+-------+------------------+------------------------------------------+
| 7     | Local Count of   | Total number of Housing Unit Address     |
|       | Housing Unit     | challenges recorded by participant       |
|       | Addresses        |                                          |
+-------+------------------+------------------------------------------+
| 7     | Census Count of  | Total number of Census Bureau Group      |
|       | Group Quarters   | Quarters Addresses on the Address Count  |
|       | Addresses        | List                                     |
+-------+------------------+------------------------------------------+
| 7     | Local Count of   | Total number of Group Quarters Address   |
|       | Group Quarters   | challenges recorded by participant       |
|       | Addresses        |                                          |
+-------+------------------+------------------------------------------+

### Software Requirements {#software-requirements .Style-Heading-3-+-Dark-Teal}

> Many commercial spreadsheet and database programs[^9] can open the
> LUCA files. Use spreadsheet programs such as Microsoft Excel or Lotus
> 123 to open, view, and edit small files. For larger files, use a
> database program such as Corel Paradox, QuattroPro, Microsoft Access,
> or dBase.
>
> **Note:** Some computer programs that can open and view pipe-delimited
> text files
>
> CANNOT save an edited file in the correct format. Make sure your
> program
>
> has the ability to save or export a file with pipe-delimited fields.

### Opening the Files {#opening-the-files .Style-Heading-3-+-Dark-Teal}

> Refer to the Readme (Readme1st.txt) file for instructions on opening
> the encrypted Address List.

-   The Census Bureau recommends that you make a copy of each of the
    files and place them on the hard drive of a computer that is
    password protected. This will preserve the original files should you
    need to look at an original record or require another original copy
    of the file.

> **Note:** The files you receive are pipe-delimited ASCII text files,
> meaning they can be viewed and read as letters and numbers with a text
> editor. All spreadsheet and database programs can read and understand
> these text files.

-   Some spreadsheet and database software packages will not recognize
    text files unless the file name includes the .TXT file name
    extension. If necessary, change the file name extension to .TXT. For
    instance, the Address List file name for Lake Zurich, Illinois,
    PL173115.8AL, must be changed to PL173115.**txt** and the Address
    List Count file, PL173115_08.ACL, must be changed to
    PL173115_08.**txt**.

```{=html}
<!-- -->
```
-   To help keep your work organized, create a new directory or new
    folder on your hard drive. Copy the files from the CD-ROM into that
    directory or folder.

-   When you open the text files with your application, some
    spreadsheets and databases will prompt you to supply some
    information about the file. Be prepared to tell the application
    program the following:

```{=html}
<!-- -->
```
-   Fields are **delimited.**

-   Delimiter is **pipe.**

-   Text qualifier is **none.**

-   All field types are **text.**

```{=html}
<!-- -->
```
-   Define all field types as "**text**" including numeric fields such
    as census tract number, census block number, ZIP Code, and so forth.

-   Follow the record layout to name and define the sizes of your
    fields.

#### Example -- Pipe-delimited Address List File -- City-style Address {#example-pipe-delimited-address-list-file-city-style-address .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

####  {#section-13 .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> The following is an example of how the information may appear in the
> Address List file before importing the file using your software
> program. The example is a city-style address, 10 Main Street, Mytown,
> PA 15888.

PL429059\|107\|1234567898765\| \|42\|134\|7654.01\|2345\| \|10\| \|
\|Main\|St\| \| \| \| \|15888\| \| \| \|4063010\|

7922646

> Figure 3.4 displays the data in the appropriate fields.
>
> []{#__RefHeading___Toc137619577 .anchor}Figure 3.4: Pipe-delimited
> LUCA Program Address List File -- City-style Address

+---------+---------------------------------------+--------------------+
| >       | **Field Name**                        | **Example**        |
| **Field |                                       |                    |
| > N     |                                       |                    |
| umber** |                                       |                    |
+---------+---------------------------------------+--------------------+
| > 1     | Entity ID Code                        | PL429059           |
+---------+---------------------------------------+--------------------+
| > 2     | Line Number                           | 107                |
+---------+---------------------------------------+--------------------+
| > 3     | MAFID                                 | 1234567898765      |
+---------+---------------------------------------+--------------------+
| > 4     | Action Code                           | Blank              |
+---------+---------------------------------------+--------------------+
| > 5     | State Code                            | 42                 |
+---------+---------------------------------------+--------------------+
| > 6     | County Code                           | 134                |
+---------+---------------------------------------+--------------------+
| > 7     | Census Tract Number                   | 7654.01            |
+---------+---------------------------------------+--------------------+
| > 8     | Census Block Number                   | 2345               |
+---------+---------------------------------------+--------------------+
| > 9     | Group Quarters Flag                   | Blank              |
+---------+---------------------------------------+--------------------+
| > 10    | House Number                          | 10                 |
+---------+---------------------------------------+--------------------+
| > 11    | Street Name Prefix Direction          | Blank              |
+---------+---------------------------------------+--------------------+
| > 12    | Street Name Prefix Type               | Blank              |
+---------+---------------------------------------+--------------------+
| > 13    | Street Name                           | Main               |
+---------+---------------------------------------+--------------------+
| > 14    | Street Name Suffix Type               | St                 |
+---------+---------------------------------------+--------------------+
| > 15    | Street Name Suffix Direction          | Blank              |
+---------+---------------------------------------+--------------------+
| > 16    | Street Name Street Extension          | Blank              |
+---------+---------------------------------------+--------------------+
| > 17    | Location Description or GQ Name       | Blank              |
+---------+---------------------------------------+--------------------+
| > 18    | Apartment/Unit Number                 | Blank              |
+---------+---------------------------------------+--------------------+
| > 19    | City-Style Mailing ZIP Code           | 15888              |
+---------+---------------------------------------+--------------------+
| > 20    | Noncity-Style Mail Delivery Address   | Blank              |
|         | (RR#, HCR#, or PO BOX#)               |                    |
+---------+---------------------------------------+--------------------+
| > 21    | Noncity-Style Mailing ZIP Code        | Blank              |
+---------+---------------------------------------+--------------------+
| > 22    | Structure Point                       | Blank              |
+---------+---------------------------------------+--------------------+
| > 23    | Structure Latitude                    | 4063010            |
+---------+---------------------------------------+--------------------+
| > 24    | Structure Longitude                   | 7922646            |
+---------+---------------------------------------+--------------------+

#### Example -- Pipe-delimited Address List File -- Noncity-style Address {#example-pipe-delimited-address-list-file-noncity-style-address .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

####  {#section-14 .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> The following is an example of how the information may appear in the
> Address List file for a noncity-style address: Box 223, Scott Level
> Road, Myhome, Ohio 45555. Note that the information includes a
> description in the location description field --
>
> 2-STORY BRICK W/ATTACHED GARAGE ON LEFT.

PL394868\|678\|2345678912345\| \|39\|074\|2345\|5432\| \| \| \| \|Scott
Level\|Road\| \| \|2-story brick w/ATTACHED GARAGE ON LEFT\| \| \|Box
223\|45555\|9\|4005716\|8461787

> Figure 3.5 displays the data in the appropriate fields.
>
> []{#__RefHeading___Toc137619578 .anchor}Figure 3.5: Pipe-delimited
> LUCA Program Address List File -- Noncity-style Address

####  {#section-15 .Style-Heading-4-+-Left:--0.75\"-Right:---0.5\"}

+---------+-----------------------------+------------------------------+
| >       | **Field Name**              | **Example**                  |
| **Field |                             |                              |
| > N     |                             |                              |
| umber** |                             |                              |
+---------+-----------------------------+------------------------------+
| > 1     | Entity ID Code              | PL394868                     |
+---------+-----------------------------+------------------------------+
| > 2     | Line Number                 | 678                          |
+---------+-----------------------------+------------------------------+
| > 3     | MAFID                       | 2345678912345                |
+---------+-----------------------------+------------------------------+
| > 4     | Action Code                 | Blank                        |
+---------+-----------------------------+------------------------------+
| > 5     | State Code                  | 39                           |
+---------+-----------------------------+------------------------------+
| > 6     | County Code                 | 074                          |
+---------+-----------------------------+------------------------------+
| > 7     | Census Tract Number         | 2345                         |
+---------+-----------------------------+------------------------------+
| > 8     | Census Block Number         | 5432                         |
+---------+-----------------------------+------------------------------+
| > 9     | Group Quarters Flag         | Blank                        |
+---------+-----------------------------+------------------------------+
| > 10    | House Number                | Blank                        |
+---------+-----------------------------+------------------------------+
| > 11    | Street Name Prefix          | Blank                        |
|         | Direction                   |                              |
+---------+-----------------------------+------------------------------+
| > 12    | Street Name Prefix Type     | Blank                        |
+---------+-----------------------------+------------------------------+
| > 13    | Street Name                 | Scott Level                  |
+---------+-----------------------------+------------------------------+
| > 14    | Street Name Suffix Type     | Road                         |
+---------+-----------------------------+------------------------------+
| > 15    | Street Name Suffix          | Blank                        |
|         | Direction                   |                              |
+---------+-----------------------------+------------------------------+
| > 16    | Street Name Street          | Blank                        |
|         | Extension                   |                              |
+---------+-----------------------------+------------------------------+
| > 17    | Location Description or GQ  | 2-story brick w/ATTACHED     |
|         | Name                        | GARAGE ON LEFT               |
+---------+-----------------------------+------------------------------+
| > 18    | Apartment/Unit Number       | Blank                        |
+---------+-----------------------------+------------------------------+
| > 19    | City-Style Mailing ZIP Code | Blank                        |
+---------+-----------------------------+------------------------------+
| > 20    | Noncity-Style Mail Delivery | Box 223                      |
|         | Address (RR#, HCR#, or PO   |                              |
|         | BOX#)                       |                              |
+---------+-----------------------------+------------------------------+
| > 21    | Noncity-Style Mailing ZIP   | 45555                        |
|         | Code                        |                              |
+---------+-----------------------------+------------------------------+
| > 22    | Structure Point             | 9                            |
+---------+-----------------------------+------------------------------+
| > 23    | Structure Latitude          | 4005716                      |
+---------+-----------------------------+------------------------------+
| > 24    | Structure Longitude         | 8461787                      |
+---------+-----------------------------+------------------------------+

#### Example -- Pipe-delimited Address Count List File {#example-pipe-delimited-address-count-list-file .Style-Heading-4-+-Left:--0.75\"-Right:---0.5\"}

> Figure 3.6 is an example of how the information may appear in the
> Address Count List file before importing the file using your software
> program. This example is for a place, entity ID code PL162233, in the
> state of Idaho, state code 16, place code 2233. There are 765
> addresses and three (3) group quarters addresses in Census Tract
> 6789.01, Census Block 5432.
>
> PL162233\|16\|089\|6789.01\|5432\|765\| \|3\|
>
> []{#__RefHeading___Toc137619579 .anchor}Figure 3.6: Pipe-delimited
> Address Count List File

  ---------- -------------------------------------- ----------------------
  **Field    **Field Name**                         **Example**
  Number**                                          

  1          Entity ID Code                         PL162233

  2          State Code                             16

  3          County Code                            089

  4          Census Tract and Suffix                6789.01

  5          Census Block and Suffix                5432

  6          Census Count of Housing Unit Addresses 765

  7          Local Count of Housing Unit Addresses  Blank

  8          Census Count of Group Quarters         3
             Addresses                              

  9          Local Count of Group Quarters          Blank
             Addresses                              
  ---------- -------------------------------------- ----------------------

#### 

####  

# Chapter 4 The Census Bureau Maps {#chapter-4-the-census-bureau-maps .Style-Heading-1-+-Centered}

> Introduction
>
> Reading a Census Bureau Paper Map
>
> Examples
>
> Map Example 1: Adding a New Street and Associated Address Ranges
>
> Map Example 2: Correcting a Street Name
>
> Map Example 3: Moving a Street
>
> Map Example 4: Deleting a Street
>
> The MAF/TIGER Accuracy Improvement Project: Digital Update of the
> TIGER^^ Database
>
> Shapefiles
>
> Submitting Shapefile Feature Information
>
> Data Dictionary and Metadata
>
> Digital File Submission
>
> Boundary and Annexation Survey (BAS)

### 

### Introduction

### 

> The Census Bureau provides you with one set of paper maps or a digital
> file (shapefile) to use in conjunction with the Address List and
> Address Count List. If you requested paper maps, you receive a Map
> Sheet to Block Number Relationship List that identifies the map
> sheet(s) on which each census block is located. You may use the paper
> maps or shapefile to submit any needed updates and/or corrections to
> your jurisdiction's features and boundaries. The Boundary and
> Annexation Survey (BAS) section of this chapter provides an overview
> of the BAS program. If you need to make changes or corrections to your
> jurisdiction's boundaries, refer to Appendixes C and D for
> instructions.
>
> This chapter also provides an overview of the Census Bureau's
> MAF/TIGER Accuracy Improvement Project (MTAIP) undertaken by the
> Census Bureau to update and improve the accuracy of the TIGER^^
> database.
>
> The map updates you provide will allow the Census Bureau to update the
> TIGER^^ database so that all subsequent map and address list products
> reflect these changes.
>
> **Note**: Census Bureau maps that show structure points in selected
> areas (generally those with sparse settlement) are Title 13, U.S.C.
> confidential material.

### Reading a Census Bureau Paper Map

> The Census Bureau paper map shows some of the same information found
> on a typical road map, such as streets and roads, water features, and
> legal boundaries. However, the Census Bureau map displays this
> information using symbols unique to the Census Bureau. See *Appendix
> J* for a detailed explanation of the map legend. Figure 4.1 provides a
> sample of a Census Bureau map. The maps display the following
> information:

-   The area inside your jurisdiction is colored white.

-   The area outside of your entity is shaded.

-   Boundaries.

-   Streets/roads and their names.

-   Water features and their names, if any.

-   Other features, including their name, if applicable.

-   Jurisdiction codes and names for your jurisdiction and the adjacent
    area.

-   Census blocks.

-   Census tracts.

-   Fishhooks.

-   Structure points and structure point numbers.

-   All map sheets contain a legend that display the symbols used on the
    maps (*See Appendix J*)

> []{#__RefHeading___Toc137619580 .anchor}Figure 4.1: Sample of a Census
> Bureau Paper Map

![](media/image4.png){width="1.2708661417322835in"
height="0.2917322834645669in"}![](media/image3.png){width="4.869291338582677in"
height="4.15in"}

### 

> The following examples display the most common updates you can make to
> the Census Bureau maps.

### Examples

#####  {#section-21 .Style-Heading-5-+-11-pt-Not-Bold}

##### Map Example 1: Adding a New Street and Associated Address Ranges  {#map-example-1-adding-a-new-street-and-associated-address-ranges .Style-Heading-5-+-11-pt-Not-Bold}

> During your review, you may find addresses missing from the Address
> List that are on streets that are partially or entirely missing from
> the maps.
>
> For example, Spring Street is a new street with newly constructed
> housing units in census tract **9704** and census block **1017**. The
> addresses are missing from the Address List and the street is missing
> from the map.

[]{#__RefHeading___Toc137619581 .anchor}Figure 4.2: Adding a New Street
and Associated Address Ranges

> ![](media/image5.png){width="3.749212598425197in"
> height="3.604724409448819in"}
>
> Using a **red** pencil, draw the location of Spring Street on the map
> and label it **Spring St**.

-   Print the address range[^10] for each side of Spring St.

-   Print the address breaks[^11] where the new street intersects 4^th^
    Street NE.

-   Add the missing addresses to the Address List, ensuring that the
    street names match between the Address List and the map.

####  {#section-22 .Style-Heading-4-+-Left:--0.75\"}

####  {#section-23 .Style-Heading-4-+-Left:--0.75\"}

####  {#section-24 .Style-Heading-4-+-Left:--0.75\"}

##### Map Example 2: Correcting a Street Name {#map-example-2-correcting-a-street-name .Style-Heading-5-+-11-pt-Not-Bold}

> The Address List and map show **MILTON *HOSE* DR** instead of the
> correct name, **MILTON *HOUSE* DR**.
>
> []{#__RefHeading___Toc137619582 .anchor}Figure 4.3: Correcting a
> Street Name

-   ![](media/image6.png){width="3.208267716535433in"
    height="3.4791338582677165in"}Using a **red** pencil, cross out
    **HOSE** and print **HOUSE** above it.

-   Use double hatch marks to show the extent of the name change on the
    maps, if applicable.

-   Provide, if applicable, any alternate names that may exist for a
    street (such as Co Rd 9) by printing this name in parentheses on the
    map.

-   Make any corrections to the Address List, as needed, so that the
    maps match the Address List.

##### Map Example 3: Moving a Street {#map-example-3-moving-a-street .Style-Heading-5-+-11-pt-Not-Bold}

[]{#__RefHeading___Toc137619583 .anchor}Figure 4.4: Moving a Street

![](media/image7.png){width="3.3751968503937007in"
height="3.601574803149606in"}The Census Bureau map shows **2^nd^ Ct NW**
located in census block **5032**. Actually, **2^nd^ Ct NW** is located
in census block **5035**.

-   Using a **red** pencil, circle the feature in its current location

-   Redraw the feature and print the feature name in the correct census
    block

-   Draw an arrow to the correct location of the moved street

-   Print any necessary address ranges and address breaks along the
    street as shown in Figure 4.4.

-   Make corrections to the Address List, as needed, so that the Address
    List matches the map.

##### Map Example 4: Deleting a Street  {#map-example-4-deleting-a-street .Style-Heading-5-+-11-pt-Not-Bold}

> []{#__RefHeading___Toc137619584 .anchor}Figure 4.5: Deleting a Street
>
> ![](media/image8.png){width="3.138888888888889in"
> height="2.8069444444444445in"}All of the housing units along a portion
> of **9^th^ Avenue NE** in census block **1018** have been demolished
> and this section of the street no longer exists.

-   Using a **red** pencil, "**X**" out the section of **9^th^ Avenue
    NE** that no longer exists. Use double hatch marks to define the
    extent of the deleted segment when deleting only part of the street.
    When deleting an entire street, "**X**" out the street and put a
    **red** line through its name.

-   Correct all affected addresses on the Address List so that the maps
    match the list.

### 

### The MAF/TIGER Accuracy Improvement Project: Digital Update of the TIGER^^ Database

> In 2002, the Census Bureau initiated the MAF/TIGER Accuracy
> Improvement Project (MTAIP) as part of the MAF/TIGER Enhancements
> Program (MTEP). This project acquired geographic information system
> (GIS) files, aerial photography, and GPS data from various sources
> nationwide to update the TIGER^^ database. One of the primary goals
> of the project was to develop a highly accurate geographic database of
> the United States. The Census Bureau focused on improving the accuracy
> of street feature coordinates to provide base information suitable for
> use with GPS-equipped hand-held devices that would facilitate the
> gathering of accurate location and census information for all living
> quarters and workplaces.
>
> If your jurisdiction has been updated through the MTAIP process,
> carefully review the features and boundaries and make corrections
> where necessary. Pay special attention to the shape of the overall
> boundary because boundary segments may have been realigned based on
> changes to underlying roads or water features. Boundary segments that
> do not follow physical features (i.e., boundary lines through space)
> were adjusted relative to the surrounding physical features. Some
> water and road features shown as a single line may now be shown as two
> lines representing shorelines where you will need to determine the
> correct alignment of the boundary.

### Shapefiles

> The shapefiles, created from the Census Bureau's Topographically
> Integrated Geographic Encoding and Referencing System (TIGER^^),
> allows participants to submit map feature updates electronically.
> Shapefiles require the use GIS software. All shapefiles provided by
> the Census Bureau are in Environmental Systems Research Institute
> (ESRI) shapefile format. Participants that submit shapefiles with
> feature updates must follow Census Bureau requirements.
>
> In order to maintain topology, the Census Bureau has provided an "all
> lines" shapefile layer. In addition to the all lines layer, the Census
> Bureau has provided shapefile layers for legal and statistical
> boundaries that may be edited by the user. For more details on the
> contents of the shapefiles, view the readme.txt file that is included
> in the CD containing the shapefiles.

### 

### Submitting Shapefile Feature Information

> In order to submit digital feature information, you must have a GIS
> capable of importing ESRI shapefiles, editing the features, and
> exporting layers back into ESRI shapefile format.

.

#### The Census Bureau's Shapefile Coordinate System and Projection Information {#the-census-bureaus-shapefile-coordinate-system-and-projection-information .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> All shapefiles provided by the Census Bureau are in the following
> unprojected
>
> geographic based coordinate system:

-   GCS_NAD83

-   Angular Unit: Degree (0.017453292519943299)

-   Prime Meridian: Greenwich (0.000000000000000000)

-   Datum: D_North_American_1983

-   Spheroid: GRS_1980

-   Semi-major Axis: 6378137.000000000000000000

-   Semi-minor Axis: 6356752.314140356100000000

-   Inverse Flattening: 298.257222101000020000

> Please feel free to project these files into your local coordinate
> system/projection.

#### General File Setup Guidelines {#general-file-setup-guidelines .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> Upon receipt of your shapefile, please follow the setup guidelines
> listed below before beginning actual updates:

-   Open the CD and enclosed zip file to ensure it contains the
    shapefile for your entity.

-   Copy and decompress the shapefile to a directory on your server or
    hard drive.

-   Open the shapefile in a GIS.

> **Note**: The use of brand names does not represent an endorsement of
> a company or its products by the U.S. government. Due to the wide use
> of ESRI products by our partners in the GIS community, and the
> ubiquitous use of the shapefile format as a medium for GIS data
> exchange, the Census Bureau is providing this data in shapefile
> format. You should not encounter any problems when importing these
> shapefiles into your local GIS software. If you are using GIS software
> that does not contain a shapefile translator, please contact the
> Census Bureau at 301-763-1099 for further instructions.

#### Changing Our Coordinate System to Match Yours {#changing-our-coordinate-system-to-match-yours .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> Our files are in GCS NAD83 format. The spatial referencing information
> is also stored in each shapefile\'s \*.PRJ file. Most GIS software
> packages contain projection wizards, or something similar, allowing
> the user to transform file coordinate systems and projections. For
> example, if your office uses ArcView to update files, please activate
> and utilize ArcView's "Projection Utility Wizard" extension. If using
> ArcGIS, please use its "Projection Utilities" in ArcToolbox. TIGER^^
> extract shapefiles contain defined projection information in the
> \*.PRJ file. Both ArcView and ArcGIS access the \*.PRJ file for
> projection information; therefore, there is no need for you to define
> these parameters before changing a file's coordinate system.
>
> In addition, if your files are in a datum other than NAD83, you must
> geographically transform our files to match your datum. Most GIS
> software has tools for performing geographic transformations on files.
> However, if you encounter problems transforming our files, please
> contact the Census Bureau at
>
> 301-763-1099 for assistance.

#### Feature Information {#feature-information .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> The Census Bureau will collect feature changes designated by the
> participant. Please note that all feature-related update processing
> occurs at a different location and time within the Census Bureau.
>
> If you have reviewed your features using our line feature network and
> have determined that the Census Bureau needs to add, remove, or rename
> features in a given area, you may submit your modifications in a
> separate layer. To move or correct a feature, first delete the feature
> then add the correction.
>
> **Note**: In the future, large numbers of feature changes will be made
> through a program called the Automated Feature and Attribute Update
> System (AFAUS). AFAUS will have the ability to add new road features,
> names, and address ranges to the MAF/TIGER database directly from
> local GIS files (we cannot process scanned maps or cadastral boundary
> files). The files must represent road centerlines (and eventually
> other feature types). The update process will be able to match local
> features to the MAF/TIGER database and update it with new and revised
> information. The Census Bureau will evaluate local files provided. The
> AFAUS is scheduled to begin production in 2007.
>
> Please use the appropriate update code located in the coding scheme as
> shown in Figure 4.6 to identify the type of feature modification
> needed for submission.
>
> If any issues arise with the feature layer that you submitted, a
> member of the RO team will attempt to contact you to clarify the
> issue. If clarification is not made prior to our project deadline, the
> updates may not be incorporated into TIGER^^. Your updates are
> considered provisional until their existence is confirmed during our
> field check.

#### Updating the Feature Shapefile  {#updating-the-feature-shapefile .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> Create a new line layer in the shapefile provided by the Census Bureau
> that includes the following feature updates:

-   Each change must contain a separate line record for each update made
    to the file.

-   Each update related line must contain one of the codes listed in the
    coding scheme and that code must be recorded in the attribute field
    for the line.

> See Figure 4.7 for an example.

[]{#__RefHeading___Toc137619585 .anchor}Figure 4.6: Change Type Codes
for Feature Corrections

**Change Type Codes for Feature Corrections**

  ------------------------ ------------------------------- ---------------------------------------------
  **[Code]{.underline}**   **[Translation]{.underline}**   **[Additional Requirements (if
                                                           applicable]{.underline}**

  NF                       New Feature                     If adding a new feature (Road, Railroad,
                                                           Hydrography, etc.), code all new feature
                                                           segments with a 'NF' value in CHNG_TYPE
                                                           field.

  CN                       Change Name                     If changing the name of a feature, code the
                                                           line segment(s) with a 'CN' in the CHNG_TYPE
                                                           field, and provide the feature's new name in
                                                           the 'FENAME' field.

  CF                       Change Feature Class            If changing the feature class code for a
                                                           feature, code the CHNG_TYPE field with a 'CF'
                                                           (i.e., a local road was mistakenly coded as a
                                                           highway).

  DF                       Delete Feature                  If deleting a feature, provide all deleted
                                                           feature segments in a change line layer, and
                                                           code all deleted segments with a 'DF' value
                                                           in the CHNG_TYPE field.
  ------------------------ ------------------------------- ---------------------------------------------

#### Displaying Features Based on CFCC1 {#displaying-features-based-on-cfcc1 .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> Within the \*.shp file you may want to display different feature types
> based on the Census Feature Class Code (CFCC1). For example, you may
> want to display all roads in black, hydro features in blue, etc. Some
> of the CFCC1 values listed below may not appear in the shapefile you
> have, but for your reference:

-   'A'  Roads

-   'B'  Railroad

-   'C'  Miscellaneous Ground Transportation

-   'D'  Landmark

-   'E'  Physical Features

-   'F'  Nonvisible Features (such as boundaries for

> incorporated places, counties, school districts, etc.)

-   'G'  US Census Bureau Usage (for internal

> programs)

-   'H'  Hydrography

-   'P'  Provisional Features

-   'X'  Not Yet Classified

> For more detailed information on CFCC's, you can refer to pp. 3-28 to
> 3-45 of the most recent TIGER/Line^^ documentation at
> http://www.census.gov/geo/www/tiger/index.html.
>
> []{#__RefHeading___Toc137619586 .anchor}Figure 4.7: Digital Road
> Correction Example
>
> Figure 4.7 consists of road corrections that you may wish to submit.
> Create a separate layer containing just those road/feature segments
> that you would like the Census Bureau to add, remove, or rename.

[]{#__RefHeading___Toc137619587 .anchor}Figure 4.8: Table Extract for
Figure 4.7

  ------------ ------ ------- ---------- ----------------------- ------------
  TLID         CFCC   CFCC1   FIDELITY   FENAME                  CHNG_TYPE

               A41    A       0          Oak Street              NF

               A41    A       0          Oak Street              NF

               A41    A       0          Oak Street              NF

  9999999998   A41    A       0          Cherry Street           CN

  9999999998   A41    A       0          Cherry Street           CN

  9999999998   A41    A       0          Cherry Street           CN

  9999999998   A41    A       0          Cherry Street           CN

  9999999998   A41    A       0          Cherry Street           CN

  9999999998   A41    A       0          Cherry Street           CN

  9999999998   A41    A       0          Elm Street              DF

  9999999998   A41    A       0          Elm Street              DF

  9999999998   A41    A       0          Elm Street              DF

  9999999998   A41    A       0          Elm Street              DF
  ------------ ------ ------- ---------- ----------------------- ------------

> Figure 4.8 is an example of a table extract from Figure 4.7. Provide
> the CFCC, CFCC1, Fidelity, FENAME, and CHNG_TYPE when adding new road
> features. The participant is required to provide CFCC, FENAME, and
> CHNG_TYPE information only for each road name change. The "TLID,"
> "CFCC," "CFCC1," and "Fidelity" fields are informational fields that
> do not require filling by the participant for existing road features.
> When deleting roads/features, provide the CHNG_TYPE.

#### Address Information {#address-information .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> The Census Bureau will not collect address break information through
> digital feature submission. A process is being designed to capture
> this information digitally in future programs. If you have an accurate
> address source that you would like to share with the Census Bureau at
> this time, please contact your Census Bureau Regional Office.

### Data Dictionary and Metadata

#### Data Dictionary {#data-dictionary .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> Submit a data dictionary[^12], either as part of the metadata or as a
> separate file. The table in Figure 4.9 provides a data dictionary for
> all line shapefiles, while Figure 4.10 provides a data dictionary for
> census tracts and Figure 4.11 provides a data dictionary for census
> blocks.

[]{#__RefHeading___Toc137619588 .anchor}Figure 4.9: Data Dictionary for
all Line Shapefiles

**Data Dictionary for all Line Shapefiles**

  ------------------------- -------------------------- ------------------------ -------------------------------
  **[Field]{.underline}**   **[Length]{.underline}**   **[Type]{.underline}**   **[Description]{.underline}**

  TLID                      10                         Integer                  TIGER/Line^^ ID

  CFCC                      3                          String                   Feature CFCC

  CFCC1                     1                          String                   First Character of feature CFCC

  Fidelity                  1                          Integer                  Shape Fidelity Flag

  FENAME                    90                         String                   Feature Name

  CHNG_TYPE                 2                          String                   Type of digital linear update
  ------------------------- -------------------------- ------------------------ -------------------------------

[]{#__RefHeading___Toc137619589 .anchor}Figure 4.10: Data Dictionary for
Census Tracts

**Data Dictionary for Census Tracts**

####  {#section-27 .Style-Heading-4-+-Left:--0.75\"}

  ------------------------- -------------------------- ------------------------ -------------------------------
  **[Field]{.underline}**   **[Length]{.underline}**   **[Type]{.underline}**   **[Description]{.underline}**

  STATE                     2                          String                   Current state Federal
                                                                                Information Processing Standard
                                                                                (FIPS) code

  COUNTY                    3                          String                   Current county FIPS code

  TRACT                     6                          String                   Current census tract code

  GEOID                     11                         String                   Current state and county FIPS
                                                                                codes, and current census tract
                                                                                code
  ------------------------- -------------------------- ------------------------ -------------------------------

[]{#__RefHeading___Toc137619590 .anchor}Figure 4.11: Data Dictionary for
Census Blocks

**Data Dictionary for Census Blocks**

  ------------------------- -------------------------- ------------------------ -------------------------------
  **[Field]{.underline}**   **[Length]{.underline}**   **[Type]{.underline}**   **[Description]{.underline}**

  STATE                     2                          String                   Current state Federal
                                                                                Information Processing Standard
                                                                                (FIPS) code

  COUNTY                    3                          String                   Current county FIPS code

  TRACT                     6                          String                   Current census tract code

  BLOCKCU                   4                          String                   Current census block (base)
                                                                                code

  BLOCKCU_SUF               1                          String                   Current census block (suffix)
                                                                                code

  GEOID                     16                         String                   Current state and county FIPS
                                                                                codes, current census tract
                                                                                code, current census block
                                                                                (base) code, and current census
                                                                                block (suffix) code
  ------------------------- -------------------------- ------------------------ -------------------------------

####  {#section-28 .Style-Heading-4-+-Left:--0.75\"}

####  {#section-29 .Style-Heading-4-+-Left:--0.75\"}

#### Metadata Requirements {#metadata-requirements .Style-Heading-4-+-Left:--0.75\"}

> Submit appropriate metadata with your file.
>
> Metadata that describe the data content, coordinate system/projection,
> author, source, and other characteristics of GIS files are critical
> for Census Bureau staff to efficiently and accurately process files.
> The Census Bureau requires that a metadata text file accompany every
> GIS file and layer submitted.
>
> The Federal Geographic Data Committee's (FGDC) Content Standard for
> Digital Spatial Metadata provides a national standard that enables the
> data-sharing public to easily locate critical information about a file
> and ensure that no critical information is omitted inadvertently when
> creating metadata. For this reason, the Census Bureau requests that
> metadata be submitted using this standard. For information about the
> FGDC and its geospatial metadata standards, please visit
> <http://www.fgdc.gov/metadata/metadata.html>
>
> The Census Bureau requires that the following sections of the FGDC
> metadata form be completed:

-   Citation (information about the originator, publication date, title
    edition, and other publications or information).

-   Description (section that contains an abstract describing your data
    set).

-   Time period of content (section that describes the vintage of the
    data).

-   Spatial domain (information about bounding coordinates).

-   Point of contact (general contact information).

-   Data quality information (information about attribute accuracy).

-   Spatial reference information (section on coordinate system /
    projection of the data set).

-   Entity and attribute information (section that describes the
    contents of your table).

> To help you fulfill the requirement of filling out and submitting
> metadata, the Census Bureau suggests visiting the USGS web site. This
> site contains useful information about FGDC compliant metadata, from
> which one can read about metadata frequently asked questions, view
> FGDC metadata examples, and connect to other FGDC related Web pages.
> The USGS\'s metadata URL is
> <http://geology.usgs.gov/tools/metadata/>**.**
>
> Moreover, if you are using Arc/Info, the following link points to a
> useful Arc Macro Language (AML) tool that, when executed, completes
> most of the required sections of the metadata form automatically
> http://marinemetadata.org/tools/refs/FGDCMeta. (This AML is a product
> of the Illinois State Geological Survey.)
>
> **Note**: ESRI's ArcCatalog also has an embedded program that uses the
> FGDC standard in its creation of geospatial metadata.
>
> If you have questions regarding the data dictionary or metadata
> requirements, please contact the Census Bureau at 301-763-1099.

### Digital File Submission

> Use the following as a guide to ensure that you have included all the
> required layers.

-   Name the feature update layer as the following (this file is only
    required if making updates to your features) and export the layer to
    a shapefile:

> **LUCA08\_\<ST\>\<COU\>\_FEAUpdates.shp**
>
> The feature update layer must include:

-   A value in its "CHNG_TYPE" field that indicates the type of change.

-   Only feature updates (do not include unmodified features).

#### Compressing the File {#compressing-the-file .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> Compress all updated materials, Shapefile, Data Dictionary, and
> Metadata, into one ZIP formatted file called**:**
>
> **LUCA08\_\<ST\>\<COU\>\_Return.ZIP**.
>
> **Note**: Please use PkZip or GZip software, if possible.
>
> Burn the file to a CD-ROM and submit according to the directions
> provided in Chapter 7.

### Boundary and Annexation Survey (BAS)

> The Census Bureau conducts the Boundary and Annexation Survey (BAS)
> each year to determine the inventory of correct names, legal
> descriptions, and legal boundaries of counties and equivalent
> entities, minor civil divisions, incorporated places, American Indian
> reservations, and American Indian off-reservation trust lands. The
> Census Bureau enters all boundary and area information obtained
> through the BAS into the TIGER^^ database so that all subsequent map
> and address list products reflect these changes.
>
> During your review, you may find that the boundary for your
> jurisdiction, as shown on the Census Bureau map, does not depict the
> correct current location. You may submit boundary corrections on the
> paper Census Bureau map as explained in *Appendix C* or using a
> digital file as described in the *Appendix D, Digital BAS Guidelines
> Supplement Boundary and Annexation Survey (BAS) User's Guide*. This
> user's guide is included for your reference as a supplement to the
> LUCA Program.
>
> For more information on submitting digital boundary files and the BAS
> program, please, visit the BAS Web site at
> <http://www.census.gov/geo/www.bas/bashome.html>.

# Chapter 5 Reviewing and Updating the Address List File {#chapter-5-reviewing-and-updating-the-address-list-file .Style-Heading-1-+-Centered}

> Action Codes for Updating Address List File
>
> A -- Adding Addresses
>
> C -- Correcting Addresses
>
> D -- Deleting Addresses
>
> J -- Not in Our Jurisdiction Addresses
>
> N -- Nonresidential Addresses
>
> Saving the File

### Action Codes for Updating the Address List File {#action-codes-for-updating-the-address-list-file .Style-Heading-3-+-Dark-Teal}

> There are five action codes you can use to make updates to the Address
> List:

1.  A -- Add

2.  C -- Correction

3.  D -- Delete

4.  J -- Not in Jurisdiction

5.  N -- Nonresidential

> You can add or make updates to **city-style** addresses\* only. This
> chapter provides instructions on making updates to the Address List.
> (Please refer to Chapter 4 for instructions for updating corresponding
> paper or digital maps.)

#### A -- Adding Addresses {#a-adding-addresses .Style-Heading-4-+-Left:--0.75\"}

> **Note: It is important that you provide the correct census geography
> (geographic codes, i.e., state code, county code, census tract number,
> and census block number) when adding an address record.**

####  {#section-30 .Style-Heading-4-+-Left:--0.75\"}

> You can only add **city-style** addresses to the Address List.

-   Create a new record or start/insert a new row.

-   Enter an "**A**" in the **"Action Code"** field.

```{=html}
<!-- -->
```
-   Enter the required address information in the appropriate fields for
    each new address:

```{=html}
<!-- -->
```
-   Entity code

-   State code

-   County code

-   Census tract number

-   Census block number

-   House number

-   Street or road name

\* For census blocks containing all **noncity-style** addresses, you can
only challenge the count of addresses for census blocks. For census
blocks containing a mix of city-style and noncity-style addresses, you
can only update these individual city-style address or challenge the
count of addresses for the entire census block; you **cannot** do both.
*See Chapter 6.*

-   Apartment/unit number, if applicable:

```{=html}
<!-- -->
```
-   Create one record for each individual unit and add each individual
    unit designator, if known.

-   If the apartment/unit designators are unknown, but you know the
    number of units at the multi-unit structure, enter "\*#" in the
    "**Apartment/Unit Number**" field for each unit added.

> For example, the new multi unit structure located at the basic street
> address 505 Wells Blvd, contains twenty units.

-   Create twenty records with the correct census geography (i.e., state
    code, county code, census tract number, census block number) and the
    basic street address, 505 Wells Blvd.

-   For each unit added at 505 Wells Blvd enter in order, the
    appropriate "\*#" in the "**Apartment/Unit Number**" field. For
    example, for the first unit added at 505 Wells Blvd, enter "\*1" in
    the "**Apartment/Unit Number**" field; for the second unit record
    added, enter "\*2" in the "**Apartment/Unit Number**" field, and so
    on, until you get to the twentieth unit record, where you enter
    "\*20" in the "**Apartment/Unit Number**" field.

> *The "\*" character will alert the Census Bureau that the actual unit
> identifiers are unknown and that we need to obtain further information
> during our field check of the addresses.*
>
> **Note**: To add mobile home or trailer lots, whether occupied or
> vacant, use the procedure described above.

-   ZIP Code (if the address is a mailing address)

-   Group quarters flag, if applicable:

```{=html}
<!-- -->
```
-   Enter a "Y" in the "**Group Quarters Flag"** field for a group
    quarters address.

-   Add the name of the group quarters in the **"Location Description or
    GQ Name"** field.

```{=html}
<!-- -->
```
-   If applicable, add new streets or other map features on the Census
    Bureau map(s) as shown in Map Example 1 in Chapter 4.

####  {#section-31 .Style-Heading-4-+-Left:--0.75\"}

#### C -- Correcting Addresses {#c-correcting-addresses .Style-Heading-4-+-Left:--0.75\"}

> Enter a "**C**" in the **"Action Code"** field for the following
> situations and replace all incorrect geographic codes (i.e., state
> code, county code, census tract number, and census block number)
> and/or address information with the correct information:

-   Incorrect state code

-   Incorrect county code

-   Incorrect census tract number

-   Incorrect census block number

-   Incorrect group quarters designation

-   Incorrect house number

-   Incorrect street name, including directional and type information

-   Incorrect group quarters name

-   Incorrect apt/unit number

-   Incorrect ZIP Code

-   Conversion of a housing unit to a multi-unit structure:

```{=html}
<!-- -->
```
-   Make any corrections to the geographic code information, if
    necessary.

-   Copy the corrected address record as many times as needed for each
    additional unit (**do not** copy the MAFID).

-   Enter a **"C"** in the **"Action Code"** field for the original
    corrected address. Enter the first unit designator in the
    **"Apartment/Unit Number"** field.

-   For each new record at the address:

```{=html}
<!-- -->
```
-   Delete the MAFID number in Field# 3 (if copied from the original
    record).

-   Enter an **"A"** in the "**Action Code"** field.

-   Enter the unit designation in the **"Apartment/Unit Number"** field,
    if known.

```{=html}
<!-- -->
```
-   If the apartment/unit numbers are unknown, but you know the number
    of units at the multi-unit structure, enter "\*#" in the
    "**Apartment/Unit Number**" field for each unit added. For example,
    the new multi unit structure located at the basic street address 505
    Wells Blvd, contains twenty units.

    -   Create twenty records with the correct census geography (i.e.,
        state code, county code, census tract number, census block
        number) and the basic street address, 505 Wells Blvd.

    -   For each unit added at 505 Wells Blvd enter in order, the
        appropriate "\*#" in the "**Apartment/Unit Number**" field. For
        example, for the first unit added at 505 Wells Blvd, enter "\*1"
        in the "**Apartment/Unit Number**" field; for the second unit
        record added, enter "\*2" in the "**Apartment/Unit Number**"
        field, and so on, until you get to the twentieth unit record,
        where you enter "\*20" in the "**Apartment/Unit Number**" field.

> **Note**: To correct addresses for mobile home or trailer lots,
> whether occupied or vacant, use the procedure described above.

-   Conversion of a multi-unit structure to a housing unit:

```{=html}
<!-- -->
```
-   Enter a **"C"** in the **"Action Code"** field for the first unit
    address record.

-   Remove the unit designation in the **"Apartment/Unit Number"**
    field.

-   For the remaining units, enter a **"D"** in the **"Action Code"**
    field.

```{=html}
<!-- -->
```
-   Conversion of a group quarters to a housing unit:

```{=html}
<!-- -->
```
-   Enter a **"C"** in the **"Action Code"** field.

-   Remove the **"Y"** in the "**Group Quarters Flag"** field.

-   Remove the name of the group quarters in the **"Location Description
    or GQ Name"** field.

```{=html}
<!-- -->
```
-   Conversion of a housing unit to a group quarters:

```{=html}
<!-- -->
```
-   Enter a **"Y"** in the "**Group Quarters Flag"** field for a group
    quarters address.

-   Add the name of the group quarters in the **"Location Description or
    GQ Name"** field.

```{=html}
<!-- -->
```
-   Make corrections to the map(s) as needed so that the maps match the
    new information on the Address List. Map Example 2 in Chapter 4
    provides an example for correcting a street name while Map Example 3
    explains how to move an existing street to its correct location
    within another census block.

#### D -- Deleting Addresses {#d-deleting-addresses .Style-Heading-4-+-Left:--0.75\"}

-   Enter a "**D**" in the **"Action Code"** field (Field# 4). *Be very
    careful when using this action code*. Ensure that the housing unit
    or group quarters does not exist or is a duplicate address
    (Duplicate addresses are those that are incorrectly listed twice on
    the Census Address List).

> **Note:** Do not use the "**D**" action code for existing commercial
> or institutional addresses; instead, use the "**N**" nonresidential
> action code.

-   Make deletions to the map(s), as explained in Chapter 4, so that the
    maps match the Address List.

#### J -- Not in Jurisdiction Addresses {#j-not-in-jurisdiction-addresses .Style-Heading-4-+-Left:--0.75\"}

-   Enter a "**J**" in the **"Action Code"** field for addresses that
    are not in your jurisdiction.

#### N -- Nonresidential Addresses {#n-nonresidential-addresses .Style-Heading-4-+-Left:--0.75\"}

-   Enter an "**N**" in the **"Action Code"** field for addresses that
    are used for any purpose other than residential (such as a business,
    school, church, school, government office, etc.). **Ensure that the
    address does not contain a living quarters.**

> It is **very important** that you provide the correct information (in
> particular, geographic codes, i.e., state code, county code, census
> tract number, and census block number) in the appropriate fields.
> Accurate information will enable the Census Bureau to be successful in
> finding addresses during our field verification operation.

### Saving the File {#saving-the-file .Style-Heading-3-+-Dark-Teal}

> Save the file frequently - - at least once every 10 minutes - - to
> avoid possible loss of work. In addition to saving the file often, you
> should back up the file each week. Do this in the event of hardware
> faults and/or software corruption. This process ensures that, at most,
> a week's worth of work is lost.
>
> When you have finished updating the Address List file:

-   Save to a new file only those records that have an entry in the
    Action Code field.

-   Make a copy of your edited file.

-   Save this file in a pipe-delimited format and burn it to a CD-ROM.

-   Send the CD-ROM with updates to your regional office.\*

-   Keep the backup copy of your edited file until the regional office
    staff informs you that they have received and successfully processed
    your file.

#  {#section-32 .Style-Heading-1-+-Centered}

> **\* See Chapter 7 for returning materials to the Census Bureau.**

# Chapter 6 Reviewing and Updating the Address Count List File {#chapter-6-reviewing-and-updating-the-address-count-list-file .Style-Heading-1-+-Centered}

> The Address Count List File
>
> Reviewing and Editing the Address Count List File
>
> Saving the File

### The Address Count List File {#the-address-count-list-file .Style-Heading-3-+-Right:---0.5\"}

> The Address Count List file contains the number of housing unit and
> group quarters addresses on the Address List for each census block
> within your jurisdiction. Use this list to challenge the count of
> addresses for any census block within your jurisdiction that you
> believe to be incorrect. If a census block contains all city-style
> addresses or a mix of city-style and noncity-style addresses, you can
> update the individual city-style addresses only *or* challenge the
> count of addresses for the entire census block, but you **cannot** do
> both.
>
> If a census block contains all noncity-style addresses, you can only
> challenge the count of addresses for that block.

### Reviewing and Editing the Address Count List File {#reviewing-and-editing-the-address-count-list-file .Style-Heading-3-+-Right:---0.5\"}

> Once you have successfully imported and opened the file, review the
> Census Bureau's current housing unit address count for each census
> block within your jurisdiction. If there is a discrepancy between the
> Census Bureau's current housing unit address count and your local
> address count for any census block, fill in the "**Local Housing Unit
> Address Count"** column for that particular census block. Record any
> discrepancy between the Census Bureau's current address counts for
> group quarters and your local address counts for group quarters in the
> **"Local Group Quarters Address Count"** column.
>
> The Map Sheet to Block Number Relationship List lists all of the
> census blocks within your jurisdiction and identifies the map sheet(s)
> on which each census block is located.
>
> Make any necessary annotations to the Census Bureau's maps.

###  {#section-33 .Style-Heading-3-+-Dark-Teal1}

### Saving the File {#saving-the-file-1 .Style-Heading-3-+-Right:---0.5\"}

> Save the file frequently - - at least every 10 minutes - - to avoid
> possible loss of work. In addition to saving the file often, you
> should back up the file each week. Do this in the event of hardware
> faults and/or software corruption. This process ensures that, at most,
> only a week's worth of work is lost.
>
> When you have finished updating the Address Count List file:

-   Save to a new file only those records with an entry in the "**Local
    Housing Unit Address Count**" field and/or the "**Local Group
    Quarters Address Count**" field.

-   Make a backup copy of your edited file.

-   Save this file in a pipe-delimited format and burn it to a CD-ROM.

-   Send the CD-ROM with updates to your regional office.\*

-   Keep the backup copy of your edited file until the regional office
    staff informs you that they have received and successfully processed
    your file.

> **\* See Chapter 7 for returning materials to the Census Bureau.**

# Chapter 7 Submitting Your LUCA Program Updates {#chapter-7-submitting-your-luca-program-updates .Style-Heading-1-+-Centered}

> Submitting LUCA Program Updates
>
> Files
>
> Census Bureau Paper Maps
>
> Shapefile
>
> Shipping Census Bureau Title 13 Materials

### Submitting LUCA Program Updates {#submitting-luca-program-updates .Style-Heading-3-+-Dark-Teal}

###  {#section-34 .Style-Heading-3-+-Dark-Teal}

> After completing your review and update of the LUCA materials, return
> the materials with updates to the **Census Bureau's Regional Office**
> responsible for your jurisdiction. See the back cover for a list of
> Regional Offices. Please include the **inventory form**, *Appendix G*,
> with your returned materials. Be sure to follow the guidelines below
> for the procedures for shipping Census Bureau Title 13 Materials
> (address list and maps containing structure points).

#### Files {#files .Style-Heading-4-+-Left:--0.75\"}

-   Send only those records with updates on the CD-ROM, as explained in
    the section "Saving the File" in Chapters 5 and 6, to your regional
    office.

-   Keep a backup copy of your edited files until the regional office
    staff informs you that they have received and successfully processed
    your files.

#### Census Bureau Paper Maps {#census-bureau-paper-maps .Style-Heading-4-+-Left:--0.75\"}

-   Separate the Census map sheets with annotations from those without
    annotations.

-   Make a copy of all map sheets containing annotations to keep for
    your records and to use during the Feedback process, if necessary.

-   Organize the map sheets by map sheet number.

-   Fold the maps if there are five or fewer map sheets.

-   If there are more than five map sheets, roll the maps and mail them
    in a mailing tube or box.

> **Note**: Maps containing structure points must be double-wrapped.

#### Shapefile {#shapefile .Style-Heading-4-+-Left:--0.75\"}

-   Keep a backup copy of your updated digital file for your records and
    to use during the Feedback process, if necessary.

-   Contact you Census Bureau Regional Office if you have questions
    about submitting your shapefile for the LUCA Program.

### Shipping Census Bureau Title 13 Materials {#shipping-census-bureau-title-13-materials .Style-Heading-3-+-Dark-Teal1}

-   Use shipping contractors that provide tracing services, such as U.S.
    Postal Service (USPS) certified or registered mail, Fed Ex, United
    Parcel Service (UPS), or similar service.

-   Ship all Census Bureau Title 13 materials in **two** opaque sealed
    envelopes that are durable enough to prevent someone from viewing or
    tampering with the enclosed materials.

-   Label both sides of the inner envelope or wrapping with
    **"DISCLOSURE PROHIBITED BY Title 13 U.S.C."** as shown in *Appendix
    H*.

-   **DO NOT** label the outer addressed envelope with the **"DISCLOSURE
    PROHIBITED BY Title 13 U.S.C."** notice.

-   Address the outer envelope to the Director, Census Bureau Regional
    Office for your jurisdiction as provided on the back cover, ATTN:
    LUCA Staff.

# Chapter 8 Returning Or Destroying Census Bureau Title 13 Materials  {#chapter-8-returning-or-destroying-census-bureau-title-13-materials .Style-Heading-1-+-Centered}

Shipping Census Bureau Title 13 Materials

Methods for Destroying Census Bureau Title 13 Materials

###  {#section-35 .Style-Heading-3-+-Dark-Teal}

### Returning or Destroying Census Bureau Title 13 Materials {#returning-or-destroying-census-bureau-title-13-materials .Style-Heading-3-+-Dark-Teal}

> Once you have reviewed your LUCA Program feedback materials, you must
> return or destroy all Title 13, U.S.C. address lists and maps
> containing structure points according to the Census Bureau's specific
> guidelines for returning or destroying Title 13 materials.
>
> The primary liaison is required to verify the return or destruction of
> any remaining Title 13 materials, both paper and computer-readable
> (i.e., paper copies, backup files, etc.). The primary liaison must
> sign and return to the Census Bureau the Return/Destruction of Title
> 13, U.S.C. Materials form found in *Appendix I*. (This form must be
> included with your returned Title 13 materials.) All LUCA Program
> reviewers are required to sign and date this form at the completion of
> the LUCA Program. Should any liaison or reviewer leave before the
> completion of the LUCA Program, they are required to "sign-out" of the
> program by signing and dating this form. If any liaison or reviewer
> leaves and fails to sign and date this form, the current liaison can
> "sign-out" on their behalf.

#### Shipping Census Bureau Title 13 Materials {#shipping-census-bureau-title-13-materials-1 .Style-Heading-4-+-Left:--0.75\"}

> If you choose to return the Census Bureau's Address List and maps
> containing structure points:

-   Use shipping contractors that provide tracing services, such as U.S.
    Postal Service (USPS) certified or registered mail, Fed Ex, United
    Parcel Service (UPS), or similar service.

-   Ship all Census Bureau Title 13 materials in **two** opaque sealed
    envelopes that are durable enough to prevent someone from viewing or
    tampering with the enclosed materials.

-   Label both sides of the inner envelope or wrapping with
    **"DISCLOSURE PROHIBITED BY Title 13 U.S.C."** as shown in *Appendix
    H*.

-   **DO NOT** label the outer addressed envelope with the **"DISCLOSURE
    PROHIBITED BY Title 13 U.S.C."** notice.

-   Address the outer envelope to the Director, Census Bureau Regional
    Office for your jurisdiction as provided on the back cover, ATTN:
    LUCA Staff.

#### Methods for Destroying Census Bureau Title 13 Materials {#methods-for-destroying-census-bureau-title-13-materials .Style-Heading-4-+-10-pt-Left:--0.75\"-Right:---0.5\"}

> Only those individuals who signed the Confidentiality Agreement Form
> are permitted to destroy the Census Bureau's Title 13 materials.

-   Never deposit Census Bureau confidential materials in a trash or
    recycle container.

-   Store the materials in a secure area in a container labeled
    "document destruction container" until they are destroyed.

-   The destruction process must prevent recognition or reconstruction
    of the paper or computer-readable information. Use one of the
    following methods to destroy census confidential materials:

```{=html}
<!-- -->
```
-   Shredding.

-   Chemical decomposition.

-   Pulverizing (such as, hammer mills, choppers, etc.).

-   Burning (only in a facility approved by the Environmental Protection
    Agency).

-   Clear magnetic media (tapes, disks, hard drives) containing Census
    Bureau address information before reuse. To clear, overwrite all
    Title 13 data a minimum of three times using a commercial disk
    utility program or degauss using a commercial degausser.

-   Clear diskettes by running a magnetic strip, of sufficient length to
    reach all areas of the disk over and under each surface a minimum of
    three times. If the information cannot be destroyed as suggested,
    the disk must be damaged in an obvious manner to prevent use in any
    disk drive unit and discarded.

> **Note:** Hand tearing or burying information in a landfill are
> unacceptable methods of disposal.

-   Destroy CD-ROMs and DVDs using a commercial grade shredder, suitable
    for rendering them un-useable; or cut them up with scissors in an
    obvious manner to prevent use in a drive unit.

> If you have any questions regarding the destruction of Title 13
> materials, please call your Census Bureau Regional Office.

#  {#section-36 .Style-Heading-1-+-Centered}

#  {#section-37 .Style-Heading-1-+-Centered}

#  {#section-38 .Style-Heading-1-+-Centered}

#  {#section-39 .Style-Heading-1-+-Centered}

#  {#section-40 .Style-Heading-1-+-Centered}

#  {#section-41 .Style-Heading-1-+-Centered}

#  {#section-42 .Style-Heading-1-+-Centered}

#  {#section-43 .Style-Heading-1-+-Centered}

#  {#section-44 .Style-Heading-1-+-Centered}

#  {#section-45 .Style-Heading-1-+-Centered}

#  {#section-46 .Style-Heading-1-+-Centered}

# 

# 

# 

Appendixes []{#__RefHeading___Toc137619556 .anchor}

### Appendix A Confidentiality and Security Guidelines {#appendix-a-confidentiality-and-security-guidelines .Style-Heading-3-+-Right:---0.5\"}

**Confidentiality and Security Guidelines**

> The law requires the U.S. Census Bureau to maintain the
> confidentiality for all of the information that it collects. The
> Census Bureau takes its responsibility to protect the confidentiality
> of the information it collects very seriously. Respondents place their
> trust in the Census Bureau each time they complete a survey or an
> interview. This trust in confidentiality is critical to the success of
> the Census Bureau's mission to collect and report the most accurate
> data possible. To uphold the law, the Census Bureau requires that all
> individuals who work with the Census Bureau's confidential materials
> read, understand, and agree to abide by the confidentiality and
> security guidelines outlined below.

**Why Address Information Is Protected**

> Title 13, United States Code (U.S.C.), provides for the confidential
> treatment of census-related information. Chapter 1, Section 9 of the
> code states:
>
> *"Neither the Secretary, nor any other officer or employee of the
> Department of Commerce or bureau or agency thereof, or local
> government census liaison, may, except as provided in section 8 or 16
> or chapter 10 of this title...*

1)  *use the information furnished under the provisions of this title
    for any purpose other than the statistical purposes for which it is
    supplied; or*

2)  *make any publication whereby the data furnished by any particular
    establishment or individual under this title can be identified; or*

3)  *permit anyone other than the sworn officers and employees of the
    Department or bureau or agency thereof to examine the individual
    reports."*

> Section 214 of the Code and the Uniform Sentencing Act of 1984 set the
> penalty for the wrongful disclosure or release of information
> protected by Title 13 at a fine of not more than \$250,000 or
> imprisonment for not more than 5 years, or both.
>
> To implement this law, all Census Bureau employees (both temporary and
> permanent) take an oath to maintain the confidentiality of the census
> information they encounter in their work. Census information includes:

-   Everything on a completed or partially completed questionnaire or
    obtained in a personal or telephone interview.

-   Individual addresses maintained by the Census Bureau that Local
    Update of Census Addresses (LUCA) Program liaisons review.

```{=html}
<!-- -->
```
-   Maps that identify the location of individual housing units and/or
    group quarters ("structure points").

> Title 13 of the U.S.C. does not protect generalized address
> information, such as the address range data available in the Census
> Bureau's TIGER/Line products.
>
> In 1994, the U.S. Congress amended Chapter 1 of Title 13 to allow
> local government designated census liaisons to review the Census
> Bureau's address list for their area. This amendment recognizes the
> important role that local knowledge and participation can play in
> building and updating an accurate, comprehensive census address list.
> In amending this chapter, the Congress reaffirmed the confidential
> nature of address information.

**The Confidentiality Agreement**

> Each participating government must designate a primary liaison. The
> primary liaison and all reviewers must understand and sign the
> Confidentiality Agreement. The Census Bureau considers all individuals
> who have access to the Census Bureau's address information and maps
> showing the location of housing units and group quarters, liaisons.
> Therefore, all Option 1 and
>
> Option 2 LUCA Program reviewers must sign the Confidentiality
> Agreement and Self-Assessment Forms.
>
> Signatures on this form constitute an agreement by each individual to
> abide by the security guidelines outlined below. While access to Title
> 13 protected information is temporary, the commitment to keep the
> information confidential is permanent.

-   **The Census Bureau will not deliver the address list materials to
    participants choosing Option 1 and Option 2 until we have received a
    completed and signed Confidentiality Agreement and Self-Assessment
    Form.**

-   **Although you may have prior confidentiality agreements on file at
    the Census Bureau, these will not fulfill the requirements of the
    LUCA Program.**

**Security Guidelines**

> The Census Bureau recognizes the fact that the implementation of these
> guidelines may vary slightly from one participant to another.
> Regardless, the result must be the same for each participant --
> nondisclosure of information protected by Title 13, U.S.C.
>
> The primary liaison accepts the responsibility for protecting and
> safeguarding the LUCA Program materials covered by Title 13, U.S.C.
> This includes any list that shows individual Census Bureau addresses
> and any Census Bureau map or digital file that shows individual
> housing units and/or group quarters location ("structure points"). The
> primary liaison must restrict access to the Census Bureau's address
> information to those individuals who have signed the Confidentiality
> Agreement. Only those individuals directly involved in the review
> should sign the Confidentiality Agreement.
>
> As you read the Census Bureau's security requirements, keep in mind
> the important role security plays in the overall responsibilities of
> each LUCA Program liaison and reviewer. The Census Bureau must have
> your full cooperation and commitment to following these guidelines.
> Together, we will maintain the confidential information entrusted to
> the Census Bureau by the Congress and the American public.

**Protecting Census Bureau Address Information**

> The Census Bureau will conduct workshops covering all aspects of the
> LUCA Program. In addition, the workshops will provide the
> participating governments with an opportunity to review the security
> guidelines and safeguards to protect against illegal use of Census
> Bureau address information. Census Bureau staff conducting the
> workshops will help you decide who in your organization needs to have
> access to the Address List and will review the civil and criminal
> penalties for improper or illegal use of the data.

**Onsite Visits**

> To ensure that participating entities or organizations are maintaining
> adequate security safeguards, the Census Bureau may make on-site
> visits to review your entity or organization's security procedures.
> The Census Bureau will strive not to disrupt your office's operations.
> A typical visit would include a review of:

-   Storage and handling of Census Bureau address information.

-   Employee access to Census Bureau address information.

-   The physical safeguard of the computers, rooms, and buildings where
    the Census Bureau address information is stored.

-   Instructions to employees about security.

-   Data processing operations (including use of passwords).

-   Employee awareness of their responsibilities to protect the
    confidentiality of Census Bureau addresses.

**Protecting Paper Copies of Census Bureau Address Information and
Maps**

-   Keep all Census Bureau address information in a locked room during
    non-work hours. If possible, store the Census address materials and
    maps showing structure points in locked desks or cabinets.

-   During work hours, do not leave a room unattended where Census
    Bureau address information is stored. Lock the room whenever you
    leave.

-   Do not leave Census Bureau address information unattended at your
    desk. Return any Title 13 data to secure storage when you are not
    using it.

-   Only make copies of the information necessary to complete your task.
    Do not leave the copying machine unattended while making copies. All
    copied material containing Title 13 information must bear the
    statement:

> ***"This document contains information, the release of which is
> prohibited by Title 13, U.S.C., and is for U.S. Census Bureau official
> use only."***

-   To FAX a document containing Census Bureau address information to a
    Census Bureau location, make sure the document is properly labeled,
    verify the FAX number before sending, and arrange for a Census
    Bureau employee to be at the FAX machine to receive it and
    acknowledge receipt.

-   Do not disclose precise or even anecdotal information about Census
    Bureau addresses or locations to anyone who is not a liaison,
    reviewer, or a Census Bureau employee.

**Protecting Electronic Census Bureau Address Information and Maps**

> Operating systems, programs, applications, and data related to the
> review of Census Bureau addresses must be accessible only to LUCA
> Program liaisons and reviewers. The automated data processing (ADP)
> system should restrict the read, write, delete, and execute functions
> applicable to the Census Bureau's addresses.
>
> The ADP system must use log-on routines that require a user-ID and
> password that conform to the following guidelines:

-   Assign a unique user-ID and password for liaisons and reviewers.

-   Passwords must consist of at least 8, nonblank characters consisting
    of at least one alphabet letter and either one number or one special
    character (\$,\*, &). No more than six consecutive characters
    (AAAAAA) may appear in the password, and then only once.

```{=html}
<!-- -->
```
-   Reject passwords that are the same as the user-ID or that have been
    used within the last 6 months.

-   Encrypt passwords.

-   Disable passwords after three bad attempts.

-   Do not display passwords on terminals or printers.

-   Change passwords every 90 days (more frequent change is optional) or
    immediately, if compromised.

-   On new accounts, the user must change the assigned password to a
    unique password the first time they log on.

> The ADP system must display a warning log-on feature. Computer screens
> must display a warning that states:
>
> **\*\*WARNING\*WARNING\*WARNING\*\***
>
> **YOU HAVE ACCESSED A COMPUTER SYSTEM CONTAINING UNITED STATES
> GOVERNMENT INFORMATION. USE OF THIS COMPUTER WITHOUT AUTHORIZATION OR
> FOR PURPOSES FOR WHICH AUTHORIZATION HAS NOT BEEN EXTENDED IS A
> VIOLATION OF FEDERAL LAW AND CAN BE PUNISHED BY FINE OR IMPRISONMENT
> (Public Law 99-474). ALL USE MAY BE INTERCEPTED, MONITORED, RECORDED,
> COPIED, AUDITED, INSPECTED, AND DISCLOSED TO AUTHORIZED LAW
> ENFORCEMENT OFFICIALS. REPORT SUSPECTED VIOLATIONS TO YOUR AGENCY
> SECURITY OFFICER. USE OF THIS SYSTEM INDICATES YOU CONSENT TO THIS
> WARNING. LOG OFF IMMEDIATELY IF YOU DO NOT AGREE TO THE CONDITIONS OF
> THIS WARNING.**
>
> **\*\*WARNING\*WARNING\*WARNING\*\***
>
> If Census Bureau address information is placed on a shared computer
> system, construct electronic security profiles to allow only LUCA
> Program liaisons and reviewers access to the Census Bureau's address
> information. Test your security to ensure that only LUCA liaisons and
> reviewers are permitted access to the Census Bureau's address
> information.
>
> Encrypt all Title 13 Census Bureau address information transmitted via
> FTP to the Census Bureau's data site with an appropriate product.
>
> Lock all rooms containing computers and all associated media during
> nonwork hours.
>
> Do not leave computers with Census Bureau address information
> unattended during work hours. Log-off the computer or lock the room
> whenever you leave.
>
> Label any computer diskettes, CD-ROMs, DVDs, tapes, cartridges or
> other computer storage media containing Census Bureau address
> information with the following:
>
> ***"This document contains information, the release of which is
> prohibited by Title 13, U.S.C., and is for U.S. Census Bureau official
> use only."***
>
> If backup is necessary, do not send the tapes, cartridges, or disks
> off-site. Store them in a secured area. **Do not mix, store, or
> back-up LUCA data with other data.**
>
> Clear magnetic media (tapes, disks, hard drives) containing Census
> Bureau address information before reuse. To clear magnetic media,
> overwrite all Title 13 data three times at a minimum using a
> commercial disk utility program or degauss using a commercial
> degausser.
>
> Program any software you develop for displaying the Census Bureau
> addresses to label each affected page of a printout containing Census
> Bureau address information with the following:
>
> ***"This document contains information, the release of which is
> prohibited by***
>
> ***Title 13, U.S.C., and is for U.S. Census Bureau official use
> only."***

**Returning Census Bureau Title 13 Materials**

> Once you have completed your initial review and update of the LUCA
> materials, return only those materials with updates to the Census
> Bureau's Regional Office responsible for your jurisdiction. Retain all
> nonannotated Title 13 materials until you receive your feedback
> materials. Use the following guidelines to ship the updated materials:

-   Enclose a letter to the Census Bureau's Regional Office notifying
    them of the shipment and listing its contents.

-   Ship all Census Bureau confidential material in two opaque sealed
    envelopes that are durable enough to prevent someone from viewing or
    tampering with the enclosed materials.

-   Seal and reinforce all packages.

```{=html}
<!-- -->
```
-   Label both sides of the inner envelope or wrapping with
    **"DISCLOSURE PROHIBITED BY Title 13, U.S.C."**

-   **DO NOT** label the outer addressed envelope with the **"DISCLOSURE
    PROHIBITED BY Title 13, U.S.C."** notice.

-   Address the outer envelope to the Director, Census Bureau Regional
    Office for your jurisdiction, to the attention of the LUCA Staff.

-   Use shipping contractors that provide tracing services, such as U.S.
    Postal Service certified or registered mail, FedEx, United Parcel
    Service, or similar service.

**Methods for Destroying Census Bureau Confidential Materials**

> After receiving and reviewing your feedback materials, all Title 13,
> U.S.C., Census Bureau address lists and maps containing structure
> points **must be destroyed and/or returned** according to the Census
> Bureau's specific guidelines for destroying or returning confidential
> material.
>
> The primary liaison is required to verify the destruction of any
> remaining Title 13 materials, both paper and computer-readable (i.e.,
> paper copies, backup files, etc.). The primary liaison must sign and
> return to the Census Bureau the Destruction of Title 13, U.S.C.,
> Materials form. In addition, all LUCA Program reviewers are required
> to sign this form at the completion of the LUCA Program. Should any
> liaison or reviewer leave before the completion of the LUCA Program,
> they are required to "sign-out" of the program by signing and dating
> this form.
>
> Only those individuals who signed the Confidentiality Agreement are
> permitted to destroy the materials.

-   Never deposit Census Bureau confidential materials in a trash or
    recycle container.

-   Store the materials in a secure area in a container labeled
    "document destruction container" until they are destroyed.

-   The destruction process must prevent recognition or reconstruction
    of the paper or computer-readable information. Use one of the
    following methods to destroy census confidential materials:

```{=html}
<!-- -->
```
-   Shredding.

-   Chemical decomposition.

-   Pulverizing (such as, hammer mills, choppers, etc.).

-   Burning (only in a facility approved by the Environmental Protection
    Agency).

-   Clear magnetic media (tapes, disks, hard drives) containing Census
    Bureau address information before reuse. To clear, overwrite all

> Title 13 data a minimum of three times using a commercial disk utility
> program or degauss using a commercial degausser.

-   Clear diskettes by running a magnetic strip of sufficient length to
    reach all areas of the disk over and under each surface a minimum of
    three times. If the information cannot be destroyed as suggested,
    damage the disk in an obvious manner to prevent use in any disk
    drive unit and discard.

> **Note:** Hand tearing or burying information in a landfill are
> unacceptable methods of disposal.

-   Destroy CD-ROMs and DVDs using a commercial grade shredder, suitable
    for rendering them un-usable, or cut them up with scissors in an
    obvious manner to prevent use in a drive unit.

> Once you have selected a method of destruction, contact the Census
> Bureau's Regional Office staff who will provide you with the precise
> specifications for the destruction method you have selected*.*

### Appendix B Confidentiality Agreement Form {#appendix-b-confidentiality-agreement-form .Style-Heading-3-+-Dark-Teal}

**Confidentiality Agreement**

**2008 Census Dress Rehearsal Local Update of Census Addresses (LUCA)
Program**

+-------+------------------------------+---------+--------------------+
| **1.  |                              |         |                    |
| Name  |                              |         |                    |
| of    |                              |         |                    |
| the   |                              |         |                    |
| Par   |                              |         |                    |
| ticip |                              |         |                    |
| ating |                              |         |                    |
| Go    |                              |         |                    |
| vernm |                              |         |                    |
| ental |                              |         |                    |
| U     |                              |         |                    |
| nit** |                              |         |                    |
+-------+------------------------------+---------+--------------------+
| **2.  |                              |         |                    |
| Name  |                              |         |                    |
| of    |                              |         |                    |
| LUCA  |                              |         |                    |
| Liai  |                              |         |                    |
| son's |                              |         |                    |
| O     |                              |         |                    |
| ffice |                              |         |                    |
| or    |                              |         |                    |
| De    |                              |         |                    |
| partm |                              |         |                    |
| ent** |                              |         |                    |
| *(    |                              |         |                    |
| Asses |                              |         |                    |
| sor's |                              |         |                    |
| Of    |                              |         |                    |
| fice, |                              |         |                    |
| Pla   |                              |         |                    |
| nning |                              |         |                    |
| D     |                              |         |                    |
| epart |                              |         |                    |
| ment, |                              |         |                    |
| e     |                              |         |                    |
| tc.)* |                              |         |                    |
+-------+------------------------------+---------+--------------------+
| **3.  |                              |         |                    |
| Addr  |                              |         |                    |
| ess** |                              |         |                    |
| *(    |                              |         |                    |
| House |                              |         |                    |
| N     |                              |         |                    |
| umber |                              |         |                    |
| and   |                              |         |                    |
| S     |                              |         |                    |
| treet |                              |         |                    |
| Name, |                              |         |                    |
| RR,   |                              |         |                    |
| HC,   |                              |         |                    |
| or PO |                              |         |                    |
| Box   |                              |         |                    |
| Num   |                              |         |                    |
| ber)* |                              |         |                    |
+-------+------------------------------+---------+--------------------+
| **4.  |                              |         |                    |
| City, |                              |         |                    |
| S     |                              |         |                    |
| tate, |                              |         |                    |
| ZIP   |                              |         |                    |
| C     |                              |         |                    |
| ode** |                              |         |                    |
+-------+------------------------------+---------+--------------------+
| **5.  |                              |         |                    |
| R     |                              |         |                    |
| espon |                              |         |                    |
| sibil |                              |         |                    |
| ities |                              |         |                    |
| of    |                              |         |                    |
| Lia   |                              |         |                    |
| isons |                              |         |                    |
| and   |                              |         |                    |
| Revi  |                              |         |                    |
| ewers |                              |         |                    |
| Par   |                              |         |                    |
| ticip |                              |         |                    |
| ating |                              |         |                    |
| in    |                              |         |                    |
| the   |                              |         |                    |
| 2008  |                              |         |                    |
| C     |                              |         |                    |
| ensus |                              |         |                    |
| Dress |                              |         |                    |
| Rehe  |                              |         |                    |
| arsal |                              |         |                    |
| LUCA  |                              |         |                    |
| Prog  |                              |         |                    |
| ram** |                              |         |                    |
|       |                              |         |                    |
| > All |                              |         |                    |
| >     |                              |         |                    |
|  2008 |                              |         |                    |
| > C   |                              |         |                    |
| ensus |                              |         |                    |
| >     |                              |         |                    |
| Dress |                              |         |                    |
| >     |                              |         |                    |
|  Rehe |                              |         |                    |
| arsal |                              |         |                    |
| >     |                              |         |                    |
|  LUCA |                              |         |                    |
| > Pr  |                              |         |                    |
| ogram |                              |         |                    |
| > lia |                              |         |                    |
| isons |                              |         |                    |
| > and |                              |         |                    |
| >     |                              |         |                    |
|  revi |                              |         |                    |
| ewers |                              |         |                    |
| >     |                              |         |                    |
|  must |                              |         |                    |
| >     |                              |         |                    |
| agree |                              |         |                    |
| > to  |                              |         |                    |
| >     |                              |         |                    |
|  keep |                              |         |                    |
| > co  |                              |         |                    |
| nfide |                              |         |                    |
| ntial |                              |         |                    |
| > the |                              |         |                    |
| >     |                              |         |                    |
|  U.S. |                              |         |                    |
| > C   |                              |         |                    |
| ensus |                              |         |                    |
| > B   |                              |         |                    |
| ureau |                              |         |                    |
| > ad  |                              |         |                    |
| dress |                              |         |                    |
| > i   |                              |         |                    |
| nform |                              |         |                    |
| ation |                              |         |                    |
| >     |                              |         |                    |
| (incl |                              |         |                    |
| uding |                              |         |                    |
| >     |                              |         |                    |
|  stru |                              |         |                    |
| cture |                              |         |                    |
| > po  |                              |         |                    |
| ints) |                              |         |                    |
| >     |                              |         |                    |
|  they |                              |         |                    |
| > r   |                              |         |                    |
| eview |                              |         |                    |
| > or  |                              |         |                    |
| > to  |                              |         |                    |
| >     |                              |         |                    |
| which |                              |         |                    |
| >     |                              |         |                    |
|  they |                              |         |                    |
| >     |                              |         |                    |
|  have |                              |         |                    |
| > ac  |                              |         |                    |
| cess. |                              |         |                    |
| >     |                              |         |                    |
|  They |                              |         |                    |
| > may |                              |         |                    |
| > use |                              |         |                    |
| >     |                              |         |                    |
|  this |                              |         |                    |
| > i   |                              |         |                    |
| nform |                              |         |                    |
| ation |                              |         |                    |
| > s   |                              |         |                    |
| olely |                              |         |                    |
| > for |                              |         |                    |
| >     |                              |         |                    |
| sugge |                              |         |                    |
| sting |                              |         |                    |
| > im  |                              |         |                    |
| prove |                              |         |                    |
| ments |                              |         |                    |
| > to  |                              |         |                    |
| > the |                              |         |                    |
| > C   |                              |         |                    |
| ensus |                              |         |                    |
| > Bur |                              |         |                    |
| eau's |                              |         |                    |
| > ad  |                              |         |                    |
| dress |                              |         |                    |
| >     |                              |         |                    |
|  list |                              |         |                    |
| > and |                              |         |                    |
| >     |                              |         |                    |
| maps. |                              |         |                    |
| > All |                              |         |                    |
| > i   |                              |         |                    |
| ndivi |                              |         |                    |
| duals |                              |         |                    |
| >     |                              |         |                    |
|  from |                              |         |                    |
| >     |                              |         |                    |
|  your |                              |         |                    |
| > or  |                              |         |                    |
| ganiz |                              |         |                    |
| ation |                              |         |                    |
| > who |                              |         |                    |
| >     |                              |         |                    |
|  will |                              |         |                    |
| > be  |                              |         |                    |
| >     |                              |         |                    |
|  revi |                              |         |                    |
| ewing |                              |         |                    |
| > C   |                              |         |                    |
| ensus |                              |         |                    |
| > B   |                              |         |                    |
| ureau |                              |         |                    |
| >     |                              |         |                    |
|  addr |                              |         |                    |
| esses |                              |         |                    |
| >     |                              |         |                    |
|  must |                              |         |                    |
| >     |                              |         |                    |
|  sign |                              |         |                    |
| >     |                              |         |                    |
| below |                              |         |                    |
| > to  |                              |         |                    |
| > ind |                              |         |                    |
| icate |                              |         |                    |
| >     |                              |         |                    |
|  they |                              |         |                    |
| >     |                              |         |                    |
|  have |                              |         |                    |
| >     |                              |         |                    |
|  read |                              |         |                    |
| > and |                              |         |                    |
| >     |                              |         |                    |
| under |                              |         |                    |
| stand |                              |         |                    |
| > the |                              |         |                    |
| > C   |                              |         |                    |
| ensus |                              |         |                    |
| > Bur |                              |         |                    |
| eau's |                              |         |                    |
| >     |                              |         |                    |
| rules |                              |         |                    |
| >     |                              |         |                    |
|  rega |                              |         |                    |
| rding |                              |         |                    |
| > re  |                              |         |                    |
| stric |                              |         |                    |
| tions |                              |         |                    |
| > re  |                              |         |                    |
| lated |                              |         |                    |
| > to  |                              |         |                    |
| > co  |                              |         |                    |
| nfide |                              |         |                    |
| ntial |                              |         |                    |
| > in  |                              |         |                    |
| forma |                              |         |                    |
| tion. |                              |         |                    |
| >     |                              |         |                    |
|  Upon |                              |         |                    |
| > si  |                              |         |                    |
| gning |                              |         |                    |
| >     |                              |         |                    |
|  this |                              |         |                    |
| >     |                              |         |                    |
| agree |                              |         |                    |
| ment, |                              |         |                    |
| >     |                              |         |                    |
|  your |                              |         |                    |
| > go  |                              |         |                    |
| vernm |                              |         |                    |
| ental |                              |         |                    |
| >     |                              |         |                    |
|  unit |                              |         |                    |
| > a   |                              |         |                    |
| grees |                              |         |                    |
| > to  |                              |         |                    |
| > de  |                              |         |                    |
| stroy |                              |         |                    |
| > a   |                              |         |                    |
| nd/or |                              |         |                    |
| > r   |                              |         |                    |
| eturn |                              |         |                    |
| > all |                              |         |                    |
| >     |                              |         |                    |
| Title |                              |         |                    |
| > 13, |                              |         |                    |
| > C   |                              |         |                    |
| ensus |                              |         |                    |
| > B   |                              |         |                    |
| ureau |                              |         |                    |
| > co  |                              |         |                    |
| nfide |                              |         |                    |
| ntial |                              |         |                    |
| >     |                              |         |                    |
|  mate |                              |         |                    |
| rials |                              |         |                    |
| > to  |                              |         |                    |
| > the |                              |         |                    |
| > C   |                              |         |                    |
| ensus |                              |         |                    |
| > B   |                              |         |                    |
| ureau |                              |         |                    |
| >     |                              |         |                    |
| after |                              |         |                    |
| >     |                              |         |                    |
|  revi |                              |         |                    |
| ewing |                              |         |                    |
| >     |                              |         |                    |
|  your |                              |         |                    |
| >     |                              |         |                    |
|  LUCA |                              |         |                    |
| > Pr  |                              |         |                    |
| ogram |                              |         |                    |
| > fee |                              |         |                    |
| dback |                              |         |                    |
| >     |                              |         |                    |
| mater |                              |         |                    |
| ials. |                              |         |                    |
| > In  |                              |         |                    |
| >     |                              |         |                    |
|  addi |                              |         |                    |
| tion, |                              |         |                    |
| >     |                              |         |                    |
| those |                              |         |                    |
| > who |                              |         |                    |
| >     |                              |         |                    |
|  sign |                              |         |                    |
| > the |                              |         |                    |
| >     |                              |         |                    |
|  agre |                              |         |                    |
| ement |                              |         |                    |
| > ind |                              |         |                    |
| icate |                              |         |                    |
| >     |                              |         |                    |
|  they |                              |         |                    |
| >     |                              |         |                    |
|  that |                              |         |                    |
| >     |                              |         |                    |
| under |                              |         |                    |
| stand |                              |         |                    |
| > the |                              |         |                    |
| > pe  |                              |         |                    |
| nalty |                              |         |                    |
| > for |                              |         |                    |
| >     |                              |         |                    |
| discl |                              |         |                    |
| osing |                              |         |                    |
| > i   |                              |         |                    |
| nform |                              |         |                    |
| ation |                              |         |                    |
| >     |                              |         |                    |
| about |                              |         |                    |
| >     |                              |         |                    |
|  addr |                              |         |                    |
| esses |                              |         |                    |
| > or  |                              |         |                    |
| > i   |                              |         |                    |
| ndivi |                              |         |                    |
| duals |                              |         |                    |
| > obt |                              |         |                    |
| ained |                              |         |                    |
| > by  |                              |         |                    |
| > the |                              |         |                    |
| > C   |                              |         |                    |
| ensus |                              |         |                    |
| > Bu  |                              |         |                    |
| reau, |                              |         |                    |
| >     |                              |         |                    |
|  incl |                              |         |                    |
| uding |                              |         |                    |
| >     |                              |         |                    |
|  maps |                              |         |                    |
| >     |                              |         |                    |
|  that |                              |         |                    |
| > co  |                              |         |                    |
| ntain |                              |         |                    |
| >     |                              |         |                    |
|  stru |                              |         |                    |
| cture |                              |         |                    |
| > p   |                              |         |                    |
| oints |                              |         |                    |
| > sh  |                              |         |                    |
| owing |                              |         |                    |
| > the |                              |         |                    |
| > loc |                              |         |                    |
| ation |                              |         |                    |
| > of  |                              |         |                    |
| > ho  |                              |         |                    |
| using |                              |         |                    |
| >     |                              |         |                    |
| units |                              |         |                    |
| > or  |                              |         |                    |
| >     |                              |         |                    |
| group |                              |         |                    |
| >     |                              |         |                    |
|  quar |                              |         |                    |
| ters, |                              |         |                    |
| > is  |                              |         |                    |
| > a   |                              |         |                    |
| >     |                              |         |                    |
|  fine |                              |         |                    |
| > of  |                              |         |                    |
| > not |                              |         |                    |
| >     |                              |         |                    |
|  more |                              |         |                    |
| >     |                              |         |                    |
|  than |                              |         |                    |
| >     |                              |         |                    |
| \$250 |                              |         |                    |
| ,000, |                              |         |                    |
| > or  |                              |         |                    |
| > im  |                              |         |                    |
| priso |                              |         |                    |
| nment |                              |         |                    |
| > for |                              |         |                    |
| > not |                              |         |                    |
| >     |                              |         |                    |
|  more |                              |         |                    |
| >     |                              |         |                    |
|  than |                              |         |                    |
| > 5   |                              |         |                    |
| > y   |                              |         |                    |
| ears, |                              |         |                    |
| > or  |                              |         |                    |
| >     |                              |         |                    |
| both. |                              |         |                    |
| > Alt |                              |         |                    |
| hough |                              |         |                    |
| > a   |                              |         |                    |
| ccess |                              |         |                    |
| > to  |                              |         |                    |
| > the |                              |         |                    |
| >     |                              |         |                    |
|  data |                              |         |                    |
| > is  |                              |         |                    |
| >     |                              |         |                    |
| tempo |                              |         |                    |
| rary, |                              |         |                    |
| >     |                              |         |                    |
|  this |                              |         |                    |
| >     |                              |         |                    |
| commi |                              |         |                    |
| tment |                              |         |                    |
| > is  |                              |         |                    |
| >     |                              |         |                    |
| perma |                              |         |                    |
| nent. |                              |         |                    |
+-------+------------------------------+---------+--------------------+
| **D   | **Liaison's Printed Name and | **Te    | **Your address, if |
| ate** | Signature**                  | lephone | different from     |
|       |                              | N       | above**            |
|       |                              | umber** |                    |
+-------+------------------------------+---------+--------------------+
|       |                              |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Printed Name*               |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Signature*                  |         | *City State ZIP    |
|       |                              |         | Code*              |
+-------+------------------------------+---------+--------------------+
| **D   | **Reviewers' Printed Name(s) | **Te    | **Your address, if |
| ate** | and Signature(s)**           | lephone | different from     |
|       |                              | N       | above**            |
|       |                              | umber** |                    |
+-------+------------------------------+---------+--------------------+
|       |                              |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Printed Name*               |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Signature*                  |         | *City State ZIP    |
|       |                              |         | Code*              |
+-------+------------------------------+---------+--------------------+
|       |                              |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Printed Name*               |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Signature*                  |         | *City State ZIP    |
|       |                              |         | Code*              |
+-------+------------------------------+---------+--------------------+
|       |                              |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Printed Name*               |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Signature*                  |         | *City State ZIP    |
|       |                              |         | Code*              |
+-------+------------------------------+---------+--------------------+
|       |                              |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Printed Name*               |         |                    |
+-------+------------------------------+---------+--------------------+
|       | *Signature*                  |         | *City State ZIP    |
|       |                              |         | Code*              |
+-------+------------------------------+---------+--------------------+

*If you require more signature blocks, you may duplicate this form.*

*You may **FAX** this form to the number listed on the back for your
Census Bureau Regional Office*

### Appendix C Boundary and Annexation Survey (BAS) Paper Map {#appendix-c-boundary-and-annexation-survey-bas-paper-map .Style-Heading-3-+-Right:---0.5\"}

> The Census Bureau conducts the Boundary and Annexation Survey (BAS)
> each year to determine the inventory of correct names, legal
> descriptions, and legal boundaries of counties and equivalent
> entities, minor civil divisions, incorporated places, American Indian
> reservations, and American off-reservation trust lands. Title 13,
> U.S.C. authorizes this voluntary survey. Specifically, the Census
> Bureau requests up-to-date boundary information for local governments
> and information on the legal actions associated with the changed
> boundaries. The Census Bureau enters all boundary and area information
> obtained through the BAS into the TIGER^^ database so that all
> subsequent map and address list products reflect these changes.
>
> **Boundary Changes**
>
> During your review, you may find that the boundary for your
> jurisdiction, as shown on the Census Bureau map, does not depict the
> correct current location. If there is a discrepancy, you can correct
> the Census Bureau map to reflect the current boundary for your
> jurisdiction and complete the signature box located in the lower right
> corner on the map. For the Census Bureau to process this correction
> you must complete the 2008 Census Dress Rehearsal LUCA Annexations and
> Detachments form found in *Appendix E*. Photocopy this form if you
> need additional pages. It is not necessary to correct the Address
> List. Addresses are geocoded[^13] to the correct jurisdiction when the
> Census Bureau digitizes the maps.
>
> Using a **red** pencil, update the Census Bureau map as shown in
> Figure C.1.

-   Draw the new boundary in its correct location and cross out the
    portion of the old boundary using a string of red "**X**'s".

-   Add the ordinance number or other legal identifier of the action
    authorizing the change, along with the effective date of each
    annexation or detachment that you draw on the map.

-   Complete the red signature box found in the lower right corner of
    the Census Bureau map as shown in Figure C.2.

> **Note:** If the boundary change represents a correction to the Census
> Bureau map where the boundary was previously reported correctly, but
> not digitized accurately, correct the location of the boundary using a
> **red** pencil, and annotate with the letters "**BC**" for boundary
> correction next to the corrected line as shown in Figure C.2.

-   If a boundary is shown as coincident with a feature, but the feature
    location is not shown correctly, use a **purple pencil** to cross
    out the incorrect feature location and redraw the feature in
    **purple pencil** in the correct location. There is no need to make
    any annotation to the boundary.

```{=html}
<!-- -->
```
-   Complete the 2008 Census Dress Rehearsal LUCA Annexation and
    Detachment form found in *Appendix E.* Figure C.3 provides an
    example of a completed form.

> **Note:** Use the 5-digit FIPS code in the subject matter area of your
> map. (Minor civil division FIPS codes are in red, while incorporated
> place codes are in green.)

[]{#__RefHeading___Toc137619591 .anchor}Figure C.1: Boundary Changes

### ![](media/image9.png){width="3.4484251968503936in" height="4.631102362204724in"} {#section-50 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-51 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-52 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-53 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-54 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-55 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-56 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-57 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-58 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-59 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-60 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-61 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-62 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-63 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-64 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-65 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-66 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-67 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-68 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-69 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-70 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-71 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-72 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-73 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-74 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-75 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-76 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-77 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-78 .Style-Heading-3-+-Right:---0.5\"}

[]{#__RefHeading___Toc137619592 .anchor}Figure C.2: Signature Box

![](media/image10.png){width="5.970138888888889in"
height="1.9520833333333334in"}

[]{#__RefHeading___Toc137619593 .anchor}Figure C.3: Example of a
Completed Annexations and Detachments Form

**2008 Census Dress Rehearsal**

**Local Update of Census Addresses (LUCA) Program**

**Annexations and Detachments Form**

Please print or type the information about your government in the boxes
below.

**Government Name Mitchell, Wyoming**

**Entity Code\* 56789**

**[PERSON COMPLETING THIS FORM]{.mark}**

**Signature** Joan A. Smith

**Your Name (Printed) Joan A. Smith**

**Title City Clerk**

**[Telephone]{.mark} (800) 555-9876**

**[FAX]{.mark} (800) 555-9876 [E-Mail Address]{.mark}
smithj@mitchell.com**

Record below the information requested for all annexations (A) or
detachments (D) that you have added to the 2008 Dress Rehearsal LUCA
program map(s). Be sure that you put the authorization number and
effective date in or near the area on the map. The Census Bureau will
supply this information to the state certifying agency for your state;
please ensure that you properly file all legal changes with your state
government in accordance with your state's laws.

+-----+------------+---------+----------+-----------+----------------+
| **T | **Autho    | **Ef    | **County | **Minor   | **Estimated    |
| ype | rization** | fective | or       | Civil     | Area**         |
| o   |            | date**  | parish** | Division  |                |
| f** | ***Enter   |         |          | (if any)  | **Square miles |
|     | in column  | ***Mon  | **in     | in        | o r Acres (in  |
| *   | 2 -***     | th/day/ | which**  | which**   | hundredths)    |
| *Ch |            | year*** |          |           | (in tenths)**  |
| ang | O **--     |         | A        | A         |                |
| e** | O          | **(4)** | **(annex | **(anne   | **(7) (8)**    |
|     | rdinance** |         | ation)** | xation)** |                |
| A   |            |         |          |           |                |
| **o | R **--     |         | D        | D         |                |
| r** | Re         |         | **(detac | **(deta   |                |
| D   | solution** |         | hment)** | chment)** |                |
|     |            |         |          |           |                |
| *   | L **--     |         | **or**   | **or**    |                |
| *(1 | Local      |         |          |           |                |
| )** | Law**      |         | O        | O         |                |
|     |            |         | *        | **(other) |                |
|     | S **--     |         | *(other) | o         |                |
|     | S          |         | oc       | ccurred** |                |
|     | tate-level |         | curred** |           |                |
|     | action**   |         |          | **(6)**   |                |
|     |            |         | **(5)**  |           |                |
|     | X **--     |         |          |           |                |
|     | Other      |         |          |           |                |
|     | type**     |         |          |           |                |
|     |            |         |          |           |                |
|     | **Type     |         |          |           |                |
|     | Number**   |         |          |           |                |
|     |            |         |          |           |                |
|     | **(2)      |         |          |           |                |
|     | (3)**      |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
| A   | O 01-3     | 3/      | Cameron  |           | 8 sq miles     |
|     |            | 13/2005 |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+

D-1642

###  {#section-79 .Style-Heading-3-+-Right:---0.5\"}

***\*** Use the 5-digit FIPS code in the subject matter area of your
map. (Minor civil division FIPS codes are in red, while*

*incorporated place codes are in green.)*

###  {#section-80 .Style-Heading-3-+-Dark-Teal .unnumbered}

### Appendix D Boundary and Annexation Survey (BAS) Digital File Submission {#appendix-d-boundary-and-annexation-survey-bas-digital-file-submission .Style-Heading-3-+-Dark-Teal}

*This user guide is included for your reference as a supplement to the
LUCA Program*

**Digital BAS Guidelines Supplement Boundary and Annexation Survey (BAS)
User's Guide**

**1. Introduction 57**

**2. Digital BAS Submission Requirements 57**

**3. Topologically Integrated Geographic Encoding and Referencing System
(TIGER^^) and Master Address File (MAF) 58**

**4. MAF/TIGER Accuracy Improvement Project (MTAIP) 59**

**5. Census Provided Shapefiles 59**

**6. Updating the Provided Shapefile 60**

> 6.1 General File Setup Guidelines 60
>
> 6.2 Changing Our Coordinate System to Match Yours 61
>
> 6.3 Annexations, Deannexations and Boundary Corrections 61

Example 1: Shapefile Example of County Update for Two Entities 63

> Example 2: New Place Annexation 64
>
> Example 3: Annexation with Geographic Offset 65
>
> Example 4: Union 66
>
> Example 5: MCD Annexation 67
>
> Example 6: Changes in One Layer 68
>
> Example 7: Example 6 Extract 68
>
> Example 8: Current Entity Boundaries for Updated Entities 69
>
> 6.4 Feature Information (Optional) 70
>
> Example 9: Road Correction Examples 72
>
> Example 10: Example 9 Extract 73
>
> 6.5 Address Information 73
>
> 6.6 Metadata and Data Dictionary 73
>
> 6.7 File Submission 73

**7. Submitting BAS Form via Electronic BAS 20**

> Appendix D 1 -- Coding Scheme 77
>
> Appendix D 2 -- Data Dictionary 79
>
> Appendix D 3 -- Metadata Requirements 82
>
> Appendix D 4 -- Flowchart 84
>
> Appendix D 5 -- Flowchart Boundary Update Example 86

**1. Introduction**

> The U.S. Census Bureau conducts an annual survey called the Boundary
> and Annexation Survey (BAS) to collect information about selected
> legally defined geographic areas, such as counties, cities, and towns.
> The BAS also provides an opportunity for participants to review the
> names and geographic relationships for these areas. The BAS
> information is used to provide an appropriate record for reporting the
> results of the decennial and economic censuses, and to support the
> population estimates program and the American Community Survey. In
> compliance with the Office of Management and Budget Circular A-16, the
> BAS supports the spatial data steward responsibilities of the
> Geospatial One-Stop by updating the inventory of, and boundaries, for
> governmental units. In addition, the BAS is the source of up-to-date
> information on boundaries, codes, and names for the U. S. Geological
> Survey's (USGS) National Map, the Federal Information Processing
> Standards (FIPS) program and the Geographic Names Information System.
> The BAS is also the source for changes in the boundaries of
> incorporated places, minor civil divisions (MCDs), counties, and
> federally recognized American Indian Areas, which include reservations
> and off-reservation trust lands.

**2. Digital BAS Submission Requirements**

> The Digital BAS program is an added option to report changes for the
> BAS. In order to facilitate the accurate transfer of boundary data
> from our Digital BAS partners and to aide in their ability to analyze
> and understand the differences between the Topologically Integrated
> Geographic Encoding and Referencing System (TIGER^^) and local files,
> the Census Bureau has created new guidelines and procedures for the
> submission of digital files for BAS. This process will allow
> participants to submit changes via updating shapefiles created from a
> version of the Census Bureau's TIGER^^. The new process allows the
> Census Bureau to process boundary changes, corrections, and
> differences between files. To participate in the Digital BAS program,
> you must meet the following requirements:

-   Your county must have completed the realignment process for the
    MAF/TIGER Accuracy Improvement Project (MTAIP). The current list of
    counties that have completed the realignment process is posted on
    our Web site at
    <http://www.census.gov/geo/www/bas/bashome.html>**.**

-   You must provide information for the BAS point of contact, the
    person updating the shapefiles, and the highest elected official for
    your entity (See form at end of document for required data.).

-   You must have the ability to edit a Census Bureau shapefile extract
    of your entity.

> If you have questions or concerns about the participation
> requirements, please contact a member of the BAS team at 301-763-1099
> or e-mail
>
> geo.bas@census.gov with your contact information and someone will
> respond.

**3. Topologically Integrated Geographic Encoding and Referencing
System**

**(TIGER^^) and Master Address File (MAF)**

> The Geography Division of the Census Bureau is responsible for
> developing geographic applications and executing the geographic and
> cartographic activities needed to support the Census Bureau in
> collecting and disseminating census data. For the last 20 years, the
> Census Bureau's Topologically Integrated Geographic Encoding and
> Referencing System (TIGER^^) and Master Address File (MAF) have
> become the two most critical geographic resources for supporting the
> Census Bureau in its collection and dissemination of data.
>
> The Census Bureau's TIGER^^ system automates the mapping and related
> geographic activities required to support the decennial census and
> sample survey programs of the Census Bureau starting with the 1990
> decennial census. The TIGER^^ database includes geographic features
> such as roads, railroads, water, boundaries, and other geographic
> information needed to support the programs of the Census Bureau. In
> addition, the TIGER^^ database is repository of street address
> ranges, ZIP codes, and feature names. However, note that TIGER^^ does
> not contain specific addresses. TIGER^^ is a topologically integrated
> geographic database, in which the topological structures of TIGER^^
> define the location and relationship of streets, rivers, railroads,
> and other features to each other and to the numerous geographic
> entities for which the Census Bureau tabulates data for its censuses
> and sample surveys. Because TIGER^^ is an integrated database where
> all boundaries and features reside within one layer, we must adhere to
> strict topology rules and be cognizant of feature/boundary
> relationships when making modifications to entities in TIGER^^. If
> you are interested in acquiring more information about the Census
> Bureau's TIGER^^ database and products, please visit the following
> Web site http://www.census.gov/geo/www/tiger/index.html.
>
> To assemble accurate address data that could be maintained and
> updated, the Census Bureau developed the MAF in the 1990s. The MAF
> includes addresses that allow census forms to be mailed and, in some
> cases, provide descriptions of living quarters enabling census
> enumerators to deliver forms. In addition, the MAF has a geocoding
> linkage to the postal information in TIGER^^. Although TIGER^^ is
> part of the public domain, the MAF is restricted from public use by
> Title 13 of the U.S. Code.

**4. MAF/TIGER Accuracy Improvement Project (MTAIP)**

The Census Bureau has embarked on an initiative to enhance and
streamline the

> MAF/TIGER system. This effort is referred to as MTAIP. The Census
> Bureau's goal for MTAIP is to spatially improve features and
> boundaries in the TIGER^^ database. The Census Bureau is currently in
> the process of updating TIGER^^ based on digital files submitted by
> state, local, and tribal governments. This is because many state,
> local, and tribal governments have geographic information systems
> (GIS) that maintain a significantly greater positional accuracy than
> that in the TIGER^^ database and meet our minimum accuracy
> requirements. Once acquired, the Census Bureau evaluates the various
> layers associated with the file(s) submitted and determines whether
> the file(s) can be used for the MTAIP process. Because we are
> improving feature and boundary coordinates based on state, local, and
> tribal MTAIP submissions there is a greater likelihood that Digital
> BAS submissions from the aforementioned governments will closely align
> with modified TIGER^^ making both boundary corrections and changes
> easier to identify. This will also create a solid common geographic
> foundation for future boundary exchanges for governments that have
> participated in the MTAIP process. If you have additional questions
> about the MTAIP process, please contact a geographer at your Census
> Bureau Regional Office listed on the back cover.

**5. Census Provided Shapefiles**

> The Census Bureau is providing all Digital BAS participants with
> entity layers in
>
> Environmental Systems Research Institute (ESRI) shapefile format[^14].
> The number of polygon-based shapefiles that the Census Bureau sends to
> each Digital BAS participant depends on the type of entities contained
> within each county. However, each participant, regardless of the
> number of geographic entities, receives only one shapefile for the
> linear feature network for the county.

All shapefiles, provided by the Census Bureau, are in the following
unprojected

geographic based coordinate system:

> GCS_NAD83,
>
> Angular Unit: Degree (0.017453292519943299),
>
> Prime Meridian: Greenwich (0.000000000000000000),
>
> Datum: D_North_American_1983,
>
> Spheroid: GRS_1980,
>
> Semi-major Axis: 6378137.000000000000000000,
>
> Semi-minor Axis: 6356752.314140356100000000, and
>
> Inverse Flattening: 298.257222101000020000.
>
> Please feel free to project these files into your local coordinate
> system/projection. After completing your updates, you may submit the
> boundary shapefile using your local coordinate system/projection
> provided that the shapefile\'s coordinate system contains a defined
> projection file (e.g., \*.PRJ file) and spatial reference materials
> (e.g., metadata).

**6. Updating the Provided Shapefile**

> The following will describe how to update the Census provided
> shapefiles to reflect corrections to your boundary or changes that may
> have occurred since the last BAS survey. You may also use the
> following procedures to submit information documenting the creation of
> new incorporations and dissolutions of incorporated places, MCDs,
> counties, and county equivalent areas. Please use the feature layers
> provided to create edits, which maintain accurate boundary to feature
> relationships. This is important since TIGER^^ is a topologically
> integrated system.
>
> In order to update our digital file, overlay our digital boundary file
> with your entity's individual boundary shapefile. Code each boundary
> update with the appropriate boundary coding scheme found in Appendix
> D 1. The data dictionary in Appendix D 2 will provide you with field
> definitions and naming conventions used for updating the attribute
> table with the appropriate boundary codes. The following subsections
> will provide detailed explanations and examples of the boundary update
> process. As a supplement, flowcharts can be located in Appendixes D 4
> and D 5 to aide in the boundary update and submission processes.
>
> If we have any problems processing the boundary file which you
> submitted, a member of the Census Bureau's BAS team will get in touch
> with the point of contact to clarify the issue. If we cannot clarify
> the problem prior to our project deadline, the updates will not be
> incorporated into TIGER^^. We will continue to try to resolve these
> issues before the next BAS cycle.

**6.1 General File Setup Guidelines**

> Upon receipt of your shapefile, please follow the setup guidelines
> listed below before beginning actual updates:

-   open the CD and enclosed zip file to ensure it contains the
    shapefiles for your entity,

-   copy and decompress shapefiles to a directory on your server or hard
    drive, and

-   open the shapefiles in a GIS.

**6.2 Changing Our Coordinate System to Match Yours**

> Our files are in GCS NAD83 format. The spatial referencing information
> is also stored in each shapefile\'s \*.PRJ file. Most GIS software
> packages contain projection wizards, or something similar, that allows
> the user to transform file coordinate systems and projections. For
> example, if your office uses ArcView to update files, please activate
> and utilize ArcView's 'Projection Utility Wizard' extension. If using
> ArcGIS, please use its 'Projection Utilities' in ArcToolbox. TIGER^^
> extract shapefiles contain defined projection information in the
> \*.PRJ file. Both ArcView and ArcGIS access the \*.PRJ file for
> projection information; therefore, there is no need for you to define
> these parameters before changing the file coordinate systems.

**6.3 Annexations, Deannexations, and Boundary Corrections:** (Areas
added, deleted,

or corrected for your entity)

> The Census Bureau has provided shapefiles for all entities that are
> eligible for update as part of the BAS. Select the shapefile that
> contains the entity requiring updates, and make all revisions to that
> shapefile. Once all updates are completed, create a new polygon layer
> that contains only the new updates that you would like the Census
> Bureau to make for your entity(s). If a boundary update crosses into a
> new county and additional shapefiles are needed, please contact a BAS
> team member at 301-763-1099, or send e-mail to geo.bas@census.gov.
>
> Geographic corridors and offsets can be submitted through the Digital
> BAS process. Please refer to the 2006 BAS User's Guide for definitions
> of Geographic Corridors (formerly Corporate Corridors) and Geographic
> Offsets (formerly Corporate Offsets).
> http://www.census.gov/geo/www/bas/bashome.html
>
> For your reference, we are providing detailed examples of how you can
> update the
>
> Shapefiles. For example, a county planner wishes to make two
> annexations for a place within their county. Although there are many
> ways to use GIS to accomplish these updates, we are providing one
> suggested method:

-   Make a copy of the Census Bureau place shapefile.

-   Make all updates to the newly created layer using GIS editing
    techniques (as a reminder, please use the Census Bureau provided
    linear features layer as a referencing guide when making boundary
    placement decisions) (See Examples 2-3).

-   Union the modified place layer with the original Census Bureau place
    shapefile to identify the changes which you made (See Example 4).

-   Create a new polygon layer by selecting the change polygons from the
    newly created unionized layer. Be sure to only select the change
    polygons before exporting to a new file (See Examples 5-6)

-   Populate the various BAS-related fields in the polygon's attribute
    table with annexation information and other census related codes
    (use the coding scheme in Appendix D 1 for information on how to
    fill-in the CHNG_TYPE field because every change polygon requires a
    code - See Example 7).

> If more than one level of geography requires updating (e.g., MCDs and
> places), continue making updates to each layer using methods similar
> to those mentioned above. Merge all the change polygons for the
> modified boundary layers into one change polygon layer.
>
> The attribute table should contain all BAS-related fields (e.g.,
> annexation date, ordinance number, etc.), and the various levels of
> geography being updated. The spatial examples illustrate how to make
> updates to our spatial layers for two entities, at different
> geographic levels.
>
> *Note: If you are utilizing ArcGIS 9.x software you may simplify the
> process by using the 'Symmetrical Difference' and 'Multipart to
> Singlepart' tools in ArcToolbox. Instead of creating a union between
> the modified layer and the Census Bureau layer you may use the
> 'Symmetrical Difference' tool. Input the modified feature layer into
> the 'Input Features' box and the Census Bureau layer into the 'Union
> Features' box. This will provide you with a change polygon layer. In
> order to separate the grouped change polygons into single change
> polygons, utilize the 'Multipart to Singlepart' tool. This will free
> you from having to select change polygons from the union layer and
> then use XTOOLS or REGIONPOLY to separate your change polygons. The
> remainder of the process will stay the same.*

**Example 1**

![](media/image11.png){width="5.999305555555556in"
height="6.370138888888889in"}

This example depicts two entities (e.g., MCD and place) from the Census
Bureau provided shapefiles that County A wishes to update. Note, make
copies of all Census Bureau shapefiles that you wish to update and make
changes only to those copied versions.

**Example 2**

![](media/image12.png){width="5.995833333333334in"
height="6.002777777777778in"}

The participant made two updates to the copied version of Place A's
Census Bureau provided place boundary, using the linear feature network
provided by the Census Bureau (e.g., DB06\<ST\>\<COU\>AllLines.shp) as a
guide for boundary placement. These updates were made using various GIS
editing methods (e.g., vertex edit in ArcView).

**Example 3**

![](media/image13.png){width="5.993055555555555in"
height="6.152083333333334in"}

In the above example, one of Place A's two annexations involves a
geographic offset 35 feet from a road feature. In the change polygon
attribute table, the participant must populate the CHNG_TYPE field with
a 'AO' code. This code alerts the Census Bureau that an annexation is
offset from a feature. In addition, the participant will also populate
the OFFSET field in the polygon's attribute table with the distance
value that the boundary is offset from the road (See Example 7 below).

**Example 4**

**Place A Union**

![](media/image14.png){width="5.993055555555555in"
height="5.495138888888889in"}

Upon completion of your boundary updates for a particular entity, union
the modified copy and the original to create a layer that contains only
separate change polygons. However, if multiple changes occurred to one
entity (see above), the result of the union is a multipart shape record.
In order for the participant to input all the necessary annexation
related information into the attribute table, each polygon must be a
separate record. There are several methods for creating single parts
from multipart shapes (e.g., XTOOL extension for ArcView or ArcGIS,
REGIONPOLY in ArcInfo, etc), so please ensure that each polygon has its
own record in the attribute table. If each polygon does not have its own
record, the Census Bureau may be unable to process your changes.

**Example 5**

![](media/image15.png){width="5.993055555555555in"
height="5.601388888888889in"}

In the above example, MCD A is annexing a piece of MCD B. Therefore, MCD
B is losing territory to MCD A. Using similar editing techniques used in
Example 4 for places, you should have one polygon record for each
update. Create a change polygon layer for the MCD boundary change.

**Example 6**

> ![](media/image16.png){width="5.997916666666667in"
> height="5.518055555555556in"}

At this point you will have two change polygon layers (place and MCD).
Please merge those two layers into one polygon layer. This can be done
by using the "merge" GIS geoprocessing tool. Example 6 depicts the
change layer the Census Bureau requires for Digital BAS submissions.

**Example 7**

![](media/image17.png){width="5.998611111111111in" height="1.04375in"}

This table extract is from Example 6. Note: the first record in the
table is the geographic offset depicted in Example 3. Remember to use
actual state/county/entity FIPS codes for the state, county, MCD, and
place fields above. Also remember to use actual local codes in the
LEGAL_DOC field.

**Example 8**

![](media/image18.png){width="5.997222222222222in"
height="5.915277777777778in"}

In the example above, the participant will submit two more layers
(current place and MCD boundaries) in addition to the layer containing
the change polygons. Therefore, the participant for this county will
submit a total of three layers to the Census Bureau unless feature
updates are being included along with boundary submissions. If feature
updates accompany the boundary layers, then the total number will be
four (See Example 9).

**6.4 Feature Information (Optional)**

> The Census Bureau will collect feature changes designated by the
> participant. Please note that all feature-related update processing
> occurs at a different location and time within the Census Bureau. This
> may delay the inclusion of your feature updates on next year's BAS
> maps. If you have reviewed your features using our line feature
> network and have determined that the Census Bureau needs to add,
> remove, or rename features in a given area, you may submit your
> modifications in a separate layer. If your entity requires a large
> number of feature changes (\>50), please contact the Census Bureau
> Regional Office for your area to discuss sending them your updates. To
> locate the Regional Office for your area, please click the link below:
>
> <http://www.census.gov/field/www/>
>
> *Note: In the future, large numbers of feature changes will be made
> through a program called the Automated Feature and Attribute Update
> System (AFAUS). AFAUS will have the ability to add new road features,
> names, and address ranges to the MAF/TIGER database directly from
> local GIS files (we cannot process scanned maps or cadastral boundary
> files). The files must represent road centerlines (and eventually
> other feature types). The update process will be able to match local
> features to the MAF/TIGER database and update it with new and revised
> information. The Census Bureau will evaluate local files provided. The
> AFAUS is scheduled to begin production in 2007.*
>
> *There is no guarantee that street and name updates from local files
> will appear in the next BAS update cycle products at this time.*
>
> Please use the appropriate update code located in the coding scheme
> (Appendix D 1) to identify the type of feature modification being
> submitted. If any issues arise with the feature layer, which you
> submitted, a member of the BAS team will attempt to contact the
> respondent to clarify the issue. If clarification is not made prior to
> our project deadline, the updates may not be incorporated into
> TIGER^^. These updates will then be held in suspense until
> clarification has been made.
>
> *6.4.1 Updating the Feature Shapefile (See Examples 9 and 10)*
>
> Create a new line layer which includes the following feature updates:

-   Each change must contain a separate line record for each update made
    to the file, and

-   Each update related line must contain one of the codes listed in the
    coding scheme (Appendix D 1) and that code must be recorded in the
    attribute field for the line.

> *6.4.2 Displaying Features Based on CFCC1*
>
> Within the \*.shp file you may want to display different feature types
> based on the Census Feature Class Code (CFCC1). For example, you may
> want to display all roads in black,hydro features in blue, etc. Some
> of the CFCC1 values listed below may not appear in the shapefiles you
> have, but for your reference:

-   'A'  Roads

-   'B'  Railroad

-   'C'  Miscellaneous Ground Transportation

-   'D'  Landmark

-   'E'  Physical Feature

-   'F'  Nonvisible Features (such as boundaries for incorporated

-   places, counties, school districts, etc.)

-   'G'  US Census Bureau Usage (for internal programs)

-   'H'  Hydrography

-   'P'  Provisional Features

-   'X'  Not Yet Classified

> For more detailed information on CFCC's, you can refer to pp. 3-28 to
> 3-45 of the most recent TIGER/Line^^ documentation at:
>
> http://www.census.gov/geo/www/tiger/index.html

**Example 9**

![](media/image19.png){width="5.992361111111111in"
height="5.5777777777777775in"}

This example consists of road corrections that you may wish to submit in
addition to your boundary update layers. Please create a separate layer
containing just those road segments that you would the like the Census
Bureau to add, remove, or rename. Include this layer along with all the
other required boundary layers in your return submission to the Census
Bureau.

**Example 10**

![](media/image20.png){width="5.997916666666667in"
height="3.060416666666667in"}

This is a table extract from Example 9. The participant is only required
to provide

CHNG_TYPE and FENAME information for each road change. The "TLID,"
"CFCC," "CFCC1," and "Fidelity" fields are informational fields that do
not require filling by the participant.

**6.5 Address Information**

> The Census Bureau will not collect address break information through
> Digital BAS in 2006. A process is being designed to capture this
> information digitally in future surveys. If you have an accurate
> address source that you would like to share with the Census Bureau at
> this time, please contact your Census Bureau Regional Office. Contact
> information can be found on the back cover.

**6.6 Metadata and Data Dictionary**

-   Submit a data dictionary, either as part of the metadata or as a
    separate file. (See Appendix D 2)

```{=html}
<!-- -->
```
-   A data dictionary describes the fields included in any data tables
    associated with your submission. A data dictionary should list all
    the fields, describe the data in each field, and provide the legal
    values and their definitions for each field.

```{=html}
<!-- -->
```
-   Submit appropriate metadata with your file (See Appendix D 3).

**6.7 File Submission**

> The Census Bureau requires the participant to submit at least two
> spatial layers with the potential of more (e.g., a layer containing
> road updates). These layers are described below:

-   *Change Polygon Layer (required)*

```{=html}
<!-- -->
```
-   This layer consists of all the changes that you would like the
    Census Bureau to make to your entity.

```{=html}
<!-- -->
```
-   *Whole Modified Entity Layer (required)*

```{=html}
<!-- -->
```
-   This layer should only contain the complete and current boundary for
    the entity being updated.

```{=html}
<!-- -->
```
-   *Feature Update Layer (required only if there are road additions,
    deletions, or name changes)*

```{=html}
<!-- -->
```
-   If you have road updates that you would like the Census Bureau to
    make, include this layer with just the road segments that you would
    like us to adjust.

> Use the following as a guide to be sure you have included all the
> required layers.
>
> *6.7.1 Change Polygon Layer*
>
> Name the return change polygon layer as the following where
> \<ST\>\<COU\> refers to the state/county FIPS code for your area:
>
> **DB06\_\<ST\>\<COU\>\_Changes.\***

-   The change polygon layer must include:

```{=html}
<!-- -->
```
-   a separate record for each polygon in the layer,

-   a code from the coding scheme (Appendix D 1), in the "CHNG_TYPE"
    field for

-   each record. No exceptions,

-   closed polygons,

-   legal document or ordinance numbers (except Georgia). This
    information goes in the "LEGAL_DOC" field,

-   effective dates,

-   acreage of each change polygon (for the State of Georgia only) in
    the "AREA" field, and

-   distance (in feet) in the "OFFSET" field if identified as on offset
    in the "CHNG_TYPE" field.

> *6.7.2 The Whole Modified Entity Layer*
>
> Name the whole modified entity layer as the following:
>
> **DB06\_\<ST\>\<COU\>\_WholeEntity\_\<{PLC, MCD or COU}\>.\***

-   The whole modified entity layer includes:

```{=html}
<!-- -->
```
-   the whole entity as it currently exists after updating (this is
    essentially an "outline" of your updated entity), and

-   the entity name and code (e.g., five-digit FIPS from the "PLACE"
    field and Name from the "PLC_NAME" field for places).

-   Please submit each level of geography in a separate whole entity
    layer and name as follows:

    -   Place  PLC

    -   Minor Civil Division  MCD

    -   County  COU

> *6.7.3 The Feature Update Layer (Optional)*
>
> Name the feature update layer as the following (this file is only
> required if making updates to your road features):
>
> **DB06\_\<ST\>\<COU\>\_RDUpdates.shp**

-   The feature update layer must include:

```{=html}
<!-- -->
```
-   a value in its "CHNG_TYPE" field that indicates the type of change,
    and

-   only feature updates (please do not include unmodified features).

> *6.7.4 Compressing the File*
>
> Compress all updated materials, Shapefile, Data Dictionary, and
> Metadata, into one ZIP formatted file called**:
> DB06\_\<ST\>\<COU\>\_Return.ZIP**. *(Please use PkZip or GZip software
> if possible).*
>
> *6.7.5 Submit File via File Transfer Protocol (FTP)*
>
> Please FTP all files to the following address:
>
> <ftp://ftp2.census.gov/pub/incoming/geo/Digital_BAS/>
>
> To submit your file you must obtain a user name and password. Contact
> a member of the BAS team at 301-763-1099, or geo.bas@census.gov to
> obtain your user name and password. If you contact the BAS team via
> e-mail include a phone number where we can reach you. This is
> necessary because we will not provide your FTP password in e-mail.
>
> *6.7.6 Additional Information*
>
> The Census Bureau recommends using FIPS codes to identify entities
> such as counties, county subdivisions, and places. Using a standard
> code scheme facilitates the digital exchange of data. The USGS
> maintains FIPS codes for incorporated places and MCDs. The codes can
> be obtained at:
>
> <http://geonames.usgs.gov/fips55.html>
>
> If you have any questions or problems, please contact us by e-mail at
>
> geo.bas@census.gov or telephone at 301-763-1099.

7.  **Submitting BAS form via Electronic BAS**

> Please complete and submit your BAS form through Electronic BAS using
> the
>
> instructions provided below.

-   Using Internet Explorer navigate to the BAS web site

```{=html}
<!-- -->
```
-   www.census.gov/geo/www/bas/bashome.html

    -   Select the appropriate BAS survey

        -   BAS 1: Incorporated Place Survey

        -   BAS 2: County or Statistically Equivalent Entity Survey

        -   BAS 3: Minor Civil Division (MCD) Survey

            -   Enter your 'User Name' and Password located under
                Special Instructions (pp. 2 for Places and MCDs and pp.
                5 for Counties) on your paper BAS form.

> *(Note: The User Name and Password are not the same as those obtained
> for the FTP process.)*

-   Enter the required information into Electronic BA

**Appendix D 1 - Coding Scheme**

**(CHNG_TYPE Field Information for both Change Polygon and Line
Layers)**

***Polygon Codes***

**Polygon Change Layer:**

> This participant-provided layer should contain a separate update
> polygon record for each update made to our files. Each update related
> polygon must contain one of the following codes.

+------+---------------------+----------------------------------------+
| **   | **[Transla          | **[Additional Requirements (if         |
| [Cod | tion]{.underline}** | applicable)]{.underline}**             |
| e]{. |                     |                                        |
| unde |                     |                                        |
| rlin |                     |                                        |
| e}** |                     |                                        |
+------+---------------------+----------------------------------------+
| A    | Annexation          | All polygons coded with an 'A' value   |
|      |                     | require an annexation effective date.  |
|      |                     | Note: Only supply ordinance and/or     |
|      |                     | area values if your state requires     |
|      |                     | such information.                      |
+------+---------------------+----------------------------------------+
| AO   | Geographic Offset   | Same requirements as 'A.' However,     |
|      |                     | supply an offset value (e.g., feet     |
|      |                     | from road feature) if your annexation  |
|      |                     | is offset from a road feature. An      |
|      |                     | offset requires a value in the         |
|      |                     | CHNG_TYPE field if the change polygon  |
|      |                     | contains an 'AO.' Note: If a polygon   |
|      |                     | gives the appearance of being offset   |
|      |                     | and does not contain an 'AO,' then the |
|      |                     | change polygon boundary will be        |
|      |                     | snapped to the nearest road            |
|      |                     | centerline. For a definition of        |
|      |                     | geographic offsets and corridors,      |
|      |                     | refer to the BAS User's Guide.         |
+------+---------------------+----------------------------------------+
| AC   | Geographic Corridor | Same requirements as 'AO.' However,    |
|      |                     | provide                                |
|      |                     |                                        |
|      |                     | change polygon with an 'AC' value if   |
|      |                     | annexation                             |
|      |                     |                                        |
|      |                     | creates a geographic corridor.         |
+------+---------------------+----------------------------------------+
| B    | Boundary Correction | Boundary corrections do not require    |
|      |                     | filling the                            |
|      |                     |                                        |
|      |                     | annexation, offset, or area fields     |
|      |                     | unless the correction involves offsets |
|      |                     | or geographic corridors. If a boundary |
|      |                     | correction creates an offset or a      |
|      |                     | corridor, assign one of the codes      |
|      |                     | documented below.                      |
+------+---------------------+----------------------------------------+
| BO   | Boundary Geographic | Same requirements as 'B' above,        |
|      | Offset              | however, provide                       |
|      |                     |                                        |
|      |                     | an offset distance (e.g., feet from    |
|      |                     | road feature).                         |
+------+---------------------+----------------------------------------+
| BC   | Boundary Geographic | Same requirements as 'B.' However,     |
|      |                     | provide a                              |
|      |                     |                                        |
|      |                     | Corridor geographic corridor distance  |
|      |                     | (e.g. feet from road feature).         |
+------+---------------------+----------------------------------------+

***Line Codes***

**Road Corrections:**

> After reviewing road features in our line feature network and you have
> determined that the Census Bureau needs to add, delete, or rename road
> features in a given area, you may submit, in a separate layer, your
> road modifications using one of the following codes to identify the
> type of road modification needed:

+-------+-------------------+------------------------------------------+
| **    | **[Translati      | **[Additional Requirements (if           |
| [Code | on]{.underline}** | applicable)]{.underline}**               |
| ]{.un |                   |                                          |
| derli |                   |                                          |
| ne}** |                   |                                          |
+-------+-------------------+------------------------------------------+
| NR    | New Road Feature  | Within the change line layer, please     |
|       |                   | code all new road segments with a 'NR'   |
|       |                   | value in the CHNG_TYPE field.            |
+-------+-------------------+------------------------------------------+
| CN    | Change Road Name  | If changing the name of a road feature,  |
|       |                   | code                                     |
|       |                   |                                          |
|       |                   | the line segment(s) with a 'CN' in the   |
|       |                   | CHNG_TYPE field and provide the road     |
|       |                   | feature's new name in the "FENAME field. |
+-------+-------------------+------------------------------------------+
| CF    | Change Feature    | If you are changing the feature class    |
|       | Class             | code for a                               |
|       |                   |                                          |
|       |                   | road, code the CHNG_TYPE field with a    |
|       |                   | 'CF.'                                    |
|       |                   |                                          |
|       |                   | For instance, a local road was           |
|       |                   | mistakenly coded as a                    |
|       |                   |                                          |
|       |                   | highway.                                 |
+-------+-------------------+------------------------------------------+
| DR    | Delete Road       | If deleting a road from you network,     |
|       |                   | please provide                           |
|       |                   |                                          |
|       |                   | all deleted road segments in a change    |
|       |                   | line layer and                           |
|       |                   |                                          |
|       |                   | code all deleted segments with a 'DR'    |
|       |                   | value in the                             |
|       |                   |                                          |
|       |                   | CHNG_TYPE field.                         |
+-------+-------------------+------------------------------------------+

> As mentioned in Section 6.4, the Census Bureau will collect any road
> modification designated by the participant. However, please note that
> all road-related updates are processed at a different location and
> time within the Census Bureau which may delay the inclusion of your
> road updates on next year's BAS maps.

**Appendix D 2 - Data Dictionary**

**[County Boundary Shapefile]{.underline}**

  --------------------- ---------------------- -------------------- -----------------------------
  [Field]{.underline}   [Length]{.underline}   [Type]{.underline}   [Description]{.underline}

  STATE                 2                      String               Current State FIPS Code

  COUNTY                3                      String               Current County FIPS Code

  COU_NAME              30                     String               Current County Name

  CHNG_TYPE             2                      String               Type of Digital BAS Area
                                                                    Update

  EFF_DATE              8                      String               Annexation Effective Date

  LEGAL_DOC             20                     String               Annexation Ordinance Number

  OFFSET                10                     String               Geographic Corridor or Offset
                                                                    Dist.

  AREA                  10                     Double               Acreage of Annexation
  --------------------- ---------------------- -------------------- -----------------------------

**[Consolidated City Shapefile]{.underline}**

  --------------------- ---------------------- -------------------- -----------------------------
  [Field]{.underline}   [Length]{.underline}   [Type]{.underline}   [Description]{.underline}

  STATE                 2                      String               Current State FIPS Code

  COUNTY                3                      String               Current County FIPS Code

  CONCITY               5                      String               Current Consolidated City
                                                                    FIPS

  CC_NAME               90                     String               Current Consolidated City
                                                                    Name

  CHNG_TYPE             2                      String               Type of Digital BAS Area
                                                                    Update

  EFF_DATE              8                      String               Annexation Effective Date

  LEGAL_DOC             20                     String               Annexation Ordinance Number

  OFFSET                10                     String               Geographic Corridor or Offset
                                                                    Dist.

  AREA                  10                     Double               Acreage of Annexation
  --------------------- ---------------------- -------------------- -----------------------------

**[Area Landmark Shapefile:]{.underline}**

  --------------------- ---------------------- -------------------- ----------------------------
  [Field]{.underline}   [Length]{.underline}   [Type]{.underline}   [Description]{.underline}

  LNDK_CFCC             3                      String               Area Landmark CFCC

  LNDK_CFCC1            1                      String               First Char. of Area Land.
                                                                    CFCC

  LNDK_NAME             90                     String               Primary Area Landmark Name
  --------------------- ---------------------- -------------------- ----------------------------

**[Minor Civil Division (MCD) Shapefile]{.underline}**

  --------------------- ---------------------- -------------------- -----------------------------
  [Field]{.underline}   [Length]{.underline}   [Type]{.underline}   [Description]{.underline}

  STATE                 2                      String               Current State FIPS Code

  COUNTY                3                      String               Current County FIPS Code

  MCD                   5                      String               Current MCD FIPS

  MCD_NAME              90                     String               Current MCD Name

  CHNG_TYPE             2                      String               Type of Digital BAS Area
                                                                    Update

  EFF_DATE              8                      String               Annexation Effective Date

  LEGAL_DOC             20                     String               Annexation Ordinance Number

  OFFSET                10                     String               Geographic Corridor or Offset
                                                                    Dist.

  AREA                  10                     Double               Acreage of Annexation
  --------------------- ---------------------- -------------------- -----------------------------

**[Incorporated Place Shapefile]{.underline}**

  --------------------- ---------------------- -------------------- -----------------------------
  [Field]{.underline}   [Length]{.underline}   [Type]{.underline}   [Description]{.underline}

  STATE                 2                      String               Current State FIPS Code

  COUNTY                3                      String               Current County FIPS Code

  PLACE                 5                      String               Current Place FIPS

  PLC_NAME              90                     String               Current Place Name

  CHNG_TYPE             2                      String               Type of Digital BAS Area
                                                                    Update

  EFF_DATE              8                      String               Annexation Effective Date

  LEGAL_DOC             20                     String               Annexation Ordinance Number

  OFFSET                10                     String               Geographic Corridor or Offset
                                                                    Dist.

  AREA                  10                     Double               Acreage of Annexation
  --------------------- ---------------------- -------------------- -----------------------------

**[All Line Shapefiles]{.underline}**

  --------------------- ---------------------- -------------------- -----------------------------
  [Field]{.underline}   [Length]{.underline}   [Type]{.underline}   [Description]{.underline}

  TLID                  10                     Integer              TIGER/Line^^ ID

  CFCC                  3                      String               Feature CFCC

  CFCC1                 1                      String               First Character of feature
                                                                    CFCC

  FIDELITY              1                      Integer              Shape Fidelity Flag

  FENAME                90                     String               Feature Name

  CHNG_TYPE             2                      String               Type of Digital BAS linear
                                                                    update

                                                                    

                                                                    

                                                                    
  --------------------- ---------------------- -------------------- -----------------------------

*Note: If the 'Fidelity' flag contains a value of '1,' then the Census
Bureau was unable to*

*maintain the boundary's shape fidelity during the MTAIP process. Please
review all line*

*segments (not just roads) in the Census Bureau's all-line layer for
lines with this flag and make any necessary boundary corrections to the
affected entity if the boundary has been coordinately shifted.*

**Appendix D 3 -- Metadata Requirements**

> Metadata that describes the data content, coordinate
> system/projection, author, source, and other characteristics of GIS
> files is critical for Census Bureau staff to efficiently and
> accurately process files for Digital BAS. The Census Bureau requires
> that a metadata text file accompany every GIS file and layer
> submitted.
>
> The Federal Geographic Data Committee's (FGDC) Content Standard for
> Digital Spatial Metadata provides a national standard that enables the
> data-sharing public to easily locate critical information about a file
> and ensure that no critical information is omitted inadvertently when
> creating metadata. For this reason, the Census Bureau requests that
> metadata submitted as part of Digital BAS is submitted using this
> standard. For information about the FGDC and its geospatial metadata
> standards, please visit the following site:
>
> <http://www.fgdc.gov/metadata/metadata.html>
>
> The Census Bureau requires that the following sections of the FGDC
> metadata form be completed as a minimum for considerations:

-   citation (information about the originator, publication date, title
    edition, and other publications or information),

-   description (section that contains an abstract describing your data
    set),

-   time period of content (section that describes the vintage of the
    data),

-   spatial domain (information about bounding coordinates),

-   point of contact (general contact information),

-   data quality information (information about attribute accuracy),

-   spatial reference information (section on coordinate system /
    projection of the data set), and

-   entity and attribute information (section that describes the
    contents of your table)

> To help you fulfill the requirement of filling out and submitting
> metadata, the Census Bureau suggests visiting the USGS web site. This
> site contains useful information about FGDC compliant metadata, from
> which one can read about metadata frequently asked questions, view
> FGDC metadata examples, and connect to other FGDC related Web pages.
> The following is the USGS\'s metadata URL:
>
> <http://geology.usgs.gov/tools/metadata/>
>
> Moreover, if you are using Arc/Info, the FGDC link relating to
> metadata creation Tools
> (http://www.FGDC.gov/metadata/toollist/fgdcmeta.html) contains a
> useful Arc Macro Language (AML) (e.g., fgdcmeta.aml) that when
> executed, completes most of the aforementioned required sections of
> the metadata form automatically. This AML is a product of the Illinois
> State Geological Survey.
>
> *Note: ESRI's ArcCatalog also has an imbedded program that uses the
> FGDC standard in its creation of geospatial metadata.*

**Appendix D 4 -- Flowchart**

![](media/image21.png){width="5.992361111111111in"
height="7.938888888888889in"}

**Appendix D 4 -- Flowchart Continued**

![](media/image22.png){width="5.991666666666666in"
height="8.280555555555555in"}

**Appendix D 5**

![](media/image23.png){width="3.0708333333333333in" height="8.99375in"}

###  {#section-81 .Style-Heading-3-+-Dark-Teal .unnumbered}

### Appendix E Annexations and Detachments Form {#appendix-e-annexations-and-detachments-form .Style-Heading-3-+-Dark-Teal}

###  {#section-82 .Style-Heading-3-+-Right:---0.5\"}

**2008 Census Dress Rehearsal**

**Local Update of Census Addresses (LUCA) Program**

**Annexations and Detachments Form**

Please print or type the information about your government in the boxes
below.

**Government Name
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Entity Code\*
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**[PERSON COMPLETING THIS FORM]{.mark}**

**Signature
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Your Name (Printed)
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Title
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**[Telephone]{.mark}
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**[FAX]{.mark}
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_[E-Mail
Address]{.mark}
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

Record below the information requested for all annexations (A) or
detachments (D) that you have added to the 2008 Dress Rehearsal LUCA
program map(s). Be sure that you put the authorization number and
effective date in or near the area on the map. The Census Bureau will
supply this information to the state certifying agency for your state;
please ensure that you properly file all legal changes with your state
government in accordance with your state's laws.

+-----+------------+---------+----------+-----------+----------------+
| **T | **Autho    | **Ef    | **County | **Minor   | **Estimated    |
| ype | rization** | fective | or       | Civil     | Area**         |
| o   |            | date**  | parish** | Division  |                |
| f** | ***Enter   |         |          | (if any)  | **Square miles |
|     | in column  | ***Mon  | **in     | in        | o r Acres (in  |
| *   | 2 -***     | th/day/ | which**  | which**   | hundredths)    |
| *Ch |            | year*** |          |           | (in tenths)**  |
| ang | O **--     |         | A        | A         |                |
| e** | O          | **(4)** | **(annex | **(anne   | **(7) (8)**    |
|     | rdinance** |         | ation)** | xation)** |                |
| A   |            |         |          |           |                |
| **o | R **--     |         | D        | D         |                |
| r** | Re         |         | **(detac | **(deta   |                |
| D   | solution** |         | hment)** | chment)** |                |
|     |            |         |          |           |                |
| *   | L **--     |         | **or**   | **or**    |                |
| *(1 | Local      |         |          |           |                |
| )** | Law**      |         | O        | O         |                |
|     |            |         | *        | **(other) |                |
|     | S **--     |         | *(other) | o         |                |
|     | S          |         | oc       | ccurred** |                |
|     | tate-level |         | curred** |           |                |
|     | action**   |         |          | **(6)**   |                |
|     |            |         | **(5)**  |           |                |
|     | X **--     |         |          |           |                |
|     | Other      |         |          |           |                |
|     | type**     |         |          |           |                |
|     |            |         |          |           |                |
|     | **Type     |         |          |           |                |
|     | Number**   |         |          |           |                |
|     |            |         |          |           |                |
|     | **(2)      |         |          |           |                |
|     | (3)**      |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+
|     |            |         |          |           |                |
+-----+------------+---------+----------+-----------+----------------+

D-1642

***\*** Use the 5-digit FIPS code in the subject matter area of your
map. (Minor civil division FIPS codes are in red, while*

*incorporated place codes are in green.)*

### Appendix F Contact Update Information Form {#appendix-f-contact-update-information-form .Style-Heading-3-+-Dark-Teal}

**Contact Information Update Form**

Person completing this form: Name
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Address:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Phone:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**[New or Corrected Chief Executive/Highest Elected Official
Information]{.underline}**

**Title** (mark one):  Ms.  Miss  Mrs.  Mr.  Dr.  The Honorable

>  Tribal President  Tribal Chairperson  Tribal Chief  Tribal
> Governor

**Name:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
*(First Name, MI, Last Name)*

**Name Suffix** (mark if appropriate):  Jr.  Sr.  II  III  IV

**Position:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

*(e.g., Commissioner, Mayor, Supervisor, please do not abbreviate)*

**Department/Office:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

*(e.g., Commissioner's Office, Mayor's Office, please do not
abbreviate)*

**Address:**
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**
*(City, State, ZIP)*

**Phone:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
**Ext\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Fax:**\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**E-mail:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**[New or Corrected Contact Information]{.underline}**

**Title** (mark one):  Ms.  Miss  Mrs.  Mr.  Dr.  The Honorable

>  Tribal President  Tribal Chairperson  Tribal Chief  Tribal
> Governor

**Name:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
*(First Name, MI, Last Name)*

**Name Suffix** (mark if appropriate):  Jr.  Sr.  II  III  IV

**Position:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

*(e.g., Planning Director, Planner, Clerk, please do not abbreviate))*

**Department/Office:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

*(e.g. Planning and Zoning, please do not abbreviate)*

**Address:**
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**
*(City, State, ZIP)*

**Phone:** \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
**Ext\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Fax:**\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**E-mail:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

###  {#section-83 .Style-Heading-3-+-Dark-Teal}

###  {#section-84 .Style-Heading-3-+-Dark-Teal .unnumbered}

### Appendix G Inventory Form {#appendix-g-inventory-form .Style-Heading-3-+-Dark-Teal}

###  {#section-85 .Style-Heading-3-+-Dark-Teal}

###  {#section-86 .Style-Heading-3-+-Dark-Teal}

###  {#section-87 .Style-Heading-3-+-Dark-Teal}

> Please use this form to identify the LUCA materials that you have
> updated and are returning to the Census Bureau for the 2008 Census
> Dress Rehearsal LUCA Program.
>
> Government Name
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> Entity ID Code (i.e., CO18057, MC18057020, PL181420)
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> State \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ County
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \[ \] Address List File Name
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \_\_\_\_\_\_\_ Number of address records
>
> \[ \] Address Count List File Name
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \_\_\_\_\_\_\_ Number of records
>
> \[ \] Census Bureau map sheets
>
> \_\_\_\_\_\_\_ Number of map sheets
>
> \[ \] Annexations and Detachments Form
>
> \[ \] Shapefile

###  {#section-88 .Style-Heading-3-+-Dark-Teal}

###  {#section-89 .Style-Heading-3-+-Dark-Teal}

###  {#section-90 .Style-Heading-3-+-Dark-Teal}

###  {#section-91 .Style-Heading-3-+-Dark-Teal}

###  {#section-92 .Style-Heading-3-+-Dark-Teal}

###  {#section-93 .Style-Heading-3-+-Dark-Teal}

###  {#section-94 .Style-Heading-3-+-Dark-Teal}

###  {#section-95 .Style-Heading-3-+-Dark-Teal}

###  {#section-96 .Style-Heading-3-+-Dark-Teal}

###  {#section-97 .Style-Heading-3-+-Dark-Teal}

###  {#section-98 .Style-Heading-3-+-Dark-Teal}

###  {#section-99 .Style-Heading-3-+-Dark-Teal}

D-1656

###  {#section-100 .Style-Heading-3-+-Dark-Teal .unnumbered}

### Appendix H Special Disclosure Notice  {#appendix-h-special-disclosure-notice .Style-Heading-3-+-Dark-Teal}

**Special Notice**

**This Package Contains**

**U.S. Census Bureau**

**Address Information**

**Disclosure Prohibited by**

**Title 13, U.S.C.**

U.S. Department of Commerce

U.S. Census Bureau

2/14/2006

D-1657

### Appendix I Return/Destruction of Title 13, U.S.C. Materials Form {#appendix-i-returndestruction-of-title-13-u.s.c.-materials-form .Style-Heading-3-+-Dark-Teal}

###  {#section-101 .Style-Heading-3-+-Dark-Teal}

**2008 Census Dress Rehearsal LUCA Program**

**Return/Destruction of Title 13, U.S.C. Materials**

*(fill in the name of your government or organization)*

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Date Signature *(2008 Census Dress Rehearsal LUCA Program Liaison)*

has properly destroyed or returned to the U.S. Census Bureau, the
original 2008 Census Dress Rehearsal Local Update of Census Addresses
(LUCA) Program materials and any copies using the security requirements
provided to us by the U.S. Census Bureau.

**2008 Census Dress Rehearsal LUCA Program Reviewers**

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Date Signature

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Date Signature

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Date Signature

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Date Signature

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Date Signature

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Date Signature

[All LUCA Program reviewers are required to sign and date this form at
the completion of the LUCA Program. Should any liaison or reviewer leave
before the completion of the LUCA Program, they are required to
"sign-out" of the program by signing and dating this form. If any
liaison or reviewer fails to sign and date this form, the current
liaison can "sign-out" on their behalf.]{.mark}

D-1658

### Appendix J The Map Legend {#appendix-j-the-map-legend .Style-Heading-3-+-Right:---0.5\"}

![](media/image24.png){width="5.564583333333333in"
height="8.86111111111111in"}

> The map legend describes the various symbols and colors used on the
> maps. The legend is divided into three columns:

1)  The Symbol Description column includes the type of features,
    boundaries, and geography shown on the map.

2)  The Symbol column shows the symbols representing the feature in the
    symbol description.

3)  The Name Style column shows an example of the name of a particular
    feature such as a road, waterway, or geographic area displayed on
    the map.

**Boundaries**

> The first group of symbols in the legend refers to different boundary
> types or geographic area shown on the map. Each type of boundary has a
> distinct color.

![](media/image25.png){width="7.027777777777778in"
height="3.1958333333333333in"}

**Transportation**

> The second group of symbols represents various types of transportation
> features. Thicker lines identify major roadways while thinner lines
> represent secondary roads and city streets. Private roads, walkways,
> ferries, and railroads represented by distinctive dashed lines are
> included in this section.

![](media/image26.png){width="6.966666666666667in"
height="2.1819444444444445in"}

**Other Features**

> The third group of symbols represents other feature types such as
> pipelines and streams, and non-visible boundaries. Streams and
> shorelines are blue, airport landing strips are purple, corporate
> corridors are a dashed red line, and offset corporate boundaries are a
> solid red line.

![](media/image27.png){width="6.961111111111111in"
height="2.120138888888889in"}

**Census Blocks and Symbols**

> The fourth group of symbols are associated with census blocks. Census
> blocks are identified numerically and are color-coded. An asterisk
> next to a census block number indicates that the block number is
> repeated elsewhere on the map or is partially shown on an adjacent
> map.
>
> A fishhook symbol across a map feature or boundary area indicates that
> the area on both sides of the feature or boundary belong to the same
> census block.
>
> For those participants choosing Option 1, Full Address List Review and
> Option 2, Title 13 Local Address List Submission, this section also
> contains structure point symbols, which represent the exact location
> of residential structures. Structure points for multi-unit structures,
> such as apartment buildings, are identified by a structure point
> number, followed by the number of units within the structure in
> parentheses.

![](media/image28.png){width="5.978472222222222in"
height="1.2604166666666667in"}

**Landmarks**

> The last group of symbols represents various landmarks on the map such
> as rivers and lakes, campgrounds, jails, schools, airports, and parks.
> The Census Bureau maps for the 2008 Census Dress Rehearsal LUCA
> Program show the rivers and lakes in blue while campgrounds, jails,
> schools, airport, and parks are gray. The area outside of the subject
> area is speckled gray.

![](media/image29.png){width="6.738194444444445in" height="1.78125in"}

**Footnotes and Notes**

> The footnote and notes section of the legend provide additional
> information and details on geographic relationships, boundaries, and
> symbols

![](media/image30.png){width="6.781944444444444in"
height="1.7013888888888888in"}

### Appendix K Physical Location Description and Street Type Abbreviation Examples {#appendix-k-physical-location-description-and-street-type-abbreviation-examples .Style-Heading-3-+-Right:---0.5\"}

### Appendix L Unit Designation Abbreviation Examples {#appendix-l-unit-designation-abbreviation-examples .Style-Heading-3-+-Right:---0.5\"}

###  {#section-102 .Style-Heading-3-+-Right:---0.5\"}

###  {#section-103 .Style-Heading-3-+-Dark-Teal}

###  {#section-104 .Style-Heading-3-+-Dark-Teal}

###  {#section-105 .Style-Heading-3-+-Dark-Teal}

# Glossary

**Address breaks --** Address breaks are the city-style address on each
side of a boundary or at an intersection of a street with another
feature.

**Address Count List** -- Identifies the number of housing units and
group quarters on the Census Bureau's address list for each census block
within a jurisdiction.

**Address range** -- The lowest and highest address numbers used to
identify structures along each side of a street segment that has
city-style addresses. Usually one side of the street has even address
numbers and the other side has odd address numbers.

**Annexations and Detachments Form** -- To be used by the participant to
document legal boundary changes for the jurisdiction.

**Block** -- See census block.

**Block number** -- A 4-digit number, plus 1 alpha character block
suffix, if applicable, used by the Census Bureau to identify each census
block. For this program, census blocks are numbered uniquely within each
census tract.

**Boundary** -- A line, either invisible or coincident with a visible
feature that identifies the extent of a geographic entity, such as a
census tract, city, or county.

**Boundary and Annexation Survey** -- An annual survey of all counties,
and selected incorporated places and minor civil divisions conducted by
the Census Bureau to determine the correct legal limits and related
information as of January 1 of the survey year.

 

**Census Bureau address list** -- A nationwide list of all housing unit
and group quarter addresses known to the Census Bureau. In addition to
the mailing address and ZIP Code, the Address List may identify the
location of each housing unit and group quarters.

**Census block** -- A geographic area bounded by visible features, such
as streets, roads, streams, and railroad tracks, and invisible features,
such as the boundaries of governmental units and other legal entities. A
census block is the smallest area for which the Census Bureau collects
and tabulates statistical information.

**Census Bureau** -- An agency within the U.S. Department of Commerce.
The Census Bureau is the country\'s preeminent statistical collection
and dissemination agency. It publishes a wide variety of statistical
data about people and the economy of the nation. The Census Bureau
conducts approximately 200 annual surveys and conducts the decennial
census of the United States population.

**Census Bureau map** -- Any map produced by the Census Bureau. A Census
Bureau map displays geographic entities used in a Census Bureau
sponsored census or survey for which the Census Bureau tabulates data.

**Census tract** -- A small, relatively permanent statistical division
of a county or statistically equivalent entity, delineated for the
purpose of presenting Census Bureau statistical data. Census tract
boundaries were delineated for Census 2000 in accordance with Census
Bureau guidelines that specify the need for visible and stable
boundaries. Census tracts never cross the boundary of a county or
statistically equivalent entity, but may split other geographic
entities; e.g., minor civil divisions and places.

**Census tract number** -- A 4-digit, plus 2-digit suffix, if
applicable, used to identify a census tract uniquely within a county or
statistically equivalent entity. Leading zeros are not shown on Census
Bureau maps

**Chief executive/highest elected official** -- The person most
responsible for the governmental activities of a local government. This
person receives the LUCA Program invitation letter, and must designate a
LUCA liaison, if desired.

**City-style address** -- An address that consists of a house number and
street name; for example, 201 Main Street. The address may or may not be
used for the delivery of mail and may include apartment
numbers/designations or similar identifiers.

**Confidentiality** -- The guarantee made by law (Title 13, United
States Code) to individuals who provide information about themselves or
their business to the Census Bureau. This item refers to the Census
Bureau's promise of nondisclosure of that information to others.

**County** -- The primary legal division of most states. Most are
governmental units with powers defined by state law.

**Delivery Sequence File (DSF)** -- A computerized file containing all
delivery point addresses serviced by the U.S. Postal Service (USPS). The
USPS updates the DSF continuously as its letter carriers identify
addresses for new delivery points or changes in the status of existing
addresses.

**Feature** -- Any part of the landscape, whether natural (such as, a
stream or ridge) or artificial (such as, a road or power line). In a
geographic context, features are any part of the landscape portrayed on
a map, including nonvisible boundaries of legal entities, such as, city
limits or county lines.

**Geocode** -- A code that identifies a specific geographic entity. For
example, geocodes needed to identify a census block for data collection
are the state code, the county code, and the block number. 

**Geographic Information System (GIS)** -- A computer system for the
storage, retrieval, and maintenance of information about the points,
lines, and areas that represent the streets and roads, rivers,
railroads, geographic entities, and other features on the surface of the
Earth-information that previously was available only on paper maps.

**Global Positioning System (GPS)** -- A satellite navigation system
that provides coded satellite signals to a GPS receiver to compute
location.

**Governmental unit** -- A geographic entity established by legal action
for the purpose of implementing specified governmental functions. Most
governmental units provide a number of general government services and
raise revenues (usually through taxing authority).

**Group quarters** -- The Census Bureau classifies a group quarters as a
place where people live or stay that is normally owned or managed by an
entity or organization providing housing and/or services for the
residents. These services may include custodial or medical care, as well
as other types of assistance, and residency is commonly restricted to
those receiving those services. People living in group quarters are
usually not related to each other.

Group quarters include such places as college residence halls,
residential treatment centers, skilled nursing facilities, group homes,
military barracks, correctional facilities, workers' dormitories, and
facilities for people experiencing homelessness.

**Housing unit (HU)** -- A single-family house, townhouse, mobile home,
trailer, vacant trailer park pad, apartment, group of rooms, or single
room occupied as a separate living quarters, or, if vacant, intended for
occupancy as a separate living quarters. A separate living quarters is
one in which one or more occupants (or, intended occupants, if vacant)
live separate from any other individual(s) in the building and have
direct access from outside the building or through a common hall.

**Incorporated place** -- A type of governmental unit, incorporated
under state law as a city, town, village, or borough, having legally
prescribed boundaries, powers, and functions.

**Legal boundary** -- The legally defined boundary of a governmental
unit, usually referring to a county, minor civil division, or
incorporated place. The legal boundary identifies the area within a
local government\'s jurisdiction, and thus bounds the area of LUCA
responsibility.

**LUCA liaison** -- Also known as the program liaison or designated
liaison. A person voluntarily appointed by the chief executive/highest
elected official of each jurisdiction to review the Census Bureau's
address list and maps against local records to identify differences.

**Map Sheet to Block Number Relationship List** -- A list identifying
census block numbers and the Census Bureau map(s) on which each block is
located.

**Master Address File (MAF)** -- A nationwide list of all addresses to
support many of the Census Bureau's operations. Besides containing
mailing addresses and ZIP Codes, a MAF record also contains geographic
information about the location of addresses.

**Minor civil division (MCD)** -- A type of governmental unit that is
the primary governmental or administrative subdivision of a county. MCDs
are identified by a variety of terms, such as town (in 8 states),
township, and/or district, and include both functioning and
nonfunctioning governmental entities.

**Noncity-style address** -- An address that does not use a house number
and street name. This includes rural route and box number address and
highway contract route addresses, etc., which may include a box number,
post office boxes and drawers, and general delivery.

**Occupied housing unit** -- A housing unit is classified as occupied if
it is the usual place of residence of the individual or group of persons
living in it at the time of enumeration or if the occupants are only
temporarily absent; for example, away on vacation. Occupied rooms or
suites of rooms in hotels, motels, and similar places are classified as
housing units only when occupied by permanent residents, that is,
individuals for whom the facility is their usual place of residence.

**Regional Office** -- One of 12 permanent Census Bureau offices
responsible for the Census Bureau's office and field operations within
its region.

**Shapefile** -- Data set used to represent geographic features such as
streets and boundaries. Shapefiles can represent point, line, or area
features and require GIS or mapping software.

**Street segment** -- The portion of a street or road between two
features that intersect that street or road, such as, other streets or
roads, railroad tracks, streams, and governmental unit boundaries. The
Census Bureau records the known address ranges for every street segment
with city-style addresses.

**Structure Point** -- A dot on a Census Bureau map, used to show the
location of one or more living quarters. Unique numbers are assigned
within the census block to each structure point, which corresponds to
the entry in the address register for a basic street address. Structure
points are stored in the TIGER^^ database.

**TIGER/Line® file** -- The computer-readable extract of the TIGER^®^
database that the Census Bureau makes available to the public. It
contains data representing the locations of all roads, railroads, bodies
of water, boundaries of legal and statistical entities, and other
visible and nonvisible features, along with their attributes (names,
address ranges, geographic codes, census feature class codes, and the
like).

**Topologically Integrated Geographic Encoding and Referencing
(TIGER^®^)** -- A computer database that contains a digital
representation of all map features (streets, roads, rivers, railroads,
lakes, and so forth) required to support Census Bureau operations, the
related attributes for each, and the geographic identification codes for
all entities used by the Census Bureau to tabulate data for the United
States, Puerto Rico, and Island Areas.

**Tract** -- See Census tract.

**Vacant housing unit** -- A habitable structure containing living
quarters that is not occupied. New housing units not yet occupied are
classified as vacant housing units if construction has reached a point
where exterior windows and doors are installed and final usable floors
and a roof are in place. Vacant units are excluded if open to the
elements, or if there is positive evidence, such as a sign on the house,
that the housing unit is to be demolished or has been condemned.

**1990 Address Control File** -- The 1990 residential address list used
to label questionnaires, control the mail response check-in operation,
and determine the nonresponse followup workload.

# Index

A

Action codes

adding addresses, 35

correcting addresses, 36

deleting addresses, 38

group quarters flag, 36

nonresidential addresses, 39

not in your jurisdiction addresses, 38

Adding addresses

action code, 35

Address control file 1990, 2

defined, 2

Address count list

file name, 13

file record layout, 16

pipe-delimited file, 20

reviewing and editing, 40

Address list

protecting information, 11

Title 13, 46

Address range, 23

adding a new street, 23

in Census Bureau records, 102

moving a street, 24

Address types, 8

nonresidential, 8

residential, 8

Annexations and detachments

boundary changes, 53

completed form example, 55

defined, 53, 99

form, 87

B

Block. *See* Census block

Block number

defined, 99

Boundary

corrections, 53

defined, 99

Boundary and annexation survey

defined, 53, 99

paper map, 53

submitting digital files, 56

Boundary changes, 53

annexations and detachments, 53

C

Census address list improvement act of 1994, 2

Census block

defined, 99

Census Bureau

responsibilities, 3

Census Bureau map

information, 21

sample, 22

Census tract. *See* also census tract number

defined, 100

Census tract number. *See* also census tract

defined, 100

Chief executive/highest elected official

defined, 100

invitation, 1

City-style address. *See* house number and street name addresses, *See*
house number and street name addresses

defined, 1, 8, 100

street segment, 102

Confidentiality

defined, 100

Correcting addresses

action code, 36

Correcting street names, 24

D

Deleting addresses

action code, 38

Deleting streets, 25

Delivery sequence file (DSF), 2

Destroying Title 13 materials, 44

F

Feature

defined, 100

Fishhook

defined, 95

G

Governmental unit

defined, 100

Group quarters

defined, 101

unacceptable types, 8

H

House number and street name addresses. See city-style addresses

Housing unit

defined, 7, 101

unacceptable types, 8

I

Incorporated place

defined, 101

L

Legal boundary

defined, 101

Liaison

chief-executive/highest elected official, 100

defined, 101

Local address sources, 9

LUCA program

2010 census dress rehearsal, 1

explained, 1

schedule, 4

training, 4

LUCA program address list

file format, 14

file name, 13

file record layout, 17

opening the file, 17

pipe-delimited file, 18, 19

saving the file, 39

software requirements, 16

LUCA program materials

destruction, 44

return, 42

M

Master address file (MAF)

creation, 2

defined, 101

updates, 3

Minor civil division. *See* legal boundary

in computer readable files, 13

Mobile home or trailer lots

adding addresses, 36

correcting addresses, 37

Moving streets

on maps, 24

N

Noncity-style address

defined, 9, 101

mailing addresses, 9

Non-house number and street name addresses. See noncity-style addresses

Nonresidential addresses, 8

action code, 39

Not in your jurisdiction addresses

action code, 38

O

Occupied housing unit

defined, 101

P

Participant responsibilities, 3

Pipe-delimited file

address count list, 20

address list, 18, 19

defined, 17

Protecting Title 13 information, 11

R

Residential addresses, 8

S

Shapefile

Boundary and annexation survey (BAS) digital file submission, 56

defined, 102

submitting feature information, 26

Software requirements, 16

Strategies for review, 9

Street segment

defined, 102

Structure point

confidential, 46

defined, 102

Title 13, 46

T

TIGER^^, 25

TIGER/Line^^ file. *See* also topologically integrated geographic
encoding and referencing

defined, 102

Topologically integrated geographic encoding and referencing. *See* also
TIGER/Line^^ file

defined, 102

Tract. *See* census tract

V

Vacant housing unit

defined, 102

> **Census Bureau Regional Offices**
>
> ![](media/image31.jpeg){width="1.9583333333333333in"
> height="1.2236111111111112in"}![](media/image32.jpeg){width="2.03125in"
> height="1.6in"}

[^1]: An address that consists of a house number and street name; for
    example, 201 Main Street. The address may or may not be used for the
    delivery of mail and may include apartment numbers/designations or
    similar identifiers.

[^2]: A group quarters is a place where people live or stay that is
    normally owned or managed by an entity or organization providing
    housing and/or services for the residents. *See Chapter 2 for a
    complete definition.*

[^3]: An address that does not use a house number and street name. This
    includes rural route and box number addresses and highway contract
    route addresses, etc., which may include a box number, post office
    boxes and drawers, and general delivery.

[^4]: The 1990 residential address list used to label questionnaires,
    control the mail response check-in operation, and determine the
    nonresponse followup workload.

[^5]: A computerized file containing all delivery point addresses
    serviced by the U.S. Postal Service (USPS). The USPS updates the DSF
    continuously as its letter carriers identify addresses for new
    delivery points or changes in the status of existing addresses.

[^6]: A census tract is a small, relatively permanent statistical
    division of a county or statistically equivalent entity, delineated
    for the purpose of presenting Census Bureau statistical data.

[^7]: A census block is a geographic area bounded by visible features,
    such as streets, roads, streams, and railroad tracks, and invisible
    features, such as the boundaries of governmental units and other
    legal entities. Census blocks are the smallest area for which the
    Census Bureau collects and tabulates statistical information.

[^8]: A structure point is a coordinate location that represents the
    location of one or more housing units and/or group quarters.
    Structure points are protected by Title 13. *See Appendix A,
    Confidentiality and Security Guidelines.*

[^9]: The Census Bureau does not endorse or recommend the use of any
    specific software to view its files. The program names included here
    are only examples of programs that are able to read
    computer-readable files.

[^10]: Address ranges are the first and last house address numbers that
    could exist along a given section of a street. An address range is
    usually separated into two component ranges to reflect addresses
    along the left and right sides of the street. Usually one side of
    the street has only even address numbers and the other side has only
    odd address numbers.

[^11]: Address breaks are the city-style address on each side of a
    boundary or at an intersection of a street with another feature.

[^12]: A data dictionary describes the fields included in any data
    tables associated with your submission. A data dictionary should
    list all the fields, describe the data in each field, and provide
    the legal values and their definitions for each field.

[^13]: A code that identifies a specific geographic entity. For example,
    geocodes needed to identify a census block for data collection are
    the state code, the county code, the census track number, and the
    block number. 

[^14]: The use of brand names does not represent an endorsement of a
    company or its products by the U.S. government. Due to the wide use
    of ESRI products by our partners in the GIS community, and the
    ubiquitous use of the shapefile format as a medium for GIS data
    exchange, the Census Bureau is providing this data in shapefile
    format. You should encounter no problems when importing these
    shapefiles into your local GIS software. However, if you are using
    GIS software that does not contain a shapefile translator, please
    contact the Census Bureau for further instructions (301-763-1099 or
    e-mail <geo.bas@census.gov>).