2004 First Edition TIGER/Line(R) Files Technical Documentation Chapter 4: Geographic Entities Overview The 2004 First Edition TIGER/Line(R) files contain the boundaries of legal and statistical entities. Some boundaries of the legal entities contained in the 2004 First Edition TIGER/Line files are those reported to the U.S. Census Bureau to be legally in effect on January 1, 2000 while others are updated boundaries. It is important to note that the boundary information in the TIGER/Line files for both legal and statistical entities are for U.S. Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement. No warranty, expressed or implied is made with regard to the accuracy of these data, and no liability is assumed by the U.S. Government in general or the U.S. Census Bureau, specifically as to the positional or attribute accuracy of the data. The legal entities shown in the files are: States and their statistical equivalents-Census 2000, current, corrected, and economic Counties and their statistical equivalents-Census 2000, current, corrected and economic Minor civil divisions (MCDs)-Census 2000, current, and corrected Subbarrios (Puerto Rico only)-Census 2000, current, and corrected Consolidated cities-Census 2000, current, and corrected Incorporated places-Census 2000, current, corrected, and economic American Indian reservations (both federally and state-recognized)-Census 2000, current, and corrected American Indian trust lands-Census 2000, current, and corrected American Indian tribal subdivisions-Census 2000, current, and corrected Alaska Native Regional Corporations-Census 2000 and corrected Hawaiian home lands-Census 2000 and corrected Oregon urban growth areas-Census 2000 only Congressional districts-Census 2000 and current (108th) Voting districts-Census 2000 only State legislative districts-Census 2000 only School districts-Census 2000 and current The statistical entities included in the files are: Census areas (statistical county equivalents in Alaska)-Census 2000, current, corrected, and economic Census county divisions and unorganized territories (statistical county subdivisions)-Census 2000; current for unorganized territories only Census designated places (statistical place equivalents)-Census 2000; current in Hawaii, Guam, Northern Mariana Islands, and Puerto Rico; and corrected in Hawaii only Place (balance) entities (statistical place equivalents within consolidated cities)-Census 2000 and current American Indian/Alaska Native statistical areas-Census 2000 and corrected 1) Alaska Native village statistical areas 2) Tribal designated statistical areas 4) Oklahoma tribal statistical areas 5) State designated American Indian statistical areas Census tracts-Census 2000 only Census block groups-Census 2000 only Census blocks-Census 2000 and current suffix for Census 2000 block number Urban areas 1) Urbanized areas-Census 2000 and current 2) Urban clusters-Census 2000 and current Metropolitan areas and Core based statistical areas (CBSAs): 1) Consolidated metropolitan statistical areas-Census 2000 only 2) Metropolitan statistical areas-Census 2000 and June 2003 3) Primary metropolitan statistical areas-Census 2000 only 4) New England County Metropolitan areas-Census 2000 only 5) Micropolitan statistical areas-June 2003 only 6) Metropolitan divisions-June 2003 only 7) Combined statistical areas-June 2003 only 8) New England city and town areas-June 2003 only 9) New England city and town area divisions-June 2003 only 10) Combined New England city and town areas-June 2003 only Traffic analysis zones-Census 2000 only ZIP Code(R) Tabulation Areas (ZCTAs)-Census 2000 and 2002 Public Use Microdata Areas-Census 2000 only Geographic entities tabulated by the U.S. Census Bureau generally are hierarchical; that is, in a progression from the Nation to the block level. This hierarchical structure is derived from the legal, administrative, or areal relationships of the entities. The smallest level of census geography is the census block. Census blocks are defined within block groups, block groups are defined within census tracts, census tracts are defined within counties and statistically equivalent entities, counties and statistically equivalent entities are within states and statistically equivalent entities, states and statistically equivalent entities are within the Nation. American Indian areas, Alaska Native areas, and Hawaiian home lands; Core Based Statistical Areas; Urban Areas; and ZIP Code Tabulation Areas (ZCTAs(TM)) are within the Nation and comprised of census blocks. Within states and statistically equivalent entities and comprised of census blocks are Congressional Districts, Alaska Native Regional Corporations (ANRCs), School Districts, Urban Growth Areas (UGAs), State Legislative Districts (SLDs), and Places. Within counties and statistically equivalent entities and comprised of census blocks are County Subdivisions, Voting Districts (VTDs), and Traffic Analysis Zones (TAZs). In Puerto Rico, Subbarrios are within County Subdivisions and are comprised of census blocks. See Appendix G for a count of legal and statistical entities. The TIGER/Line files identify geographic areas using the Federal Information Processing Standard (FIPS) codes or U.S. Census Bureau-assigned codes. The TIGER/Line files depict geographic areas in two ways: The assignment of codes to the left and the right sides of the complete chains (Record Type 1) The identification of codes that belong to each GT-polygon (Record Types A, B, E, and S) The TIGER/Line files identify some geographic entities in both the complete chain and polygon records for certain boundary vintages. This chapter provides detailed information on the record types and fields for the geographic entities. Boundary and Area Changes The boundaries identified as current for some legal areas are updated boundaries collected since Census 2000 as part of the U.S. Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all federally recognized American Indian Reservations and off-reservation trust lands, tribal subdivisions, states and their statistical equivalents, all counties and their statistical equivalents, all minor civil divisions (MCDs), and all incorporated places are those that were legally in effect as of the latest BAS. This may vary by county record or the date of extraction from the Census TIGER(R) database. In some Record Type A records, the current state and county, when combined with the Census 2000 census tract and block numbers, create nonexistent geographic areas. To avoid nonexistent geographic areas, it is important not to mix Census 2000 geographic codes with the current geographic codes. For all other legal entities and nearly all statistical areas, the boundaries shown are those in effect at the time of Census 2000 whether the data are identified as Census 2000 or current. Because unorganized territories and census designated places (CDPs) occupy the same level of geography as legal MCDs and incorporated places, updates to the legal boundaries may affect the current boundaries for some of these entities, including the elimination of some of the statistical entities. With the exception of Hawaii, Guam, the Northern Mariana Islands, and Puerto Rico, which do not have any incorporated places, CDPs do not appear on Record Type A-Current Geography. All CDPs appear in Record Types 1 and S-Census 2000 Geography. The boundaries identified as corrected are updated boundaries generally resulting from the Census 2000 Count Question Resolution (CQR) Program. Where the Census Bureau placed a jurisdictional boundary of a functioning governmental unit in the wrong location for Census 2000, the corrected boundaries show the location of the governmental unit legally in effect on January 1, 2000. Since the release of the Census 2000 versions of the TIGER/Line files, the U.S. Census Bureau has shifted and reshaped some line features including the lines forming some boundaries. These changes involved the realignment of complete chains associated with a legal or statistical area boundary. The shape and area of the Census 2000 geographic entities portrayed in the 2004 First Edition TIGER/Line files may differ from their portrayal in the Census 2000 versions of the TIGER/Line files, but the inventory of Census 2000 tabulation entities remains the same. Changes in the shape and location of complete chains will change the polygon internal point locations. See the Internal Points section in Chapter 3. Codes for Entities Appendix A is a list of FIPS state and county codes. A list of valid codes and names for other legal entities does not appear in the documentation for the TIGER/Line files. The TIGER/Line files include Record Type C which lists the geographic codes and names plus some attribute data (FIPS 55 class code, census place description code, legal/statistical area description code, and entity type) for certain entities. The codes and names are identified as Census 2000, current, corrected, economic census or all four. The FIPS Code, Name, and/or Attribute Data Applicable Year field (field name DATAYR) may have five values: 2000 for Census 2000 geographic names and codes, 200n (where 200n is the year of extraction from the Census TIGER database) for geographic names and codes valid for the current year, CQR0 for geographic names and codes valid for corrected geography, EC02 for geographic names and codes valid for the 2002 Economic Census, or blank when the geographic names and codes for Census 2000, 200n, CQR0, and EC02 are the same. The U.S. Census Bureau maintains the FIPS codes for states and counties. The U.S. Geological Survey (USGS) maintains the FIPS 55 codes. Information about FIPS 55 codes is available from USGS's Geographic Names FIPS codes for more information. The URL for FIPS codes is http://www.census.gov/geo/www/fips/fips.html. The FIPS publications include: FIPS PUB 5-2, Codes for the Identification of the States, the District of Columbia and the Outlying Areas of the United States, and Associated Areas FIPS PUB 6-5, Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas FIPS PUB 8-6, Metropolitan Areas (Including MSAs, CMSAs, PMSAs, and NECMAs) FIPS 55, Codes for Named Populated Places, Primary County Divisions, and Other Locational Entities of the United States, Puerto Rico, and the Outlying Areas The U.S. Census Bureau uses the codes in FIPS 55 to identify both legal and statistical entities for county subdivisions, places, and American Indian areas/Alaska Native areas/Hawaiian home lands. FIPS 55 includes many more entity records than those for which the U.S. Census Bureau tabulates data. The FIPS 55 codes are state-based. American Indian reservations, off-reservation trust land areas, American Indian tribal subdivisions, Oklahoma tribal statistical areas, State designated American Indian statistical areas, and/or tribal designated statistical areas in more than one state will have a different FIPS 55 code for each state portion of the single American Indian entity. Entity Type Codes The U.S. Census Bureau uses the Entity Type Code field on Record Type C to identify what type of legal or statistical entity the record, including its FIPS or Census code (American Indian areas/Alaska Native areas/Hawaiian home lands only) and name references. For example, the FIPS codes for both places and county subdivisions appear in the FIPS 55 Code field. The Entity Type Code field identifies whether the FIPS code references a place, consolidated city, county subdivision, Alaska Native Regional Corporation, American Indian/Alaska Native Area/Hawaiian home land, or American Indian tribal subdivision. Entity Type Codes Code Geographic Entity Type C County or Statistically Equivalent Entity E Economic Census Place F Economic Census Commercial Region G Consolidated City I American Indian/Alaska Native Area /Hawaiian Home Land except for Alaska Native Regional Corporation J Metropolitan Area (Consolidated Metropolitan Statistical Area, Metropolitan Statistical Area, Primary Metropolitan Statistical Area), Census 2000 L Subbarrio M County Subdivision O Urban Area, Census 2000 P Place R Urban Area, 1990 redefined based on Census 2000 urban/rural criteria S State or Statistically Equivalent Entity T Census Tract U Urbanized Area, 1990 V Voting District W Alaska Native Regional Corporation X American Indian Tribal Subdivision Y Oregon Urban Growth Area 3 Unified School District 4 Secondary School District 5 Elementary School District 6 Core Based Statistical Area (Metropolitan Statistical Area, Micropolitan Statistical Area, Metropolitan Division, Combined Statistical Area, New England City and Town Area, New England City and Town Area Division, and Combined New England City and Town Area), Current Names for Entities The TIGER/Line files contain not only the codes for geographic entities, but also the geographic entity names. Record Type C links the geographic entity codes appearing in a TIGER/Line file to the name of the geographic entity associated with that code. Multiple records for the same geographic entity may appear in a TIGER/Line file. The FIPS Code, Name, and/or Attribute Data Applicable Year field (field name DATAYR) identifies the names and codes as Census 2000, 200n (where 200n is the year of extraction from the Census TIGER database), CQR0, EC02, or all four. Refer to the section on Codes for Entities in this chapter for information on the five possible DATAYR values. Geographic Entities American Indian Areas, Alaska Native Areas, and Hawaiian Home Lands (AIANA/HHL) There are both legal and statistical American Indian, Alaska Native, and native Hawaiian entities for which the U.S. Census Bureau provides data. The legal entities consist of federally recognized American Indian reservations and off- reservation trust land areas, the tribal subdivisions that can divide these entities, state recognized American Indian reservations, Alaska Native Regional Corporations (ANRCs), and Hawaiian home lands (HHLs). The statistical entities are Alaska Native village statistical areas (ANVSAs), Oklahoma tribal statistical areas (OTSAs), tribal designated statistical areas (TDSAs), and state designated American Indian statistical areas (SDAISAs). Tribal subdivisions can exist within the statistical Oklahoma tribal statistical areas. In all cases, these areas are mutually exclusive in that no American Indian, Alaska Native, or Hawaiian home land can overlap another tribal entity, except for tribal subdivisions, which subdivide some American Indian entities, and Alaska Native village statistical areas (ANVSAs), which exist within Alaska Native Regional Corporations (ANRCs). In some cases where more than one tribe claims jurisdiction over an area, the U.S. Census Bureau creates a joint use area as a separate entity to define this area of dual claims. The American Indian areas, Alaska Native areas, and Hawaiian home lands (AIANA/HHLs) are represented in the TIGER/Line files by a 5-character numeric FIPS code field, a 4-character numeric census code field (except for American Indian Tribal subdivisions which have a 3-character numeric census code field), and a single alphabetic character American Indian/Hawaiian home land trust land indicator field. FIPS codes are assigned in alphabetical sequence within state; because of this the FIPS code is different in each state for American Indian entities in more than one state. The census codes are assigned in alphabetical order nationwide, except that joint use areas appear at the end of the code range. The U.S. Census Bureau assigns the 3-character American Indian tribal subdivision code alphabetically in order and unique within each reservation, associated off-reservation trust land, and Oklahoma tribal statistical area (OTSA). The TIGER/Line files use multiple fields to identify the legal and statistical AIANA/HHLs: Legal Entities Alaska Native Regional Corporations (ANRCs) are corporate entities organized to conduct both business and nonprofit affairs for Alaska Natives pursuant to the Alaska Native Claims Settlement Act of 1972 (Public Law 92-203). Twelve ANRCs are geographic entities that cover most of the state of Alaska (the Annette Islands Reserve, an American Indian reservation, is excluded from any ANRC). A thirteenth ANRC represents Alaska Natives who do not live in Alaska and do not identify with any of the 12 corporations. The U.S. Census Bureau does not provide data for this ANRC because it has no geographic extent and it does not appear in the TIGER/Line files. ANRC boundaries have been legally established. The U.S. Census Bureau offers representatives of the 12 nonprofit ANRCs the opportunity to review and update the ANRC boundaries. American Indian reservations-Federal (federal AIRs) are areas that have been set aside by the United States for the use of tribes, the exterior boundaries of which are more particularly defined in the final tribal treaties, agreements, executive orders, federal statutes, secretarial orders, or judicial determinations. The U.S. Census Bureau recognizes federal reservations as territory over which American Indian tribes have primary governmental authority. These entities are known as colonies, communities, pueblos, rancherias, ranches, reservations, reserves, villages, Indian communities, and Indian villages. The Bureau of Indian Affairs maintains a list of federally recognized tribal governments. The U.S. Census Bureau contacts representatives of American Indian tribal governments to identify the boundaries for federal reservations. Federal reservations may cross state, county, county subdivision, and place boundaries. American Indian reservations-State (state AIRs) are reservations established by some state governments for tribes recognized by the state. A governor-appointed state liaison provides the names and boundaries for state recognized American Indian reservations to the U.S. Census Bureau. State reservations may cross county, county subdivision, and place boundaries. American Indian tribal subdivisions are administrative subdivisions of federally recognized American Indian reservations, off-reservation trust land, or Oklahoma tribal statistical areas (OTSAs). Tribal subdivisions are known as areas, chapters, communities, or districts. These entities are internal units of self- government or administration that serve social, cultural, and/or economic purposes for the American Indians on the reservations, off-reservation trust lands, or OTSAs. The U.S. Census Bureau obtains the boundary and name information for tribal subdivisions from tribal governments. American Indian trust lands are areas for which the United States holds title in trust for the benefit of a tribe (tribal trust land) or for an individual Indian (individual trust land). Trust lands can be alienated or encumbered only by the owner with the approval of the Secretary of the Interior or his/her authorized representative. Trust lands may be located on or off a reservation. The U.S. Census Bureau recognizes and tabulates data for reservations and off- reservation trust lands because American Indian tribes have primary governmental authority over these lands. Primary tribal governmental authority generally is not attached to tribal lands located off the reservation until the lands are placed in trust. In U.S. Census Bureau data tabulations, off-reservation trust lands always are associated with a specific federally recognized reservation and/or tribal government. A tribal government appointed liaison provides the name and boundaries of their trust lands. The U.S. Census Bureau does not identify fee land (or land in fee simple status) or restricted fee lands as specific geographic categories and they are not identified in the TIGER/Line files. Trust lands are assigned the same code as the reservation with which they are associated. Trust lands associated with tribes that do not have a reservation are assigned codes based on tribal name. In the TIGER/Line files, a letter code- "T" for tribal and "I" for individual-appears in a separate field and identifies off-reservation trust lands. Hawaiian Home Lands (HHLs) are areas held in trust for native Hawaiians by the state of Hawaii, pursuant to the Hawaiian Homes Commission Act of 1920, as amended. Based on a compact between the federal government and the new state of Hawaii in 1959, the Hawaii Admission Act vested land title and responsibility for the program with the state. However, a Hawaiian home land is not a governmental unit; rather, a home land is a tract of land, with a legally defined boundary, that is owned by the state, which, as authorized by the Act, it may lease to one or more native Hawaiians for residential, agricultural, commercial, industrial, pastoral, and any other activities authorized by state law. The U.S. Census Bureau obtains the names and boundaries for Hawaiian home lands from state officials. The names of the home lands are based on the traditional ahupua'a names of the Crown and government lands of the Kingdom of Hawai'i from which the lands were designated, or from the local name for an area. Joint use areas, as applied to any American Indian area/Alaska Native area by the U.S. Census Bureau, means an area that is administered jointly and/or claimed by two or more American Indian tribes. The U.S. Census Bureau designates both legal and statistical joint use areas as unique geographic entities for the purpose of presenting statistical data. Statistical Entities Alaska Native village statistical areas (ANVSAs) represent the densely settled portion of Alaska Native villages (ANVs). The ANVs constitute associations, bands, clans, communities, groups, tribes, or villages recognized pursuant to the Alaska Native Claims Settlement Act of 1972 (Public Law 92-203). Because ANVs do not have boundaries that are easily locatable, the U.S. Census Bureau does not delimit ANVs for the purpose of presenting statistical data. Instead, the U.S. Census Bureau presents statistical data for ANVSAs which represent the settled portion of ANVs. ANVSAs are delineated or reviewed by officials of the ANV or, if no ANV official chose to participate in the delineation process, officials of the Alaska Native Regional Corporation (ANRC) in which the ANV is located. An ANVSA may not overlap the boundary of another ANVSA, an American Indian reservation, or a tribal designated statistical area (TDSA). Joint use areas, as applied to any American Indian area/Alaska Native area by the U.S. Census Bureau, means an area that is administered jointly and/or claimed by two or more American Indian tribes. The U.S. Census Bureau designates both legal and statistical joint use areas as unique geographic entities for the purpose of presenting statistical data. Oklahoma tribal statistical areas (OTSAs) are statistical entities identified and delineated by the U.S. Census Bureau in consultation with federally recognized American Indian tribes that do not currently have a reservation, but once had a reservation in Oklahoma. The boundary of an OTSA will be that of the former reservation in Oklahoma, except where modified by agreements with neighboring tribes for statistical data presentation purposes. State designated American Indian statistical areas (SDAISAs) are statistical entities for state recognized American Indian tribes that do not have a state recognized land base (reservation). SDAISAs are identified and delineated for the U.S. Census Bureau by a state liaison identified by the governor's office in each state. SDAISAs generally encompass a compact and contiguous area that contains a concentration of people who identify with a state recognized American Indian tribe and in which there is structured or organized tribal activity. A SDAISA may not be located in more than one state unless the tribe is recognized by both states, and it may not include area within an American Indian reservation, off-reservation trust land, Alaska Native village statistical area (ANVSA), tribal designated statistical area (TDSA), or Oklahoma tribal statistical area (OTSA). Tribal designated statistical areas (TDSAs) are statistical entities identified and delineated for the U.S. Census Bureau by federally recognized American Indian tribes that do not currently have a federally recognized land base (reservation or off-reservation trust land). A TDSA generally encompasses a compact and contiguous area that contains a concentration of individuals who identify with a federally recognized American Indian tribe and in which there is structured or organized tribal activity. A TDSA may be located in more than one state, but it may not include area within an American Indian reservation, off- reservation trust land, Alaska Native village statistical area (ANVSA), or Oklahoma tribal statistical area (OTSA). Current Geography The boundaries identified as current on Record Type A for some federally recognized American Indian Reservations, off-reservation trust lands, and tribal subdivisions are updated boundaries collected since Census 2000 as part of the Census Bureau's BAS. For all other legal entities and nearly all statistical areas, the boundaries shown are those in effect at the time of Census 2000 whether the data are identified as Census 2000 or current. Because OTSAs, SDAISAs, and TDSAs occupy the same level of geography as federally recognized American Indian Reservations and off-reservation trust lands, updates to the legal boundaries may affect the current boundaries for some of these entities. AIANA/HHL Code Record Locations Record Type Field Name Description 1 AIANHHFPL FIPS 55 Code (American Indian/Alaska Native Area/Hawaiian Home Land), 2000 Left 1 AIANHHFPR FIPS 55 Code (American Indian/Alaska Native Area/Hawaiian Home Land), 2000 Right 1 AIHHTLIL American Indian/Hawaiian Home Land Trust Land Indicator, 2000 Left 1 AIHHTLIR American Indian/Hawaiian Home Land Trust Land Indicator, 2000 Right A AIANHHFPCU FIPS 55 Code (American Indian/Alaska Native Area/Hawaiian Home Land), Current A AIANHHCU Census Code (American Indian/Alaska Native Area/Hawaiian Home Land), Current A AIHHTLICU American Indian/Hawaiian Home Land Trust Land Indicator, Current A ANRCCU FIPS 55 Code (ANRC), Current A AITSCECU Census Code (American Indian Tribal Subdivision), Current A AITSCU FIPS 55 Code (American Indian Tribal Subdivision), Current B AIANHHFPCQ FIPS 55 Code (American Indian/Alaska Native Area/Hawaiian Home Land), 2000 CQR B AIANHHCQ Census Code (American Indian/Alaska Native Area/Hawaiian Home Land), 2000 CQR B AIHHTLICQ American Indian/Hawaiian Home Land Trust Land Indicator, 2000 CQR B AITSCECQ Census Code (American Indian Tribal Subdivision), 2000 CQR B AITSCQ FIPS 55 Code (American Indian Tribal Subdivision), 2000 CQR B ANRCCQ FIPS 55 Code (ANRC), 2000 CQR C FIPS FIPS 55 Code C FIPSCC FIPS 55 Class Code C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C AIANHH Census American Indian/Alaska Native Area /Hawaiian Home Land Code C AITSCE Census American Indian Tribal Subdivision Code C NAME Name of Geographic Area S AIANHHFP FIPS 55 Code (American Indian/Alaska Native Area/Hawaiian Home Land), 2000 S AIANHH Census Code (American Indian/Alaska Native Area/Hawaiian Home Land), 2000 S AIHHTLI American Indian /Hawaiian Home Land Trust Land Indicator, 2000 S ANRC FIPS 55 Code (ANRC), 2000 S AITSCE FIPS 55 Code (American Indian Tribal Subdivision), 2000 S AITS FIPS 55 Code (American Indian Tribal Subdivision), 2000 AIANA/HHL Codes Record Type C shows one record for each AIANA/ HHL entity by year. Also, refer to FIPS 55 for a list of valid codes and entity names. The type of AIANA/HHL area can be identified either by the census code or by the FIPS 55 class code on each entity record in Record Type C. The range of census codes allocated to each AIANA/HHL and the valid FIPS 55 class code(s) associated with each are as follows: Type Census Code Range Valid FIPS 55 Class Federal AIR 0001 to 4999 D1, D2, D3 Hawaiian Home Land 5000 to 5499 F1 OTSA 5500 to 5999 D6 ANVSA 6000 to 7999 E1, E2, E6 TDSA 8000 to 8999 D6 State AIR 9000 to 9499 D4 SDAISA 9500 to 9998 D9 Type Trust Land Indicator Hawaiian Home Land H Individual Trust Land I Tribal Trust Land T Block Groups (BGs) Block groups are clusters of blocks within the same census tract having the same first digit of their 4-digit census block number. For example, blocks 3001, 3002, 3003, . . ., 3999 in census tract 1210.02 belong to BG 3. Census 2000 BGs generally contain between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the U.S. Census Bureau's Participant Statistical Areas Program. The U.S. Census Bureau delineated BGs only where a local or tribal government declined to participate or where the U.S. Census Bureau could not identify a potential local participant. A BG usually covers a contiguous area. Each census tract contains at least one BG and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy BGs never cross county or census tract boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian/Alaska Native areas/Hawaiian home lands. Under the Census 2000 American Indian/Alaska Native area/Hawaiian home land census geographic hierarchy, census tracts and BGs are defined within American Indian entities and can cross state and county boundaries. These are commonly referred to as tribal BGs. BGs have a valid range of 0 through 9. BGs beginning with a 0 generally are in coastal and Great Lakes water and territorial seas. Rather than extending a census tract boundary into the Great Lakes or out to the three-mile territorial sea limit, the U.S. Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The U.S. Census Bureau assigned a default census tract number of 0000 and BG of 0 to the offshore areas not included in regularly numbered census tract areas. In decennial census data tabulations, a block group may be split to present data for every unique combination of county subdivision, place, voting district, congressional district, American Indian area/Alaska Native area/Hawaiian home land shown in the data tabulation products. Current Geography BG boundaries follow legal county boundaries as of January 1, 2000. Because there have been state and/or county boundary changes since 2000, data users are cautioned that combining the Census 2000 census tract and block group numbers with the current state and county codes create nonexistent geographic areas. To avoid nonexistent geographic areas, it is important not to mix Census 2000 geographic codes with the current geographic codes. Block Group Number Record Locations Record Type Field Name Description S BLKGRP Census Block Group, 2000 All polygons have a non-blank BG number. The left- and right-side complete chain block numbers should not be blank except where they are located along the outside edge of the county boundary. The TIGER/Line files do not contain codes for areas outside the county file. Census Blocks Census blocks are statistical areas bounded on all sides by visible features such as streets, roads, streams, and railroad tracks, and by nonvisible boundaries such as city, town, township, and county limits, and short imaginary extensions of streets and roads. Generally census blocks are small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas may be large and irregular and contain hundreds of square miles. All territory in the United States, Puerto Rico, and the Island Areas have block numbers. Blocks are composed of one or more GT-polygons; that is, several GT- polygons can share the same block number. Tabulation blocks, used in Census 2000 data products, never cross county or census tract boundaries. Nor do they cross the boundaries of any entity for which the U.S. Census Bureau tabulates data including American Indian areas, Alaska Native areas, Hawaiian home lands, congressional districts, county subdivisions, military installations, national parks and monuments, places, state legislative districts, urbanized areas, urban clusters, school districts, voting districts, or ZIP Code Tabulation Areas (ZCTAs). Census Block Numbers Census 2000 tabulation blocks are numbered uniquely within each state/county/census tract with a four-digit census block number. The U.S. Census Bureau created the tabulation block numbers immediately before beginning its Census 2000 data tabulation process, thereby eliminating block suffixes for Census 2000. The first digit of the tabulation block number identifies the block group. Current Geography To accommodate changes in legal entity boundaries occurring after January 1, 2000, the U.S. Census Bureau assigns a current alphabetic suffix for a Census 2000 block number. The current suffixes for Census 2000 block numbers, which appear on Record Type A, are not permanent and will change with each annual cycle of current block suffixing. Data users are cautioned that in some Record Type A records, the current state and county codes, when combined with the Census 2000 census tract and block numbers, create nonexistent geographic areas. To avoid nonexistent geographic areas, it is important not to mix Census 2000 geographic codes with the current geographic codes. The Census 2000 state, county, census tract, and census block codes all are found on Record Type S. Since the distribution unit for the 2004 First Edition TIGER/Line files is current county, it is possible that to fully match all the Census 2000 blocks numbers in a Census 2000 county a user will need to reference multiple current 2004 First Edition TIGER/Line files. Water Blocks The U.S. Census Bureau introduced a different method for identifying the water areas of census blocks for Census 2000. For Census 2000, water area located completely within the boundary of a single land block has the same block number as that land block. Water area that touches more than one land block is assigned a unique block number not associated with any adjacent land block. The U.S. Census Bureau assigned water block numbers beginning with the block group number followed by "999 " and preceding in descending order. For example, in block group 3, the block numbers assigned to water areas that border multiple land blocks are 3999, 3998, 3997, and so forth. In some block groups, the numbering of land blocks used enough of the available tabulation block numbers to reach beyond the 900 range within the block group. For this reason, and because some land blocks include water (ponds and small lakes), no conclusions about whether or not a block is all land or all water can be made by looking at the Census 2000 block numbers. Data users must use the WATER field on Record Type P to determine if the GT-polygon is land or water. The WATER field has three values, blank for land, 1 for perennial water, or 2 for intermittent water. Census Block Number Record Locations Record Type Field Name Description 1 BLOCKL Census Block Number, 2000 Left 1 BLOCKR Census Block Number, 2000 Right A BLOCK Census Block Number, 2000 A BLOCKSUFCU Current Suffix for Census 2000 Block Number B BLOCKCQ Census Block Number, 2000 CQR S BLOCK Census Block Number, 2000 Census Block Codes Census 2000 Tabulation Blocks Block Group Number 0 to 9-First character 000 to 999-Second, third, and forth characters Current Suffix for Census 2000 Block Number A to Z-Codes for Current Suffix for Census 2000 Block Numbers Census 2000 block information appears on Record Type B-Corrected Geography for information purposes only. There are no corrections for census blocks. All polygons have a non-blank 4-digit Census 2000 block number. The left- and right- side complete chain block numbers are not blank except where they are located along the outside edge of the county. The TIGER/Line files do not contain geographic codes for the area outside of the county file. The TIGER/Line files identify boundary complete chains by placing a 1 in the single-side segment field in Record Type 1. Census Tracts Census tracts are small, relatively permanent statistical subdivisions of a county (or statistical equivalent of a county), and were defined by local participants as part of the U.S. Census Bureau's Participant Statistical Areas Program. The U.S. Census Bureau delineated the census tracts in situations where no local participant existed or where local or tribal governments declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of decennial census data. Census tracts generally have a population size between 1,500 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts are designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Census tract boundaries are delineated with the intention of being maintained over a long time so that statistical comparisons can be made from census to census. However, physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. Census tract boundaries may follow legal boundaries, such as minor civil division (MCD) or incorporated place boundaries, in some states and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries are always census tract boundaries in the standard census geographic hierarchy. Under the Census 2000 American Indian/Alaska Native area/Hawaiian home land census geographic hierarchy, tribal census tracts are defined within American Indian entities and can cross state and county boundaries. In a few rare instances, a census tract may consist of discontiguous areas. These discontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves discontiguous. Census Tract Numbering Census tract numbers have a 4-digit basic number and may have an optional 2- digit suffix; for example, 1457.02. Census tract numbers range from 0001 to 9999 and are unique within a county or equivalent area. The U.S. Census Bureau reserved the census tract numbering range of 9400 to 9499 for use by American Indian area participants in situations where an American Indian entity crosses county or state lines. See the section on Census Tracts in American Indian Areas below for further information. The U.S. Census Bureau assigned a default census tract number of 0000 to some coastal and Great Lakes water and territorial sea rather than extend the census tract boundary into the Great Lakes or out to the three-mile limit. By closing off some census tracts along the shoreline or just offshore and assigning the default census tract to the offshore water areas, the U.S. Census Bureau provides complete census tract coverage of water areas in territorial seas and the Great Lakes. Census tract suffixes may range from .01 to .98. For Census 2000, the U.S. Census Bureau did not identify separate crews- of-vessels census tracts; the crews-of-vessels population is part of the Census 2000 census tract identified as associated with the homeport of the vessel. See the section on Crews-of-Vessels later in this chapter for further information. The U.S. Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Local participants have an opportunity to review the existing census tracts before each census. If local participants split a census tract, the split parts usually retain the basic number, but receive different suffixes. In a few counties, local participants request major changes to, and renumber, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes. In printed reports and on mapping products, the U.S. Census Bureau uses a decimal point (.) to separate the basic number from the suffix. However, in the TIGER/Line files and Summary File (SF) data products, the decimal point is implied. The basic number and the suffix appear together in a single 6-character field in Record Types 1, A, B, and S. A basic number smaller than 1000 will contain leading zeros (for example, 002502). Leading zeros are shown on machine- readable products, but are not shown in printed reports or on census maps. The TIGER/Line files use the right-most two characters in the census tract field for the suffix. Where a census tract suffix does not exist, the suffix is zero filled in machine-readable products, but blank in printed reports and on census maps. Suffixes smaller than 10 have a leading zero. For example, census tract 0077.01 is shown as 007701 in the TIGER/Line files. Census Tract "Name" The 2004 First Edition TIGER/Line files contain the census tract numbers formatted to display as they appear on U.S. Census Bureau printed reports and on mapping products. That is, in the census tract "name" the leading and trailing zeros in the census tract number are omitted and the decimal point appears in those census tract numbers with a suffix. For example, census tract 000302 has a census tract "name" of 3.02 and the "name" for census tract 020800 is 208. Data users will find the census tract numbers formatted to display as a "name" on Record Type C. The census tract number appears in the Census Voting District Code/Census Tract Code field (field name VTDTRACT) and the census tract "name" appears in the Name of Geographic Area field. To distinguish between the voting district codes and census tract codes in the VTDTRACT field, users should use the Entity Type Code field on Record Type C. Census tract numbers have an entity type code of "T." Current Geography Census tract boundaries follow legal county boundaries as of January 1, 2000. Because there have been state and/or county boundary changes since 2000, data users are cautioned that in some Record Type A records the current state and county codes, when combined with the Census 2000 census tract numbers, create nonexistent geographic areas. To avoid nonexistent geographic areas, it is important not to mix Census 2000 geographic codes with the current geographic codes. The Census 2000 state, county, and census tract codes all are found on Record Type S. Census Tracts in American Indian Areas The U.S. Census Bureau reserved the census tract numbering range of 9400 to 9499 for use by American Indian area participants in situations where an American Indian entity crosses county or state boundaries. Under the Census 2000 American Indian/Alaska Native area/Hawaiian home land census geographic hierarchy, the U.S. Census Bureau tabulates census tract data within federally recognized American Indian reservations and off-reservation trust lands ignoring state and county boundaries. These are commonly referred to as tribal census tracts. Not all tribal census tracts are numbered in the 9400 to 9499 census tract numbering range. Under the Census 2000 American Indian/Alaska Native area/Hawaiian home land census geographic hierarchy the U.S. Census Bureau identifies all census tracts on federally recognized American Indian reservations and off-reservation trust lands as tribal census tracts. Relationship to Other Geographic Entities Within the standard census geographic hierarchy, census tracts never cross state or county boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian/Alaska Native areas/Hawaiian home lands. Under the Census 2000 American Indian/Alaska Native area/Hawaiian home land census geographic hierarchy, tribal census tracts are defined within American Indian entities and cross state and county boundaries. Census Tract Code Record Locations Record Type Field Name Description 1 TRACTL Census Tract Code, 2000 Left 1 TRACTR Census Tract Code, 2000 Right A TRACT Census Tract, 2000 B TRACTCQ Census Tract, 2000 CQR C ENTITY Entity Type Code C VTDTRACT Census Voting District Code/Census Tract Code C NAME Name of Geographic Area S TRACT Census Tract, 2000 Census Tract Codes 0001 to 9989-Basic number range for census tracts 0000-Default basic number for census tracts 01 to 98-Suffix codes for census tracts 00-Suffix code for census tracts without a suffix Census 2000 census tract information appears on Record Type B-Corrected Geography for information purposes only. There are no corrections for census tracts. All polygons have a non-blank census tract basic number. The left- and right-side complete chain census tract numbers are not blank except where they are located along the outside edge of the county boundary. The TIGER/Line files do not contain geographic codes for the area outside of the county file. The TIGER/Line files identify the boundary complete chains by placing a 1 in the single-side segment field in Record Type 1. Congressional Districts Congressional districts are the 435 areas from which people are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the states, based on census population counts, each state is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a state as practicable. The 2004 First Edition TIGER/Line files contain both the 108th and 106th Congressional Districts. The congressional districts for the 108th Congress (January 2003 to 2005) are the first to reflect redistricting based on Census 2000. Where the boundary of a congressional district for the 108th Congress splits a Census 2000 block, the Census Bureau's TIGER/Line files depict the location of the boundary correctly. For data tabulation purposes, the population of that split block is allocated in its entirety to the 108th Congressional District specified by the state. The 108th Congressional Districts appearing in the 2004 First Edition TIGER/Line files reflect the information provided to the Census Bureau by the states. The congressional districts in effect at the time of Census 2000 were those of the 106th Congress, whose session began in January 1999. In North Carolina the "1998 Congressional Plan A" was used for the 1998 congressional elections. It was created in response to a court ruling which held the 1997 plan, "97 House/Senate Plan A," unconstitutional. The Supreme Court has since reversed that lower court ruling and the "1998 Congressional Plan A" was used for the 2000 North Carolina congressional elections. The 106th Congressional Districts appearing in the 2004 First Edition TIGER/Line files for North Carolina are the "97 House/Senate Plan A" Congressional Districts. Congressional districts are identified by a 2-character numeric FIPS code. The 2004 First Edition TIGER/Line files contain fields for the current, the 106th, and the 108th Congressional Districts. Congressional districts are numbered uniquely within state. Congressional District Record Locations Record Type Field Name Description A CDCU Congressional District Code, Current (108th) S CD106 Congressional District Code, 106th S CD108 Congressional District Code, 108th Congressional District Codes 01 to 53-Congressional district codes 00-At large (single district for state) 98-Nonvoting delegate 99-Area with no representative in Congress Counties and Statistically Equivalent Entities The primary legal divisions of most states are termed "counties." In Louisiana, these divisions are known as "parishes." In Alaska, which has no counties, the statistically equivalent entities are the organized "boroughs," "city and boroughs," "municipality," and "census areas;" the latter are delineated cooperatively for statistical purposes by the State of Alaska and the U.S. Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as "independent cities" and are treated as statistically equivalent entities for purposes of data presentation. The District of Columbia has no primary divisions, and the entire area is considered a statistically equivalent entity for purposes of data presentation. The U.S. Census Bureau treats the following entities as statistical equivalents of counties for purposes of data presentation: municipios in Puerto Rico; Islands in the U.S. Virgin Islands; and a variety of entities in the Pacific Island Areas. The TIGER/Line files contain several 3-character numeric fields identifying the FIPS county code for Census 2000. Each individual TIGER/Line file contains state and county code fields to uniquely identify its records. See Appendix A for a list of FIPS codes for county and statistically equivalent entities. Current Geography Since Census 2000, there have been two changes to the universe of county or statistically equivalent entities. In Colorado, Broomfield County was created from parts of Adams, Boulder, Jefferson, and Weld Counties. The independent city of Clifton Forge, Virginia changed its status to become Clifton Forge town and is now part of Alleghany County, Virginia. The 2004 First Edition TIGER/Line files are based on the boundaries of the counties or statistical equivalent entities based on the latest available governmental unit boundaries. In some Record Type A records, the current state and county, when combined with the Census 2000 census tract and block numbers, create nonexistent geographic areas. To avoid nonexistent geographic areas, it is important not to mix Census 2000 geographic codes with the current geographic codes. The Census 2000 state, county, census tract, and census block codes all are found on Record Type S. County and Statistically Equivalent Entity Code Record Locations Record Type Field Name Description 1 COUNTYL FIPS County Code, 2000 Left 1 COUNTYR FIPS County Code, 2000 Right A COUNTYCU FIPS County Code, Current B COUNTYCQ FIPS County Code, 2000 CQR C COUNTY FIPS County Code C FIPSCC FIPS 55 Class Code C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C NAME Name of Geographic Area E COUNTYEC FIPS County Code, Economic Census S COUNTY FIPS County Code, 2000 All polygons have a non-blank county code. To improve the ability of data users to merge multiple counties, the U.S. Census Bureau has added the state and county codes to those Record Type 1 records of the adjacent county (these are the Record Type 1 records that have a 1 in the single-side segment field). The 2002 TIGER/Line files are the first version of the TIGER/Line files to include the county code for the side of the record "outside" the county. The left- and right-side complete chain county codes are not blank except where they are located along the outside edge of the boundary of the United States. In counties or statistically equivalent entities that have gained territory since January 1, 2000, it is possible to have a complete chain that is a current county boundary and has the SIDE1 flag set, but has the same state and county codes on both sides of the complete chain. This occurs because a polygon that was, for example, in the Census 2000 TIGER/Line file for County A now is in the post-Census 2000 TIGER/Line file for County B. Since Record Type 1 displays the Census 2000 geography, the state and county code for County A (the county or statistically equivalent entity the lost territory) appears on this complete chain even though it currently is part of County B. The other side of this complete chain is in an adjacent TIGER/Line file and the U.S. Census Bureau appends the current state and county code of the adjacent county (County A) to this complete chain. The result is a complete chain that is a current county boundary yet has the same state and county codes on both sides of the complete chain. County Subdivisions County subdivisions are the primary divisions of counties and their statistical equivalents for the reporting of decennial census data. They include census county divisions, census subareas, minor civil divisions, and unorganized territories. The TIGER/Line files contain a 5-character numeric FIPS code field for county subdivisions. They use a single field to identify the two functional types (legal and statistical) of county sub-divisions. Record Type C contains all valid codes and entity names. Legal Entities Minor Civil Divisions (MCDs) MCDs are the primary governmental or administrative divisions of a county in many states. MCDs represent many different kinds of legal entities with a wide variety of governmental and/or administrative functions. MCDs are variously designated as American Indian reservations, assessment districts, boroughs, election districts, gores, grants. locations, magisterial districts, parish governing authority districts, plantations, precincts, purchases, road districts, supervisor's districts, towns, and townships. The U.S. Census Bureau recognizes MCDs in 28 states, Puerto Rico, and the Island Areas. The District of Columbia has no primary divisions, and the District of Columbia is considered equivalent to an MCD for statistical purposes. In some states, all or some incorporated places are not part of any MCD. These places also serve as primary legal subdivisions and have a unique FIPS MCD code that is the same as the FIPS place code. The TIGER/Line files will show the same FIPS 55 code in the county subdivision field and the place field. In other states, incorporated places are part of the MCDs in which they are located, or the pattern is mixed-some incorporated places are independent of MCDs and others are included within one or more MCDs. The MCDs in 12 states (Connecticut, Maine, Massachusetts, Michigan, Minnesota, New Hampshire, New Jersey, New York, Pennsylvania, Rhode Island, Vermont, and Wisconsin) also serve as general -purpose local governments that generally can perform the same governmental functions as incorporated places. The U.S. Census Bureau presents data for these MCDs in all data products in which it provides data for places. In New York and Maine, American Indian reservations (AIRs) exist outside the jurisdiction of any town (MCD) and thus also serve as the statistical equivalent of MCDs for purposes of data presentation. Statistical Entities Census County Divisions (CCDs) CCDs are areas delineated by the U.S. Census Bureau, in cooperation with state officials and local officials for statistical purposes. CCDs have no legal function and are not governmental units. CCD boundaries usually follow visible features and in most cases, coincide with census tract boundaries. The name of each CCD is based on a place, county, or well-known local name that identifies its location. CCDs exist where: 1) There are no legally established minor civil divisions (MCDs). 2) The legally established MCDs do not have governmental or administrative purposes. 3) The boundaries of the MCDs change frequently. 4) The MCDs are not generally known to the public. CCDs have been established for the following 21 states: Alabama Hawaii Oregon Arizona Idaho South Carolina California Kentucky Tennessee Colorado Montana Texas Delaware Nevada Utah Florida New Mexico Washington Georgia Oklahoma Wyoming Census Subareas Census subareas are statistical subdivisions of boroughs, city and boroughs, municipalities, and census areas, the statistical equivalent entities for counties in Alaska. The state of Alaska and the U.S. Census Bureau cooperatively delineate the census subareas to serve as the statistical equivalents of MCDs. Census subareas were first used in the 1980 census. Unorganized Territories (UTs) The U.S. Census Bureau defines unorganized territories in 10 minor civil division (MCD) states where portions of counties are not included in any legally established MCD or incorporated place. The U.S. Census Bureau recognizes such separate pieces of territory as one or more separate county subdivisions for census purposes. It assigns each unorganized territory a descriptive name, followed by the designation "unorganized territory" and a county subdivision code. Unorganized territories were first reported in the 1960 census. The following states have unorganized territories: Arkansas Indiana Iowa Louisiana Maine Minnesota North Carolina North Dakota Ohio South Dakota Current Geography The boundaries identified as current for MCDs are updated boundaries collected since Census 2000 as part of the U.S. Census Bureau's Boundary and Annexation Survey. Because unorganized territories occupy the same level of geography as legal MCDs, updates to the MCD boundaries may affect the current boundaries of the unorganized territories, including the elimination of some of the Census 2000 unorganized territories. For all other statistical county subdivision entities, the boundaries shown are those in effect at the time of Census 2000 whether the data are identified as Census 2000 or current. County Subdivision Code Record Locations Record Type Field Name Description 1 COUSUBL FIPS 55 Code (County Subdivision), 2000 Left 1 COUSUBR FIPS 55 Code (County Subdivision), 2000 Right A COUSUBCU FIPS 55 Code (County Subdivision), Current B COUSUBCQ FIPS 55 Code (County Subdivision), 2000 CQR C FIPSCC FIPS 55 Class Code C PLACEDC Place Description Code C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C NAME Name of Geographic Area E COUSUBEC FIPS 55 Code (County Subdivision), Economic Census S COUSUB FIPS 55 Code (County Subdivision), 2000 The U.S. Census Bureau assigns a default county subdivision code of 00000 in some coastal and Great Lakes water where county subdivisions do not extend into the Great Lakes or out to the three-mile limit. Crews-of-Vessels Crews-of-vessels refers to the population on military (including Coast Guard) and merchant ships; they do not include the inhabitants of house-boats or marinas. For Census 2000, the U.S. Census Bureau is not delineating separate crews-of-vessels census tracts or blocks. Instead it is assigning the crews-of- vessels population to the land block identified as being associated with the home-port of the vessel. A point landmark, with the census feature class code (CFCC) of D25, appears in the TIGER/Line files indicating within which Census 2000 tabulation block(s) the crews-of-vessels population is assigned. Metropolitan and Micropolitan Statistical Areas On June 6, 2003, the U.S. Office of Management and Budget (OMB) announced the definition of metropolitan statistical areas and micropolitan statistical areas based on the official standards that were published in the Federal Register on December 27, 2000. These standards were developed by the interagency Metropolitan Area Standards Review Committee to provide a nationally consistent set of geographic entities. The general concept of a metropolitan statistical area or micropolitan statistical area is that of a core area containing a substantial population nucleus, together with adjacent communities having a high degree of economic and social integration with that core. The term core based statistical area (CBSA) became effective in 2000 and refers collectively to metropolitan statistical areas and micropolitan statistical areas. The 2000 standards provide that each CBSA must contain at least one urban area of 10,000 or more population. Each metropolitan statistical area must have at least one urbanized area of 50,000 or more inhabitants. Each micropolitan statistical area must have at least one urban cluster of at least 10,000 but less than 50,000 population. The categorization of CBSAs as either a metropolitan statistical area or a micropolitan statistical area is based on the population in the most populous (or dominant) core not the total CBSA population or the total population of all (multiple) cores within the CBSA. If specified criteria are met, a metropolitan statistical area containing a single core with a population of 2.5 million or more may be subdivided to form smaller groupings of counties referred to as metropolitan divisions. Under the standards, the county (or counties) or statistically equivalent entity (or entities) in which at least 50 percent of the population resides within urban areas of 10,000 or more population, or that contain at least 5,000 people residing within a single urban area of 10,000 or more population, is identified as a central county (counties). Additional outlying counties are included in the CBSA if they meet specified requirements of commuting to or from the central counties. Counties or statistically equivalent entities form the building blocks for metropolitan and micropolitan statistical areas throughout the United States and Puerto Rico. In New England the OMB has defined an alternative city and town based definition of CBSAs known as New England City and Town Areas (NECTAs). The NECTAs are defined using the same criteria as metropolitan statistical areas and micropolitan statistical areas and are identified as either metropolitan or micropolitan, based, respectively, on the presence of either and urbanized area of 50,000 or more population or an urban cluster of at least 10,000 and less than 50,000 population. A NECTA containing a single core with a population of at least 2.5 million may be subdivided to form smaller groupings of cities and towns referred to as NECTA Divisions. The metropolitan and micropolitan statistical area boundaries, names, and codes appearing in the 2004 First Edition TIGER/Line files are those in effect at the time of OMB's announcement on June 6, 2003. Users interested in the December, 2003 updates should refer to OMB Bulletin No. 04-03 at URL: http://www.whitehouse.gov/omb/bulletins/fy04/b04-03.html. The boundaries of the legal entities (that is counties, incorporated places, and county subdivisions) are those as of January 1, 2000 as determined in the Boundary and Annexation Survey except for the following Colorado Counties; Adams, Boulder, Broomfield, Jefferson, and Weld. Broomfield County, Colorado is the only component of a metropolitan or micropolitan statistical area that did not exist as a county as of January 1, 2000. Because Broomfield County was in existence for a year and a half before OMB's announcement of new metropolitan and micropolitan statistical area definitions in mid-2003, OMB decided to treat Broomfield city as if it was a county at the time of the decennial census, and the CBSA standards were applied to data for Broomfield city. As part of the CBSA delineation, the boundaries for Adams, Boulder, Jefferson, and Weld Counties were adjusted to remove the area covered by Broomfield city on January 1, 2000. The TIGER/Line files contain six different fields to identify the CBSAs. Data users will find the metropolitan and micropolitan statistical areas in the CBSA field and the metropolitan and micropolitan New England Town and City Areas (NECTAs) in the NECTA field. Record Type C uses two fields to identify the CBSAs. The three-digit CSACNECTA field contains the Combined Statistical Area and Combined New England City and Town Area codes. The five-digit CBSANECTA field contains the CBSA, NECTA, Metropolitan Division, and New England City and Town Area Division codes. The Legal/Statistical Area Description code identifies the type (metropolitan or micropolitan) of CBSA or NECTA. Combined New England City and Town Areas (CNECTAs) A combined New England city and town area consists of two or more adjacent New England city and town areas (NECTAs) that have employment interchange measures of at least 15. The NECTAs that combine retain separate identities within the larger combined statistical areas. Because combined New England city and town areas represent groupings of NECTAs they should not be ranked or compared with individual NECTAs. Combined Statistical Areas (CSAs) A combined statistical area consists of two or more adjacent CBSAs that have employment interchange measures of at least 15. The CBSAs that combine retain separate identities within the larger combined statistical areas. Because combined statistical areas represent groupings of metropolitan and micropolitan statistical areas they should not be ranked or compared with individual metropolitan and micropolitan areas. Core Based Statistical Areas (CBSAs) A CBSA consists of the county or counties or statistically equivalent entities associated with at least one core (urbanized area or urban cluster) of at least 10,000 population, plus adjacent counties having a high degree of social and economic integration with the core as measured through commuting ties with the counties containing the core. A CBSA receives a category based on the population of the largest urban area within the CBSA. Categories of CBSAs are: metropolitan statistical areas, based on urbanized areas of 50,000 or more population, and micropolitan statistical areas, based on urban clusters of at least 10,000 population but less than 50,000 population. Counties or statistically equivalent entities that do not fall within a CBSA are identified as "Outside Core Based Statistical Areas." Metropolitan Divisions A metropolitan statistical area containing a single core with a population of at least 2.5 million may be subdivided to form smaller groupings of counties or statistically equivalent entities referred to as Metropolitan Divisions. Not all metropolitan statistical areas with urbanized areas of this size will contain metropolitan divisions. A metropolitan division consists of one or more main/secondary counties that represent an employment center or centers, plus adjacent counties associated with the main county or counties through commuting ties. Because metropolitan divisions represent subdivisions of (larger) metropolitan statistical areas, it is not appropriate to rank or compare metropolitan divisions with metropolitan and micropolitan statistical areas. It would be appropriate to rank and compare metropolitan divisions. Metropolitan Statistical Areas A metropolitan statistical area is a CBSA associated with at least one urbanized area that has a population of at least 50,000. The metropolitan statistical area comprises the central county or counties or statistically equivalent entities containing the core, plus adjacent outlying counties having a high degree of social and economic integration with the central county as measured through commuting. Micropolitan Statistical Areas A micropolitan statistical area is a CBSA associated with at least one urban cluster that has a population of at least 10,000, but less than 50,000. The micropolitan statistical area comprises the central county or counties or statistically equivalent entities containing the core, plus adjacent outlying counties having a high degree of social and economic integration with the central county as measured through commuting. New England City and Town Areas (NECTAs) NECTAs are an alternative set of geographic entities, similar in concept to the county based CBSAs, that OMB defines in New England based on cites and towns. NECTAs receive a category in a manner similar to CBSAs and are referred to as Metropolitan NECTAs or a Micropolitan NECTAs. New England City and Town Area (NECTA) Divisions A NECTA containing a single core with a population of at least 2.5 million may be subdivided to form smaller groupings of cities and towns referred to as NECTA Divisions. A NECTA division consists of a main city or town that represents an employment center, plus adjacent cities and towns associated with the main city or town through commuting ties. Each NECTA division must contain a total population of 100,000 or more. Because NECTA divisions represent subdivisions of (larger) NECTAs, it is not appropriate to rank or compare NECTA divisions with NECTAs. It would be appropriate to rank and compare NECTA divisions. Principle Cities The Principle City of a CBSA (metropolitan statistical area, micropolitan statistical area or NECTA) includes the largest incorporated place with a Census 2000 population of at least 10,000 in the CBSA or, if no incorporated place of at least 10,000 population is present in the CBSA, the largest incorporated place or census designated place (CDP) in the CBSA. Principle cities also include any additional incorporated place or CDP with a Census 2000 population of at least 250,000 or in which 100,000 or more persons work. The OMB also defines as principle cities any additional incorporated place or CDP with a Census 2000 population of at least 10,000, but less than 50,000, and one-third the population size of the largest place, and in which the number of jobs meets or exceeds the number of employed residents. The term "principle city" replaces "central city." Census 2000 Metropolitan Areas (MAs) Metropolitan areas (MAs) were designated and defined by the U.S. Office of Management and Budget (OMB), following a set of official standards that were published in a Federal Register Notice. These standards were developed by the interagency Metropolitan Area Standards Review Committee, with the aim of producing definitions that are as consistent as possible for all MAs nationwide. The general concept of an MA is one of a large population nucleus, together with adjacent communities that have a high degree of economic and social integration with that nucleus. Some MAs were defined around two or more nuclei. Each MA contains either a place with a minimum population of 50,000 or a U.S. Census Bureau defined urbanized area and a total MA population of at least 100,000 (75,000 in New England). An MA contains one or more central counties and may include one or more outlying counties that have close economic and social relationships with the central county. An outlying county must have had a specified level of commuting to the central counties and also must have met certain standards regarding metropolitan character, such as population density, urban population, and population growth. In New England, MAs consist of cities and towns rather than whole counties. The territory, population, and housing units in Census 2000 MAs are referred to as "metropolitan." The territory, population, and housing units located outside MAs is referred to as "nonmetropolitan." The metropolitan and nonmetropolitan classification cut across the other hierarchies; for example, there is generally both urban and rural territory within both metropolitan and nonmetropolitan areas. There are three types of Census 2000 metropolitan areas. If a metropolitan area had a total population of less than 1,000,000, the area was designated a Metropolitan Statistical Area (MSA). Metropolitan areas with a population of 1,000,000 or greater qualified for designation as a Consolidated Metropolitan Statistical Area (CMSA) that was composed of smaller Primary Metropolitan Statistical Areas (PMSAs). In New England, there also was an alternative county- based definition of MSAs known as the New England County Metropolitan Areas (NECMAs). The TIGER/Line files contain three different 4-character numeric fields to identify the FIPS code for each Census 2000 metropolitan area or NECMA and to differentiate CMSAs and MSAs from PMSAs. The FIPS codes are from FIPS PUB 8. If the Census 2000 metropolitan area is a CMSA then a value exists in the MSACMSA field identifying the CMSA and the value in the PMSA field identifies the PMSA. A blank PMSA field indicates the code in the MSACMSA field is for the MSA. The NECMA code appears in the NECMA field. Record Type C uses a single metropolitan area field to identify CMSAs, MSAs, PMSAs, and NECMAs. The Legal/Statistical Area Description code identifies the type of metropolitan area. Census 2000 Metropolitan Area Central Cities In each metropolitan statistical area (MSA) and consolidated metropolitan statistical area (CMSA), the largest place and, in some cases, additional places were designated as "central cities" under the official standards. A few primary metropolitan statistical areas (PMSAs) do not have central cities. The largest central city and, in some cases, up to two additional central cities are included in the title of the MA; there also are central cities that were not included in an MA title. An MA central city does not include any part of that place that extends outside the MA boundary. Census 2000 Consolidated Metropolitan Statistical Areas (CMSAs) and Primary Metropolitan Statistical Areas (PMSAs) If an area that qualified as a Census 2000 MA had more than one million people, primary metropolitan statistical areas (PMSAs) may have been defined within it. PMSAs consist of a county or cluster of counties (cities and towns in New England) that demonstrate very strong internal economic and social links, in addition to close ties to other portions of the larger area. When PMSAs were established, the larger MA of which they were component parts was designated a consolidated metropolitan statistical area (CMSA). CMSAs and PMSAs were established only where local governments favored such a designation for a large MA. Census 2000 Metropolitan Statistical Areas (MSAs) Census 2000 Metropolitan statistical areas (MSAs) are MAs that are not closely associated with other MAs. These areas typically are surrounded by nonmetropolitan counties (county subdivisions in New England). Census 2000 New England County Metropolitan Areas (NECMAs) New England county metropolitan areas (NECMAs) are defined as a county-based alternative to the city and town based Census 2000 New England MSAs and CMSAs. The NECMA defined for an MSA or CMSA includes: The county containing the first-named city in that MSA/CMSA title (this county may include the first-named cities of other MSAs/CMSAs as well. Each additional county having at least half its population in the MSAs/CMSAs whose first-named cities are in the previously identified county. NECMAs are not identified for individual PMSAs. Core Based Statistical Area and Metropolitan Area Code Record Locations Record Type Field Name Description A CBSACU FIPS Core Based Statistical Area Code, Current A CSACU FIPS Combined Statistical Area Code, Current A NECTACU FIPS New England City and Town Area Code, Current A CNECTACU FIPS Combined New England City and Town Area Code, Current A METDIVCU FIPS Metropolitan Division Code, Current A NECTADIVCU FIPS New England City and Town Area Division Code, Current C MA Census 2000 Metropolitan Area Code C CSACNECTA Combined Statistical Area/Combined New England City and Town Area Code C CBSANECTA Core Based Statistical Area/New England City and Town Area/Metropolitan Division/New England City and Town Area Division Code C LSADC Legal/Statistical Area Description Code C ENTITY Entity Type Code C NAME Name of Geographic Area S MSACMSA FIPS Consolidated Metropolitan Statistical Area/Metropolitan Statistical Area Code, 2000 S PMSA FIPS Primary Metropolitan Statistical Area Code, 2000 S NECMA FIPS New England County Metropolitan Statistical Area Code, 2000 Core Based Statistical Area and Census 2000 Metropolitan Area Codes The Metropolitan Statistical Areas, Micropolitan Statistical Areas, New England City and Town Areas (NECTAs), Metropolitan Divisions, and New England City and Town Area (NECTA) Divisions are identified using a 5-digit numeric code. The codes for metropolitan and micropolitan statistical areas and metropolitan divisions are assigned in alphabetical order by area title and fall within the 10000 to 59999 range. Metropolitan divisions are distinguished by a 5-digit code ending in "4." NECTA and NECTA division codes fall within the 70000 to 79999 range and are assigned in alphabetical order by area title. NECTA divisions are distinguished by a 5-digit code ending in "4." The Combined Statistical Area and Combined New England City and Town Areas are identified using a 3-digit numeric code. Combined statistical area codes fall within the 100 to 599 range. Combined NECTA codes fall within the 700 to 799 range. Record Type C in the TIGER/Line files contains all the valid CBSA, Combined Statistical Area, NECTA, Combined New England City and Town Area, Metropolitan Division and NECTA Division codes and entity names. The Census 2000 metropolitan areas are identified using the 4-character numeric FIPS codes. Record Type C contains all the valid Census 2000 codes and entity names for CMSAs, MSAs, PMSAs, and NECMAs. Places Places, for the reporting of decennial census data, include census designated places (CDPs), consolidated cities, and incorporated places. The TIGER/Line files use a single field to identify places that are legal entities, and places that are statistical entities. The FIPS place code uniquely identifies a place within a state. If place names are duplicated within a state and they represent distinctly different areas, a separate code is assigned to each place name alphabetically by primary county in which each place is located, or if both places are in the same county, alphabetically by their legal descriptions (for example, "city" before "village"). Legal Entities Consolidated Cities A consolidated government is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have merged. The legal aspects of this action may result in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated government, the primary incorporated place is referred to as a "consolidated city." The U.S. Census Bureau classifies the separately incorporated places within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any other place. Refer to the section on Consolidated City (Balance) Portions below for additional information. Consolidated cities are represented in the TIGER/Line files by a 5-character numeric FIPS code. Record Type C has the complete list of valid codes and entity names. Incorporated Places Incorporated places are those reported to the U.S. Census Bureau as legally in existence as of the latest Boundary and Annexation (BAS) Survey, under the laws of their respective states. An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division, which generally is created to provide services or administer an area without regard, necessarily, to population. Places may extend across county and county subdivision boundaries. An incorporated place can be a city, city and borough, borough, municipality, town, village, or rarely, undesignated. But, for census purposes, incorporated places exclude: The boroughs in Alaska (treated as statistical equivalents of counties) Towns in the New England States, New York, and Wisconsin (treated as MCDs) The boroughs in New York (treated as MCDs) The balance portions of consolidated cities (statistical equivalents of incorporated places) The incorporated places known as "independent cities" in Maryland, Missouri, Nevada, and Virginia (treated as statistical equivalents of counties) Statistical Entities Census Designated Places (CDPs) CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name but are not legally incorporated under the laws of the state in which they are located. The boundaries usually are defined in cooperation with local or tribal officials. These boundaries, which usually coincide with visible features or the boundary of an adjacent incorporated place or a other legal entity boundary, have no legal status, nor do these places have officials elected to serve traditional municipal functions. CDP boundaries may change from one decennial census to the next with changes in the settlement pattern; a CDP with the same name as in an earlier census does not necessarily have the same boundary. There are no population size requirements for CDPs for Census 2000. Hawaii is the only state that has no incorporated places recognized by the U.S. Census Bureau. All places shown in the Census 2000 data products for Hawaii are CDPs. By agreement with the State of Hawaii, the U.S. Census Bureau does not show data separately for the city of Honolulu, which is coextensive with Honolulu County. In Puerto Rico, which also does not have incorporated places, the U.S. Census Bureau recognizes only CDPs. The CDPs in Puerto Rico are called comunidades or zonas urbanas. Guam and the Northern Mariana Islands also have only CDPs. Since CDPs are valid only for the presentation of decennial census data, CDPs appear on Record Types 1 and S, but not in Record Type A which contains current geography. The exception is in Hawaii, Puerto Rico, Guam, and the Northern Mariana Islands which have only CDPs. In these states and statistically equivalent entities CDPs appear in Record Types 1, A, and S. Consolidated City (Balance) Portions Consolidated city (balance) portions refer to the areas of a consolidated city not included in another incorporated place. For example, Columbus city, GA, is a consolidated city that includes the separately incorporated municipality of Bibb City town. The area of the consolidated city that is not in Bibb City town is assigned to Columbus city (balance). The name always includes the "(balance)" identifier. Dependent and Independent Places Depending on the state, incorporated places are either dependent within, or independent of, county subdivisions, or there is a mixture of dependent and independent places in the state. Dependent places are part of the county subdivision; the county subdivision code of the place is the same as that of the underlying county subdivision(s), but is different from the FIPS place code. Independent places are separate from the adjoining county subdivisions and have their own county subdivision code (or codes if the place lies in multiple counties). These places also serve as primary county subdivisions. The TIGER/Line files will show the same FIPS 55 code in the FIPS county subdivision code field and the FIPS place code field for independent places. The only exception is if the place is independent of the MCDs in a state in which the FIPS MCD codes are in the 90000 range. Then, the FIPS MCD and FIPS place codes will differ. CDPs and balance portions of consolidated cities (Class C8) always are dependent within county subdivisions. Corporate Corridors and Offset Corporate Boundaries A corporate corridor is a narrow, linear part of an incorporated place (or in a very few instances, another legal entity). The corporate corridor includes the street and/or right-of-way, or a portion of the street and/or right-of-way within the incorporated place. It excludes from the incorporated place those structures such as houses, apartments, or businesses, that front along the street or road. A corporate limit offset boundary exists where the incorporated place lies on only one side of the street, and may include all or part of the street and/or the right-of-way. It does not include the houses or land that adjoin the side of the street with the corporate limit offset boundary. It is possible to have two or more corporate limit offset boundaries in the same street or right-of-way. Corporate limit offset boundaries use the same map symbology as non-offset boundaries. To facilitate address coding, the street name and address ranges are generally duplicated on complete chains with a CFCC of F11 (offset boundary of a legal entity) or F12 (corridor boundary of a legal entity). The duplicate street names for the F11 and F12 features are on Record Type 5 and the duplicate address ranges are on Record Type 6. However, Record Type 1 will not indicate that the street or right-of-way lies within a corporate corridor or offset boundary, or that the address ranges lie outside, and are encoded on either side, of the corporate corridor or offset boundary. When data users find duplicate address ranges where one of the duplicates is on a complete chain with a CFCC of F11 or F12, they should use this address range for address geocoding rather than the range on the street feature that has a CFCC beginning with A. Likewise, use the street name and address ranges on the related street feature (CFCC beginning with A) for mapping or vehicle routing. Current Geography The boundaries identified as current for incorporated places are updated boundaries collected since Census 2000 as part of the U.S. Census Bureau's Boundary and Annexation Survey. Because CDPs occupy the same level of geography as legal incorporated places, updates to the incorporated place boundaries may affect the current boundaries of the CDPs, including the elimination of some of the Census 2000 CDPs. Since CDPs are valid only for the presentation of decennial census data, CDPs appear on Record Types 1 and S, but not in Record Type A which contains current geography. The exception is in Hawaii, Puerto Rico, Guam, and the Northern Mariana Islands which have only CDPs. In these states and statistically equivalent entities CDPs appear in Record Types 1, A, and S. Incorporated Place/CDP Code Record Locations Record Type Field Name Description 1 PLACEL FIPS 55 Code (Place/CDP), 2000 Left 1 PLACER FIPS 55 Code (Place/CDP), 2000 Right A CONCITCU FIPS 55 Code (Consolidated City), Current A PLACECU FIPS 55 Code (Incorporated Place), Current B CONCITCQ FIPS 55 Code (Consolidated City), 2000 CQR B PLACECQ FIPS 55 Code (Incorporated Place), 2000 CQR C FIPS FIPS 55 Code C FIPSCC FIPS 55 Class Code C PLACEDC Place Description Code C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C NAME Name of Geographic Area E CONCITEC FIPS 55 Code (Consolidated City), Economic Census E PLACEEC FIPS 55 Code (Economic Census Place), Economic Census S CONCIT FIPS 55 Code (Consolidated City), 2000 S PLACE FIPS 55 Code (Incorporated Place/CDP), 2000 Legally incorporated places and CDPs are mutually exclusive and are identified in the same TIGER/Line field. Public Use Microdata Areas (PUMAs) A public use microdata area (PUMA) is a decennial census area for which the U.S. Census Bureau provides selected extracts of raw data from a small sample of long-form census records that are screened to protect confidentiality. These extracts are referred to as public use microdata sample (PUMS) files. For Census 2000, state, District of Columbia, and Puerto Rico participants, following U.S. Census Bureau criteria, delineated two types of PUMAs within their states or statistically equivalent entity. PUMAs of one type comprise areas that contain at least 100,000 people. The PUMS files for these PUMAs contain a 5-percent sample of the long-form records. The other type of PUMAs, super-PUMAs, comprise areas of at least 400,000 people. The sample size is 1- percent for the PUMS files for super-PUMAs. PUMAs cannot be in more than one state or statistically equivalent entity. The larger 1-percent PUMAs are aggregations of the smaller 5-percent PUMAs. The 2004 First Edition TIGER/Line files contain Public Use Microdata Area File, 2000 fields containing the PUMA codes from both the 5-percent and 1-percent samples. Where PUMA codes do not exist or have not yet been defined a PUMA code of "99999" will appear. In Guam and the U.S. Virgin Islands the U.S. Census Bureau has defined a single PUMA file containing a 10-percent sample of the records. The 10-percent sample will appear in the PUMA5 field. Public Use Microdata Area Code Record Locations Record Type Field Name Description S PUMA5 Public Use Microdata Area File, 5% File, 2000 S PUMA1 Public Use Microdata Area File, 1% File, 2000 School Districts School districts are service areas within which local officials provide public educational services for the area's residents. The U.S. Census Bureau obtains the boundaries and names for school districts from state and local school officials for the primary purpose of providing the U.S. Department of Education with estimates of the number of children in poverty within each school district, county, and state. This information serves as the basis for the Department of Education to determine the annual allocation of Title 1 funding to states and school districts. The 2004 First Edition TIGER/Line files contain school district information from the 1999-2000 school year in Record Type S and the 2003-2004 school year in Record Type A. The 2003-2004 school districts represent districts in operation as of January 1, 2004. The 2004 First Edition TIGER/Line files identify three levels of school districts: unified, secondary, and elementary. The unified school districts are districts that provide education to children of all school ages in their service areas. The elementary school districts provide education to the lower grade/age levels and the secondary school districts provide service to the upper grade/age levels. In general, where there is a unified school district the elementary and secondary school district fields are blank (see exceptions described below), and where there is an elementary school district the secondary school district field may or may not be blank (see explanation below). In additional to regular school districts the TIGER/Line files contain false school districts (see the explanation/description below). The U.S. Census Bureau's representation of school districts is based both on the grade range that a school district operates and also the grade range for which the school district is financially responsible (the grade range that reflects financial responsibility is very important for the allocation of Title 1 funds). For example, a school district is defined as an elementary school district if it's operational grade range is less than the full K-12 or PK-12 grade range. These elementary school districts do not provide direct educational services for grades 9-12 or 7-12 or similar ranges. However, some of these elementary school districts are financially responsible for the education of all school-aged children within their service areas, and for Title 1 allocation purposes all school-aged children in their service areas are allocated to these types of elementary school districts. These financially responsible elementary school districts rely on other school districts to provide service for those grade ranges that are not operated by these elementary school districts, and these elementary school district pay tuition to those school districts that are providing these educational services to their students. In these situations, in order to allocate all school-aged children to these school districts the secondary school district field is blank. For all other elementary school districts where their operational grade range and financial responsible grade range are the same the secondary school district field will contain a secondary school district code. Note: There are no situations where there the elementary school district field is blank and the secondary school district field contains a code. The following are exceptions to the above information: Officially, the State of Hawaii is one unified school district and the five counties that represent the five boroughs of New York City are one school district, but for the 1999-2000 school year the U.S. Census Bureau included elementary and secondary school districts in Hawaii and elementary in the five boroughs in order to provide additional statistics for administrative areas within these school districts. Massachusetts, Nebraska, South Carolina, and Tennessee contain pseudo secondary school districts that represent regular unified school districts where the unified school districts share service with elementary school districts. These pseudo secondary school districts were created in order for the U.S. Census Bureau to allocate the high school aged children to the unified school districts (the U.S. Census Bureau could not assign the official unified school district codes, but had to create pseudo school district codes to represent a service area where less than the entire K-12 service area of the unified school districts). In these locations there were no regular secondary school districts serving the area and the elementary school districts in these areas were not paying tuition to the unified school districts (the elementary school districts' financial responsibilities did not extend to grade 12). There are two similar pseudo school districts (one elementary and one secondary) in Klamath County, Oregon where two unified school districts share a joint service area. A list of these pseudo school districts and their codes appears below. The TIGER/Line files store the school district codes in a set of three, 5- character fields. All codes consist of numeric characters. The value, 99998, is a pseudo school district code which is used for some large bodies of water, and 99997, is a pseudo-school district code assigned to land where no official school district is defined by a state. School District Code Record Locations Record Type Field Name Description A SDELMCU Elementary School District Code, Current A SDSECCU Secondary School District Code, Current A SDUNICU Unified School District Code, Current C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C SD School District Code C NAME Name of Geographic Area S SDELM Elementary School District Code, 2000 S SDSEC Secondary School District Code, 2000 S SDUNI Unified School District Code, 2000 List of Pseudo School Districts State SD Code Name 25 22222 MOHAWK TRAIL REG. S.D. IN HAWLEY TOWN AND CHARLEMONT TOWN 31 85050 SILVER LAKE AFFILIATION 31 83650 NEBRASKA UNIFIED DISTRICT 1 AFFILIATION 31 83700 NELIGH-OAKDALE AFFILIATION 31 84400 PLAINVIEW AFFILIATION 31 80200 ANSELMO-MERNA AFFILIATION 31 80650 BOONE CENTRAL AFFILIATION 31 80950 CEDAR RAPIDS AFFILIATION 31 81600 ELKHORN VALLEY AFFILIATION 31 82000 FULLERTON AFFILIATION 31 83750 NEWMAN GROVE AFFILIATION 31 80100 ALLIANCE AFFILIATION 31 80550 BAYARD AFFILIATION 31 82250 HEMINGFORD AFFILIATION 31 80050 AINSWORTH AFFILIATION 31 80150 AMHERST AFFILIATION 31 81650 ELM CREEK AFFILIATION 31 82100 GIBBON AFFILIATION 31 82700 KEARNEY AFFILIATION 31 84500 PLEASANTON AFFILIATION 31 84650 RAVENNA AFFILIATION 31 83100 LYONS-DECATUR NORTHEAST AFFILIATION 31 81400 DAVID CITY AFFILIATION 31 81500 EAST BUTLER AFFILIATION 31 84450 PLATTSMOUTH AFFILIATION 31 85800 WEEPING WATER AFFILIATION 31 82900 LEYTON AFFILIATION 31 85000 SIDNEY AFFILIATION 31 81150 CLARKSON AFFILIATION 31 82500 HOWELLS AFFILIATION 31 82750 LAKEVIEW AFFILIATION 31 82800 LEIGH AFFILIATION 31 80450 BANCROFT-ROSALIE AFFILIATION 31 80600 BEEMER AFFILIATION 31 84300 PENDER AFFILIATION 31 85900 WEST POINT AFFILIATION 31 86000 WISNER-PILGER AFFILIATION 31 80200 ANSELMO-MERNA AFFILIATION 31 80250 ANSLEY AFFILIATION 31 80750 BROKEN BOW AFFILIATION 31 80850 CALLAWAY AFFILIATION 31 81250 COZAD CITY AFFILIATION 31 82150 GOTHENBURG AFFILIATION 31 83000 LITCHFIELD AFFILIATION 31 84100 ORD AFFILIATION 31 84800 SARGENT AFFILIATION 31 85300 SUMNER-EDDYVILLE-MILLER AFFILIATION 31 82450 HOMER AFFILIATION 31 84550 PONCA AFFILIATION 31 85100 SO SIOUX CITY AFFILIATION 31 81050 CHADRON AFFILIATION 31 81300 CRAWFORD AFFILIATION 31 82200 HAY SPRINGS AFFILIATION 31 82250 HEMINGFORD AFFILIATION 31 80850 CALLAWAY AFFILIATION 31 81250 COZAD CITY AFFILIATION 31 81700 ELWOOD AFFILIATION 31 81750 EUSTIS-FARNAM AFFILIATION 31 82150 GOTHENBURG AFFILIATION 31 82850 LEXINGTON AFFILIATION 31 84150 OVERTON AFFILIATION 31 81950 FREMONT AFFILIATION 31 80800 BRUNING-DAVENPORT AFFILIATION 31 81900 FILLMORE CENTRAL AFFILIATION 31 84950 SHICKLEY AFFILIATION 31 83350 MC COOK AFFILIATION 31 81700 ELWOOD AFFILIATION 31 82850 LEXINGTON AFFILIATION 31 82400 HOLDREGE AFFILIATION 31 83050 LOOMIS AFFILIATION 31 82350 HITCHCOCK CO AFFILIATION 31 83350 MC COOK AFFILIATION 31 81100 CHAMBERS AFFILIATION 31 81800 EWING AFFILIATION 31 83650 NEBRASKA UNIFIED DISTRICT 1 AFFILIATION 31 84000 O'NEILL AFFILIATION 31 85650 UNIFIED NIOBRARA-LYNCH AFFILIATION 31 85850 WEST BOYD AFFILIATION 31 81000 CENTURA AFFILIATION 31 81550 ELBA AFFILIATION 31 85150 ST PAUL AFFILIATION 31 85550 TRI COUNTY AFFILIATION 31 82550 HUMBOLDT TABLE ROCK STEINAUER AFFILIATION 31 82650 JOHNSON-BROCK AFFILIATION 31 85450 TECUMSEH AFFILIATION 31 85050 SILVER LAKE AFFILIATION 31 84050 OGALLALA AFFILIATION 31 84250 PAXTON AFFILIATION 31 81350 CRETE AFFILIATION 31 82950 LINCOLN AFFILIATION 31 83200 MALCOLM AFFILIATION 31 83500 MILFORD AFFILIATION 31 83850 NORRIS SD 160 AFFILIATION 31 84200 PALMYRA DISTRICT O R 1 AFFILIATION 31 85750 WAVERLY SD 145 AFFILIATION 31 85950 WILBER-CLATONIA AFFILIATION 31 82150 GOTHENBURG AFFILIATION 31 82300 HERSHEY AFFILIATION 31 83250 MAXWELL AFFILIATION 31 83300 MAYWOOD AFFILIATION 31 83950 NORTH PLATTE AFFILIATION 31 85250 STAPLETON AFFILIATION 31 85350 SUTHERLAND AFFILIATION 31 80500 BATTLE CREEK AFFILIATION 31 81600 ELKHORN VALLEY AFFILIATION 31 82600 HUMPHREY AFFILIATION 31 83150 MADISON AFFILIATION 31 83750 NEWMAN GROVE AFFILIATION 31 83800 NORFOLK AFFILIATION 31 84350 PIERCE AFFILIATION 31 80100 ALLIANCE AFFILIATION 31 80550 BAYARD AFFILIATION 31 80700 BRIDGEPORT AFFILIATION 31 82900 LEYTON AFFILIATION 31 84850 SCOTTSBLUFF AFFILIATION 31 80950 CEDAR RAPIDS AFFILIATION 31 82000 FULLERTON AFFILIATION 31 85600 TWIN RIVER AFFILIATION 31 80350 AUBURN AFFILIATION 31 82550 HUMBOLDT TABLE ROCK STEINAUER AFFILIATION 31 82650 JOHNSON-BROCK AFFILIATION 31 85450 TECUMSEH AFFILIATION 31 81200 CONESTOGA AFFILIATION 31 83600 NEBRASKA CITY AFFILIATION 31 85400 SYRACUSE-DUNBAR-AVOCA AFFILIATION 31 82550 HUMBOLDT TABLE ROCK STEINAUER AFFILIATION 31 82650 JOHNSON-BROCK AFFILIATION 31 85450 TECUMSEH AFFILIATION 31 80400 AXTELL AFFILIATION 31 81650 ELM CREEK AFFILIATION 31 82400 HOLDREGE AFFILIATION 31 82700 KEARNEY AFFILIATION 31 83050 LOOMIS AFFILIATION 31 84150 OVERTON AFFILIATION 31 83800 NORFOLK AFFILIATION 31 84350 PIERCE AFFILIATION 31 82600 HUMPHREY AFFILIATION 31 82750 LAKEVIEW AFFILIATION 31 82800 LEIGH AFFILIATION 31 82350 HITCHCOCK CO AFFILIATION 31 83350 MC COOK AFFILIATION 31 84750 REP/TWIN VALLEY AFFILIATION 31 81850 FALLS CITY AFFILIATION 31 81350 CRETE AFFILIATION 31 81450 DORCHESTER AFFILIATION 31 83450 MERIDIAN AFFILIATION 31 85550 TRI COUNTY AFFILIATION 31 80300 ASHLAND-GREENWOOD AFFILIATION 31 80900 CEDAR BLUFFS AFFILIATION 31 81400 DAVID CITY AFFILIATION 31 81500 EAST BUTLER AFFILIATION 31 81950 FREMONT AFFILIATION 31 83400 MEAD AFFILIATION 31 84600 PRAGUE AFFILIATION 31 84700 RAYMOND CENTRAL AFFILIATION 31 85700 WAHOO AFFILIATION 31 82050 GERING AFFILIATION 31 83550 MORRILL AFFILIATION 31 84850 SCOTTSBLUFF AFFILIATION 31 81350 CRETE AFFILIATION 31 81500 EAST BUTLER AFFILIATION 31 84900 SEWARD AFFILIATION 31 80100 ALLIANCE AFFILIATION 31 81050 CHADRON AFFILIATION 31 82200 HAY SPRINGS AFFILIATION 31 83000 LITCHFIELD AFFILIATION 31 84500 PLEASANTON AFFILIATION 31 84650 RAVENNA AFFILIATION 31 82800 LEIGH AFFILIATION 31 83150 MADISON AFFILIATION 31 83800 NORFOLK AFFILIATION 31 85200 STANTON AFFILIATION 31 80800 BRUNING-DAVENPORT AFFILIATION 31 85500 THAYER CENTRAL AFFILIATION 31 83900 NORTH LOUP SCOTIA AFFILIATION 31 84100 ORD AFFILIATION 41 41034 KLAMATH FALLS CITY OVERLAP AREA 41 41035 KLAMATH COUNTY OVERLAP AREA 45 45013 BEAUFORT COUNTY SD W/I BEAUFORT MARINE CORPS AIR STATION 45 45079 RICHLAND COUNTY SCHOOL DISTRICT 02 WITHIN FORT JACKSON 47 47001 ANDERSON COUNTY SCHOOL DISTRICT IN CLINTON 47 47029 COCKE COUNTY SCHOOL DISTRICT IN NEWPORT 47 47031 COFFEE COUNTY SCHOOL DISTRICT IN MANCHESTER 47 47033 CROCKETT COUNTY SCHOOL DISTRICT IN ALAMO 47 47034 CROCKETT COUNTY SCHOOL DISTRICT IN BELLS 47 47073 HAWKINS COUNTY SCHOOL DISTRICT IN ROGERSVILLE 47 47077 HENDERSON COUNTY SCHOOL DISTRICT IN LEXINGTON 47 47079 HENRY COUNTY SCHOOL DISTRICT IN PARIS 47 47103 LINCOLN COUNTY SCHOOL DISTRICT IN FAYETTEVILLE 47 47107 MCMINN COUNTY SCHOOL DISTRICT IN ATHENS 47 47108 MCMINN COUNTY SCHOOL DISTRICT IN ETOWAH 47 47123 MONROE COUNTY SCHOOL DISTRICT IN SWEETWATER 47 47143 RHEA COUNTY SCHOOL DISTRICT IN DAYTON 47 47149 RUTHERFORD COUNTY SCHOOL DISTRICT IN MURFREESBORO 47 47187 WILLIAMSON COUNTY SCHOOL DISTRICT IN FRANKLIN 47 47189 WILSON COUNTY SCHOOL DISTRICT IN LEBANON States and Statistically Equivalent Entities States are the primary governmental divisions of the United States. In addition to the 50 States, the U.S. Census Bureau treats the District of Columbia, Puerto Rico, the U.S. Virgin Islands, and the Pacific Island Areas (American Samoa, Guam, and the Northern Mariana Islands) as the statistical equivalent of a state for the purpose of data presentation. TIGER/Line files are produced for the 50 States, the District of Columbia, the U.S. Virgin Islands, Puerto Rico, and the Pacific Island Areas. See Appendix A for a list of the FIPS state codes. Current Geography In some Record Type A records, the current state and county, when combined with the Census 2000 census tract and block numbers, create nonexistent geographic areas. To avoid nonexistent geographic areas, it is important not to mix Census 2000 geographic codes with the current geographic codes. The Census 2000 state, county, census tract, and census block codes all are found on Record Type S. State Code Record Locations Record Type Field Name Description 1 STATEL FIPS State Code, 2000 Left 1 STATER FIPS State Code, 2000 Right A STATECU FIPS State Code, Current B STATECQ FIPS State Code, 2000 CQR C STATE FIPS State Code C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C NAME Name of Geographic Area E STATEEC FIPS State Code, Economic Census S STATE FIPS State Code, 2000 All polygons have a non-blank state code. To improve the ability of data users to merge multiple counties, the U.S. Census Bureau has added the state and county codes to those Record Type 1 records of the adjacent county (these are the Record Type 1 records that have a 1 in the single-side segment field). The 2002 TIGER/Line files are the first version of the TIGER/Line files to include the state code for the side of the record "outside" the county. The left- and right-side complete chain state codes are not blank except where they are located along the outside edge of the boundary of the United States. State Legislative Districts (SLDs) State legislative districts (SLDs) are the areas from which members are elected to state legislatures. States participating in the Census 2000 Redistricting Data Program as part of Public Law 94-171 (1975) provided the U.S. Census Bureau with boundaries and codes for their SLDs. The U.S. Census Bureau reported data for SLDs for the first time for Census 2000. The SLDs embody the upper (senate) and lower (house) chambers of the state legislature. (Nebraska has a unicameral legislature that the U.S. Census Bureau treats as an upper-chamber legislative area for purposes of data presentation. New Hampshire only submitted SLDs for the upper chamber. Therefore, there are no data by lower chamber for these two states.) A unique 1- to 3-character census code, identified by state participants, is assigned to SLD within state. It is possible to have SLDs that cover only part of a state. In such instances, any areas for which SLDs are not defined are coded "ZZZ" and treated as a single SLD for purposes of data presentation. The following states did not participate in Phase 2 (the Voting District Project) of the Census 2000 Redistricting Data Program and no SLDs appear for these states: California Florida Kentucky Montana Of the participating states (or statistically equivalent entities), the following did not submit SLD boundaries or codes as part of Phase 2 (the Voting District Project) of the Census 2000 Redistricting Data Program, but submitted Voting Districts (VTDs) only: Arkansas Maine Texas District of Columbia Maryland Puerto Rico Hawaii Minnesota SLD Code Record Locations Record Type Field Name Description S SLDU State Legislative District Code (Upper Chamber), 2000 S SLDL State Legislative District Code (Lower Chamber), 2000 Subbarrios (Sub-Minor Civil Divisions or Sub-MCDs) Subbarrios are legally defined subdivisions of the minor civil division barrios- pueblo and barrios in Puerto Rico. The TIGER/Line files contain the 5-character FIPS 55 code field for Subbarrios. Subbarrio Code Record Locations Record Type Field Name Description 1 SUBMCDL FIPS 55 Code (Subbarrio), 2000 Left 1 SUBMCDR FIPS 55 Code (Subbarrio), 2000 Right A SUBMCDCU FIPS 55 Code (Subbarrio), Current B SUBMCDCQ FIPS 55 Code (Subbarrio), 2000 CQR C FIPS FIPS 55 Code C LSADC Legal/Statistical Area Description C FIPSCC FIPS 55 Class Code C ENTITY Entity Type Code C NAME Name of Geographic Area S SUBMCD FIPS 55 Code (Subbarrio), 2000 Traffic Analysis Zones (TAZs) Traffic analysis zones (TAZs) are special-purpose geographic entities delineated by state and local transportation officials for tabulating traffic related data from the decennial census, especially journey-to-work and place-of-work statistics. A TAZ usually consists of one or more census blocks, block groups, or census tracts. For Census 2000 TAZs were defined within county. Each TAZ is identified by a 6-character alphanumeric census code that is unique within county or statistically equivalent entity. A code of ZZZZZZ indicates a portion of a county where no TAZs were defined. The Census 2000 TAZ program was conducted on behalf of the Federal Highway Administration, Department of Transportation, which offered participation to the Metropolitan Planning Organizations (MPOs) and the Departments of Transportation (DOTs) in the 50 states and the District of Columbia. In addition to the TAZ field, the 2004 First Edition TIGER/Line files contain a TAZCOMB field that, in future versions of the TIGER/Line files, will contain State Combined Zones. Defined by State DOTs, the State Combined Zones will be aggregations of the MPO defined TAZs, or where MPOs did not define TAZs, aggregations of census tracts. The TAZCOMB field is blank in the 2004 First Edition TIGER/Line files. The following states did not have a participating MPO or State DOT for the Census 2000 TAZ Program: Delaware Hawaii Montana The following states did not submit TAZ boundaries or codes for all counties: Alabama Louisiana Oklahoma Alaska Maryland Oregon Arizona Massachusetts Pennsylvania Arkansas Minnesota Tennessee California Mississippi Texas Colorado Missouri Utah Florida Nevada Vermont Georgia New Jersey Virginia Idaho New Mexico Washington Illinois New York Wisconsin Indiana North Carolina Wyoming Iowa North Dakota Kansas Ohio TAZ Code Record Locations Record Type Field Name Description S TAZ Traffic Analysis Zone Code, 2000 S TAZCOMB Traffic Analysis Zone Code-State Combined, 2000 Urban and Rural For Census 2000 the U.S. Census Bureau classifies as urban all territory, population, and housing units located within urbanized areas (UAs) and urban clusters (UCs). It delineates UA and UC boundaries to encompass densely settled territory, which generally consists of: A cluster of one or more block groups or census blocks each of which has a population density of at least 1,000 people per square mile at the time, and Surrounding block groups and census blocks each of which has a population density of at least 500 people per square mile at the time, and Less densely settled blocks that form enclaves or indentations, or are used to connect discontiguous areas with qualifying densities. Rural consists of all territory, population, and housing units located outside of UAs and UCs. For Census 2000 this urban and rural classification applies to the 50 states, the District of Columbia, Puerto Rico, American Samoa, Guam, the Northern Mariana Islands, and the Virgin Islands of the United States. Urbanized Areas (UAs) An urbanized area consists of densely settled territory that contains 50,000 or more people. The U.S. Census Bureau delineates UAs to provide a better separation of urban and rural territory, population, and housing in the vicinity of large places. For Census 2000, the UA criteria were extensively revised and the delineations were performed using a zero-based approach. Because of more stringent density requirements, some territory that was classified as urbanized for the 1990 census has been reclassified as rural. (Area that was part of a 1990 UA has not been automatically grandfathered into the 2000 UA.) In addition, some areas that were identified as UAs for the 1990 census have been reclassified as urban clusters. Urban Clusters (UCs) An urban cluster consists of densely settled territory that has at least 2,500 people but fewer than 50,000 people. The U.S. Census Bureau introduced the UC for Census 2000 to provide a more consistent and accurate measure of the population concentration in and around places. UCs are defined using the same criteria that are used to define UAs. UCs replace the provision in the 1990 and previous censuses that defined as urban only those places with 2,500 or more people located outside of urbanized areas. All urban areas defined within Guam based on the results of Census 2000 are designated as urban clusters regardless of their total population. Urban Area Title and Code The title of each UA and UC may contain up to three incorporated place names, and will include the two-letter U.S. Postal Service abbreviation for each state into which the UA or UC extends. However, if the UA or UC does not contain an incorporated place, the urban area title will include the single name of a census designated place (CDP), minor civil division, or populated place recognized by the U.S. Geological Survey's Geographic Names Information System. Each UC and UA is assigned a 5-digit numeric code, based on a national alphabetical sequence of all urban area names. A separate flag is included in data tabulation files to differentiate between UAs and UCs. In printed reports, this differentiation is included in the name. Urban Area Central Places A central place functions as the dominant center of an urban area. The U.S. Census Bureau identifies one or more central places for each UA or UC that contains a place. Any incorporated place or census designated place (CDP) that is in the title of the urban area is a central place of that UA or UC. In addition, any other incorporated place or CDP that has an urban population of 50,000 or an urban population of at least 2,500 people and is at least 2/3 the size of the largest place within the urban area also is a central place. Extended Places As a result of the UA and UC delineations, an incorporated place or census designated place (CDP) may be partially within and partially outside of a UA or UC. Any place that is split by a UA or UC is referred to as an extended place. Urban/Rural (U/R) Designation The TIGER/Line files include a 1-character Urban/Rural Indicator: R-Rural, not urban U-Urban, in a UA or UC The U.S. Census Bureau assigns the U/R indicator to Census 2000 tabulation blocks, so all GT-polygons within a Census 2000 block have the same U/R indicator. All Census 2000 blocks with a Census 2000 UA or UC code (other than blank) will have a U/R indicator equal to U. Rural areas are identified by the R indicator and do not have a UA or UC code. Relationship to Other Geographic Entities Geographic entities, such as metropolitan areas, counties, minor civil divisions (MCDs), places, and census tracts often contain both urban and rural territory, population, and housing units. Current Urban Areas On August 23, 2002, the U.S. Census Bureau announced corrections to the Census 2000 Urbanized Areas and Urban Clusters. The U.S. Census Bureau recently integrated those corrections into its current TIGER database. The current urban areas, including the corrections, appear in Record Type A. The Census 2000 representation of urban areas, minus all corrections, is still available in Record Type S. Corrected Urban Areas The corrected urban area information appears in Record Types B and C for those data users interested in identifying where the U.S. Census Bureau made corrections. Record Type B includes only those polygons with corrected geography; it does not include all the polygons within the corrected urban areas. Data users interested in the boundaries of the corrected urban areas should use the current urban area information on Record Type A. For some corrected urban areas, only the designation as a urbanized area or urban cluster changed and no corrected geography appears in Record Type B. In these areas Record Type C contains the corrected attribute data. Urban/Rural Code Record Locations Record Type Field Name Description A UACU Urban Area, Current A URCU Urban/Rural Indicator, 2000 Current B UACC Urban Area, 2000 Corrected B URCC Urban/Rural Indicator, 2000 Corrected C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C UAUGA Urban Area Code/Urban Growth Area Code C NAME Name of Geographic Area S UA Urban Area, 2000 S UR Urban/Rural Indicator, 2000 Urban Growth Areas (UGAs) An urban growth area (UGA) is a legally defined entity in Oregon that the U.S. Census Bureau includes in the TIGER(R) database in agreement with the state. UGAs, which are defined around incorporated places, are used to regulate urban growth. UGA boundaries, which need not follow visible features, are delineated cooperatively by state and local officials and then confirmed in state law. UGAs, which are a pilot project, are a new geo-graphic entity for Census 2000. Each UGA is identified by a 5-digit numeric census code, usually associated with the incorporated place name. UGA Code Record Locations Record Type Field Name Description C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C UAUGA Urban Area Code/Urban Growth Area Code, 2000 C NAME Name of Geographic Area S UGA Oregon Urban Growth Area, 2000 Voting Districts (VTDs) Voting district (VTD) is the generic name for geographic entities such as precincts, wards, and election districts established by state governments for the purpose of conducting elections. States participating in the Census 2000 Redistricting Data Program as part of Public Law 94-171 (1975) provided the U.S. Census Bureau with boundaries, codes, and names for their VTDs. Each VTD is identified by a 1- to 6-character alphanumeric census code that is unique within county. The code "ZZZZZZ" identifies bodies of water for which no VTDs were identified. For a state or county that did not participate in Phase 2 (the Voting District Project) of the Census 2000 Redistricting Data Program, the codes fields are blank. Because the U.S. Census Bureau required that VTDs follow boundaries of tabulation census blocks, participating states often show the boundaries of the VTDs they submit as conforming to tabulation census block boundaries. If requested by the participating state, the U.S. Census Bureau identified the VTDs that represent an actual voting district with a Place Description Code of X. Where a participating state indicated that the VTD is a "pseudo" VTD, the Place Description Code is Z. Where a participating state did not indicate to the U.S. Census Bureau whether or not the VTD followed the actual boundaries of the VTD or is a pseudo-VTD the Place Description Code is blank. The following states did not participate in Phase 2 (the Voting District Project) of the Census 2000 Redistricting Data Program and no VTDs appear for these states: California Florida Kentucky Montana Of the participating states (or statistically equivalent entities), the following did not submit VTD boundaries or codes as part of Phase 2 (the Voting District Project) of the Census 2000 Redistricting Data Program, but submitted State Legislative Districts (SLDs) only: North Dakota Ohio Oregon Wisconsin The following state has partial coverage for Phase 2 (the Voting District Project) of the Census 2000 Redistricting Data Program: Arizona Did not submit VTDs in all counties VTD Code Record Locations Record Type Field Name Description C VTDTRACT Census Voting District Code/Census Tract Code C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C PLACEDC Place Description Code C NAME Name of Geographic Area S VTD Census Voting District Code, 2000 ZIP Code(R) Tabulation Areas (ZCTAs(TM)) ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of United States Postal Service (USPS) ZIP Code service areas that the U.S. Census Bureau created for statistical purposes for Census 2000. The Census Bureau did not create ZCTAs for American Samoa, Guam, the Northern Mariana Islands, or the U.S. Virgin Islands. In these Island Areas the ZCTA(TM) field is blank in the 2004 First Edition TIGER/Line files. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. Except in the Island Areas, each Census 2000 tabulation block will have a single ZCTA code that reflects the majority ZIP Code for addresses within that tabulation block. As a result, ZIP Codes associated with address ranges found in Record Types 1 and 6 may not exactly match the ZCTA. Because addresses and ZIP Codes will not exist within all Census 2000 census tabulation blocks, the U.S. Census Bureau used automated ex-tension algorithms to close coverage gaps and assigned either a 5- or 3-digit ZCTA code to each Census 2000 tabulation block. The ZCTA delineation process attempted to assign a 5-digit ZCTA code to areas with no ZIP Code or address data. Where reliable data were unavailable for extensive areas, the ZCTA code may represent the more general 3-digit ZIP Code. The U.S. Census Bureau is identifying ZCTAs by using a five-character alphanumeric code. The first three characters will represent the 3-digit ZIP Code and may contain leading zeros. For ZCTAs defined only by a 3-digit ZIP Code the last two characters of the ZCTA code is "XX." For example, ZCTA code "290XX" represents the generic 3-digit ZIP Code 290 where no 5-digit ZIP Code was available. For ZCTA codes that reflect the 5-digit ZIP Code, the last two characters of the ZCTA code will be numeric. For example, the ZCTA code "00601" represents the 5-digit ZIP Code 00601. The ZCTA delineation process did not recognize ZCTA codes ending in "00", such as "29000", as valid 5-digit ZCTA codes. Some water features have a 3-digit ZCTA code followed by "HH", for example "290HH". For Census 2000, these codes were applied only to water features and usually belong to water features located along the edges of 5-digit ZCTAs. After Census 2000, efforts to improve the spatial accuracy of the TIGER database have and continue to add land area such as small islands or sections of shoreline to census blocks that were entirely water in Census 2000. Census 2000 tabulation blocks that once consisted entirely of water features may now contain a mix of water and small land features. As a result, "HH" ZCTA codes may no longer represent purely water areas. A recent review made in early 2003 prior to the preparation of the 2003 TIGER/Line files indicates that no addresses fall within any "HH" ZCTA. The U.S. Postal Service (USPS) makes periodic changes to ZIP Codes to support more efficient mail delivery. As a result, the original Census 2000 ZCTAs may no longer match current ZIP Codes. The 2004 First Edition TIGER/Line files contain updated national ZCTAs reflecting USPS ZIP Code changes through October, 2002 in Record Type A. In addition, the U.S. Census Bureau adjusted ZCTA boundaries in 2002 to account for new growth, ZIP Code delivery changes, and more precise ZIP Code information. The U.S. Census Bureau also modified some of the generic "XX" and "HH" ZCTAs in 2002 to reflect expansion of 5-digit ZCTAs and to achieve more consistent "XX" and "HH" coverage within and across county boundaries. A ZCTA may not exist for every USPS ZIP Code. For instance, a special purpose ZIP Code may represent a point location that does not characterize the majority of the addresses for a Census 2000 tabulation block. Under these circumstances the special purpose ZIP Code will not appear as a ZCTA. For more information on ZCTAs go to URL: http://www.census.gov/geo/ZCTA/zcta.html. ZCTA Code Record Locations Record Type Field Name Description A ZCTA5CU 5-Digit ZIP Code(R) Tabulation Area, Current A ZCTA3CU 3-Digit ZIP Code(R) Tabulation Area, Current S ZCTA5 5-Digit ZIP Code(R) Tabulation Area, 2000 S ZCTA3 3-Digit ZIP Code(R) Tabulation Area, 2000 Economic Census Geography The Economic Census is the major economic statistical program of the United States. It provides a detailed portrait of the Nation's economy once every five years. The geographic entities used in an Economic Census can differ from those used in decennial censuses. The boundaries used for geographic entities for the 2002 Economic Census are those reported to the U.S. Census Bureau through the Boundary and Annexation Survey to be legally in effect on January 1, 2002. To build economic census geography data users must use the geographic entity codes on Record Type E and aggregate the polygons that comprise each economic census entity. Data users are cautioned not to mix the Economic Census geography with either current or Census 2000 geography. For example, users can not use the current blocks on Record Type A to build the economic census places because the current blocks use the January 1, 2004 governmental unit boundaries not the January 1, 2002 governmental unit boundaries used in the economic census. Governmental unit boundaries change, and a polygon that was not part of a place in 2002 may now be part of a place in 2004. Economic Census Commercial Regions For purposes of economic census data presentations, the municipios in Puerto Rico are grouped into nine Commercial Regions. The following are the codes and names for the Commercial Regions: Commercial Region Code Name 1 Aguadilla, PR Commercial Region 2 Arecibo, PR Commercial Region 3 Bayamon, PR Commercial Region 4 Caguas, PR Commercial Region 5 Fajardo, PR Commercial Region 6 Guayama, PR Commercial Region 7 Mayaguez, PR Commercial Region 8 Ponce, PR Commercial Region 9 San Juan, PR Commercial Region Economic Census County and Statistically Equivalent Entities The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the statistically equivalent entities are boroughs, city and boroughs, municipality, and census areas. In Maryland, Missouri, Nevada, and Virginia, there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as statistically equivalent entities in the 2002 Economic Census. The District of Columbia has no primary divisions, and the entire area is considered a statistically equivalent entity for purposes of data presentation. Kalawao County, Hawaii, which has no functioning local government, is included with Maui County for statistical purposes in economic census presentations. In Puerto Rico municipios are recognized as the statistical equivalent of counties for the purposes of economic census data presentation. The districts and islands in American Samoa are recognized as the statistical equivalent of counties for the 2002 Economic Census. In the Northern Mariana Islands, municipalities are recognized as the statistical equivalents of counties for the presentation of economic census data. Each island in the U.S. Virgin Islands is recognized for the 2002 Economic Census as the statistical equivalent of county. Guam is recognized as both the statistical equivalent of a county and of a state. The county and state are coextensive. For economic census data presentation purposes, the election districts (minor civil divisions) in Guam are recognized as county equivalents. The following are the legal values for the statistically equivalent entities for counties in Guam for the 2002 Economic Census: State Code County Code Guam County Equivalents 66 020 Agana Heights District 66 030 Agat District 66 040 Asan District 66 050 Barrigada District 66 060 Chalan Pago-Ordot District 66 070 Dededo District 66 075 Hagatna District 66 080 Inarajan District 66 090 Mangilao District 66 100 Merizo District 66 110 Mongmong-Toto-Maite District 66 120 Piti District 66 130 Santa Rita District 66 140 Sinajana District 66 150 Talofofo District 66 160 Tamuning District 66 170 Umatac District 66 180 Yigo District 66 190 Yona District Economic Census Places Qualification of economic census places is based on a population threshold. The 2002 Economic Census provides information for places with a Census 2000, Count Question Resolution, or 2002 U.S. Census Bureau population estimate of 2,500 population or greater. By special criteria, Guam, the Commonwealth of the Northern Mariana Islands, and Puerto Rico do not have any economic census places. Incorporated places that have a population of 2,500 or more are recognized for economic census data tabulations. New places reported to the U.S. Census Bureau and legally in effect on January 1, 2002, are recognized if they meet the minimum population requirement. CDPs are not recognized as places for the economic census except in Hawaii. For Hawaii, which does not have incorporated municipalities recognized for decennial census purposes, CDPs have been delineated for statistical purposes by the state government in cooperation with the U.S. Census Bureau. Those CDPs in Hawaii with a Census 2000 or Count Question Resolution population of 2,500 or more are recognized as place equivalents for the economic census. Six consolidated governments in the United states include separately incorporated municipalities. These consolidated cities result from a legal action between a city, its surrounding county, and any other governmental units within that county and are represented by a single entity. For more information about consolidated cities refer to the section on Places in this chapter. For the economic census, the U.S. Census Bureau recognizes the "balance of consolidated city" which excludes the incorporated place(s) that are recognized separately as places. (An entity containing a population of 2,500 or more is treated as a separate place and is omitted from the balance of the consolidated city.) The balance of a consolidated city may refer to a whole consolidated city if none of the included places had a population of 2,500 or more. Milford, Connecticut consolidated city is coextensive with Milford town. It includes Woodmont, which does not meet the minimum population criteria for data presentation as a separate place. Therefore, "Milford City" refers to the whole consolidated city in the 2002 Economic Census data presentations. Athens-Clarke County, Georgia consolidated city is coextensive with Clarke County. It includes Winterville and Bogart (part of which is in Clarke County), neither of which meet the minimum population criteria for data presentation as separate places. Therefore, "Athens-Clarke County" refers to the whole consolidated city in the 2002 Economic Census data presentations. Augusta-Richmond County, Georgia consolidated city is coextensive with Richmond County. It includes Hephzibah, which meets the minimum population threshold and will have data presented separately as a place. "Augusta-Richmond County (balance)" which is a place equivalent, includes Blythe (part in Richmond County), which does not meet the minimum population criteria for data presentation as a separate place. Indianapolis, Indiana consolidated city includes all of Marion County except Beech Grove, Lawrence, Southport, and Speedway, each of which meet the minimum population criteria for data presentation as separate places. The consolidated city includes Cumberland (part of which is in Marion County), which also will have data presented separately as a place. "Indianapolis City (balance)," which is a place equivalent, includes Clermont, Crows Nest, Homecroft, Meridian Hills, North Crows Nest, Rocky Ripple, Spring Hill, Warren Park, Williams Creek, and Wynnedale, none of which meet the minimum population criteria to have data presented as separate places in the 2002 Economic Census. Butte-Silver Bow, Montana consolidated city is coextensive with Silver Bow County. It includes Walkerville, which does not meet the minimum population criteria for data presentation as a separate place. Therefore, "Butte-Silver Bow" refers to the whole consolidated city. Nashville-Davidson, Tennessee consolidated city is coextensive with Davidson County. It includes Belle Meade, Forest Hills, Goddlettsville (part of which is in Davidson County), and Oak Hill, each of which will have data presented separately as a place. "Nashville-Davidson (balance)," which is place equivalent, includes Berry Hill, Lakewood, and Ridgetop (part of which is in Davidson County), none of which meet the minimum population criteria to have data presented as separate places. Maui County, Hawaii consists of four islands. At the request of the State of Hawaii, the U.S. Census Bureau recognizes the "Island of Lanai" and the "Island of Molokai (balance)" as places for data presentation purposes in the 2002 Economic Census. The "Island of Molokai (balance)" excludes Kaunakakai CDP, which meets the minimum population criteria for data presentation as a separate place. The economic census place representing the Balance of Maui County excludes these two islands, as well as other qualifying census designated places (CDPs) in the county and basically consists of the islands of Maui and Kaho'olawe. Data for Kalawao County, a nonfunctioning governmental unit, is included in the "Island of Molokai (balance)" place for the 2002 Economic Census. In American Samoa, the minor civil divisions (MCDs) identified as counties and islands are treated as economic census places. Balance of county or equivalent entity is included in the economic censuses as a statistically equivalent entity to a place. The balance of county includes those areas not recognized as places and place-equivalents under the above definitions. A FIPS place code of "99999" indicates "Balance of county." The Census Bureau recognizes minor civil divisions (MCDs) in selected states that have a population of 10,000 or more as economic census places. Qualifying MCDs are townships in Michigan (including charter townships), Minnesota, New Jersey, and Pennsylvania; and towns in Connecticut, Maine, Massachusetts, New Hampshire, New York, Rhode Island, Vermont, and Wisconsin. If a town or township qualifies as an economic census place and contains an incorporated place that is recognized separately for economic census data presentation, the U.S. Census Bureau recognizes the balance of the MCD as a place equivalent if the balance has a population of 10,000 or more. These can be identified by the addition of "(balance)" to the name or by FIPS class code. Economic Census State and Statistically Equivalent Entities States are the primary governmental divisions of the United States. In addition to the 50 States, the U.S. Census Bureau treats the District of Columbia, Puerto Rico, the U.S. Virgin Islands, Guam, American Samoa, and the Northern Mariana Islands as statistically equivalent entities for the purpose of data presentation in the 2002 Economic Census. Economic Census Geographic Entity Record Locations Record Type Field Name Description C FIPSCC FIPS 55 Class Code C PLACEDC Place Description Code C LSADC Legal/Statistical Area Description C ENTITY Entity Type Code C COMMREG Commercial Region, Economic Census C NAME Name of Geographic Area E STATEEC FIPS State Code, 2002 Economic Census E COUNTYEC FIPS County Code, 2002 Economic Census E PLACEEC FIPS Economic Census Place Code, 2002 Economic Census E COMMREGEC Commercial Region Code, 2002 Economic Census