2008 TIGER/Line Shapefiles Technical Documentation Chapter 3 Geography 3.1 Geography Overview The 2008 TIGER/Line Shapefiles represent geographic linear features such as roads, railroads, rivers, and non-visible legal boundaries, selected point features, such as schools and churches, and area features, such as tabulation geographic areas, parks, and cemeteries. The files also contain attribute information about these features, such as names, the type of feature, address ranges for most streets, the geographic relationship to other features, and other related information. The files include information for the fifty states, the District of Columbia, Puerto Rico, and the Island Areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the Virgin Islands of the United States). The 2008 TIGER/Line Shapefiles are available in multiple vintages to enable data users to match geography of the appropriate vintage with the data they are linking to the shapefiles. The following is an explanation of the vintages available in the 2008 TIGER/Line Shapefiles. Table 3.1.1 shows the vintages available for each shapefile or relationship file. Census 2000 geography is defined as the geographic extent of legally defined geographic areas (boundaries of governmental units) or statistical areas in effect on January 1, 2000. The Census Bureau has not systematically updated the inventory or boundaries of statistical areas since 2000; however, changes to legal areas may affect statistical areas. This vintage enables users to work with Census 2000 data using boundaries as they exisited in 2000. Current geography is defined as the latest version of the geographic extent of legally defined geographic areas as reported, generally reflecting the boundaries of governmental units in effect as of January 1, 2008, or legal and statistical area boundaries that have been adjusted and/or corrected since Census 2000. This vintage enables users to see the most current boundaries of governmental units so that they match the 2008 American Community Survey data or 2008 population estimates. 2007 Economic Census geography is defined as the version of the geographic extent of legally defined geographic areas legally in effect on January 1, 2007. The Economic Census is the major economic statistical program of the United States, and 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 2007 Economic Census are those reported to the Census Bureau through the Boundary and Annexation Survey to be legally in effect on January 1, 2007. Table 3.1.1 shows the vintages available for each layer. Table 3.1.1: 2008 TIGER/Line Shapefile Layers by Vintage Layer 2000 Current Economic Census 108th Congressional District (Congress elected in 2002) X 110th Congressional District (Congress elected in 2006) X 1-Percent Public Use Microdata Area X 5- or 10-Percent Public Use Microdata Area X 3-Digit ZIP Code Tabulation Area X 2002* 5-Digit ZIP Code Tabulation Area X 2002* Address Range-Feature Name Relationship File X Address Ranges Relationship File X Alaska Native Regional Corporation X X All Lines X American Indian Tribal Subdivision X X American Indian/Alaska Native/Native Hawaiian Area X X Area Hydrography X Area Landmark X Block X X Block Group X Census Tract X Combined New England City and Town Area X Combined Statistical Area X Commercial Region X Consolidated City X X X County and Equivalent X X X County Subdivision X X Elementary School District X X Feature Names Relationship File X Metropolitan Division X Metropolitan/Micropolitan Statistical Area X Military Installation X New England City and Town Area X New England City and Town Area Division X Other Identifiers Relationship File X Place X X X Point Landmark X Secondary School District X X State and Equivalent X X X State Legislative District—Lower Chamber X X State Legislative District—Upper Chamber X X Subbarrio X X Topological Faces (2-Cells With All Geocodes) Relationship File X Topological Faces-Area Hydrography Relationship File X Topological Faces-Area Landmark Relationship File X Traffic Analysis Zone X Unified School District X X Urban Areas X CORRECTED 2000** Urban Growth Area X X Voting District X * An updated version of the ZCTAs reflecting a 2002 vintage is the most current file available. ** This file contains corrections to the Census 2000 urbanized areas and urban clusters. These corrections were announced in 2002, and are the official urban areas for Census 2000. For more information, please see the “Urban Areas” section in Chapter 3. 3.2 Features Available in 2008 TIGER/Line Shapefiles The data within the TIGER/Line Shapefiles represent three major types of features: Polygon Features (faces)—geographic areas used to tabulate the Census 2000 and Economic Census, and current geographic areas and area hydrography Linear Features (edges)—roads, railroads, hydrography, miscellaneous transportation features, selected power lines and pipelines, and non-visible legal boundaries Landmark Features (points and faces)—point landmarks such as schools and churches and area landmarks such as parks and cemeteries 3.3 Boundaries Available in the 2008 TIGER/Line Shapefiles The 2008 TIGER/Line Shapefiles contain the boundaries of both legal and statistical entities. Some boundaries of the legal entities contained in the 2008 TIGER/Line Shapefiles are those reported to the Census Bureau to be legally in effect on January 1, 2000 (Census 2000 boundaries), while others are updated boundaries. It is important to note that the boundary information in the TIGER/Line Shapefiles for both legal and statistical entities are for 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 Census Bureau specifically, as to the positional or attribute accuracy of the data. The legal entities included in the files are: States and equivalent entities Counties and equivalent entities Minor civil divisions (MCDs, legal county subdivisions) Subbarrios (Puerto Rico only) Consolidated cities Incorporated places American Indian reservations (both federally and state-recognized) American Indian off-reservation trust lands American Indian tribal subdivisions Alaska Native Regional Corporations Hawaiian home lands Oregon urban growth areas Congressional districts Voting districts State legislative districts (upper and lower chambers) School districts The statistical entities included in the files are: Census areas (statistical county equivalents in Alaska) Census county divisions, census subareas, and unorganized territories (statistical county subdivisions) Census designated places (statistical place equivalents) American Indian/Alaska Native statistical areas 1) Alaska Native village statistical areas 2) Tribal designated statistical areas 3) Oklahoma tribal statistical areas 4) State designated tribal statistical areas Census tracts Census block groups Census blocks Core based statistical areas (CBSAs)—November 2007 1) Metropolitan and micropolitan statistical areas 2) Metropolitan divisions 3) Combined statistical areas 4) New England city and town areas 5) New England city and town area divisions 6) Combined New England city and town areas Traffic analysis zones ZIP Code Tabulation Areas (ZCTAs) Public use microdata areas Urban areas Commercial regions 3.3.1 Boundary and Area Changes The boundaries identified as current for some legal areas are updated boundaries collected since Census 2000 as part of the 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 equivalent entities, all counties and equivalent entities, all minor civil divisions (MCDs), all consolidated cities, and all incorporated places generally are those that were legally in effect as of the latest BAS. Current geography for these entities reflects legal changes to boundaries, such as annexations or deannexations of territory. Current boundaries for elementary, secondary, and unified school districts are collected through a survey of state school authorities under the auspices of the U.S. Department of Education. 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. Current geography may differ from Census 2000 geography due to feature updates that cause boundary shifts. For example, if a street feature that acts as a census tract boundary is moved, then the census tract boundary will move as well. Since the release of the Census 2000 versions of the TIGER/Line files, the Census Bureau has shifted and reshaped most linear features, including some that form legal or statistical area boundaries. The shape and area of the Census 2000 geographic entities portrayed in the 2008 TIGER/Line Shapefiles 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. 3.4 Codes for Entities The TIGER/Line Shapefiles identify geographic areas using the former Federal Information Processing Standard (FIPS) codes or Census Bureau-assigned codes. The National Institute of Science and Technology (NIST) formally withdrew FIPS coding standards for pertinent entities for which census data are presented, however, the Census Bureau intends to retain these codes for data presentation. In some cases, the former FIPS codes are being reissued, virtually unchanged, as standards under the aegis of the American National Standards Institute (ANSI). The Census Bureau, citing thirty years of common use, will continue to refer to these codes as FIPS. Although the NIST has withdrawn the FIPS publications, they are still applicable until the publication of the new ANSI standards. The withdrawn codes that remain in use and will be migrated to ANSI standards are: 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 8-6, Codes for the Identification of Metropolitan and Micropolitan Statistical Areas and Related Statistical Areas of the United States and Puerto Rico FIPS PUB 6-4, Counties and Equivalent Entities of the United States, Its Possessions, and Associated Areas FIPS PUB 9-1, Codes for the Identification of Congressional Districts and Equivalent Areas of the United States, Puerto Rico, and the Insular Areas FIPS PUB 55-3, Codes for Named Populated Places, Primary County Divisions, and Other Locational Entities of the United States, Puerto Rico, and the Outlying Areas, is being replaced by a new ANSI code standard using the United States Geological Survey (USGS) Geographic Names Information System (GNIS) identifier. The Census Bureau is retaining the FIPS 55 codes for all features for which the FIPS 55 codes are applicable. The FIPS 55 code still has significance for data processing and sorting and for historical comparisons. The Census Bureau now maintains the FIPS codes referenced above. The USGS, which formerly maintained the FIPS 55 codes, has information about FIPS 55 codes available from their GNIS home page at http://geonames.usgs.gov. The URL for the FIPS 55 codes is: http://geonames.usgs.gov/fips55.html. The URL for Census Bureau related FIPS codes is: http://www.census.gov/geo/www/fips/fips.html. The Census Bureau uses the codes in FIPS 55 to identify both legal and statistical entities for county subdivisions, sub-minor civil divisions, places, and American Indian areas, Alaska Native areas, and Native Hawaiian areas. FIPS 55 includes many more entity records than those for which the Census Bureau tabulates data. The FIPS 55 codes are state-based. American Indian reservations, off-reservation trust land areas, American Indian tribal subdivisions, 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. American National Standards Institute Codes—With the withdrawal of the Federal Information Processing Standards (FIPS) 55 codes, the United States Geological Survey (USGS) is proposing adoption of the Geographic Names Information System (GNIS) identifier as a new National Standard Feature Identifier code standard under the aegis of the American National Standards Institute (ANSI). These National Standard ANSI codes are found in many geographic area shapefiles. 3.5 Content Overview The following sections contain descriptive information about the content of each shapefile or relationship file, as well as the record layout for each file. Nation-based shapefiles are presented first, followed by American Indian Area-based shapefiles, state-based shapefiles, and county-based shapefiles and relationship files. 3.6 Nation-Based Shapefiles 3.6.1 American Indian, Alaska Native, and Native Hawaiian (AIANNH) Areas American Indian, Alaska Native, and Native Hawaiian area geography and attributes are available in the following nation-based shapefiles: Current American Indian/Alaska Native/Native Hawaiian Area (AIANNH) Shapefile Census 2000 American Indian/Alaska Native/Native Hawaiian Area (AIANNH) Shapefile These shapefiles contain both legal and statistical American Indian, Alaska Native, and Native Hawaiian entities for which the Census Bureau publishes data. The legal entities consist of federally recognized American Indian reservations and off- reservation trust land areas, state-recognized American Indian reservations, and Hawaiian home lands (HHLs). [Note: Tribal subdivisions and Alaska Native Regional Corporations (ANRCs) are additional types of legal entities, but are displayed in separate shapefiles and are discussed later in this chapter.] The statistical entities displayed in these shapefiles are Alaska Native village statistical areas (ANVSAs), Oklahoma tribal statistical areas (OTSAs), tribal designated statistical areas (TDSAs), and state designated tribal statistical areas (SDTSAs). In all cases, these areas are mutually exclusive in that no American Indian, Alaska Native, or Native Hawaiian area 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 Census Bureau creates a joint-use area as a separate entity to define this area of dual claims. The American Indian/Alaska Native/Native Hawaiian Area (AIANNH) shapefiles contain a unique polygon record for each combination of AIANNH reservation or statistical area and component type. For example, the Fort Peck Indian Reservation will have two records: one for the reservation portion and another for the off- reservation trust land area. Entities with only a single component will contain a single record. 3.6.1.1 AIA Legal Entities 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 Census Bureau recognizes federal reservations as territory over which American Indian tribes have primary governmental authority. These entities are known as colonies, communities, Indian colonies, Indian communities, Indian Rancherias, Indian Reservations, Indian villages, pueblos, rancherias, ranches, reservations, reserves, settlements, villages, and other descriptions. The Bureau of Indian Affairs maintains a list of federally recognized tribal governments. The 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 Census Bureau. State reservations may cross county, county subdivision, and place boundaries. The Census Bureau has not surveyed and updated the inventory or boundaries of state reservations since 2000. 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 American 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 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 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 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 Shapefiles. 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 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 Hawaii from which the lands were designated, or from the local name for an area. The Census Bureau has not surveyed and updated the inventory or boundaries of Hawaiian home lands since 2000. Joint-Use Areas, as applied to any American Indian or Alaska Native area by the Census Bureau, means an area that is administered jointly and/or claimed by two or more American Indian tribes. The Census Bureau designates both legal and statistical joint use areas as unique geographic entities for the purpose of presenting statistical data. The Census Bureau has not updated the inventory of statistical joint-use areas since 2000. Joint-use areas now only apply to overlapping federally recognized American Indian areas and overlapping Oklahoma tribal statistical areas. No other AIANNH types have joint-use areas. 3.6.1.2 AIA 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 Census Bureau does not delimit ANVs for the purpose of presenting statistical data. Instead, the 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 or Alaska Native area by the Census Bureau, means an area is administered jointly and/or claimed by two or more American Indian tribes. The 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 Census Bureau in consultation with federally recognized American Indian tribes that do not currently have, 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. Tribal subdivisions can exist within the statistical Oklahoma tribal statistical areas. State Designated Tribal Statistical Areas (SDTSAs) are statistical entities for state-recognized American Indian tribes that do not have a state-recognized land base (reservation). SDTSAs are identified and delineated for the Census Bureau by a state liaison identified by the governor's office in each state. SDTSAs 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. An SDTSA 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). Note that in 2000 these areas were termed State Designated American Indian Statistical Areas; the term was changed to bring consistency to tribal statistical area terms. Tribal Designated Statistical Areas (TDSAs) are statistical entities identified and delineated for the 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 for federally recognized American Indian Reservations, off-reservation trust lands, joint-use areas, and tribal subdivisions are updated boundaries collected since Census 2000 as part of the Census Bureau's BAS. For Hawaiian home lands, state AIRs, and all tribal 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, SDTSAs, 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 or inventory for some of these entities. AIANNH Area Codes—The American Indian, Alaska Native, and Native Hawaiian areas (AIANNH areas) are represented in the TIGER/Line Shapefiles by a 4-character numeric census code field, and a single alphabetic character American Indian/Alaska Native/Native Hawaiian area reservation/statistical area or off-reservation trust land indicator field, shown as COMPTYP (component type). The census codes are assigned in alphabetical order in assigned ranges by AIANNH area type nationwide, except that joint-use areas appear at the end of the code range. 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. There is one TIGER/Line Shapefile record created for each unique combination of AIANNH code and component type. The FIPS 55 class code and census code associated with each entity identifies the type of AIANNH area. The metadata associated with the AIANNH area shapefiles provides a translation of these codes. The type of AIANNH area also can be identified either by the census code, MAF/TIGER feature class code (MTFCC), or by the FIPS 55 class code. The range of census codes allocated to each AIANNH area and the valid FIPS 55 class code(s) associated with each are as follows: Type Census Code Range Valid FIPS 55 Class MTFCC Federal AIA 0001 to 4999 D1, D2, D3 G2100*, G2101, G2102 Hawaiian Home Land 5000 to 5499 F1 G2120 OTSA 5500 to 5999 D6 G2140 ANVSA 6000 to 7999 E1, E2, E6 G2130 TDSA 8000 to 8999 D6 G2160 State AIR 9000 to 9499 D4 G2100* SDTSA 9500 to 9998 D9 G2150 *Note: G2100 can represent both federally and state-recognized areas; the recognition level can be determined using the federal/state recognition flag field. Joint-use areas are identified uniquely by MTFCC G2170. An “A” in the functional status field identifies federal AIA joint-use areas, while an “S” in the field represents joint-use OTSAs. Type Component Type (COMPTYP) American Indian Trust Land T Reservation or Statistical Entity R 3.6.1.3 Current American Indian/Alaska Native/Native Hawaiian Area (AIANNH) Shapefile Record Layout The shapefile name is: tl_2008_us_aiannh.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description AIANNHCE 4 String Current American Indian/Alaska Native/Native Hawaiian area census code AIANNHNS 8 String Current American Indian/Alaska Native/Native Hawaiian area ANSI code AIANNHID 5 String Current American Indian/Alaska Native/Native Hawaiian area reservation/statistical area or trust land identifier; a concatenation of current American Indian/Alaska Native/Native Hawaiian area census code and reservation/statistical area or off-reservation trust land indicator NAME 100 String Current American Indian/Alaska Native/Native Hawaiian area name NAMELSAD 100 String Current name and the translated legal/statistical area description for American Indian/Alaska Native/Native Hawaiian area LSAD 2 String Current legal/statistical area description code for American Indian/Alaska Native/Native Hawaiian area COMPTYP 1 String Current American Indian/Alaska Native/Native Hawaiian area reservation/statistical area or off-reservation trust land indicator CLASSFP 2 String Current FIPS 55 class code AIANNHR 1 String Current American Indian/Alaska Native/Native Hawaiian area federal/state recognition flag MTFCC 5 String MAF/TIGER feature class code (see below) FUNCSTAT 1 String Current functional status The MTFCC values are: G2100 (legal American Indian area); G2101 (American Indian Area, reservation only); G2102 (American Indian Area, off-reservation trust land only); G2120 (Hawaiian home land); G2130 (Alaska Native village statistical area); G2140 (Oklahoma tribal statistical area); G2150 (state-designated tribal statistical area); G2160 (tribal designated statistical area); G2170 (joint-use area) 3.6.1.4 Census 2000 American Indian/Alaska Native/Native Hawaiian Area (AIANNH) Shapefile Record Layout The shapefile name is: tl_2008_us_aiannh00.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description AIANNHCE00 4 String Census 2000 American Indian/Alaska Native/Native Hawaiian area census code AIANNHID00 5 String Census 2000 American Indian/Alaska Native/Native Hawaiian area reservation/statistical area or trust land identifier; a concatenation of Census 2000 American Indian/Alaska Native/Native Hawaiian area census code and reservation/statistical area or off-reservation trust land indicator NAME00 100 String Census 2000 American Indian/Alaska Native/Native Hawaiian area name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for American Indian/Alaska Native/Native Hawaiian area LSAD00 2 String Census 2000 legal/statistical area description code for American Indian/Alaska Native/Native Hawaiian area CLASSFP00 2 String Census 2000 FIPS 55 class code COMPTYP00 1 String Census 2000 American Indian/Alaska Native/Native Hawaiian area reservation/statistical area or off-reservation trust land indicator AIANNHR00 1 String Census 2000 American Indian/Alaska Native/Native Hawaiian area federal/state recognition flag MTFCC00 5 String MAF/TIGER feature class code (see below) FUNCSTAT00 1 String Census 2000 functional status The MTFCC values are: G2100 (legal American Indian area); G2101 (American Indian Area, reservation only); G2102 (American Indian Area, off-reservation trust land only); G2120 (Hawaiian home land); G2130 (Alaska Native village statistical area); G2140 (Oklahoma tribal statistical area); G2150 (state-designated tribal statistical area); G2160 (tribal designated statistical area); G2170 (joint-use area) 3.6.2 American Indian Tribal Subdivisions American Indian tribal subdivision (AITS) geography and attributes are available in the following nation-based shapefiles: Current American Indian Tribal Subdivision (AITS) National Shapefile Census 2000 American Indian Tribal Subdivision (AITS) National Shapefile Alternately, American Indian tribal subdivisions are also available by American Indian Area. Please see the section “American Indian Tribal Subdivisions” under “American Indian Area-Based Shapefiles” later in this chapter for additional shapefile information. American Indian Tribal Subdivisions (AITSs) are legally defined administrative subdivisions of federally recognized American Indian reservations and/or off- reservation trust land, or Oklahoma tribal statistical areas (OTSAs). Tribal subdivisions are known as agencies, areas, chapters, communities, districts, parcels, precincts, regions, segments, townships, tracts, or villages. 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 Census Bureau obtains the boundary and name information for tribal subdivisions from tribal governments. Current Geography—The boundaries identified as current for tribal subdivisions within legal American Indian areas are updated boundaries collected since Census 2000 as part of the Census Bureau's Boundary and Annexation Survey. For tribal subdivisions in OTSAs, the boundaries shown are those in effect at the time of Census 2000 whether the data are identified as Census 2000 or current. Updates to the legal boundaries of American Indian reservations may affect the current boundaries for some of these entities. American Indian Tribal Subdivision Codes—AITSs are represented in the TIGER/Line Shapefiles by a 3-character numeric census code. The Census Bureau assigns the 3-character American Indian tribal subdivision code alphabetically in order and uniquely within each American Indian reservation and/or associated off- reservation trust land, and Oklahoma tribal statistical area (OTSA). 3.6.2.1 Current American Indian Tribal Subdivision (AITS) National Shapefile Record Layout The shapefile name is: tl_2008_us_aitsn.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description AIANNHCE 4 String Current American Indian/Alaska Native/Native Hawaiian area census code TRSUBCE 3 String Current tribal subdivision census code TRSUBNS 8 String Current American Indian tribal subdivision ANSI code TRSUBID 7 String Current tribal subdivision identifier; a concatenation of current American Indian/Alaska Native/Native Hawaiian area census code and tribal subdivision census code NAME 100 String Current American Indian tribal subdivision name NAMELSAD 100 String Current name and the translated legal/statistical area description for American Indian tribal subdivision LSAD 2 String Current legal/statistical area description code for American Indian tribal subdivision CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code (G2300) FUNCSTAT 1 String Current functional status 3.6.2.2 Census 2000 American Indian Tribal Subdivision (AITS) National Shapefile Record Layout The shapefile name is: tl_2008_us_aitsn00.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description AIANNHCE00 4 String Census 2000 American Indian/Alaska Native/Native Hawaiian area census code TRSUBCE00 3 String Census 2000 tribal subdivision census code TRSUBID00 7 String Census 2000 tribal subdivision identifier; a concatenation of Census 2000 American Indian/Alaska Native/Native Hawaiian area census code and tribal subdivision census code NAME00 100 String Census 2000 American Indian tribal subdivision name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for American Indian tribal subdivision LSAD00 2 String Census 2000 legal/statistical area description code for American Indian tribal subdivision CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code (G2300) FUNCSTAT00 1 String Census 2000 functional status 3.6.3 Counties and Equivalent Entities County and equivalent entity geography and attributes are available in the following nation-based shapefiles: Current County and Equivalent National Shapefile Census 2000 County and Equivalent National Shapefile Alternately, current and Census 2000 counties and equivalent entities are also available in state-based shapefiles. Economic Census counties and equivalent areas are available in state-based shapefiles only. Please see the section “Counties and Equivalent Entities” under “State-Based Shapefiles” later in this chapter for information about state-based county shapefiles. Counties and 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 equivalent entities are the organized boroughs, city and boroughs, and municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the 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 equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. Current Geography—Since Census 2000, there have been several changes to the universe of county or 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. In Alaska, Skagway Municipality was created from part of Skagway-Hoonah-Angoon Census Area. Skagway-Hoonah-Angoon Census Area was renamed Hoonah-Angoon Census Area. The 2008 TIGER/Line Shapefiles are based on the latest available governmental unit boundaries of the counties and equivalent entities. 3.6.3.1 Current County and Equivalent National Shapefile Record Layout The shapefile name is: tl_2008_us_county.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code COUNTYNS 8 String Current county ANSI code CNTYIDFP 5 String Current county identifier; a concatenation of current state FIPS code and county FIPS code NAME 100 String Current county name NAMELSAD 100 String Current name and the translated legal/statistical area description for county LSAD 2 String Current legal/statistical area description code for county CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code (G4020) CSAFP 3 String Current combined statistical area code CBSAFP 5 String Current metropolitan statistical area/micropolitan statistical area code METDIVFP 5 String Current metropolitan division code FUNCSTAT 1 String Current functional status 3.6.3.2 Census 2000 County and Equivalent National Shapefile Record Layout The shapefile name is: tl_2008_us_county00.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code CNTYIDFP00 5 String Census 2000 county identifier; a concatenation of Census 2000 state FIPS code and county FIPS code NAME00 100 String Census 2000 county name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for county LSAD00 2 String Census 2000 legal/statistical area description code for county CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code (G4020) UR00 1 String Census 2000 urban/rural indicator FUNCSTAT00 1 String Census 2000 functional status 3.6.4 Metropolitan and Micropolitan Statistical Areas Metropolitan and micropolitan statistical area geography and attributes are available in the following nation-based shapefiles: Current Combined New England City and Town Area (CNECTA) Shapefile Current Combined Statistical Area (CSA) Shapefile Current Metropolitan Division Shapefile Current Metropolitan Statistical Area/Micropolitan Statistical Area (CBSA) Shapefile Current New England City and Town Area (NECTA) Shapefile Current New England City and Town Area (NECTA) Division Shapefile 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 for the United States and Puerto Rico. No metropolitan or micropolitan areas are defined in the Island Areas. 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 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 equivalent entities form the building blocks for metropolitan and micropolitan statistical areas throughout the United States and Puerto Rico. In New England (Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island, and Vermont), the OMB has defined an alternative county subdivision- (generally city- and town-) based definition of CBSAs known as New England city and town areas (NECTAs). 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 an 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 2008 TIGER/Line Shapefiles are the updates to metropolitan and micropolitan statistical areas as of November 2007, announced by OMB on November 20, 2007. Combined New England City and Town Areas (CNECTAs) consist of two or more adjacent New England city and town areas (NECTAs) that have significant employment interchanges. The NECTAs that combine to create a CNECTA retain separate identities within the larger combined statistical areas. Because CNECTAs represent groupings of NECTAs they should not be ranked or compared with individual NECTAs. Combined Statistical Areas (CSAs) consist of two or more adjacent CBSAs that have significant employment interchanges. The CBSAs that combine to create a CSA retain separate identities within the larger CSAs. Because CSAs represent groupings of metropolitan and micropolitan statistical areas, they should not be ranked or compared with individual metropolitan and micropolitan statistical areas. Core Based Statistical Areas (CBSAs) consist of the county or counties or 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. 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 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 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 are CBSAs 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 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 are CBSAs 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 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) are an alternative set of geographic entities, similar in concept to the county-based CBSAs, that OMB defines in New England based on county subdivisions—usually cities and towns. NECTAs receive a category in a manner similar to CBSAs and are referred to as metropolitan NECTAs or 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. Principal Cities—The principal 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. Principal 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 principal 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. Note that there are some places designated as principal cities of NECTAs that are not principal cities of a CBSA. Core Based Statistical 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 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. 3.6.4.1 Current Combined New England City and Town Area (CNECTA) Shapefile Record Layout The shapefile name is: tl_2008_us_cnecta.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description CNECTAFP 3 String Current combined New England city and town area code NAME 100 String Current combined New England city and town area name NAMELSAD 100 String Current name and the translated legal/statistical area description for combined New England city and town area LSAD 2 String Current legal/statistical area description code for combined New England city and town area MTFCC 5 String MAF/TIGER feature class code (G3200) FUNCSTAT 1 String Current functional status 3.6.4.2 Current Combined Statistical Area (CSA) Shapefile Record Layout The shapefile name is: tl_2008_us_csa.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description CSAFP 3 String Current combined statistical area code NAME 100 String Current combined statistical area name NAMELSAD 100 String Current name and the translated legal/statistical area description for combined statistical area LSAD 2 String Current legal/statistical area description code for combined statistical area MTFCC 5 String MAF/TIGER feature class code (G3100) FUNCSTAT 1 String Current functional status 3.6.4.3 Current Metropolitan Division Shapefile Record Layout The shapefile name is: tl_2008_us_metdiv.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description CSAFP 3 String Current combined statistical area code CBSAFP 5 String Current metropolitan statistical area/micropolitan statistical area code METDIVFP 5 String Current metropolitan division code NAME 100 String Current metropolitan division name NAMELSAD 100 String Current name and the translated legal/statistical area description for metropolitan division LSAD 2 String Current legal/statistical area description code for metropolitan division MTFCC 5 String MAF/TIGER feature class code (G3120) FUNCSTAT 1 String Current functional status 3.6.4.4 Current Metropolitan Statistical Area/Micropolitan Statistical Area (CBSA) Shapefile Record Layout The shapefile name is: tl_2008_us_cbsa.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description CSAFP 3 String Current combined statistical area code, if applicable CBSAFP 5 String Current metropolitan statistical area/micropolitan statistical area code NAME 100 String Current metropolitan statistical area/micropolitan statistical area name NAMELSAD 100 String Current name and the translated legal/statistical area description for metropolitan statistical area/micropolitan statistical area LSAD 2 String Current legal/statistical area description code for metropolitan statistical area/micropolitan statistical area MEMI 1 String Current metropolitan/micropolitan status indicator MTFCC 5 String MAF/TIGER feature class code (G3110) FUNCSTAT 1 String Current functional status 3.6.4.5 Current New England City and Town Area (NECTA) Shapefile Record Layout The shapefile name is: tl_2008_us_necta.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description CNECTAFP 3 String Current combined New England city and town area code, if applicable NECTAFP 5 String Current New England city and town area code NAME 100 String Current New England city and town area name NAMELSAD 100 String Current name and the translated legal/statistical area description for New England city and town area LSAD 2 String Current legal/statistical area description code for New England city and town area NMEMI 1 String Current New England city and town area metropolitan/micropolitan status indicator MTFCC 5 String MAF/TIGER feature class code (G3210) FUNCSTAT 1 String Current functional status 3.6.4.6 Current New England City and Town Area (NECTA) Division Shapefile Record Layout The shapefile name is: tl_2008_us_nectadiv.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description CNECTAFP 3 String Current combined New England city and town area code, if applicable NECTAFP 5 String Current New England city and town area code NCTADVFP 5 String Current New England city and town area division code NAME 100 String Current New England city and town area division name NAMELSAD 100 String Current name and the translated legal/statistical area description for New England city and town area division LSAD 2 String Current legal/statistical area description code for New England city and town area division MTFCC 5 String MAF/TIGER feature class code (G3220) FUNCSTAT 1 String Current functional status 3.6.5 States and Equivalent Entities State and equivalent entity geography and attributes are available in the following nation-based shapefiles: Current State and Equivalent Shapefile Census 2000 State and Equivalent Shapefile Economic Census State and Equivalent Shapefile States and Equivalent Entities are the primary governmental divisions of the United States. In addition to the fifty states, the Census Bureau treats the District of Columbia, Puerto Rico, and the Island Areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the Virgin Islands of the United States) as the statistical equivalents of states for the purpose of data presentation. TIGER/Line Shapefiles are produced for the 50 states, the District of Columbia, the U.S. Virgin Islands, Puerto Rico, and each Pacific Island Area. Economic Census States and Equivalent Entities—In addition to the fifty states, the Census Bureau treats the District of Columbia, Puerto Rico, and the Island Areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the Virgin Islands of the United States) as the statistical equivalents of states for the purpose of data presentation in the 2007 Economic Census. 3.6.5.1 Current State and Equivalent Shapefile Record Layout The shapefile name is: tl_2008_us_state.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code STATENS 8 String Current state ANSI code STUSPS 2 String Current United States Postal Service state abbreviation NAME 100 String Current state name LSAD 2 String Current legal/statistical area description code for state MTFCC 5 String MAF/TIGER feature class code (G4000) FUNCSTAT 1 String Current functional status 3.6.5.2 Census 2000 State and Equivalent Shapefile Record Layout The shapefile name is: tl_2008_us_state00.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code STUSPS00 2 String Census 2000 United States Postal Service state abbreviation NAME00 100 String Census 2000 state name LSAD00 2 String Census 2000 legal/statistical area description code for state MTFCC00 5 String MAF/TIGER feature class code (G4000) UR00 1 String Census 2000 urban/rural indicator FUNCSTAT00 1 String Census 2000 functional status 3.6.5.3 Economic Census State Shapefile Record Layout The shapefile name is: tl_2008_us_stateec.shp The shapefile is nation-based The following is the shapefile’s attribute table layout: Field Length Type Description STATEFPEC 2 String 2007 Economic Census state FIPS code STUSPSEC 2 String 2007 Economic Census United States Postal Service state abbreviation NAMEEC 100 String 2007 Economic Census state name LSADEC 2 String 2007 Economic Census legal/statistical area description code for state MTFCCEC 5 String MAF/TIGER feature class code (G4000) FUNCSTATEC 1 String 2007 Economic Census functional status 3.6.6 Urban Areas Urban area geography and attributes are available in the following nation-based shapefiles: Corrected Census 2000 Urban Area Shapefile Census 2000 Urban Area Shapefile For Census 2000, the 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, the Commonwealth of the Northern Mariana Islands, Guam, 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 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. (An area that was part of a 1990 UA has not been automatically grandfathered into the 2000 UA.) 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 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. Note: 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 Titles and Codes—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—The 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 two-thirds 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. 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. Some shapefiles include an Urban/Rural Indicator field that indicates whether the areas contained within the shapefile are urban, rural, or mixed. Corrected Census 2000 Urban Areas—On August 23, 2002, the U.S. Census Bureau announced corrections to the Census 2000 urbanized areas and urban clusters. These corrections included changes in classification and inventory of urbanized areas and urban clusters, combining some areas that were erroneously designated separately, and corrections affecting boundaries. The U.S. Census Bureau has integrated those corrections into its current MAF/TIGER database. The current urban areas, including the corrections, appear in the Corrected Census 2000 Urban Areas shapefile. The corrected urban areas are the official areas for Census 2000. The Census 2000 representation of urban areas, minus all corrections, is available in the Census 2000 Urban Areas shapefile. 3.6.6.1 Corrected Census 2000 Urban Area Shapefile Record Layout The shapefile name is: tl_2008_us_uac.shp The shapefile is nation-based The following is the shapefile’s attribute table layout: Field Length Type Description UACE 5 String Corrected Census 2000 urban area code NAME 100 String Current urban area name NAMELSAD 100 String Current name and the translated legal/statistical area description for urban area LSAD 2 String Current legal/statistical area description code for urban area MTFCC 5 String MAF/TIGER feature class code FUNCSTAT 1 String Current functional status 3.6.6.2 Census 2000 Urban Area Shapefile Record Layout The shapefile name is: tl_2008_us_uac00.shp The shapefile is nation-based The following is the shapefile’s attribute table layout: Field Length Type Description UACE00 5 String Census 2000 urban area code NAME00 100 String Census 2000 urban area name NAMELSAD0 0 100 String Census 2000 name and the translated legal/statistical area description for urban area LSAD00 2 String Census 2000 legal/statistical area description code for urban area MTFCC00 5 String MAF/TIGER feature class code FUNCSTAT00 1 String Census 2000 functional status 3.6.7 ZIP Code Tabulation Areas (3-Digit and 5-Digit) ZIP Code Tabulation Area geography and attributes are available in the following nation-based shapefiles: 2002 3-Digit ZIP Code Tabulation Area (ZCTA3) Shapefile Census 2000 3-Digit ZIP Code Tabulation Area (ZCTA3) Shapefile 2002 5-Digit ZIP Code Tabulation Area (ZCTA3) Shapefile Census 2000 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of USPS ZIP Code service areas that the Census Bureau created for statistical purposes for Census 2000. The Census Bureau did not create ZCTAs for American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, or the U.S. Virgin Islands. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. 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. 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 the Address Ranges relationship file may not exactly match the ZCTA. Because addresses and ZIP Codes will not exist within all Census 2000 census tabulation blocks, the Census Bureau used automated extension 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 5-digit ZCTA code may represent the more general 3-digit ZIP Code. A ZCTA may not exist for every USPS ZIP Code. The delineation process excluded all ZIP Codes for specific firms and organizations that have their own 5-digit ZIP Code, as well as nearly all P.O. box delivery ZIP Codes in areas otherwise served by ZIP Codes with city-style mail delivery. For more information about ZCTAs, go to URL: http://www.census.gov/geo/ZCTA/zcta.html. ZIP Code Tabulation Area Codes—The Census Bureau identifies 3-digit ZCTAs using a three-character numeric code that represents the first three digits of the related 5-digit ZCTA. The Census Bureau identifies 5-digit ZCTAs using a five-character numeric code. The first three characters will represent the 3-digit ZIP Code and may contain leading zeros. 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 ZIP codes ending in "00", such as "29000", as valid 5-digit ZCTA codes. Previous versions of TIGER/Line Files and the 2007 TIGER/Line Shapefiles included 5-digit ZCTAs that could not be assigned to a specific ZIP Code. For land areas for which a specific 5-digit ZIP Code was unavailable, the Census Bureau used the 3- digit ZIP Code and defined the last two characters of the ZCTA code as "XX." For example, ZCTA code "290XX" represented the generic 3-digit ZIP Code 290 where no 5-digit ZIP Code was available. In water areas for which the Census Bureau did not allocate a specific 5-digit ZIP Code, the water features have a 3-digit ZCTA code followed by "HH", for example "290HH". The 2008 TIGER/Line shapefiles no longer contain the generic land and water 5-digit ZCTAs. 2002 ZIP Code Tabulation Areas—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 2008 TIGER/Line Shapefiles contain updated national ZCTAs reflecting USPS ZIP Code changes through October, 2002. 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. There will be no further updates of ZCTAs until the 2010 Census. 3.6.7.1 2002 3-Digit ZIP Code Tabulation Area (ZCTA3) Shapefile Record Layout The shapefile name is: tl_2008_us_zcta3.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description ZCTA3CE 3 String Current 3-digit ZIP Code Tabulation Area code CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code FUNCSTAT 1 String Current functional status 3.6.7.2 Census 2000 3-Digit ZIP Code Tabulation Area (ZCTA3) Shapefile Record Layout The shapefile name is: tl_2008_us_zcta300.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description ZCTA3CE00 3 String Census 2000 3-digit ZIP Code Tabulation Area code CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code (G6340) FUNCSTAT00 1 String Census 2000 functional status 3.6.7.3 2002 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile Record Layout The shapefile name is: tl_2008_us_zcta5.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description ZCTA5CE 5 String Current 5-digit ZIP Code Tabulation Area code CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code FUNCSTAT 1 String Current functional status 3.6.7.4 Census 2000 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile Record Layout The shapefile name is: tl_2008_us_zcta500.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description ZCTA5CE00 5 String Census 2000 5-digit ZIP Code Tabulation Area code CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code (G6350) FUNCSTAT00 1 String Census 2000 functional status 3.6.8 Military Installations Military installation geography and attributes are available in the following nation- based shapefile: Military Installation Shapefile The Census Bureau includes landmarks such as military installations in the MAF/TIGER database for locating special features and to help enumerators during field operations. The Census Bureau added landmark features to the database on an as-needed basis and made no attempt to ensure that all instances of a particular feature were included. For additional information about area landmarks, please see the “Landmarks” section under “County-Based Shapefiles” later in this chapter. 3.6.8.1 Military Installation Shapefile Record Layout The shapefile name is: tl_2008_us_mil.shp The shapefile is nation-based. The following is the shapefile’s attribute table layout: Field Length Type Description ANSICODE 8 String Current official code for the landmark for use by federal agencies for data transfer and dissemination AREAID 22 String Area landmark identifier FULLNAME 100 String Concatenation of expanded text for prefix qualifier, prefix direction, prefix type, base name, suffix type, suffix direction, and suffix qualifier (as available) with a space between each expanded text field MTFCC 5 String MAF/TIGER feature class code 3.7 American Indian Area-Based Shapefiles 3.7.1 American Indian Tribal Subdivisions American Indian tribal subdivision (AITS) geography and attributes are available by American Indian Area (AIA) in the following shapefiles: Current American Indian Tribal Subdivision (AITS) AIA-Based Shapefile Census 2000 American Indian Tribal Subdivision (AITS) AIA-Based Shapefile Alternately, American Indian tribal subdivisions are also available in nation-based shapefiles. Please see the section “American Indian Tribal Subdivisions” under “Nation-Based Shapefiles” earlier in this chapter for information about AITSs and additional shapefiles. 3.7.1.1 Current American Indian Tribal Subdivision (AITS) AIA-based Shapefile Record Layout The shapefile name is: tl_2008__aitsaia.shp The shapefile is AIA-based. The following is the shapefile’s attribute table layout: Field Length Type Description AIANNHCE 4 String Current American Indian/Alaska Native/Native Hawaiian area census code TRSUBCE 3 String Current tribal subdivision code TRSUBNS 8 String Current American Indian tribal subdivision ANSI code TRSUBID 7 String Current tribal subdivision identifier: a concatenation of current American Indian/Alaska Native/Native Hawaiian area census code and tribal subdivision census code NAME 100 String Current American Indian tribal subdivision name NAMELSAD 100 String Current name and the translated legal/statistical area description for American Indian tribal subdivision LSAD 2 String Current legal/statistical area description code for American Indian tribal subdivision CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code (G2300) FUNCSTAT 1 String Current functional status 3.7.1.2 Census 2000 American Indian Tribal Subdivision (AITS) AIA-based Shapefile Record Layout The shapefile name is: tl_2008__aitsaia00.shp The shapefile is AIA-based. The following is the shapefile’s attribute table layout: Field Length Type Description AIANNHCE00 4 String Census 2000 American Indian/Alaska Native/Native Hawaiian area census code TRSUBCE00 3 String Census 2000 tribal subdivision code TRSUBID00 7 String Census 2000 tribal subdivision identifier; a concatenation of Census 2000 American Indian/Alaska Native/Native Hawaiian area code and tribal subdivision code NAME00 100 String Census 2000 American Indian tribal subdivision name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for American Indian tribal subdivision LSAD00 2 String Census 2000 legal/statistical area description code for American Indian tribal subdivision CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code (G2300) FUNCSTAT00 1 String Census 2000 functional status 3.8 State-Based Shapefiles 3.8.1 Alaska Native Regional Corporations Alaska Native Regional Corporation geography and attributes are available in the following state-based shapefiles: Current Alaska Native Regional Corporation (ANRC) Shapefile Census 2000 Alaska Native Regional Corporation (ANRC) Shapefile Alaska Native Regional Corporations (ANRCs) are legally defined 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 exist as 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 twelve corporations. The Census Bureau does not provide data for this ANRC because it has no geographic extent and it does not appear in the TIGER/Line Shapefiles. ANRC boundaries have been legally established. The Census Bureau offers representatives of the twelve nonprofit ANRCs the opportunity to review and update the ANRC boundaries. ANRCs are represented by a 5-character numeric FIPS code. 3.8.1.1 Current Alaska Native Regional Corporation (ANRC) Shapefile Record Layout The shapefile name is: tl_2008_02_anrc.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code ANRCFP 5 String Current Alaska Native Regional Corporation FIPS code ANRCNS 8 String Current Alaska Native Regional Corporation ANSI code NAME 100 String Current Alaska Native Regional Corporation name NAMELSAD 100 String Current name and the translated legal/statistical area description for Alaska Native Regional Corporation LSAD 2 String Current legal/statistical area description code for Alaska Native Regional Corporation CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code (G2200) FUNCSTAT 1 String Current functional status 3.8.1.2 Census 2000 Alaska Native Regional Corporation (ANRC) Shapefile Record Layout The shapefile name is: tl_2008_02_anrc00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code ANRCFP00 5 String Census 2000 Alaska Native Regional Corporation FIPS code NAME00 100 String Census 2000 Alaska Native Regional Corporation name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for Alaska Native Regional Corporation LSAD00 2 String Census 2000 legal/statistical area description code for Alaska Native Regional Corporation CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code (G2200) FUNCSTAT00 1 String Census 2000 functional status 3.8.2 Blocks Block geography and attributes are available by state in the following shapefiles: Current Block State-based Shapefile Census 2000 Block State-based Shapefile Alternately, blocks are also available in county-based shapefiles. Please see the section “Blocks” under “County-based Shapefiles” later in this chapter for additional shapefile information. 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 line-of-sight 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. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas. A block may consist of one or more faces. Tabulation blocks used in Census 2000 data products never cross county or census tract boundaries. They do not cross the boundaries of any entity for which the Census Bureau tabulated 2000 data, including American Indian, Alaska Native, and Native Hawaiian areas, congressional districts, county subdivisions, places, state legislative districts, urbanized areas, urban clusters, school districts, voting districts, or ZIP Code Tabulation Areas (ZCTAs) or some special administrative areas such as military installations, and national parks and monuments. Census Block Numbers—Census 2000 tabulation blocks are numbered uniquely within the 2000 boundaries of each state/county/census tract with a 4-digit census block number. The Census Bureau created the tabulation block numbers immediately before beginning its Census 2000 data tabulation process. 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 Census Bureau assigns a current alphabetic suffix for a Census 2000 block number. The current suffixes for Census 2000 block numbers are not permanent and will change with each annual cycle of current block suffixing. Data users are cautioned that the current state and county codes, when combined with the Census 2000 census tract and block numbers, can create nonexistent geographic areas. To avoid nonexistent geographic areas, it is important not to mix Census 2000 geographic codes with current geographic codes. Water Blocks—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 Census Bureau assigned water block numbers beginning with the block group number followed by "999" and proceeding 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. Census Block Codes Census 2000 Tabulation Blocks Block group number 0 to 9—First numeric character 000 to 999—Second, third, and fourth numeric characters Current Suffix for Census 2000 Block Number A to Z—Codes for current suffix for Census 2000 block numbers 3.8.2.1 Current Block State-based Shapefile Record Layout The shapefile name is: tl_2008__tabblock.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code STATENS 8 String Current state ANSI code COUNTYFP 3 String Current county FIPS code STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TRACTCE00 6 String Census 2000 census tract code BLOCKCE00 4 String Census 2000 tabulation block number SUFFIX1CE 1 String Current census block suffix 1 BLKIDFP 16 String Current block identifier; a concatenation of Census 2000 state FIPS code, Census 2000 county FIPS code, Census 2000 census tract code, Census 2000 tabulation block number, and current block suffix 1. NAME 11 String Current tabulation block name; a concatenation of “Block”, the current tabulation block number, and the block suffix 1 MTFCC 5 String MAF/TIGER feature class code (G5040) UR 1 String Corrected Census 2000 urban/rural indicator UACE 5 String Corrected Census 2000 urban area code FUNCSTAT 1 String Current functional status 3.8.2.2 Census 2000 Block State-based Shapefile Record Layout The shapefile name is: tl_2008__tabblock00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TRACTCE00 6 String Census 2000 census tract code BLOCKCE00 4 String Census 2000 tabulation block number BLKIDFP00 15 String Census 2000 block identifier; a concatenation of state FIPS code, county FIPS code, census tract code, and tabulation block number NAME00 10 String Census 2000 tabulation block name; a concatenation of “Block” and the Census 2000 tabulation block number MTFCC00 5 String MAF/TIGER feature class code (G5040) UR00 1 String Census 2000 urban/rural indicator UACE00 5 String Census 2000 urban area code FUNCSTAT00 1 String Census 2000 functional status 3.8.3 Block Groups Block group geography and attributes are available by state in the following shapefile: Census 2000 Block Group State-based Shapefile Alternately, block groups are also available in county-based shapefiles. Please see the section “Block Groups” under “County-based Shapefiles” later in this chapter for additional shapefile information. Block Groups (BGs) are clusters of blocks within the same census tract that have 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 Census Bureau's Participant Statistical Areas Program. The Census Bureau delineated BGs only where a local or tribal government declined to participate or where the 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, and Native Hawaiian areas. Under an alternative Census 2000 AIANNH area 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 Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to the offshore areas not included in regularly numbered census tract areas. 3.8.3.1 Census 2000 Block Group State-based Shapefile Record Layout The shapefile name is: tl_2008__bg00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TRACTCE00 6 String Census 2000 census tract code BLKGRPCE00 1 String Census 2000 block group number BKGPIDFP00 12 String Census 2000 census block group identifier; a concatenation of state FIPS code, county FIPS code, census tract code, and block group number NAMELSAD00 13 String Census 2000 translated legal/statistical area description and the block group number MTFCC00 5 String MAF/TIGER feature class code (G5030) FUNCSTAT00 1 String Census 2000 functional status 3.8.4 Census Tracts Census tract geography and attributes are available by state in the following shapefile: Census 2000 Census Tract State-based Shapefile Alternately, census tracts are also available in county-based shapefiles. Please see the section “Census Tracts” under “County-based Shapefiles” later in this chapter for additional shapefile information. Census Tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the Census Bureau's 2000 Participant Statistical Areas Program. The 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. They 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 always are census tract boundaries in the standard census geographic hierarchy. Under the Census 2000 American Indian, Alaska Native, and Native Hawaiian area 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 Codes and Numbers—Census tract numbers have up to a 4-digit basic number and may have an optional 2-digit suffix; for example, 1457.02. The census tract numbers (used as names) eliminate any leading zeroes and append a suffix only if required. The 6-character numeric census tract codes, however, include leading zeroes and have an implied decimal point for the suffix. Census tract codes range from 000100 to 998998 and are unique within a county or equivalent area. The 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 “Census Tracts in American Indian Areas” below for further information. The Census Bureau assigned a default census tract code of 000000 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 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 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 home port of the vessel. The 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 renumbering of, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes. Census Tract Names—The Census 2000 Census Tract shapefiles contain the census tract codes in three formats. The TRACTCE00 field contains the 6-digit format, complete with leading and trailing zeros. The NAME00 field contains the census tract name as displayed in 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 code 000302 has a census tract name of 3.02 and the name for census tract code 020800 is 208. The NAMELSAD00 field includes both the translated legal/statistical area description and the census tract name, as in, “Census Tract 1”. Census Tracts in American Indian Areas—The 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, and Native Hawaiian areas geographic hierarchy, the 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, and Native Hawaiian areas geographic hierarchy, the Census Bureau identifies all census tracts on federally recognized American Indian reservations and off-reservation trust lands as tribal census tracts. The 2000 tribal census tracts nest within the 2000 boundaries of American Indian and Native Hawaiian areas. The current boundaries of such areas may no longer match the 2000 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, and Native Hawaiian areas. Under the Census 2000 American Indian, Alaska Native, and Native Hawaiian areas census geographic hierarchy, tribal census tracts are defined within American Indian entities and can cross state and county boundaries. Census Tract Numbers and 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 3.8.4.1 Census 2000 Census Tract State-based Shapefile Record Layout The shapefile name is: tl_2008__tract00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TRACTCE00 6 String Census 2000 census tract code CTIDFP00 11 String Census 2000 census tract identifier; a concatenation of state FIPS code, county FIPS code, and census tract code NAME00 7 String Census 2000 census tract name, including the decimal point and decimal digits if a non-zero census tract suffix exists, excluding trailing zeros unless the zeros are part of a non-zero census tract suffix, and excluding any leading zeros NAMELSAD00 20 String Census 2000 translated legal/statistical area description and the census tract name MTFCC00 5 String MAF/TIGER feature class code (G5020) FUNCSTAT00 1 String Census 2000 functional status 3.8.5 Commercial Regions Commercial region geography and attributes are available for Puerto Rico in the following shapefile: Economic Census Commercial Region Shapefile 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 3.8.5.1 Economic Census Commercial Region Shapefile Record Layout The shapefile name is: tl_2008_72_comrgec.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFPEC 2 String 2007 Economic Census state FIPS code COMRGCEEC 1 String 2007 Economic Census commercial region code COMREGIDEC 3 String 2007 Economic Census commercial region identifier; a concatenation of Economic Census state FIPS code and Economic Census commercial region census code NAMEEC 100 String 2007 Economic Census commercial region name NAMELSADEC 100 String 2007 Economic Census commercial region name and the translated legal/statistical area description for commercial region LSADEC 2 String 2007 Economic Census legal/statistical area description code for commercial region MTFCCEC 5 String MAF/TIGER feature class code FUNCSTATEC 1 String 2007 Economic Census functional status 3.8.6 Congressional Districts Congressional district geography and attributes are available by state in the following shapefiles: 110th Congressional District Shapefile 108th Congressional District Shapefile 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 2008 TIGER/Line Shapefiles contain the 110th and 108th Congressional Districts. Two states (Texas and Georgia) redistricted for the 110th Congress (January 2007 to 2009). Where the boundary of a congressional district for the 110th Congress splits a Census 2000 block, the Census Bureau's TIGER/Line Shapefiles depict the location of the boundary correctly. For data tabulation purposes, the population of that split block is allocated in its entirety to the 110th Congressional District specified by the state. A list of 110th Congressional Districts that split census blocks, showing the congressional district where the block is allocated for data tabulation, is available from URL: http://www.census.gov/geo/www/cd110th/spblk110.txt. All congressional districts appearing in the 2008 TIGER/Line Shapefiles reflect the information provided to the Census Bureau by the states. The congressional districts for the 108th Congress (January 2003 to 2005) were the first to reflect redistricting based on Census 2000. Congressional District Codes—Congressional districts are identified by a 2-character numeric FIPS code. Congressional districts are numbered uniquely within state. The District of Columbia, Puerto Rico, and the Island Areas have codes 98 and 99 assigned, as appropriate, identifying their status with respect to representation in Congress: 01 to 53—Congressional district codes 00—At large (single district for state) 98—Nonvoting delegate 99—Area with no representative in Congress 3.8.6.1 110th Congressional District Shapefile Record Layout The shapefile name is: tl_2008__cd110.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code STATENS 8 String Current state ANSI code CD110FP 2 String 110th congressional district FIPS code CD110IDFP 7 String 110th congressional district identifier; a concatenation of current state FIPS code, the 110th congressional session code, and the 110th congressional district FIPS code NAMELSAD 41 String Current name and the translated legal/statistical area description for congressional district LSAD 2 String Current legal/statistical area description code for congressional district CDSESSN 3 String 110th congressional session code MTFCC 5 String MAF/TIGER feature class code (G5200) FUNCSTAT 1 String Current functional status 3.8.6.2 108th Congressional District Shapefile Record Layout The shapefile name is: tl_2008__cd108.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code CD108FP 2 String 108th congressional district FIPS code CD108IDFP 7 String 108th congressional district identifier; a concatenation of Census 2000 state FIPS code, the 108th congressional session code, and the 108th congressional district FIPS code NAMELSAD00 41 String Census 2000 name and the translated legal/statistical area description for congressional district LSAD00 2 String Census 2000 legal/statistical area description code for congressional district CDSESSN 3 String 108th congressional session code MTFCC00 5 String MAF/TIGER feature class code (G5200) FUNCSTAT00 1 String Census 2000 functional status 3.8.7 Consolidated Cities Consolidated city geography and attributes are available by state in the following shapefiles: Current Consolidated City Shapefile Census 2000 Consolidated City Shapefile Economic Census Consolidated City Shapefile Consolidated City—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. This action results 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 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. Consolidated cities are represented in the TIGER/Line Shapefiles by a 5-character numeric FIPS code. Consolidated City (Balance) Portions refer to the areas of a consolidated city not included in another separately incorporated place. For example, Butte-Silver Bow, MT, is a consolidated city (former Butte city and Silver Bow County) that includes the separately incorporated municipality of Walkerville city. The area of the consolidated city that is not in Walkerville city is assigned to Butte-Silver Bow (balance). The name always includes the “(balance)” identifier. Balance portions of consolidated cities are included in the Place shapefiles. Economic Census Consolidated City (Balance) Portions —For the Economic Census, the Census Bureau sometimes recognizes the “balance of consolidated city” which excludes the incorporated place(s) that are recognized separately as economic places. There is no “balance of a consolidated city” if none of the included places meet the minimum population or job threshold. The entire entity qualifies simply as a place- level entity rather than “balance of consolidated city.” The seven consolidated cities and the qualifying economic places within their boundaries (if any) are: Milford, CT—the consolidated city is coextensive with Milford town. There is no “balance of consolidated city” for the 2007 Economic Census. Athens-Clarke County, GA—the consolidated city is coextensive with Clarke County. There is no “balance of consolidated city” for the 2007 Economic Census. Augusta-Richmond County, GA—the consolidated city is coextensive with Richmond County. There is no “balance of consolidated city” for the 2007 Economic Census. Indianapolis, IN—the consolidated city of Indianapolis does not contain all of the land area of Marion County. Specifically excluded from the consolidated city area of the government are Beech Grove city, Lawrence city, Southport city, and Speedway town. Although Southport city does not meet the minimum criteria, the economic census recognizes Southport city as an exceptional case since the balance of county record equates to a single government. The economic census place “Indianapolis city (balance)” will contain the remainder of Marion County excluding the above four entities and Cumberland town (part of which is in Marion County), which meets the minimum criteria for recognition as an economic place. Louisville/Jefferson County, KY—the consolidated city includes all of Jefferson County. The economic census place “Louisville/Jefferson County (balance)” will contain all of Jefferson County, except the cities of Douglass Hills, Jeffersontown, Lyndon, Middletown, St. Matthews, Shively, and Watterson Park, each of which meets the minimum criteria for recognition as an economic place. Butte-Silver Bow, MT—the consolidated city is coextensive with Silver Bow County. There is no “balance of consolidated city” for the 2007 Economic Census. Nashville-Davidson, TN—the consolidated city is coextensive with Davidson County. The economic census place “Nashville-Davidson (balance)”will contain all of Davidson County, except Berry Hill city, Forest Hill city, and Goodlettsville city (part of which is in Sumner County), each of which meets the minimum criteria for recognition as an economic place. 3.8.7.1 Current Consolidated City Shapefile Record Layout The shapefile name is: tl_2008__concity.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code CONCTYFP 5 String Current consolidated city FIPS 55 code CONCTYNS 8 String Current consolidated city ANSI code CCTYIDFP 7 String Current consolidated city identifier; a concatenation of current state FIPS code and consolidated city FIPS 55 code NAME 100 String Current consolidated city name NAMELSAD 100 String Current name and the translated legal/statistical area description for consolidated city LSAD 2 String Current legal/statistical area description code for consolidated city CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code (G4120) FUNCSTAT 1 String Current functional status 3.8.7.2 Census 2000 Consolidated City Shapefile Record Layout The shapefile name is: tl_2008__concity00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code CONCTYFP00 5 String Census 2000 consolidated city FIPS 55 code CCTYIDFP00 7 String Census 2000 consolidated city identifier; a concatenation of Census 2000 state FIPS code and consolidated city FIPS 55 code NAME00 100 String Census 2000 consolidated city name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for consolidated city LSAD00 2 String Census 2000 legal/statistical area description code for consolidated city CLASSFP00 2 String Census 2000 FIPS 55 class code CPI00 1 String Census 2000 urban area central place indicator MTFCC00 5 String MAF/TIGER feature class code (G4120) UR00 1 String Census 2000 urban/rural indicator FUNCSTAT00 1 String Census 2000 functional status 3.8.7.3 Economic Census Consolidated City Shapefile Record Layout The shapefile name is: tl_2008__concityec.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFPEC 2 String 2007 Economic Census state FIPS code CONCTYFPEC 5 String 2007 Economic Census consolidated city FIPS 55 code CCTYIDFPEC 7 String 2007 Economic Census consolidated city identifier; a concatenation of 2007 Economic Census state FIPS code and consolidated city FIPS 55 code NAMEEC 100 String 2007 Economic Census consolidated city name NAMELSADEC 100 String 2007 Economic Census name and the translated legal/statistical area description for consolidated city LSADEC 2 String 2007 Economic Census legal/statistical area description code for consolidated city CLASSFPEC 2 String 2007 Economic Census FIPS 55 class code MTFCCEC 5 String MAF/TIGER feature class code (G4120) FUNCSTATEC 1 String 2007 Economic Census functional status 3.8.8 Counties and Equivalent Entities County and equivalent entity geography and attributes are available by state in the following shapefiles: Current County and Equivalent State-based Shapefile Census 2000 County and Equivalent State-based Shapefile Economic Census County and Equivalent Shapefile Alternately, current and Census 2000 counties and equivalent entities are also available in nation-based shapefiles. Please see the section “Counties and Equivalent Entities” under “Nation-Based Shapefiles” earlier in this chapter for information about current and Census 2000 counties and additional shapefile information. Economic Census counties and equivalent entities are only available in state-based shapefiles. Economic Census Geography—The boundaries used for counties and equivalent entities for the 2007 Economic Census are those reported to the Census Bureau to be legally in effect on January 1, 2007. 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 2007 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 In Hawaii, the Economic Census combined Kalawao County into Maui County for the presentation of data. 3.8.8.1 Current County and Equivalent State-based Shapefile Record Layout The shapefile name is: tl_2008__county.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code COUNTYNS 8 String Current county ANSI code CNTYIDFP 5 String Current county identifier; a concatenation of current state FIPS code and county FIPS code NAME 100 String Current county name NAMELSAD 100 String Current name and the translated legal/statistical area description for county LSAD 2 String Current legal/statistical area description code for county CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code (G4020) CSAFP 3 String Current combined statistical area code CBSAFP 5 String Current metropolitan statistical area/micropolitan statistical area code METDIVFP 5 String Current metropolitan division code FUNCSTAT 1 String Current functional status 3.8.8.2 Census 2000 County and Equivalent State-based Shapefile Record Layout The shapefile name is: tl_2008__county00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code CNTYIDFP00 5 String Census 2000 county identifier; a concatenation of Census 2000 state FIPS code and county FIPS code NAME00 100 String Census 2000 county name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for county LSAD00 2 String Census 2000 legal/statistical area description code for county CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code (G4020) UR00 1 String Census 2000 urban/rural indicator FUNCSTAT00 1 String Census 2000 functional status 3.8.8.3 Economic Census County and Equivalent Shapefile Record Layout The shapefile name is: tl_2008__countyec.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFPEC 2 String 2007 Economic Census state FIPS code COUNTYFPEC 3 String 2007 Economic Census county FIPS code CNTYIDFPEC 5 String 2007 Economic Census county identifier; a concatenation of 2007 Economic Census state FIPS code and county FIPS code NAMEEC 100 String 2007 Economic Census county name NAMELSADEC 100 String 2007 Economic Census name and the translated legal/statistical area description for county LSADEC 2 String 2007 Economic Census legal/statistical area description code for county CLASSFPEC 2 String 2007 Economic Census FIPS 55 class code MTFCCEC 5 String MAF/TIGER feature class code (G4020) FUNCSTATEC 1 String 2007 Economic Census functional status 3.8.9 County Subdivisions County subdivision geography and attributes are available by state in the following shapefiles: Current County Subdivision State-based Shapefile Census 2000 County Subdivision State-based Shapefile Alternately, county subdivisions are also available in county-based shapefiles. Please see the section “County Subdivisions” under “County-based Shapefiles” later in this chapter for additional shapefile information. County Subdivisions—County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of decennial census data. They include census county divisions, census subareas, minor civil divisions, and unorganized territories. The TIGER/Line Shapefiles contain a 5-character numeric FIPS code field for county subdivisions. 3.8.9.1 Legal Entities Minor Civil Divisions (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 include areas variously designated as American Indian reservations, assessment districts, boroughs, election districts, gores, grants, locations, magisterial districts, parish governing authority districts, plantations, precincts, purchases, supervisor's districts, towns, and townships. The Census Bureau recognizes MCDs in 28 states, Puerto Rico, and the Island Areas. The District of Columbia has no primary divisions, and is considered equivalent to an MCD for statistical purposes (it is also considered a state equivalent and a county equivalent). 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. 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 Census Bureau presents data for these MCDs in all data products for which place data are provided. In New York and Maine, American Indian reservations (AIRs) exist outside the jurisdiction of any town (MCD) and thus also serve as the equivalent of MCDs for purposes of data presentation. 3.8.9.2 Statistical Entities Census County Divisions (CCDs) are areas delineated by the 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 Arizona California Colorado Delaware Florida Georgia Hawaii Idaho Kentucky Montana Nevada New Mexico Oklahoma Oregon South Carolina Tennessee Texas Utah Washington Wyoming 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 Census Bureau cooperatively delineate the census subareas to serve as the statistical equivalents of MCDs. Unorganized Territories (UTs) are defined by the Census Bureau in 11 minor civil division (MCD) states and American Samoa where portions of counties or equivalent entities are not included in any legally established MCD or incorporated place. The 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. The following states and equivalent entities had in Census 2000 or now have unorganized territories: Arkansas Indiana Iowa Louisiana* Maine Minnesota New York+ North Carolina North Dakota Ohio* South Dakota American Samoa+ *Unorganized territories existed in Louisiana and Ohio in 2000, but do not exist there currently. +Unorganized territories exist in New York and American Samoa currently, but did not exist there in 2000. County Subdivisions Not Defined—In water bodies, primarily Great Lakes waters and territorial sea, legal county subdivisions do not extend to cover the entire county. For these areas, the Census Bureau created a county subdivision with a FIPS code of 00000 named “county subdivision not defined”. The following states and equivalent areas have these county subdivisions for both 2000 and current geography: Connecticut Illinois Indiana Maine Massachusetts Michigan Minnesota New Hampshire New Jersey New York Ohio Pennsylvania Rhode Island Wisconsin Puerto Rico U.S. Virgin Islands Current Geography—The boundaries identified as current for MCDs are updated boundaries collected since Census 2000 as part of the 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. In some cases, corrections of locally requested updates have caused changes to the CCD inventory and boundaries. 3.8.9.3 Current County Subdivision State-based Shapefile Record Layout The shapefile name is: tl_2008__cousub.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code COUSUBFP 5 String Current county subdivision FIPS code COUSUBNS 8 String Current county subdivision ANSI code COSBIDFP 10 String Current county subdivision identifier; a concatenation of current state FIPS code, county FIPS code, and county subdivision FIPS code. NAME 100 String Current county subdivision name NAMELSAD 100 String Current name and the translated legal/statistical area description code for county subdivision LSAD 2 String Current legal/statistical area description code for county subdivision CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code CNECTAFP 3 String Current combined New England city and town area code NECTAFP 5 String Current New England city and town area code NCTADVFP 5 String Current New England city and town area division code FUNCSTAT 1 String Current functional status 3.8.9.4 Census 2000 County Subdivision State-based Shapefile Record Layout The shapefile name is: tl_2008__cousub00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code COUSUBFP00 5 String Census 2000 county subdivision FIPS code COSBIDFP00 10 String Census 2000 county subdivision identifier; a concatenation of Census 2000 state FIPS code, county FIPS code, and county subdivision FIPS code. NAME00 100 String Census 2000 county subdivision name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description code for county subdivision LSAD00 2 String Census 2000 legal/statistical area description code for county subdivision CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code UR00 1 String Census 2000 urban/rural indicator FUNCSTAT00 1 String Census 2000 functional status 3.8.10 Places Place geography and attributes are available by state in the following shapefiles: Current Place Shapefile Census 2000 Place Shapefile Economic Census Place Shapefile The TIGER/Line Shapefiles include both incorporated places (legal entities) and census designated places (statistical entities). Incorporated Places are those reported to the Census Bureau as legally in existence as of the latest BAS, 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 usually is a city, town, village, or borough, but can have other legal descriptions. 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 City and Borough of Yakutat, Alaska Census Designated Places (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 another 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 Census Bureau. All places shown in the Census 2000 data products for Hawaii are CDPs. By agreement with the State of Hawaii, the 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 Census Bureau recognizes only CDPs. The CDPs in Puerto Rico are called comunidades or zonas urbanas. Guam and the Commonwealth of the Northern Mariana Islands also have only CDPs. Place Codes—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 the 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"). 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 not part of any minor civil division (MCD) and serve as primary county subdivisions. The independent place FIPS code usually is the same as that used for the MCD for the place. 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 always are dependent within county subdivisions and all places are dependent within statistical county subdivisions. Geographic Corridors and Offset Geographic Boundaries—A geographic corridor (formerly called corporate corridor) is a narrow, linear part of an incorporated place (or in a very few instances, another type of legal entity). The geographic 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 geographic limit offset boundary (formerly called 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 adjoins the side of the street with the geographic limit offset boundary. It is possible to have two or more geographic limit offset boundaries in the same street or right-of-way. Geographic limit offset boundaries use the same map symbology as non-offset boundaries. Geographic corridor address ranges are related by TLID to the corridor bounding edge adjacent to the road edge. The street names are related to the address ranges on the geographic corridor bounding edges through the address range-feature name relationship file. Assigning the address range to the geographic corridor edge instead of the road edge will geocode structures correctly outside of the geographic corridor. Consolidated City (Balance) Portions refer to the areas of a consolidated city not included in another separately incorporated place. For example, Butte-Silver Bow, MT, is a consolidated city (former Butte city and Silver Bow County) that includes the separately incorporated municipality of Walkerville city. The area of the consolidated city that is not in Walkerville city is assigned to Butte-Silver Bow (balance). The name always includes the “(balance)” identifier. Balance portions of consolidated cities are included in the Place shapefiles. Current Geography—The boundaries identified as current for incorporated places are updated boundaries collected since Census 2000 as part of the 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. CDPs also may have changed as a result of local requests to correct errors or create CDPs for significant places that have disincorporated since 2000. Economic Census Places—Qualification of Economic Census places is based on a population threshold of 5,000 or more inhabitants or 5,000 or more workers. The Economic Census Places shapefile includes places for which the 2007 Economic Census publishes data. An incorporated place, CDP, MCD, or balance of MCD qualifies as an economic place if it contains: 5,000 or more people according to Census 2000 or the Census Bureau’s July 1, 2007 population estimate, or 5,000 or more jobs according to Census 2000. Territory within a county but outside qualifying economic census places is referred to as “balance of county” and treated as a place equivalent for data tabulation and publication purposes. Most counties or county equivalents will have a balance area. Balance of county includes those areas not recognized as places and place-equivalents under the above definitions. An MCD can only qualify as an economic census place in Connecticut, Maine, Massachusetts, Michigan, Minnesota, New Hampshire, New Jersey, New York, Pennsylvania, Rhode Island, Vermont, and Wisconsin. If an MCD contains one or more dependent incorporated places that qualify as economic census places, and after subtraction the remaining MCD still qualifies as an economic census place, the area is called a balance of MCD place. The name will include the text “(balance)”, as in “Holly township (balance)”. New places reported to the U.S. Census Bureau and legally in effect on January 1, 2007, are recognized if they meet the minimum population requirement. Guam, the Commonwealth of the Northern Mariana Islands, American Samoa, and Puerto Rico do not have any Economic Census places. Economic Census Consolidated City (Balance) Portions—For the Economic Census, the Census Bureau sometimes recognizes the “balance of consolidated city” which excludes the incorporated place(s) that are recognized separately as economic places. There is no “balance of a consolidated city” if none of the included places meet the minimum population or job threshold. The entire entity qualifies simply as a place- level entity rather than “balance of consolidated city.” The seven consolidated cities and the qualifying economic places within their boundaries (if any) are: Milford, CT—the consolidated city is coextensive with Milford town. There is no “balance of consolidated city” for the 2007 Economic Census. Athens-Clarke County, GA—the consolidated city is coextensive with Clarke County. There is no “balance of consolidated city” for the 2007 Economic Census. Augusta-Richmond County, GA—the consolidated city is coextensive with Richmond County. There is no “balance of consolidated city” for the 2007 Economic Census. Indianapolis, IN—the consolidated city of Indianapolis does not contain all of the land area of Marion County. Specifically excluded from the consolidated city area of the government are Beech Grove city, Lawrence city, Southport city, and Speedway town. Although Southport city does not meet the minimum criteria, the economic census recognizes Southport city as an exceptional case since the balance of county record equates to a single government. The economic census place “Indianapolis city (balance)” will contain the remainder of Marion County excluding the above four entities and Cumberland town (part of which is in Marion County), which meets the minimum criteria for recognition as an economic place. Louisville/Jefferson County, KY—the consolidated city includes all of Jefferson County. The economic census place “Louisville/Jefferson County (balance)” will contain all of Jefferson County, except the cities of Douglass Hills, Jeffersontown, Lyndon, Middletown, St. Matthews, Shively, and Watterson Park, each of which meets the minimum criteria for recognition as an economic place. Butte-Silver Bow, MT—the consolidated city is coextensive with Silver Bow County. There is no “balance of consolidated city” for the 2007 Economic Census. Nashville-Davidson, TN—the consolidated city is coextensive with Davidson County. The economic census place “Nashville-Davidson (balance)” will contain all of Davidson County, except Berry Hill city, Forest Hill city, and Goodlettsville city (part of which is in Sumner County), each of which meets the minimum criteria for recognition as an economic place. 3.8.10.1 Current Place Shapefile Record Layout The shapefile name is: tl_2008__place.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code PLACEFP 5 String Current place FIPS 55 code PLACENS 8 String Current place ANSI code PLCIDFP 7 String Current place identifier; a concatenation of current state FIPS code and place FIPS 55 code NAME 100 String Current place name NAMELSAD 100 String Current name and the translated legal/statistical area description for place LSAD 2 String Current legal/statistical area description code for place CLASSFP 2 String Current FIPS 55 class code CPI 1 String Current urban area central place indicator PCICBSA 1 String Current metropolitan or micropolitan statistical area principal city indicator PCINECTA 1 String Current New England city and town area principal city indicator MTFCC 5 String MAF/TIGER feature class code (see below) FUNCSTAT 1 String Current functional status The MTFCC values are G4110 (incorporated place) and G4210 (census designated place). 3.8.10.2 Census 2000 Place Shapefile Record Layout The shapefile name is: tl_2008__place00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code PLACEFP00 5 String Census 2000 place FIPS 55 code PLCIDFP00 7 String Census 2000 place identifier; a concatenation of Census 2000 state FIPS code and place FIPS 55 code. NAME00 100 String Census 2000 place name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for place LSAD00 2 String Census 2000 legal/statistical area description code for place CLASSFP00 2 String Census 2000 FIPS 55 class code CPI00 1 String Census 2000 urban area central place indicator PCICBSA00 1 String Census 2000 metropolitan or micropolitan statistical area principal city indicator. PCINECTA00 1 String Census 2000 New England city and town area principal city indicator. MTFCC00 5 String MAF/TIGER feature class code (see below) UR00 1 String Census 2000 urban/rural indicator FUNCSTAT00 1 String Census 2000 functional status The MTFCC values are G4110 (incorporated place) and G4210 (census designated place). 3.8.10.3 Economic Census Place Shapefile Record Layout The shapefile name is: tl_2008__placeec.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFPEC 2 String 2007 Economic Census state FIPS code PLACEFPEC 5 String 2007 Economic Census FIPS 55 economic place code PLCIDFPEC 7 String 2007 Economic Census place identifier; a concatenation of 2007 Economic Census state FIPS code and FIPS 55 economic place code NAMEEC 100 String 2007 Economic Census place name NAMELSADEC 100 String 2007 Economic Census name and the translated legal/statistical area description for place LSADEC 2 String 2007 Economic Census legal/statistical area description code for place CLASSFPEC 2 String 2007 Economic Census FIPS 55 class code CPIEC 1 String 2007 Economic Census urban area central place indicator PCICBSAEC 1 String 2007 Economic Census metropolitan or micropolitan statistical area principal city indicator PCINECTAEC 1 String 2007 Economic Census New England city and town area principal city indicator MTFCCEC 5 String MAF/TIGER feature class code (G4300) FUNCSTATEC 1 String 2007 Economic Census functional status 3.8.11 Public Use Microdata Areas (1-Percent and 5-Percent) Public use microdata area geography and attributes are available by state in the following shapefiles: Census 2000 1-Percent Public Use Microdata Area (PUMA1) Shapefile Census 2000 5- or 10*-Percent Public Use Microdata Area (PUMA5) Shapefile *10 percent sample used in Guam and the U.S. Virgin Islands Public Use Microdata Areas (PUMAs) are decennial census areas for which the 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 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 2008 TIGER/Line Shapefiles contain separate shapefiles for the 1-percent and 5- percent PUMAs. In Guam and the U.S. Virgin Islands, the Census Bureau has defined a single PUMA file containing a 10-percent sample of the records. The 10-percent sample PUMA will appear in the 5- or 10-percent PUMA shapefile. 3.8.11.1 Census 2000 1-Percent Public Use Microdata Area (PUMA1) Shapefile Record Layout The shapefile name is: tl_2008__puma100.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code PUMA1CE00 5 String Census 2000 1-percent public use microdata area census code PUMA1ID00 7 String Census 2000 1-percent public use microdata area identifier; a concatenation of Census 2000 state FIPS code and 1-percent public use microdata area census code NAMELSAD00 11 String Census 2000 translated legal/statistical area description and 1-percent public use microdata area census code MTFCC00 5 String MAF/TIGER feature class code (G6100) FUNCSTAT00 1 String Census 2000 functional status 3.8.11.2 Census 2000 5- or 10-Percent* Public Use Microdata Area (PUMA5) Shapefile Record Layout *10 percent sample used in Guam and the US Virgin Islands The shapefile name is: tl_2008__puma500.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code PUMA5CE00 5 String Census 2000 5- or 10-percent public use microdata area census code PUMA5ID00 7 String Census 2000 5- or 10-percent public use microdata area identifier; a concatenation of Census 2000 state FIPS code and 1- percent public use microdata area census code NAMELSAD00 11 String Census 2000 translated legal/statistical area description and 5- or 10-percent public use microdata area census code MTFCC00 5 String MAF/TIGER feature class code (G6120) FUNCSTAT00 1 String Census 2000 functional status 3.8.12 School Districts (Elementary, Secondary, and Unified) School district geography and attributes are available by state in the following shapefiles: Current Elementary School District Shapefile Census 2000 Elementary School District Shapefile Current Secondary School District Shapefile Census 2000 Secondary School District Shapefile Current Unified School District Shapefile Census 2000 Unified School District Shapefile School Districts are single-purpose governmental units within which local officials provide public educational services for the area's residents. The Census Bureau obtains the boundaries, names, local education agency codes, and school district levels 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 I funding to states and school districts. The 2008 TIGER/Line Shapefiles include separate shapefiles for elementary, secondary, and unified school districts. The Census 2000 school district shapefiles contain school district information from the 1999-2000 school year, and the current shapefiles contain information from the 2007-2008 school year. The 2007-2008 school districts represent districts in operation as of January 1, 2008. The elementary school districts provide education to the lower grade/age levels and the secondary school districts provide education to the upper grade/age levels. The unified school districts are districts that provide education to children of all school ages in their service areas. In general, where there is a unified school district, no elementary or secondary school district exists (see exceptions described below), and where there is an elementary school district the secondary school district may or may not exist (see explanation below). In additional to regular school districts, the TIGER/Line Shapefiles contain so-called false school districts (see the description below). The 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 I funds). For example, a school district is defined as an elementary school district if its operational grade range is less than the full kindergarten-12 or pre-kindergarten-12 grade range. These elementary school districts do not provide direct educational services for grades 9-12, 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 I allocation purposes, all school-aged children in their jurisdiction 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 districts 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 areas where a secondary school district is not also included in an elementary school district. 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 Census Bureau included elementary and secondary school districts in Hawaii and elementary school districts in the five New York boroughs in order to provide additional statistics for administrative areas within these school districts. The Census Bureau removed these special administrative areas from its database in 2003 upon the request of Hawaii and New York City officials. However, the Census Bureau still represents these administrative areas for Hawaii and New York in Census 2000 school district shapefiles. California, Kentucky, Massachusetts, South Carolina, Tennessee, and Texas contain pseudo-secondary school districts that represent regular unified school districts in areas where the unified school districts share financial responsibility service with elementary school districts. These pseudo-secondary school districts were created, and linked to real unified school districts in order for the Census Bureau to allocate the high school aged children to the unified school districts. (The 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 the unified school district is fiscally responsible for less than the entire kindergarten-12 grade range). In these areas, 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 (that is, the elementary school districts’ financial responsibilities did not extend to grade 12). Pseudo-secondary school districts were created in twelve Arizona counties to represent service areas where either a unified or a secondary school district can provide services to high school aged children from certain elementary school districts in the county. Each county school district superintendent is responsible for allocating Title I funding for these high school aged children, as the elementary school districts do not pay tuition to the unified or secondary school districts. A list of these pseudo-secondary school districts and their codes appears in Appendix B. There are two pseudo-school districts (one elementary and one secondary) in Klamath County, Oregon, where two unified school districts provide services to different grade ranges within a joint-service area. A list of these pseudo-school districts and their codes appears in Appendix B. School District Codes—The TIGER/Line Shapefiles contain 5-character numeric school district codes. 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 Names—The names of school districts include their description and no other field (NAMELSAD) is required. Note that school district names are always shown in all capital letters, which is different from names for all other geographic areas. 3.8.12.1 Current Elementary School District Shapefile Record Layout The shapefile name is: tl_2008__elsd.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code STATENS 8 String Current state ANSI code ELSDLEA 5 String Current elementary school district local education agency code ELSDIDFP 7 String Current school district identifier; a concatenation of current state FIPS code and elementary school district local education agency code NAME 100 String Current elementary school district name LSAD 2 String Current legal/statistical area description code for elementary school district LOGRADE 2 String Current lowest grade covered by school district HIGRADE 2 String Current highest grade covered by school district MTFCC 5 String MAF/TIGER feature class code (G5400) SDTYP 1 String Current school district type FUNCSTAT 1 String Current functional status 3.8.12.2 Census 2000 Elementary School District Shapefile Record Layout The shapefile name is: tl_2008__elsd00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code ELSDLEA00 5 String Census 2000 elementary school district local education agency code ELSDIDFP00 7 String Census 2000 school district identifier: a concatenation of Census 2000 state FIPS code and elementary school district local education agency code NAME00 100 String Census 2000 elementary school district name LSAD00 2 String Census 2000 legal/statistical area description code for elementary school district LOGRADE00 2 String Census 2000 lowest grade covered by school district HIGRADE00 2 String Census 2000 highest grade covered by school district MTFCC00 5 String MAF/TIGER feature class code (G5400) SDTYP00 1 String Census 2000 school district type FUNCSTAT00 1 String Census 2000 functional status 3.8.12.3 Current Secondary School District Shapefile Record Layout The shapefile name is: tl_2008__scsd.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code STATENS 8 String Current state ANSI code SCSDLEA 5 String Current secondary school district local education agency code SCSDIDFP 7 String Current school district identifier; a concatenation of current state FIPS code and secondary school district local education agency code NAME 100 String Current secondary school district name LSAD 2 String Current legal/statistical area description code for secondary school district LOGRADE 2 String Current lowest grade covered by school district HIGRADE 2 String Current highest grade covered by school district MTFCC 5 String MAF/TIGER feature class code (G5410) SDTYP 1 String Current school district type FUNCSTAT 1 String Current functional status 3.8.12.4 Census 2000 Secondary School District Shapefile Record Layout The shapefile name is: tl_2008__scsd00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code SCSDLEA00 5 String Census 2000 secondary school district local education agency code SCSDIDFP00 7 String Census 2000 school district identifier; a concatenation of Census 2000 state FIPS code and secondary school district local education agency code NAME00 100 String Census 2000 secondary school district name LSAD00 2 String Census 2000 legal/statistical area description code for secondary school district LOGRADE00 2 String Census 2000 lowest grade covered by school district HIGRADE00 2 String Census 2000 highest grade covered by school district MTFCC00 5 String MAF/TIGER feature class code (G5410) SDTYP00 1 String Census 2000 school district type FUNCSTAT00 1 String Census 2000 functional status 3.8.12.5 Current Unified School District Shapefile Record Layout The shapefile name is: tl_2008__unsd.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code STATENS 8 String Current state ANSI code UNSDLEA 5 String Current unified school district local education agency code UNSDIDFP 7 String Current school district identifier; a concatenation of current state FIPS code and unified school district local education agency code NAME 100 String Current unified school district name LSAD 2 String Current legal/statistical area description code for unified school district LOGRADE 2 String Current lowest grade covered by school district HIGRADE 2 String Current highest grade covered by school district MTFCC 5 String MAF/TIGER feature class code (G5420) SDTYP 1 String Current school district type FUNCSTAT 1 String Current functional status 3.8.12.6 Census 2000 Unified School District Shapefile Record Layout The shapefile name is: tl_2008__unsd00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code UNSDLEA00 5 String Census 2000 unified school district local education agency code UNSDIDFP00 7 String Census 2000 school district identifier: a concatenation of Census 2000 state FIPS code and unified school district local education agency code NAME00 100 String Census 2000 unified school district name LSAD00 2 String Census 2000 legal/statistical area description code for unified school district LOGRADE00 2 String Census 2000 lowest grade covered by school district HIGRADE00 2 String Census 2000 highest grade covered by school district MTFCC00 5 String MAF/TIGER feature class code (G5420) SDTYP00 1 String Census 2000 school district type FUNCSTAT00 1 String Census 2000 functional status 3.8.13 State Legislative Districts (Upper and Lower Chambers) State legislative district geography and attributes are available by state in the following shapefiles: Current State Legislative District Lower Chamber (SLDL) Shapefile Census 2000 State Legislative District Lower Chamber (SLDL) Shapefile Current State Legislative District Upper Chamber (SLDU) Shapefile Census 2000 State Legislative District Upper Chamber (SLDU) Shapefile State Legislative Districts (SLDs) are the areas from which members are elected to state legislatures. The Census Bureau first reported data for SLDs as part of the 2000 Public Law (P.L.) 94-171 Redistricting Data File. Current SLDs (2006 Election Cycle)—States participating in Phase 1 of the 2010 Census Redistricting Data Program, as part of P.L. 94-171, provided the Census Bureau with the 2006 election cycle boundaries, codes, and in some cases names for their SLDs. All 50 states, plus the District of Columbia and Puerto Rico, participated in Phase 1, State Legislative District Project (SLDP), of the 2010 Census Redistricting Data Program. The Census Bureau will maintain SLDs in MAF/TIGER and accept updates required by law or redistricting from our liaisons on an on-going basis. Therefore, these areas may change prior to the release of the 2010 Census P.L. 94-171 Redistricting Data Files. The SLDs embody the upper (senate—SLDU) and lower (house—SLDL) chambers of the state legislature. Nebraska has a unicameral legislature and the District of Columbia has a single council, both of which the Census Bureau treats as upper- chamber legislative areas for the purpose of data presentation. Therefore, there is no data by SLDL for either Nebraska or the District of Columbia. A unique 3-character census code, identified by state participants, is assigned to each SLD within a state. In Connecticut, Hawaii, Illinois, Louisiana, Maine, Maryland, Massachusetts, New Jersey, Ohio, and Puerto Rico, the states did not define the current SLDs to cover all of the state or state equivalent area. In states other than Maryland, the code “ZZZ” has been assigned to areas with no SLDs defined. These unassigned areas are treated within state as a single SLD for purposes of data presentation. In Maryland, the code “Z**”, where “**” represents the last two digits of the county code, has been assigned to areas with no SLDs defined. These unassigned areas are treated within county as a single SLD for purposes of data presentation. SLD Names—The Census Bureau first reported names for SLDs as part of Phase 1 of the 2010 Census Redistricting Data Program. The SLD names with their translated legal/statistical area description are associated only with the current (2006) SLDs. Not all states provided names for their SLDs and the code (or number) serves as the name. There are no SLD names associated with Census 2000 SLDs. The name and translated legal/statistical area description field in the Census 2000 shapefiles contains the SLD code. The current SLDs are the SLDs presented to the Census Bureau during Phase 1 of the 2010 Census Redistricting Data Program. These SLDs were current for the 2006 election cycle. The Census Bureau will update boundaries every two years, as necessary, per state changes brought about by court ordered changes or additional redistricting. Census 2000 SLDs—For states participating in the optional phase of the 2000 Public Law (P.L.) 94-171 Redistricting Data Program, the vintage of these legislative districts were those used in the 1998 election cycle. The following states did not submit SLDs as part of the Census 2000 Redistricting Data Program, therefore no Census 2000 SLD shapefiles exist for the following states: Arkansas California District of Columbia Florida Hawaii Kentucky Maine Maryland Minnesota Montana Texas Puerto Rico In addition, New Hampshire only submitted SLDs for their upper chamber, therefore no Census 2000 SLDL shapefile exists for the state. In Connecticut, Delaware, Illinois, Louisiana, Massachusetts, New Jersey, Pennsylvania, and Rhode Island, the states did not define the Census 2000 SLDLs to cover all of the state or state equivalent area. The same was true for Connecticut, Delaware, Illinois, Louisiana, Michigan, New Hampshire, New Jersey, and Rhode Island for Census 2000 SLDUs. In these areas, the code “ZZZ” has been assigned to areas with no SLDs defined. These unassigned areas are treated within state as a single SLD for purposes of data presentation. 3.8.13.1 Current State Legislative District Lower Chamber (SLDL) Shapefile Record Layout The shapefile name is: tl_2008__sldl.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code STATENS 8 String Current state ANSI code SLDLST 3 String Current state legislative district lower chamber code SLDLIDFP 5 String Current state legislative district lower chamber identifier; a concatenation of current state FIPS code and state legislative district lower chamber code NAMELSAD 100 String Current name and the translated legal/statistical area description for state legislative district lower chamber LSAD 2 String Current legal/statistical area description code for state legislative district lower chamber LSY 4 String Legislative session year MTFCC 5 String MAF/TIGER feature class code (G5220) FUNCSTAT 1 String Current functional status 3.8.13.2 Census 2000 State Legislative District Lower Chamber (SLDL) Shapefile Record Layout The shapefile name is: tl_2008__sldl00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code SLDLST00 3 String Census 2000 state legislative district lower chamber code SLDLIDFP00 5 String Census 2000 state legislative district lower chamber identifier; a concatenation of Census 2000 state FIPS code and state legislative district lower chamber code NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for state legislative district lower chamber LSAD00 2 String Census 2000 legal/statistical area description code for state legislative district lower chamber LSY 4 String Legislative session year MTFCC00 5 String MAF/TIGER feature class code (G5220) FUNCSTAT00 1 String Census 2000 functional status 3.8.13.3 Current State Legislative District Upper Chamber (SLDU) Shapefile Record Layout The shapefile name is: tl_2008__sldu.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code STATENS 8 String Current state ANSI code SLDUST 3 String Current state legislative district upper chamber code SLDUIDFP 5 String Current state legislative district upper chamber identifier; a concatenation of current state FIPS code and state legislative district upper chamber code NAMELSAD 100 String Current name and the translated legal/statistical area description for state legislative district upper chamber LSAD 2 String Current legal/statistical area description code for state legislative district upper chamber LSY 4 String Legislative session year MTFCC 5 String MAF/TIGER feature class code (G5210) FUNCSTAT 1 String Current functional status 3.8.13.4 Census 2000 State Legislative District Upper Chamber (SLDU) Shapefile Record Layout The shapefile name is: tl_2008__sldu00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code SLDUST00 3 String Census 2000 state legislative district upper chamber code SLDUIDFP00 5 String Census 2000 state legislative district upper chamber identifier; a concatenation of Census 2000 state FIPS code and state legislative district upper chamber code NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for state legislative district upper chamber LSAD00 2 String Census 2000 legal/statistical area description code for state legislative district upper chamber LSY 4 String Legislative session year MTFCC00 5 String MAF/TIGER feature class code (G5210) FUNCSTAT00 1 String Census 2000 functional status 3.8.14 Urban Growth Areas Urban growth area geography and attributes are available for Oregon in the following shapefile: Current Urban Growth Area (UGA) Shapefile Census 2000 Urban Growth Area (UGA) Shapefile Urban Growth Areas (UGAs) are legally defined entities in Oregon that the Census Bureau includes in the MAF/TIGER 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 in Oregon and then confirmed in state law. UGAs were a pilot project and a new geographic entity for Census 2000. Each UGA is identified by a 5-digit numeric census code, usually associated with the incorporated place for which the UGA is named. There has been no update to UGAs; the current UGAs match 2000 UGAs except for some changes to maintain consistency of data. 3.8.14.1 Current Urban Growth Area (UGA) Shapefile Record Layout The shapefile name is: tl_2008_41_uga.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code UGACE 5 String Current urban growth area code UGATYP 1 String Current urban growth area type NAME 100 String Current urban growth area name NAMELSAD 100 String Current name and the translated legal/statistical area description for urban growth area LSAD 2 String Current legal/statistical area description code for urban growth area MTFCC 5 String MAF/TIGER feature class code FUNCSTAT 1 String Current functional status 3.8.14.2 Census 2000 Urban Growth Area (UGA) Shapefile Record Layout The shapefile name is: tl_2008_41_uga00.shp The shapefile is state-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code UGACE00 5 String Census 2000 urban growth area census code UGATYP00 1 String Census 2000 urban growth area type NAME00 100 String Census 2000 urban growth area name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for urban growth area LSAD00 2 String Census 2000 legal/statistical area description code for urban growth area MTFCC00 5 String MAF/TIGER feature class code (G6330) FUNCSTAT00 1 String Census 2000 functional status 3.9 County-Based Shapefiles 3.9.1 All Lines Linear feature geography and attributes are available by county in the following shapefile: All Lines Shapefile The All Lines shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines shapefiles are available in relationship files that users must download separately (see “County-Based Relationship Files” later in this chapter). The All Lines shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TLID (TIGER/Line identifier) value. The left and right faces for an edge can be determined by linking the TFIDL (permanent face identifier on the left side of the edge) or TFIDR (permanent face identifier on the right side of the edge) attribute to the TFID (permanent face identifier) attribute in the Topological Faces relationship table. The left and right side of an edge is determined by the order of the points that form the edge. An edge is oriented from the start node to the end node. If one is standing on an edge at the start node facing the end node, data listed in the fields carrying a right qualifier would be found to the right of the edge. Data users can employ GIS software to plot the edges as directional vectors with arrows showing the orientation of edges. In the MAF/TIGER database, edges may represent several types of features. The series of indicator flags (HYDROFLG, ROADFLG, RAILFLG, and OLFFLG) indicate the classes of features that share the edge. For example, a road may have embedded tracks; the corresponding edge will have both the ROADFLG and RAILFLG set. Generally, certain feature types appear together on the same edge: Road and Rail—roads with adjacent tracks, tracks embedded in roadways, or tracks located in the median Rail and Other Linear Feature—rail features located on dams and levees Road and Other Linear Feature—road features located on dams and levees The MAF/TIGER feature class code (MTFCC) identifies the specific code for the primary feature on the edge. For edges that represent roads in combination with other features, the MTFCC in the All Lines shapefile will reflect the road feature. Spatial Accuracy of Linear Features—The initial sources used to create the Census TIGER database, predecessor to the MAF/TIGER database, were the USGS 1:100,000-scale Digital Line Graph (DLG), U.S. Geological Survey (USGS) 1:24,000-scale quadrangles, the Census Bureau’s 1980 geographic base files (GBF/DIME-Files), and a variety of miscellaneous maps for selected areas outside the contiguous 48 states. The DLG coverage is extensive, albeit of variable currency, and comprises most of the rural, small city, and suburban area of the TIGER/Line Shapefiles. GBF/DIME-File coverage areas were updated through 1987 with the manual translation of features from the most recent aerial photography available to the Census Bureau. The Census Bureau added the enumerator updates compiled during the 1990 and Census 2000 census operations to the Census TIGER database. The updates came from map annotations made by enumerators as they attempted to locate living quarters by traversing every street feature in their assignment area. The Census Bureau digitized the enumerator updates directly into the Census TIGER database without geodetic controls or the use of aerial photography to confirm the features’ locational accuracy. The Census Bureau also made other corrections and updates to the Census TIGER database that were supplied by local participants in various Census Bureau programs. Local updates originated from map reviews by local government officials or their liaisons and local participants in Census Bureau programs. Maps were sent to participants for use in various census programs, and some maps were returned with update annotations and corrections. The Census Bureau generally added the updates to the Census TIGER database without extensive checks. Changes made by local officials do not have geodetic control. In order to maintain a current geographic database from which to extract the TIGER/Line Shapefiles, the Census Bureau uses various internal and external procedures to update the MAF/TIGER database. While it has made a reasonable and systematic attempt to gather the most recent information available about the features this file portrays, the Census Bureau cautions users that the files are no more complete than the source documents used in their compilation, the vintage of those source documents, and the translation of the information on those source documents. The Census Bureau began a multi-year project called the MAF/TIGER Accuracy Improvement Project (MTAIP) in 2002 to realign and update street features in our geographic database. The project realigned and updated the street features by county (or equivalent entity). The MTAIP was completed in 2008. State, tribal, county, and local governments submitted over 2,000 files, which the Census Bureau used as sources to perform the realignment and feature update work. In other counties, contractors performed the work using recently obtained imagery and/or driving the counties with GPS enhanced mapping equipment. Though all counties have been through the process, additional realignment and corrections will continue to take place for some counties. Approximately 1,000 counties in this release of the TIGER/Line Shapefile include some new features that are distorted. These features appear to be pushed away from their position to a point and return to their correct location. These problems are the result of efforts to automatically integrate new data with existing positionally accurate features. The Census Bureau is aware of these problems and has started processes to fix them. These features should be improved and will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years. As part of this project, the Census Bureau used Global Positioning System (GPS) coordinates at street centerline intersections to test and report the Circular Error 95 (CE95) horizontal spatial accuracy of source files that may be used to realign street features in the MAF/TIGER database and test and report the horizontal spatial accuracy of the street features in the TIGER/Line Shapefiles. The test compared a survey-grade GPS coordinate to its associated street centerline intersection in the MAF/TIGER database. The test is based upon an independent collection of GPS coordinates for a random sample of right-angle street intersections from a centerline file that meet certain criteria. The points are referred to as the sample points and were gathered through a private contractor. Since the collection method used survey- quality GPS-based field techniques, the resulting control points were considered "ground truth" against which the MAF/TIGER street centerline file intersection coordinates were compared. The test verified that the spatial accuracy of the street network met the Census Bureau's horizontal spatial accuracy standard of CE95 at 7.6 meters (about twenty-five feet) or better. This accuracy standard requires that 95 percent of the time, the distance between the sample control points coordinates and their corresponding street centerline file intersection points not exceed 7.6 meters, i.e., a file point will fall within a radius of 7.6 meters of its corresponding control point. The CE95 can be calculated from the mean and standard deviation by using the formula: mean of differences plus (2.65 times the standard deviation). The CE95 results reported for each file tested were determined using a spreadsheet with an embedded statistical formula. The use and applicability of the spreadsheet and its embedded formula have been verified by Census Bureau statisticians. The basis of the calculation is the use of the root mean square error (RSME). This is the method as stated in the U.S. Government's Federal Geographic Data Committee Standard FGDC-STD-007.3-1998, Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy. The results of using this measure of accuracy are in compliance with Federal Spatial Data Accuracy requirements. The Spatial Metadata Identifier (SMID) in the All Lines shapefile identifies the source of the coordinates for each edge and provides the link between the TIGER/Line Shapefiles and the source and horizontal spatial accuracy information. Refer to the metadata for each county or equivalent entity for information on the source for each edge and the horizontal spatial accuracy, where known. There are a few occurrences where the SMIDs are missing from some All Lines metadata files; hence the spatial metadata elements are also missing. The Census Bureau is aware of this problem and is in the process of fixing them for the next release of the TIGER/Line shapefiles. Please note that the horizontal spatial accuracy, where reported, refers only to those edges identified as matched to the source with that accuracy. It is not the spatial accuracy of the TIGER/Line Shapefile as a whole. Coordinates in the TIGER/Line Shapefiles have six decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest. The spatial accuracy varies with the source materials used. In areas where the Census Bureau has not realigned street features as part of MTAIP it, at best, meets the established National Map Accuracy standards (approximately + /– 50 meters or 167 feet) where 1:100,000-scale maps from the USGS were the source. The Census Bureau cannot specify the spatial accuracy of feature changes added by its field staff or local updates or of features derived from the GBF/DIME-Files or other map or digital sources. Thus, the level of spatial accuracy in the TIGER/Line Shapefiles may not be suitable for high-precision measurement applications such as engineering problems, property transfers, or other uses that might require highly accurate measurements of the earth’s surface. 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 Census Bureau specifically, as to the spatial or attribute accuracy of the data. Address Ranges—The Census Bureau identifies the most-inclusive address range as the address range that contains the largest number of possible house numbers (potential addresses) that is associated with the street name (FULLNAME) in the All Lines shapefile. The number of possible house numbers reflects the parity of the address range and the difference between from and to house numbers. The most- inclusive address ranges are not summary or generalized address ranges where data from several ranges have been collapsed, bridging gaps between address ranges. Please refer to the discussion of the Address Ranges relationship file later in this chapter for more information about additional address range information. 3.9.1.1 All Lines Shapefile Record Layout The shapefile name is: tl_2008__edges.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code TLID 10 Integer Permanent edge ID TFIDL 10 Integer Permanent face ID on the left of the edge TFIDR 10 Integer Permanent face ID on the right of the edge MTFCC 5 String MAF/TIGER feature class code of the primary feature for the edge FULLNAME 100 String Concatenation of expanded text for prefix qualifier, prefix direction, prefix type, base name, suffix type, suffix direction, and suffix qualifier (as available) with a space between each expanded text field SMID 22 String Spatial metadata identifier LFROMADD 12 String From house number associated with the most inclusive address range on the left side of the edge LTOADD 12 String To house number associated with the most inclusive address range on the left side of the edge RFROMADD 12 String From house number associated with the most inclusive address range on the right side of the edge RTOADD 12 String To house number associated with the most inclusive address range on the right side of the edge ZIPL 5 String ZIP code associated with the most inclusive address range on the left side ZIPR 5 String ZIP code associated with the most inclusive address range on the right side FEATCAT 1 String General feature classification category HYDROFLG 1 String Hydrography feature indicator RAILFLG 1 String Rail feature indicator ROADFLG 1 String Road feature indicator OLFFLG 1 String Other linear feature indicator PASSFLG 1 String Special passage flag DIVROAD 1 String Divided road flag EXTTYP 1 String Extension type TTYP 1 String Track type DECKEDROAD 1 String Decked road indicator ARTPATH 1 String Artificial path indicator PERSIST 1 String Hydrographic persistence flag GCSEFLG 1 String Short lines flag for geographic corridors OFFSETL 1 String Left offset flag OFFSETR 1 String Right offset flag TNIDF 10 Integer From TIGER node identifier TNIDT 10 Integer To TIGER node identifier 3.9.2 Area Hydrography Area hydrography features and attributes are available by county in the following shapefile: Area Hydrography Shapefile The Area Hydrography shapefile contains the geometry and attributes of both perennial and intermittent area hydrography features, including ponds, lakes, oceans, swamps, glaciers, and the area covered by large streams represented as double-line drainage. Single-line drainage water features can be found in the All Lines shapefile. Shorelines for area hydrography can be found in the All Lines shapefiles with MTFCC set to either “P0002” (shoreline of perennial water feature) or “P0003” (shoreline of intermittent water feature). 3.9.2.1 Area Hydrography Shapefile Record Layout The shapefile name is: tl_2008__areawater.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code ANSICODE 8 String Current official code for the water body for use by federal agencies for data transfer and dissemination, if applicable HYDROID 22 String Area hydrography identifier FULLNAME 100 String Concatenation of expanded text for prefix qualifier, prefix direction, prefix type, base name, suffix type, suffix direction, and suffix qualifier (as available) with a space between each expanded text field MTFCC 5 String MAF/TIGER feature class code 3.9.3 Landmarks (Area and Point) Landmark features and attributes are available by county in the following shapefiles: Area Landmark Shapefile Point Landmark Shapefile The Census Bureau includes landmarks in the MAF/TIGER database for locating special features and to help enumerators during field operations. Some of the more common landmark types include area landmarks such as airports, cemeteries, parks, and educational facilities and point landmarks such as schools and churches. Military installations are available in a separate, nation-based shapefile. Please see the section “Military Installations” in the “Nation-based Shapefiles” section earlier in this chapter. The Census Bureau added landmark features to the database on an as-needed basis and made no attempt to ensure that all instances of a particular feature were included. The absence of a landmark such as a hospital or prison does not mean that the living quarters associated with that landmark were excluded from the Census 2000 enumeration. The address list used for the census was maintained apart from the landmark data. Landmark and water features can overlap. The most common situation is a park or other special land-use feature that includes a lake or pond. In this case, the polygon covered by the lake or pond belongs to a water feature and a park landmark feature. Other kinds of landmarks can overlap as well. Area landmarks can contain point landmarks; these are not linked in the TIGER/Line Shapefiles. Landmarks may be identified by a MAF/TIGER feature class code only and may not have a name. Each area landmark has a unique AREAID value. 3.9.3.1 Area Landmark Shapefile Record Layout The shapefile name is: tl_2008__arealm.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code ANSICODE 8 String Current official code for the landmark for use by federal agencies for data transfer and dissemination AREAID 22 String Area landmark identifier FULLNAME 100 String Concatenation of expanded text for prefix qualifier, prefix direction, prefix type, base name, suffix type, suffix direction, and suffix qualifier with a space between each expanded text field MTFCC 5 String MAF/TIGER feature class code 3.9.3.2 Point Landmark Shapefile Record Layout The shapefile name is: tl_2008__pointlm.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code ANSICODE 8 String Current official code for the point landmark for use by federal agencies for data transfer and dissemination, if applicable POINTID 22 String Point landmark identifier FULLNAME 100 String Concatenation of expanded text for prefix type, base name, and suffix type with a space between each expanded text field MTFCC 5 String MAF/TIGER feature class code 3.9.4 Blocks Block geography and attributes are available by county in the following shapefiles: Current Block County-based Shapefile Census 2000 Block County-based Shapefile Alternately, blocks are also available in state-based shapefiles. Please see the section “Blocks” under “State-based Shapefiles” earlier in this chapter for information about blocks and additional shapefiles. 3.9.4.1 Current Block County-based Shapefile Record Layout The shapefile name is: tl_2008__tabblock.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code COUNTYNS 8 String Current county ANSI code STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TRACTCE00 6 String Census 2000 census tract code BLOCKCE00 4 String Census 2000 tabulation block number SUFFIX1CE 1 String Current census block suffix 1 BLKIDFP 16 String Current block identifier; a concatenation of Census 2000 state FIPS code, Census 2000 county FIPS code, Census 2000 census tract code, Census 2000 tabulation block number, and current block suffix 1. NAME 11 String Current tabulation block name; a concatenation of “Block”, the current tabulation block number, and the block suffix 1 MTFCC 5 String MAF/TIGER feature class code (G5040) UR 1 String Corrected Census 2000 urban/rural indicator UACE 5 String Corrected Census 2000 urban area code FUNCSTAT 1 String Current functional status 3.9.4.2 Census 2000 Block County-based Shapefile Record Layout The shapefile name is: tl_2008__tabblock00.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TRACTCE00 6 String Census 2000 census tract code BLOCKCE00 4 String Census 2000 tabulation block number BLKIDFP00 15 String Census 2000 block identifier; a concatenation of state FIPS code, county FIPS code, census tract code, and tabulation block number NAME00 10 String Census 2000 tabulation block name; a concatenation of “Block” and the Census 2000 tabulation block number MTFCC00 5 String MAF/TIGER feature class code (G5040) UR00 1 String Census 2000 urban/rural indicator UACE00 5 String Census 2000 urban area code FUNCSTAT00 1 String Census 2000 functional status 3.9.5 Block Groups Block group geography and attributes are available by county in the following shapefile: Census 2000 Block Group County-based Shapefile Alternately, block groups are also available in state-based shapefiles. Please see the section “Block Groups” under “State-based Shapefiles” earlier in this chapter for information about blocks and additional shapefiles. 3.9.5.1 Census 2000 Block Group County-based Shapefile Record Layout The shapefile name is: tl_2008__bg00.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TRACTCE00 6 String Census 2000 census tract code BLKGRPCE00 1 String Census 2000 block group number BKGPIDFP00 12 String Census 2000 census block group identifier; a concatenation of state FIPS code, county FIPS code, census tract code, and block group number NAMELSAD00 13 String Census 2000 translated legal/statistical area description and the block group number MTFCC00 5 String MAF/TIGER feature class code (G5030) FUNCSTAT00 1 String Census 2000 functional status 3.9.6 Census Tracts Census tract geography and attributes are available by county in the following shapefile: Census 2000 Census Tract County-based Shapefile Alternately, census tracts are also available in state-based shapefiles. Please see the section “Census Tracts” under “State-based Shapefiles” earlier in this chapter for information about census tracts and additional shapefiles. 3.9.6.1 Census 2000 Census Tract County-based Shapefile Record Layout The shapefile name is: tl_2008__tract00.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TRACTCE00 6 String Census 2000 census tract code CTIDFP00 11 String Census 2000 census tract identifier; a concatenation of state FIPS code, county FIPS code, and census tract code NAME00 7 String Census 2000 census tract name, including the decimal point and decimal digits if a non-zero census tract suffix exists, excluding trailing zeros unless the zeros are part of a non-zero census tract suffix, and excluding any leading zeros NAMELSAD00 20 String Census 2000 translated legal/statistical area description and the census tract name MTFCC00 5 String MAF/TIGER feature class code (G5020) FUNCSTAT00 1 String Census 2000 functional status 3.9.7 County Subdivisions County subdivision geography and attributes are available by county in the following shapefiles: Current County Subdivision County-based Shapefile Census 2000 County Subdivision County-based Shapefile Alternately, county subdivisions are also available in state-based shapefiles. Please see the section “County Subdivisions” under “State-based Shapefiles” earlier in this chapter for information about county subdivisions and additional shapefiles. 3.9.7.1 Current County Subdivision County-based Shapefile Record Layout The shapefile name is: tl_2008__cousub.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code COUSUBFP 5 String Current county subdivision FIPS 55 code COUSUBNS 8 String Current county subdivision ANSI code COSBIDFP 10 String Current county subdivision identifier; a concatenation of current state FIPS code, county FIPS code, and county subdivision FIPS 55 code NAME 100 String Current county subdivision name NAMELSAD 100 String Current name and the translated legal/statistical area description for county subdivision LSAD 2 String Current legal/statistical area description code for county subdivision CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code (G4040) CNECTAFP 3 String Current combined New England city and town area code NECTAFP 5 String Current New England city and town area code NCTADVFP 5 String Current New England city and town area division code FUNCSTAT 1 String Current functional status 3.9.7.2 Census 2000 County Subdivision County-based Shapefile Record Layout The shapefile name is: tl_2008__cousub00.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code COUSUBFP00 5 String Census 2000 county subdivision FIPS 55 code COSBIDFP00 10 String Census 2000 county subdivision identifier; a concatenation of Census 2000 state FIPS code, county FIPS code, and county subdivision FIPS 55 code NAME00 100 String Census 2000 county subdivision name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for county subdivision LSAD00 2 String Census 2000 legal/statistical area description code for county subdivision CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code (G4040) UR00 1 String Census 2000 urban/rural indicator FUNCSTAT00 1 String Census 2000 functional status 3.9.8 Subbarrios (Sub-Minor Civil Divisions) Subbarrio geography and attributes are available by county (municipio) in the following shapefiles: Current Subbarrio Shapefile Census 2000 Subbarrio Shapefile Subbarrio—Subbarrios are legally defined subdivisions of the minor civil division barrios-pueblo and barrios in Puerto Rico. The TIGER/Line Shapefiles contain the 5- character FIPS 55 code for subbarrios. 3.9.8.1 Current Subbarrio Shapefile Record Layout The shapefile name is: tl_2008__submcd.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code COUSUBFP 5 String Current county subdivision FIPS 55 code SUBMCDFP 5 String Current subbarrio FIPS 55 code SUBMCDNS 8 String Current subbarrio ANSI code SMCDIDFP 15 String Current subbarrio identifier; a concatenation of current state FIPS code, county FIPS code, county subdivision FIPS 55 code, and subbarrio FIPS 55 code NAME 100 String Current subbarrio name NAMELSAD 100 String Current name and the translated legal/statistical area description for subbarrio LSAD 2 String Current legal/statistical area description code for subbarrio CLASSFP 2 String Current FIPS 55 class code MTFCC 5 String MAF/TIGER feature class code (G4060) FUNCSTAT 1 String Current functional status 3.9.8.2 Census 2000 Subbarrio Shapefile Record Layout The shapefile name is: tl_2008__submcd00.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code COUSUBFP00 5 String Census 2000 county subdivision FIPS 55 code SUBMCDFP00 5 String Census 2000 subbarrio FIPS 55 code SMCDIDFP00 15 String Census 2000 subbarrio identifier; a concatenation of Census 2000 state FIPS code, county FIPS code, county subdivision FIPS 55 code, and subbarrio FIPS 55 code NAME00 100 String Census 2000 subbarrio name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for subbarrio LSAD00 2 String Census 2000 legal/statistical area description code for subbarrio CLASSFP00 2 String Census 2000 FIPS 55 class code MTFCC00 5 String MAF/TIGER feature class code (G4060) UR00 1 String Census 2000 urban/rural indicator FUNCSTAT00 1 String Census 2000 functional status 3.9.9 Traffic Analysis Zones Traffic analysis zone geography and attributes are available by county in the following shapefile: Census 2000 Traffic Analysis Zone (TAZ) Shapefile 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 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 fifty states and the District of Columbia. No TAZs are defined in Puerto Rico or the Island Areas. 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 3.9.9.1 Census 2000 Traffic Analysis Zone (TAZ) Shapefile Record Layout The shapefile name is: tl_2008__taz00.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TAZCE00 6 String Census 2000 traffic analysis zone code TAZIDFP00 11 String Census 2000 traffic analysis zone identifier; a concatenation of Census 2000 state FIPS code, county FIPS code, and traffic analysis zone code MTFCC00 5 String MAF/TIGER feature class code FUNCSTAT00 1 String Census 2000 functional status 3.9.10 Voting Districts Voting district geography and attributes are available by county in the following shapefiles: Census 2000 Voting District (VTD) Shapefile Voting Districts (VTDs)—“Voting district” 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 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 a portion of counties (usually bodies of water) for which no VTDs were identified. No voting district shapefile exists for states or counties that did not participate in Phase 2 (the Voting District Project) of the Census 2000 Redistricting Data Program. Because the 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 Census Bureau identified the VTDs that represent an actual voting district with an “A” in the voting district indicator field (VTDI00). Where a participating state indicated that the VTD has been modified to follow visible block boundaries, the VTD is a pseudo-VTD, and the VTDI00 field contains a “P”. Where a participating state did not indicate to the Census Bureau whether or not the VTD followed the actual boundaries of the VTD or is a pseudo-VTD, the VTDI00 field is blank. The following states did not participate in Phase 2 (the Voting District Project) of the Census 2000 Redistricting Data Program and no VTD shapefile exists for these states: California Florida Kentucky Montana Of the participating states (or 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 Arizona has partial coverage for Phase 2 (the Voting District Project) of the Census 2000 Redistricting Data Program, as it did not submit VTDs in all counties. The Census 2000 Redistricting Data Program was not offered to American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, or the U.S. Virgin Islands. 3.9.10.1 Census 2000 Voting District (VTD) Shapefile Record Layout The shapefile name is: tl_2008__vtd00.shp The shapefile is county-based. The following is the shapefile’s attribute table layout: Field Length Type Description STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code VTDST00 6 String Census 2000 voting district code VTDIDFP00 11 String Census 2000 voting district identifier; a concatenation of Census 2000 state FIPS code, county FIPS code, and voting district code VTDI00 1 String Census 2000 voting district indicator NAME00 100 String Census 2000 voting district name NAMELSAD00 100 String Census 2000 name and the translated legal/statistical area description for voting district LSAD00 2 String Census 2000 legal/statistical area description code for voting district MTFCC00 5 String MAF/TIGER feature class code (G5240) FUNCSTAT00 1 String Census 2000 functional status 3.10 County-Based Relationship Files The TIGER/Line relationship files are extracts of selected geographic information from the MAF/TIGER database. Each TIGER/Line relationship file is designed to stand alone as an independent data set or can be used jointly with the shapefiles. 3.10.1 Address Range-Feature Name Relationships Address range to feature name relationship information is available by county in the following relationship file: Address Range-Feature Name Relationship File The Address Range-Feature Name relationship table contains a record for each address range-linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can have multiple feature names). The address range is identified by the ARID attribute, which can be used to link to the Address Ranges relationship table. The linear feature name is identified by the LINEARID attribute that relates the address range back to the featnames.dbf table. 3.10.1.1 Address Range-Feature Name Relationship File Record Layout The relationship file name is: tl_2008__addrfn.dbf The relationship file is county-based. The following is the relationship file’s attribute table layout: Field Length Type Description ARID 22 String Address range identifier LINEARID 22 String Linear feature identifier 3.10.2 Address Ranges Address range information is available by county in the following relationship file: Address Ranges Relationship File The Address Ranges relationship table contains the attributes of each address range. Each address range has a unique ARID value. The edge to which an address range applies can be determined by linking to the All Lines shapefile on the TLID attribute. Multiple address ranges can apply to the same edge (an edge can have multiple address ranges). Note that the most inclusive address ranges associated with each side of a street edge will also appear in the All Lines shapefile. The TIGER/Line Shapefiles contain potential address ranges, not individual addresses. The term “address range” refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between, all along an edge side relative to the direction in which the edge is coded. The address ranges in the TIGER/Line Shapefiles are potential ranges that include the full range of possible structure numbers even though the actual structures might not exist. The address numbers used to create the address ranges are commonly known as house number-street name style addresses (or city-style addresses). A house number-street name style address minimally consists of a structure number, street name, and a 5- digit ZIP Code; for example, 213 Main St 90210. In the TIGER/Line Shapefiles, the ZIP Codes usually appear only on those edges that have address ranges identified. The ZIP Code is an attribute of the address ranges. The Address Ranges relationship file has a five-character ZIP Code field containing a numeric code with leading zeros. Each address range belonging to an edge can have a different ZIP Code. Where ZIP Code boundaries follow a street, the edge may have different left- and right-side ZIP Codes, or different ZIP Codes along its length. Nearly all address ranges will have a ZIP Code; there are a few instances where the ZIP Code is not known and the ZIP Code will have a null/blank value. The U.S. Postal Service offers an Address Information System (AIS) Viewer on compact disc, which can be used to get a list of valid 5-digit ZIP codes, and an on- line ZIP Code lookup search engine for addresses, as well as other data related to administrative postal areas (see www.usps.com for online information). The 2008 TIGER/Line Shapefiles may not contain all delivery ZIP Codes and may contain some non-delivery ZIP Codes. The distribution of ZIP Codes in the TIGER/Line Shapefiles may not reflect the exact USPS ZIP Code service area. Likewise, the address range ZIP Codes may not match the ZCTA for the area. An address range also may have the full 9-digit ZIP Code that includes the USPS’s 4- digit ZIP+4® Add-On code. In the past, the Census Bureau has added the Postal Add- On code to the MAF/TIGER database using an automated match to the USPS’s ZIP+4 file. At present, these codes are not available in this release of the TIGER/Line Shapefiles The ZIP+4 codes in the TIGER/Line Shapefiles are the street-level codes the USPS assigned to address ranges. The USPS may assign more specific codes to companies and buildings, and to apartments, floors, or suites within buildings. Some address coding software that uses the USPS's ZIP+4 file may provide the more specific codes, however, the TIGER/Line Shapefiles only will contain the more general street level codes. Usually, the ZIP+4 Add-On code is not required to uniquely identify an address range. There are a few situations where a street name and address range legitimately appear more than once in the same 5-digit ZIP Code. Usually the USPS distinguishes these duplicates by using different postal station names. However, the Postal Add-On code provides the ability to uniquely identify these cases. Puerto Rico is a special case because many addresses were uniquely assigned within an urbanizacion (a community or development) and could duplicate another address in a different urbanizacion with the same 5-digit ZIP Code. To resolve this problem, the USPS added an additional line to the address to identify the urbanizacion. The 9-digit ZIP Code also may serve to uniquely identify these address ranges. The MAF/TIGER database does not yet contain all of these 9-digit ZIP Codes. Some basic characteristics of address ranges are as follows: The TIGER/Line Shapefiles generally contain only those house number-street name style address ranges used for mail delivery. They do not show rural route and post office box addresses. They may contain structure numbers assigned in select areas for use by local emergency services, but not for mail delivery. The TIGER/Line Shapefiles do include address ranges and ZIP Codes in some small places where the USPS provides only post office box service, not street delivery. These address ranges represent the structure numbers collected during the 2000 census field operations, supplemented with addresses provided through local participant programs. These structure-number addresses may have ZIP Codes associated only with post office box addresses. The USPS does not recognize these street addresses as valid mailing addresses and does not assign a ZIP+4 Code to them or include them in the ZIP+4 file. The address ranges may be used to geocode a structure to the census block, but care should be used because of potential conflicts with similar or duplicate mailing street addresses. Gaps may exist between multiple ranges for a single edge. A gap may be significant, because any numbers missing from one edge may actually appear on another edge. This situation occurs in cases where there are address anomalies such as out-of-parity or out-of-sequence addresses. The Census Bureau does not provide any single address-address ranges in the TIGER/Line Shapefiles, including out-of-parity and out-of-sequence address ranges that cover a single house number. For example, address 709 Main Street is in the middle of the even-side of the 700 block of Main Street and will be suppressed because it is a single address-address range. The following addresses ranges for the 700 block of Main Street will appear in the TIGER/Line Shapefiles: 700-798 Main Street, 701-707 Main Street, and 711- 799 Main Street. Based on the information provided, data users cannot tell where 709 Main Street is located. Suppression of single address-address ranges is to protect the confidentiality of individual addresses collected through Census 2000 census field operations as specified by Title 13 of the U.S. Code. Address ranges can include numbers with alphabetic characters. These characters help uniquely identify addresses within a county. For instance, certain unincorporated areas of Genesee County, Michigan add a letter G prefix to the address number. The characters are consistently placed within the address range field; for example, the letter G maintains a consistent column placement in the range G1 to G99. Some address systems use a hyphen to separate avenue numbers, private road designators, and grid cell numbers from the structure numbers; for example, 10- 01 Reynolds St. uses a hyphen to separate the avenue number from the structure number. Depending on the locality, the hyphen may be unnecessary for address matching. Address ranges exist only for street features, and in some cases, geographic corridor and geographic offset boundary features adjacent to street features. Address ranges (consisting of a unique combination of structure number, ZIP Code, feature name, feature type, and directional) should not overlap; addresses should belong to only one address range. The Census Bureau edits the address ranges to locate possible overlaps, but cannot guarantee that all possible overlap situations have been identified and resolved. Address ranges in the TIGER/Line Shapefiles may be associated with one or more of the street names that belong to an edge. Caution: Address range overlap conflicts may occur if the address ranges are associated with some street names or route numbers that were not intended for use in locating addresses. A route number may traverse several streets with different common names but similar house numbers that are used for mail delivery. Imputed Address Ranges—Imputed address ranges occur during the process of updating the MAF/TIGER database when a new edge intersects an existing edge with address ranges. The intersection splits the existing edge and produces two new edges connected by a new node located at the intersection point. The update program divides the old address ranges among the two new edges and imputes the address range ends at the new node. The impute process allocates either all or part of each original address range to each of the new edges in proportion to their lengths. For each side of the original edge, the process considers all address ranges appearing on each side and determines the overall low and high addresses. The process assumes the addresses are evenly distributed along the length of the edge, and applies the proportion of edge lengths to the overall address range to calculate a split point address for each side. Address ranges that fall entirely above or below the split point address are moved intact to one of the new edges. The process divides any address ranges that contain the split point address and allocates each part to one of the new edges. The new address range ends created from the split are imputed values and have the from address range type (FROMTYP) or to address range type (TOTYP) set to imputed value. Some intermediate address range ends also may carry the impute flag. These address range ends fall between the overall high and low address for edge sides that have more than one address range. In current practice, the imputation process will assign the entire address range to one of the edges if the other is very small and would receive only a single address using the proportional division of address ranges. Geocoding—To get the best match results, the Census Bureau advises data users to use all of the available address ranges to geo-reference/geocode addresses. A single pair of left- and right-side address ranges may not always provide complete address range coverage. The address ranges in the TIGER/Line Shapefiles may be separate because of ZIP Code differences or to establish gaps created by out-of-sequence addresses located elsewhere. Some address ranges may include embedded alphanumeric characters or hyphens that make them distinct from the other address ranges. Limitations—Users of the address ranges in the TIGER/Line Shapefiles should be aware that address range overlaps, gaps, odd/even reversals, and low-high orientation reversals may exist in the data. With the exception of overlaps, these may be valid. While the Census Bureau continues to edit for and correct for data errors, it is possible that some still exist. 3.10.2.1 Address Ranges Relationship File Record Layout The relationship file name is: tl_2008__addr.dbf The relationship file is county-based. The following is the relationship file’s attribute table layout: Field Length Type Description TLID 10 Integer Permanent edge ID FROMHN 12 String From house number TOHN 12 String To house number SIDE 1 String Side indicator flag ZIP 5 String 5-digit ZIP code PLUS4 4 String ZIP +4 code FROMTYP 1 String From address range end type TOTYP 1 String To address range end type FROMARMID 6 Integer From house number source metadata ID number TOARMID 6 Integer To house number source metadata ID number ARID 22 String Address range identifier MTFCC 5 String MAF/TIGER feature class code 3.10.3 Feature Names Feature name information is available by county in the following relationship file: Feature Names Relationship File The Feature Names relationship file contains a record for each feature name-edge combination, and includes the feature name attributes. The edge to which a Feature Names relationship table record applies can be determined by linking to the All Lines shapefile on the TLID attribute. Multiple Feature Names relationship table records can link to the same edge. For example, a road edge could link to U.S. Hwy 22 and Rathburn Road. The linear feature to which the feature name applies is identified by the LINEARID attribute. Multiple feature names may exist for the same edge (linear features are not included in the data set, but could be constructed using the All Lines shapefile and the relationship tables). Note that the MTFCC in this relationship file refers to the specific MAF/TIGER feature class code associated with this feature name. If the edge is both a road and a rail feature, the name associated with the rail feature will carry a rail feature MTFCC. If there are any address ranges on the edge, they apply only to the designated street features. Appendices B, C, and D of this document include additional information about feature name components. 3.10.3.1 Feature Names Relationship File Record Layout The relationship file name is: tl_2008__featnames.dbf The relationship file is county-based. The following is the relationship file’s attribute table layout: Field Length Type Description TLID 10 Integer Permanent edge ID FULLNAME 100 String Concatenation of expanded text for prefix qualifier, prefix direction, prefix type, base name, suffix type, suffix direction, and suffix qualifier (as available) with a space between each expanded text field NAME 100 String Base name portion of the standardized name PREDIRABRV 15 String Prefix direction description component of the feature name PRETYPABRV 50 String Prefix type description component of the feature name PREQUALABR 15 String Prefix qualifier description component of the feature name SUFDIRABRV 15 String Suffix direction description component of the feature name SUFTYPABRV 50 String Suffix type description component of the feature name SUFQUALABR 15 String Suffix qualifier description component of the feature name PREDIR 2 String Prefix direction code component of the feature name PRETYP 3 String Prefix type code description component of the feature name PREQUAL 2 String Prefix qualifier code component of the feature name SUFDIR 2 String Suffix direction code component of the feature name SUFTYP 3 String Suffix type code description component of the feature name SUFQUAL 2 String Suffix qualifier code component of the feature name LINEARID 22 String Linear feature identifier MTFCC 5 String MAF/TIGER feature class code PAFLAG 1 String Primary/alternate flag 3.10.4 Other Identifiers Other identifier information is available by county in the following relationship file: Other Identifiers Relationship File The Other Identifiers relationship table contains external identifier codes, such as National Hydrographic Dataset (NHD) codes and individual county identifiers. The edge to which an Other Identifiers relationship table record applies can be determined by linking to the All Lines shapefile on the TLID attribute. Not every TLID has an external identifier associated with it, and some TLIDs may have more than one. 3.10.4.1 Other Identifiers Relationship File Record Layout The relationship file name is: tl_2008__otherid.dbf The relationship file is county-based. The following is the relationship file’s attribute table layout: Field Length Type Description TLID 10 Integer Permanent edge ID EXTID 33 String External identifier EXIDTYP 1 String External identifier type 3.10.5 Topological Faces (2-Cells With All Geocodes) Topological face information is available by county in the following relationship file: Topological Faces (2-Cells With All Geocodes) Relationship File The Topological Faces relationship table contains the attributes of each topological primitive face. Each face has a unique TFID value. The face geometries can be built from the All Lines shapefile using the edges’ left and right face relationships. The geometries of each geographic entity can then be built by dissolving the face geometries on the appropriate attribute(s) in the Topological Faces relationship table. 3.10.5.1 Topological Faces (2-Cells With All Geocodes) Relationship File Record Layout The relationship file name is: tl_2008__faces.dbf The relationship file is county-based. The following is the relationship file’s attribute table layout: Field Length Type Description TFID 10 Integer Permanent face ID STATEFP00 2 String Census 2000 state FIPS code COUNTYFP00 3 String Census 2000 county FIPS code TRACTCE00 6 String Census 2000 census tract code BLKGRPCE00 1 String Census 2000 block group number BLOCKCE00 4 String Census 2000 tabulation block number SUFFIX1CE 1 String Current census block suffix 1 COUSUBFP00 5 String Census 2000 county subdivision FIPS 55 code SUBMCDFP00 5 String Census 2000 subbarrio FIPS 55 code in Puerto Rico CONCTYFP00 5 String Census 2000 consolidated city FIPS 55 code PLACEFP00 5 String Census 2000 place FIPS 55 code AIANNHCE00 4 String Census 2000 American Indian/Alaska Native/Native Hawaiian area census code COMPTYP00 1 String Census 2000 American Indian/Alaska Native/Native Hawaiian area reservation/statistical area or off-reservation trust land indicator TRSUBCE00 3 String Census 2000 tribal subdivision code TTRACTCE00 6 String Census 2000 tribal census tract number ANRCFP00 5 String Census 2000 Alaska Native Regional Corporation FIPS code ELSDLEA00 5 String Census 2000 elementary school district local education agency code SCSDLEA00 5 String Census 2000 secondary school district local education agency code UNSDLEA00 5 String Census 2000 unified school district local education agency code UACE00 5 String Census 2000 urban area code UACE 5 String Corrected Census 2000 urban area code SLDUST00 3 String Census 2000 state legislative district upper chamber code SLDLST00 3 String Census 2000 state legislative district lower chamber code VTDST00 6 String Census 2000 voting district code TAZCE00 6 String Census 2000 traffic analysis zone code UGACE00 5 String Census 2000 urban growth area code PUMA1CE00 5 String Census 2000 1-percent public use microdata area code PUMA5CE00 5 String Census 2000 5- or 10-percent public use microdata area code ZCTA5CE00 5 String Census 2000 5-digit ZIP Code Tabulation Area code ZCTA3CE00 3 String Census 2000 3-digit ZIP Code Tabulation Area code STATEFP 2 String Current state FIPS code COUNTYFP 3 String Current county FIPS code COUSUBFP 5 String Current county subdivision FIPS 55 code SUBMCDFP 5 String Current subbarrio FIPS 55 code in Puerto Rico CONCTYFP 5 String Current consolidated city FIPS 55 code PLACEFP 5 String Current place FIPS 55 code AIANNHCE 4 String Current American Indian/Alaska Native/Native Hawaiian area census code COMPTYP 1 String Current American Indian/Alaska Native/Native Hawaiian area reservation/statistical area or off-reservation trust land indicator ANRCFP 5 String Current Alaska Native Regional Corporation FIPS code TRSUBCE 3 String Current tribal subdivision code CD108FP 2 String 108th congressional district code CD110FP 2 String 110th congressional district code SLDUST 3 String Current state legislative district upper chamber code SLDLST 3 String Current state legislative district lower chamber code CSAFP 3 String Current combined statistical area code CBSAFP 5 String Current metropolitan statistical area/micropolitan statistical area code METDIVFP 5 String Current metropolitan division code CNECTAFP 3 String Current combined New England city and town area code (New England states only) NECTAFP 5 String Current New England city and town area code (New England states only) NCTADVFP 5 String Current New England city and town area division code (New England states only) ELSDLEA 5 String Current elementary school district local education agency code SCSDLEA 5 String Current secondary school district local education agency code UNSDLEA 5 String Current unified school district local education agency code UGACE 5 String Current urban growth area code ZCTA5CE 5 String Current 5-digit ZIP Code Tabulation Area code ZCTA3CE 3 String Current 3-digit ZIP Code Tabulation Area code STATEFPEC 2 String 2007 Economic Census state FIPS code COUNTYFPEC 3 String 2007 Economic Census county FIPS code CONCTYFPEC 5 String 2007 Economic Census consolidated city FIPS 55 code PLACEFPEC 5 String 2007 Economic Census FIPS 55 economic place code COMRGCEEC 1 String 2007 Economic Census commercial region code LWFLAG 1 String Land/water flag OFFSET 1 String Geographic corridor/offset flag 3.10.6 Topological Faces-Area Landmark Relationships Topological faces to area landmark relationship information is available by county in the following relationship file: Topological Faces-Area Landmark Relationship File The Topological Faces-Area Landmark relationship table contains a record for each face-area landmark relationship. The face to which a Topological Faces-Area Landmark relationship table record applies can be determined by linking to the Topological Faces relationship table on the TFID attribute. The area landmark to which a Topological Faces-Area Landmark relationship table record applies can de determined by linking to the Area Landmark shapefile on the AREAID attribute. A face may be part of multiple area landmarks. An area landmark may consist of multiple faces. 3.10.6.1 Topological Faces-Area Landmark Relationship File Record Layout The relationship file name is: tl_2008__facesal.dbf The relationship file is county-based. The following is the relationship file’s attribute table layout: Field Length Type Description TFID 10 Integer Permanent face ID AREAID 22 String Area landmark identifier 3.10.7 Topological Faces-Area Hydrography Relationships Topological faces to area hydrography relationship information is available in the following relationship file: Topological Faces-Area Hydrography Relationship File The Topological Faces-Area Hydrography relationship table contains a record for each face-area hydrography feature relationship. The face to which a Topological Faces-Area Hydrography relationship table record applies can be determined by linking to the Topological Faces table on the TFID attribute. The area hydrography feature to which a Topological Faces-Area Hydrography relationship table record applies can be determined by linking to the Area Hydrography shapefile on the HYDROID attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces. 3.10.7.1 Topological Faces-Area Hydrography Relationship File Record Layout The relationship file name is: tl_2008__facesah.dbf The relationship file is county-based. The following is the relationship file’s attribute table layout: Field Length Type Description TFID 10 Integer Permanent face ID HYDROID 22 String Area hydrography identifier