The following sections describe the geographic entity type displayed in each shapefile or relationship file, as well as the

record layout for each file. Each entity type is listed in alphabetical order. The description of the entity type is preceded by a listing of all available shapefiles, including vintage and geographic level (state, county and national).

5.1.1

Alaska Native Regional Corporations (ANRCs)

Alaska Native Regional Corporations are available by state for Alaska in the following shapefile: Alaska Native Regional Corporation (ANRC) Shapefile (Current) A corporation created pursuant to the Alaska Native Claims Settlement Act (Pub. L. 92 203, 85 Stat. 688 (1971); 43 U.S.C. 1602 et seq. (2000) as a Regional Corporation and organized under the laws of the State of Alaska to conduct both the for-profit and non-profit affairs of Alaska Natives within a defined region of Alaska. For the Census Bureau, ANRCs are considered legal geographic entities. Twelve ANRCs cover the entire State of Alaska except for the area within the Annette Island Reserve (an AIR under the governmental authority of the Metlakatla Indian Community). There is a thirteenth ANRC that represents the eligible Alaska Natives living outside of Alaska that are not members of any of the twelve ANRCs within the State of Alaska. The Census Bureau does not provide data for this thirteenth ANRC because it has no defined geographic extent and thus it does not appear in the TIGER/Line Shapefiles. The Census Bureau offers representatives of the twelve non-profit ANRCs the opportunity to review and update the ANRC boundaries. ANRCs are represented by a five-digit FIPS code unique within Alaska and a nationally unique eight-digit ANSI code. 5.1.1.1Alaska Native Regional Corporation (ANRC) Shapefile Record Layout (Current) File Name: tl_2012_02_anrc.shp STATEFP ANRCFP ANRCNS GEOID NAME NAMELSAD LSAD CLASSFP MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 5 8 7 100 100 2 2 5 1 14 14 11 12 String String String String String String String String String String Number Number String String Current state FIPS code Current Alaska Native Regional Corporation FIPS code Current Alaska Native Regional Corporation ANSI code Alaska Native Regional Corporation identifier; a concatenation of Current state FIPS code and Alaska Native Regional Corporation code Current Alaska Native Regional Corporation name Current name and the translated legal/statistical area description for Alaska Native Regional Corporation Current legal/statistical area description code for Alaska Native Regional Corporation Current FIPS class code MAF/TIGER feature class code (G2200) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5-15

5.1.2

American Indian / Alaska Native / Native Hawaiian (AIANNH) Areas

American Indian, Alaska Native, and Native Hawaiian Area geography and attributes are available in the following shapefile: American Indian / Alaska Native / Native Hawaiian (AIANNH) Area National Shapefile (Current) 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). American Indian tribal subdivisions and Alaska Native Regional Corporations (ANRCs) are additional types of legal entities, but are displayed in separate shapefiles discussed 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, American Indian, Alaska Native, and Native Hawaiian areas cannot overlap another tribal entity. An exception is made 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 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 (AIANNH) Area shapefiles contain a unique polygon record for each American Indian reservation or off-reservation trust land, Hawaiian home land, Alaska Native Village statistical area, and American Indian statistical geographic entity. For example, the Fort Peck Indian Reservation will have two records: one for the reservation portion and another for the offreservation trust land portion. Entities with only a single component will contain a single record. There is always a single record for a Hawaiian home land, Alaska Native Village statistical area, American Indian statistical geographic entity, reservations without any associated off-reservation trust land, and entities that consist only of off-reservation trust land. Legal Entities American Indian ReservationsFederal (federal AIRs) are areas that have been set aside by the United States for the use of federally recognized tribes. The exterior boundaries of federal AIRs are more particularly defined in tribal treaties, agreements, executive orders, federal statutes, secretarial orders, and/or judicial determinations. The Census Bureau recognizes federal reservations as territory over which American Indian tribes have 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, or other descriptions. The Bureau of Indian Affairs within the U.S. Department of Interior maintains a list of federally recognized tribal governments that is published regularly in the Federal Register. The Census Bureau contacts representatives of these federally recognized American Indian tribal governments to identify the boundaries for federal reservations. Federal reservations may cross state, county, county subdivision, and/or place boundaries. To obtain the list of federally recognized tribal governments and for more detailed information regarding tribal governments, please visit the Bureau of Indian Affairs website at: [Link] Each federal AIR and reservation equivalent joint-use area is assigned a nationally unique four-digit census code ranging from 0001 through 4999. These census codes are assigned in alphabetical order of AIR names nationwide, except that joint-use areas appear at the end of the code range (4900 to 4999). Each federal AIR and reservation equivalent joint-use area also is assigned a five-digit FIPS code; because FIPS codes are assigned in alphabetical sequence within each state, the FIPS code is usually different in each state for reservations that include territory in more than one state. Federal AIRs and reservation equivalent joint-use areas are also assigned a nationally unique eight-digit ANSI code. American Indian ReservationsState (state AIRs) are established by some state governments for tribes recognized by the state. A governor-appointed state liaison provides the names and boundaries for staterecognized American Indian reservations to the Census Bureau. State reservations may cross county, county subdivision, and / or place boundaries.

5-16

Each state American Indian reservation is assigned a nationally unique four-digit census code ranging from 9000 through 9499. Each state AIR also is assigned a five-digit FIPS code and a nationally unique eightdigit ANSI code. 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 tribal member (individual trust land or allotment). 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 (onreservation) or off an American Indian reservation (off-reservation). The Census Bureau recognizes and tabulates data for reservations and off-reservation trust lands (ORTLs) because American Indian tribes have governmental authority over these lands. Tribal governmental authority generally is not attached to lands located off the reservation until the lands are placed in trust status. In Census Bureau data tabulations, ORTLs are always associated with a specific federally recognized reservation and/or tribal government. A tribal government appointed liaison provides the name and boundaries of their ORTLs. The Census Bureau does not identify on-reservation trust land, fee land (or land in fee simple status), or restricted fee lands as specific geographic categories and they are not identified as such 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. An HHL 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, may lease to one or more Native Hawaiians for residential, agricultural, commercial, industrial, pastoral, and/or 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. Being lands held in trust, Hawaiian home lands are treated as equivalent to off-reservation trust land areas with an AIANNH area trust land indicator coded as T. Each Hawaiian home land area is assigned a nationally unique four-digit census code ranging from 5000 through 5499 based on the alphabetical sequence of each HHL name. Each Hawaiian home land is also assigned a five-digit FIPS code in alphabetical order within the State of Hawaii and a nationally unique eight-digit ANSI code. 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 federally recognized 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. Joint-use areas now only apply to overlapping federally recognized American Indian reservations and/or off-reservation trust lands, and overlapping Oklahoma tribal statistical areas. No other AIANNH area types have joint-use areas. Each is assigned a nationally unique four-digit census code ranging from 4800 through 4999, a five-digit FIPS code, and a nationally unique eight-digit ANSI code. Statistical Entities Alaska Native Village Statistical Areas (ANVSAs) are a statistical geographic entity that represents the residences, permanent and/or seasonal, for Alaska Natives who are members of or are primarily receiving governmental services from the defining Alaska Native village (ANV) and that are located within the region and vicinity of the ANVs historic and/or traditional location. ANVSAs are intended to represent the relatively densely settled portion of each ANV and ideally should include only an area where Alaska Natives, especially members of the defining ANV, represent a significant proportion of the population during at least one season of the year (at least three consecutive months). ANVSAs also ideally should not contain large areas that are primarily unpopulated or do not include concentrations of Alaska Natives, especially members of the defining ANV. 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 non-profit Alaska Native Regional Corporation (ANRC) in which the ANV is located. In some cases, if neither the ANV nor ANRC official chose to participate in the delineation process, the Census Bureau reviewed and delineated the ANVSA. An ANVSA may not overlap the boundary of another ANVSA or an American Indian reservation. 5-17

Each ANVSA is assigned a nationally unique four-digit census code ranging from 6000 to 7999 based on the alphabetical sequence of each ANVSAs name. Each ANVSA is also assigned a five-digit FIPS code in alphabetical order within the State of Alaska and a nationally unique eight-digit ANSI code. 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. Statistical joint-use areas only apply to overlapping Oklahoma tribal statistical areas. Oklahoma Tribal Statistical Areas (OTSAs) are statistical entities identified and delineated by the Census Bureau in consultation with federally recognized American Indian tribes that formerly had a reservation in Oklahoma. The boundary of an OTSA is generally that of the former reservation in Oklahoma, except where modified by agreements with neighboring federally recognized tribes that are eligible to delineate an OTSA. Tribal subdivisions can exist within the statistical Oklahoma tribal statistical areas. Each OTSA is assigned a nationally unique four-digit census code ranging from 5500 through 5999 based on the alphabetical sequence of each OTSAs name, except that the joint -use areas appear at the end of the code range. Each OTSA also is assigned a five-digit FIPS code in alphabetical order within Oklahoma and a nationally unique eight-digit ANSI code. State Designated Tribal Statistical Areas (SDTSAs) are statistical entities for state-recognized American Indian tribes that do not have a state-recognized 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 for Census 2000 these areas were termed State Designated American Indian Statistical Areas (SDAISAs); the term was changed to bring consistency to tribal statistical area terms. Each SDTSA is assigned a nationally unique four-digit census code ranging from 9500 through 9998 in alphabetical sequence of SDTSA names nationwide. Each SDTSA also is assigned a five-digit FIPS code in alphabetical order within state and a nationally unique eight-digit ANSI code. 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 reservation or offreservation trust land. A TDSA is intended to be comparable to the AIRs within the same state and/or region, especially those for tribes that are of similar size. A TDSA generally encompasses a compact and contiguous area that contains a concentration of individuals who identify with the delineating 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 any other AIANNH areas. Each TDSA is assigned a nationally unique four-digit census code ranging from 8000 through 8999 in alphabetical sequence of TDSA names nationwide. Each TDSA also is assigned a five-digit FIPS code in alphabetical order within state; because FIPS codes are assigned within each state, the FIPS codes are likely different for each state portion of any TDSAs that extend into more than one state. Each TDSA is also assigned a nationally unique eight-digit ANSI code. AIANNH Area Codesthe American Indian, Alaska Native, and Native Hawaiian (AIANNH) areas are represented in the TIGER/Line Shapefiles by a four-digit census code field, and a single alphabetic character AIANNH area reservation/statistical area or off-reservation trust land (ORTL) 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 their applicable code range. ORTLs are assigned the same code as the reservation with which they are associated. ORTLs associated with tribes that do not have a reservation are assigned codes based on their tribal name. There is one TIGER/Line Shapefile record created for each unique combination of AIANNH code and component type. Each AIANNH area also is assigned a nationally unique eight-digit ANSI code.

5-18

The type of AIANNH area can be identified either by its census code (AIANNHCE), its MAF/TIGER feature class code (MTFCC), or by its FIPS class code (CLASSFP). The range of census codes allocated to each AIANNH area and the valid FIPS class code(s) associated with each are as follows: Type Census code Valid FIPS Class MTFCCs Range Codes Federal AIR or ORTL 0001 to 4899 *D2, *D3, *D5,*D8 *G2101, *G2102 Federal AIR/ORTL joint-use area 4900 to 4999 D0 G2170 Hawaiian home land 5000 to 5499 F1 G2120 OTSA 5500 to 5899 D6 G2140 OTSA joint-use area 5900 to 5999 D0 G2170 ANVSA 6000 to 7999 E1 G2130 TDSA 8000 to 8999 D6 G2160 State AIR 9000 to 9499 D4 G2101 SDTSA 9500 to 9998 D9 G2150 Note: G2101 can represent both federally and state-recognized areas; the recognition level can be determined using the federal/state recognition flag (AIANNHR) field where F is federally recognized and S is state-recognized. Joint-use areas are identified uniquely by MTFCC G2170. An A in the functional status (FUNCSTAT) field identifies federal AIR/ORTL joint-use areas, while an S in the field represents joint-use OTSAs. *D2: Legal federally recognized American Indian area consisting of reservation only *D3: Legal federally recognized American Indian area consisting of off-reservation trust land only *D5: The legal off-reservation trust land portion of a federally recognized American Indian area with both a reservation and trustland *D8: The legal reservation portion of a federally recognized American Indian entity with both a reservation and trust land *G2101: Reservation or AIAN statistical entity *G2102: American Indian ORTL or Hawaiian home land Type Component Type (COMPTYP) T R

American Indian Trust Land Reservation or Statistical Entity

5-19

5.1.2.1American Indian/Alaska Native/Native Hawaiian (AIANNH) Area National Shapefile Record Layout (Current) File Name: tl_2012_us_aiannh.shp AIANNHCE AIANNHNS 4 8 String String Current American Indian/Alaska Native/Native Hawaiian area census code Current American Indian/Alaska Native/Native Hawaiian area ANSI code American Indian/Alaska Native/Native Hawaiian area identifier; a concatenation of Current American Indian/Alaska Native/Native Hawaiian area census code and reservation/statistical area or off-reservation trust land Hawaiian home land indicator Current American Indian/Alaska Native/Native Hawaiian area name Current name and the translated legal/statistical area description for American Indian/Alaska Native/Native Hawaiian area Current legal/statistical area description code for American Indian/Alaska Native/Native Hawaiian area Current FIPS class code Current American Indian/Alaska Native/Native Hawaiian area reservation/statistical area or off-reservation trust land Hawaiian home land indicator Current American Indian/Alaska Native/Native Hawaiian area federal/state recognition flag MAF/TIGER feature class code Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

GEOID

String

NAME NAMELSAD LSAD CLASSFP COMPTYP AIANNHR MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON

100 100 2 2 1 1 5 1 14 14 11 12

String String String String String String String String Number Number String String

5-20

5.1.3

American Indian Tribal Subdivisions

American Indian Tribal Subdivision geography and attributes are available in the following shapefile: American Indian Tribal Subdivision (AITS) National Shapefile (Current) American Indian Tribal Subdivisions (AITS) are legally defined administrative subdivisions of federally recognized American Indian reservations and/or off-reservation trust lands, or Oklahoma tribal statistical areas (OTSAs). Tribal subdivisions are known as additions, administrative areas, areas, chapters, county districts, districts, or segments. 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, offreservation trust lands, or OTSAs. The Census Bureau obtains the boundary and name information for tribal subdivisions from the federally recognized tribal governments. American Indian Tribal Subdivision Codes are represented in the TIGER/Line Shapefiles by a three-digit census code. The Census Bureau assigns the three-digit American Indian tribal subdivision code alphabetically in order and uniquely within each American Indian reservation and/or associated offreservation trust land, or Oklahoma tribal statistical area (OTSA). Each AITS is also assigned a nationally unique eight-digit ANSI code. 5.1.3.1American Indian Tribal Subdivision (AITS) National Shapefile Record Layout (Current) File Name: tl_2012_us_aitsn.shp AIANNHCE TRSUBCE TRSUBNS GEOID NAME NAMELSAD LSAD CLASSFP MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 4 3 8 7 100 100 2 2 5 1 14 14 11 12 String String String String String String String String String String Number Number String String Current American Indian/Alaska Native/Native Hawaiian area census code Current American Indian tribal subdivision census code Current American Indian tribal subdivision ANSI code American Indian tribal subdivision identifier; a concatenation of Current American Indian/Alaska Native/Native Hawaiian area census code and American Indian tribal subdivision census code Current American Indian tribal subdivision name Current name and the translated legal/statistical area description for American Indian tribal subdivision Current legal/statistical area description code for American Indian tribal subdivision Current FIPS class code MAF/TIGER feature class code (G2300) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5-21

5.1.4

Tribal Census Tract

Tribal Census Tract geography and attributes are available in the following shapefile: Tribal Census Tract National Shapefile (Current) Tribal census tracts are relatively small statistical subdivisions of an American Indian reservation and/or off-reservation trust land (ORTL), and were defined by federally recognized tribal government officials in the Census Bureaus Tribal Statistical Areas Program (TSAP) for the 2010 Census. If a tribal government declined to participate in TSAP, the Census Bureau delineated tribal census tracts on the American Indian reservation and/or off-reservation trust land (ORTL). Tribal census tracts are conceptually similar and equivalent to standard census tracts. Unlike standard census tracts, however, tribal census tracts may cross state and/or county boundaries. Tribal census tracts generally have at least 1,200 persons or 480 housing units, and no more than 8,000 persons or 3,200 housing units, with an optimal size of 4,000 persons or 1,600 housing units. Many American Indian reservations and/or off-reservation trust lands have less than 2,400 persons and/or 960 housing units; in those cases, one tribal census tract was delineated that covers the entire American Indian reservation and/or off-reservation trust land, since the area did not have enough population or housing units to meet the minimum population and housing requirements for more than one tribal census tract. Tribal Census Tracts CodesSimilar to standard census tracts, tribal census tracts have a four-character basic name/code plus a two-digit suffix which may be utilized if the tribal census tract is split in the future. (Because 2010 is the first Census for which this coding scheme was used, no tribal census tracts currently have suffixes, in other words they all have a suffix of 00.) Tribal census tract codes all begin with the letter T and are followed by three digits and the two-digit suffix, for example T00200. Tribal census tracts codes have an implied decimal between the basic code and the suffix, and they are unique within an American Indian reservation and/or ORTL. Tribal Census Tract Namesthe tribal census tract code also acts as its name, with the suffix only appended if required. The TTRACTCE field contains the six-digit code format (including the suffix). The NAME field contains the tribal census tract name as displayed in Census Bureau printed reports and on mapping products. The name will consist of the first four characters (T followed by three digits, including any leading or trailing zeros) and a decimal point followed by the two-digit suffix if the suffix is something other than 00. When the suffix is only zeros, the decimal point and suffix in the tribal tract are omitted from the name. For example, tribal census tract code T01000 has a tribal census tract name of T010. The NAMELSAD field includes both the translated legal/statistical area description and the tribal tract name, as in Tribal census tract T010. [Link] Tribal Census Tract National Shapefile (Current) File name: tl_2012_<US>_ttract.shp AIANNHCE TTRACTCE GEOID NAME NAMELSAD MTFCC ALAND AWATER INTPTLAT INTPTLON 4 6 10 7 27 5 14 14 11 12 String String String String String String Number Number String String Current American Indian / Alaska Native / Native Hawaiian area census code Current tribal census tract code Tribal census tract identifier; a concatenation of the American Indian Area census code and tribal census tract code Current tribal census tract name, including the decimal point and decimal digits if a non-zero census tract suffix exists Current translated legal/statistical area description and the tribal census tract name MAF/TIGER feature class code (G2400) Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5-22

5.1.5

Tribal Block Group

Tribal Block Group geography and attributes are available in the following shapefile: Tribal Block Group National Shapefile (Current) Tribal block groups are clusters of blocks within the same tribal census tract. Unlike standard block groups, the cluster of blocks that comprises each tribal block group will not necessarily begin with the same first number of their four-digit census block number, but may contain blocks from several different standard census block groups. Tribal block groups were defined by federally recognized tribal government officials in the Census Bureaus Tribal Statistical Areas Program (TSAP) for the 2010 Census. If a tribal government declined to participate in TSAP, the Census Bureau delineated tribal block groups on the American Indian reservation and/or off-reservation trust land (ORTL). Tribal block groups are intended to generally contain between 600 and 3,000 persons or between 240 and 1,200 housing units. Many American Indian reservations and ORTLs have less than the minimum population thresholds for more than one tribal block group and in those cases one tribal block group was delineated that covers the entire American Indian reservation and/or ORTL. A tribal block group usually covers a contiguous area but in some cases may consist of more than one discrete area. Tribal block groups nest within tribal census tracts and within individual federally recognized American Indian reservations and/or ORTLs. Because tribal block groups are within an American Indian reservation/ORTL and its tribal census tracts, their boundaries may cross standard census tract, standard block group, county, and/or state boundaries. Tribal block groups are uniquely named within tribal tracts. Tribal block group names and codes are identical and are a single capital letter character from A to K (except for the letter I) and must be unique within each tribal census tract. There is no relationship between the tribal block group identifier and the numbering of the census blocks that form the tribal block group. A tribal block group will always be identified in conjunction with the tribal census tract within which it is contained, for example T00100A. [Link] Tribal Block Group National Shapefile (Current) File name: tl_2012_<US>_tbg.shp AIANNHCE TTRACTCE TBLKGPCE GEOID NAMELSAD MTFCC ALAND AWATER INTPTLAT INTPTLON 4 6 1 11 20 5 14 14 11 12 String String String String String String Number Number String String Current Census American Indian / Alaska Native / Native Hawaiian area census code Current tribal census tract code Current tribal block group letter Tribal block group identifier; a concatenation of the Current American Indian / Alaska Native / Native Hawaiian area census code, tribal census tract code, and tribal block group letter Current translated legal/statistical area description and the tribal block group letter MAF/TIGER feature class code (G2410) Current land area Current water area Current latitude of the internal point Current longitude of the internal point

Block geography and attributes are available in the following shapefile: Block State-based Shapefile (Current) Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and by non-visible 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;

5-23

for example, a block in a city. Census blocks in suburban and rural areas may be large, irregular, and bounded by a variety of features, such as roads, streams, and/or transmission line rights-of-way. In remote areas census blocks may encompass hundreds of square miles. Census blocks cover all territory in the United States, Puerto Rico, and the Island areas. Blocks never cross county or census tract boundaries (See Figures 3 and 4). They do not cross the boundaries of any entity for which the Census Bureau tabulates 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 NumbersCensus 2010 blocks are numbered uniquely within the 2010 boundaries of each state/county/census tract with a 4-digit census block number. 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, 2010, the Census Bureau assigns a current alphabetic suffix for a 2010 Census block number. The current suffixes for 2010 Census block numbers are not permanent and will change with each annual cycle of current block suffixing. Due to potential updates to the codes, it is important not to mix 2010 Census geographic codes with current geographic codes. Census Block Numbers Block group number 0 to 9First numeric character 000 to 999Second, third, and fourth numeric characters Current Suffix for 2010 Census Block Number A to ZCodes for current suffix for 2010 Census block numbers

5-24

5-25

5-26

5.2.1

Block State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_tabblock.shp STATEFP COUNTYFP STATEFP10 COUNTYFP10 TRACTCE10 BLOCKCE10 SUFFIX1CE GEOID 2 3 2 3 6 4 1 16 String String String String String String String String Current state FIPS code Current county FIPS code 2010 Census state FIPS code 2010 Census county FIPS code 2010 Census census tract code 2010 Census tabulation block number Current census block suffix 1 Block identifier; a concatenation of 2010 Census state FIPS code, 2010 Census county FIPS code, 2010 Census tract code, 2010 Census tabulation block number, and current block suffix 1 Current tabulation block name; a concatenation of Block, the current tabulation block number, and current block suffix 1 MAF/TIGER feature class code (G5040) 2010 Census urban/rural indicator 2010 Census urban area code Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

NAME MTFCC UR10 UACE10 FUNCSTAT ALAND AWATER INTPTLAT INTPTLON

11 5 1 5 1 14 14 11 12

String String String String String Number Number String String

Block group geography and attributes are available in the following shapefile: Block Group State-based Shapefile (Current) Block groups are clusters of blocks within the same census tract that have the same first digit of their 4digit census block number. For example, blocks 3001, 3002, 3003, ., 3999 in census tract 1210.02 belong to Block Group 3. Block groups delineated for the 2010 Census generally contain between 600 and 3,000 people. Most block groups were delineated by local participants in the Census Bureau's Participant Statistical Areas Program. The Census Bureau delineated block groups only where a local or tribal government declined to participate or where the Census Bureau could not identify a potential local participant. A block group usually covers a contiguous area. Each census tract contains at least one block group and block groups are uniquely numbered within census tract. Within the standard census geographic hierarchy, block groups 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. Block groups have a valid range of 0 through 9. Block groups beginning with a zero 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 zero and block group of zero to the offshore areas not included in regularly numbered census tract areas.

5-27

5.3.1

Block Group State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_bg.shp STATEFP COUNTYFP TRACTCE BLKGRPCE GEOID NAMELSAD MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 3 6 1 12 13 5 1 14 14 11 12 String String String String String String String String Number Number String String Current state FIPS code Current county FIPS code Current census tract code Current block group number Census block group identifier; a concatenation of the current state FIPS code, county FIPS code, census tract code and block group number. Current translated legal/statistical area description and the block group number MAF/TIGER feature class code (G5030) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

Census tract geography and attributes are available in the following shapefile: Census Tract State-based Shapefile (Current) Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and are reviewed and updated by local participants prior to each decennial census as part of the Census Bureaus Participant Statistical Areas Program. The Census Bureau updates 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,200 and 8,000 people with an optimum size of 4,000 people. The spatial size of census tracts varies widely depending on the density of settlement. Census tracts 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. 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 NumbersCensus 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. The Census Bureau assigned a census tract code of 0000 to some coastal and Great Lakes water and territorial sea, rather than extend the census

5-28

tract boundary into the Great Lakes or out to the three-mile limit. This allowed the Census Bureau to provide complete census tract coverage of Current water areas in territorial seas and the Great Lakes. Because of updates since 2000, there are census tracts with code 000000 that now contain land. Census tract suffixes may range from .01 to .98. 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. Relationship to Other Geographic EntitiesWithin 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.

0001 to 9989Basic number range for census tracts 0000Basic number for census tracts in water areas 01 to 98Suffix codes for census tracts 00Suffix code for census tracts without a suffix

5-29

5.4.1

Census Tract State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_tract.shp STATEFP COUNTYFP TRACTCE GEOID 2 3 6 11 String String String String Current state FIPS code Current county FIPS code Current census tract code Census tract identifier; a concatenation of Current state FIPS code, county FIPS code, and census tract code Current census tract name, this is the census tract code converted to an integer or integer plus two-digit decimal if the last two characters of the code are not both zeros. Current translated legal/statistical area description and the census tract name MAF/TIGER feature class code (G5020) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

NAME NAMELSAD MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON

7 20 5 1 14 14 11 12

String String String String Number Number String String

Congressional district geography and attributes are available in the following shapefile: 112th Congressional District National 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 decennial census population counts, each state is responsible for establishing the boundaries of the 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 2012 TIGER/Line Shapefiles contain the 112th Congressional Districts. All congressional districts appearing in the 2012 TIGER/Line Shapefiles reflect the information provided to the Census Bureau by the states. The 112th Congressional District shapefile contains the areas in effect January 2011 to 2013 and are the tabulation congressional districts for the 2010 Census. Each state has a minimum of one representative in the U.S. House of Representatives. The District of Columbia, Puerto Rico, American Samoa, Guam, and the U.S. Virgin Islands have a non-voting delegate in the Congress. Congressional District CodesCongressional 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 the code of 98, which identifies their status with respect to representation in Congress: 01 to 53Congressional district codes 00At large (single district for state) 98Nonvoting delegate

5-30

5.5.1

112th Congressional District National Shapefile Record Layout File Name: tl_2012_<US>_cd112.shp STATEFP CD112FP GEOID NAMELSAD LSAD CDSESSN MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 2 4 41 2 3 5 1 14 14 11 12 String String String String String String String String Number Number String String Current state FIPS code 112th congressional district FIPS code 112th congressional district identifier; a concatenation of current state FIPS code and the 112th congressional district FIPS code Current name and the translated legal/statistical area description for congressional district Current legal/statistical area description code for congressional district 112th congressional session code MAF/TIGER feature class code (G5200) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

Consolidated city geography and attributes are available in the following shapefile: Consolidated City State-based Shapefile (Current) Consolidated CityA 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 2012 Census TIGER/Line Shapefiles by a 5 character numeric FIPS code and a National Standard (ANSI) 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.

5-31

5.6.1

Consolidated City Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_concity.shp STATEFP CONCTYFP CONCTYNS GEOID NAME NAMELSAD LSAD CLASSFP MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 5 8 7 100 100 2 2 5 1 14 14 11 12 String String String String String String String String String String Number Number String String Current state FIPS code Current consolidated city FIPS code Current consolidated city ANSI code Consolidated city identifier; a concatenation of Current state FIPS code and consolidated city FIPS code Current consolidated city name Current name and the translated legal/statistical area description for consolidated city Current legal/statistical area description code for consolidated city Current FIPS class code MAF/TIGER feature class code (G4120) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

County and equivalent entity geography and attributes are available in the following shapefile: County and Equivalent Entity National Shapefile (Current) Counties and Equivalent Entities are primary legal divisions. In most states, these entities are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, the equivalent entities are the organized boroughs, city and boroughs, and municipalities, and for the unorganized areas, 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 county equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions and each area is considered a county 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 America Samoa, municipalities in the Commonwealth of the Northern Mariana Islands, and islands in the U.S. Virgin Islands. Each county or statistically equivalent entity is assigned a three-digit FIPS code that is unique within a state, as well as an eight-digit ANSI code. The 2012 TIGER/Line Shapefiles are based on available governmental unit boundaries of the counties and equivalent entities as of January 1, 2012. Detailed information about changes in the inventory and codes for county and equivalent areas can be found at: [Link] Core-based Statistical Area (CBSA) Codes The 2012 vintage county and equivalent entity shapefiles also contain fields with codes for Combined Statistical Area, Metropolitan or Micropolitan Statistical Area, and Metropolitan Division. Counties form the building blocks for CBSAs, thus county records can be merged to form these areas without having to acquire the individual CBSA shapefiles.

5-32

5.7.1

County and Equivalent Entity National Shapefile Record Layout (Current) File Name: tl_2012_us_county.shp STATEFP COUNTYFP COUNTYNS GEOID NAME NAMELSAD LSAD CLASSFP MTFCC CSAFP CBSAFP METDIVFP FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 3 8 5 100 100 2 2 5 3 5 5 1 14 14 11 12 String String String String String String String String String String String String String Number Number String String Current state FIPS code Current county FIPS code Current county ANSI code County identifier; a concatenation of Current state FIPS code and county FIPS code Current county name Current name and the translated legal/statistical area description for county Current legal/statistical area description code for county Current FIPS class code MAF/TIGER feature class code (G4020) Current combined statistical area code Current metropolitan statistical area/micropolitan statistical area code Current metropolitan division code Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5-33

County subdivision geography and attributes are available in the following shapefile: County Subdivision State-based Shapefile (Current) 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 2012 TIGER/Line Shapefiles contain a 5-character numeric FIPS code field for county subdivisions and an 8-character numeric ANSI code. 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, barrios, barrios-pueblo, boroughs, census subdistricts, charter townships, commissioner districts, counties, election districts, election precincts, gores, grants, locations, magisterial districts, parish governing authority districts, plantations, precincts, purchases, supervisor's districts, towns, and townships. The Census Bureau recognizes MCDs in 29 states, Puerto Rico, and the Island areas. The District of Columbia has no primary divisions, and the incorporated place of Washington is treated as an equivalent to an MCD for statistical purposes (it is also considered a state equivalent and a county equivalent). In 23 states and the District of Columbia, all or some incorporated places are not part of any MCD. These places also serve as primary legal subdivisions and have a unique FIPS MCD code that is the same as the FIPS place code. The ANSI codes also match for those entities. In other states, incorporated places are part of the MCDs in which they are located, or the pattern is mixedsome 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. 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 are not governmental units and have no legal functions. 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) 2) 3) 4) There are no legally established minor civil divisions (MCDs) The legally established MCDs do not have governmental or administrative purposes The boundaries of the MCDs change frequently The MCDs are not generally known to the public

CCDs have been established for the following 20 states: Alabama Florida Montana South Carolina Arizona Georgia Nevada Texas California Hawaii New Mexico Utah Colorado Idaho Oklahoma Washington Delaware Kentucky Oregon Wyoming

Census Subareas are statistical subdivisions of boroughs, city and boroughs, municipalities, and census areas, the latter of which are the statistical equivalent entities for counties in Alaska. The state of Alaska

5-34

and the Census Bureau cooperatively delineate the census subareas to serve as the statistical equivalents of MCDs. Unorganized Territories (UTs) have been defined by the Census Bureau in 9 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 county subdivision FIPS and ANSI codes. Unorganized territories are recognized in the following states and equivalent areas: Arkansas Minnesota South Dakota Indiana New York Iowa Maine North Carolina North Dakota

Undefined county SubdivisionsIn 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 and ANSI code of 00000000 named county subdivision not defined. The following states and equivalent areas have these county subdivisions : Connecticut Massachusetts New Jersey Rhode Island Illinois Michigan New York Wisconsin Indiana Minnesota Ohio Puerto Rico Maine New Hampshire Pennsylvania

New England City and Town Area (NECTA) Codes The 2012 county subdivision shapefiles also contain fields with codes for Combined New England City and Town Area, New England City and Town Area, and New England City and Town Area Division. The NECTAs are delineated by whole county subdivision, thus county subdivision records can be merged to form these areas without having to acquire the individual NECTA shapefiles. 5.8.1 County Subdivision State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_cousub.shp STATEFP COUNTYFP COUSUBFP COUSUBNS GEOID NAME NAMELSAD LSAD CLASSFP MTFCC CNECTAFP NECTAFP NCTADVFP FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 3 5 8 10 100 100 2 2 5 3 5 5 1 14 14 11 12 String String String String String String String String String String String String String String Number Number String String Current state FIPS code Current county FIPS code Current county subdivision FIPS code Current county subdivision ANSI code County subdivision identifier; a concatenation of Current state FIPS code, county FIPS code, and county subdivision FIPS code. Current county subdivision name Current name and the translated legal/statistical area description code for county subdivision Current legal/statistical area description code for county subdivision Current FIPS class code MAF/TIGER feature class code (G4040) Current combined New England city and town area code Current Current Current Current Current Current Current New England city and town area code New England city and town area division code functional status land area water area latitude of the internal point longitude of the internal point

5-35

Estate features and attributes are available by state in the following shapefile: Estate State-based Shapefile (Current) Estates are subdivisions of the three major islands in the United States Virgin Islands (USVI). The estates have legally defined boundaries and are much smaller in area than the Census Subdistricts (county subdivisions), but do not necessarily nest within these districts. The boundaries of the estates are primarily those of the former agricultural plantations that existed at the time Denmark transferred the islands to the United States in 1917. The names and boundaries of the estates are in common usage by residents and in government administration. The boundaries of the estates are as of January 1, 2010 and were provided to the Census Bureau by the USVI Office of the Lieutenant Governor. Estates can be found in the SubMinor Civil Division (submcd) shapefile for the 2010 and the 2011 TIGER/Line products. 5.9.1 Estate Shapefile (U.S. Virgin Islands Only) Record Layout (Current) File Name: tl_2012_<78>_estate.shp STATEFP COUNTYFP ESTATEFP ESTATENS GEOID NAME NAMELSAD LSAD CLASSFP MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 3 5 8 10 100 100 2 2 5 1 14 14 11 12 String String String String String String String String String String String Number Number String String Current state FIPS code Current county FIPS code Current estate FIPS code Current estate ANSI code Estate identifier; a concatenation of current state FIPS code, county FIPS code, and estate FIPS code Current estate name Current name and the translated legal/statistical area description for estate Current legal/statistical area description code for estate Current FIPS class code MAF/TIGER feature class code Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

Hydrography features and attributes are available by county in the following shapefiles: Area Hydrography County-based Shapefile Linear Hydrography County-based 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 and Linear Hydrography Shapefile. The Linear Hydrography shapefile contains all linear hydrography features with H (Hydrography) type MTFCC in the MAF/TIGER database by county. The shapefiles are provided at a county geographic extent and in linear elemental feature geometry. The content of the linear hydrography shapefile includes streams/rivers, braided streams, canals, ditches, artificial paths and aqueducts. A linear hydrography feature may include edges with both perennial and intermittent persistence. The artificial path features may correspond to those in the USGS National Hydrographic Dataset (NHD). However, in many cases the features do not match NHD equivalent feature and will not carry the NHD metadata codes.

5-36

Single-line drainage water features include artificial path features that run through double-line drainage features such as rivers and streams, and serve as a linear representation of these features. 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). 5.10.1 Area Hydrography County-based Shapefile Record Layout File Name: tl_2012_<state-county FIPS>_areawater.shp STATEFP COUNTYFP ANSICODE HYDROID FULLNAME MTFCC ALAND AWATER INTPTLAT INTPTLON 2 3 8 22 100 5 14 14 11 12 String String String String String String Number Number String String State FIPS code County FIPS code Official code for the water body for use by federal agencies for data transfer and dissemination, if applicable Area hydrography identifier 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 MAF/TIGER feature class code Land area Water area Latitude of the internal point Longitude of the internal point

5-37

5.10.2 Linear Hydrography County-based Shapefile Record Layout File Name: tl_2012_<state-county FIPS>_linearwater.shp ANSICODE LINEARID FULLNAME ARTPATH MTFCC 8 22 100 1 5 String String String String String Official code for use by federal agencies for data transfer and dissemination, if applicable Linear hydrography identifier 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 Artificial path flag MAF/TIGER feature class code

Landmark features and attributes are available by state in the following shapefiles: Area Landmark State-based Shapefile Point Landmark State-based Shapefile The Census Bureau includes landmarks in the MAF/TIGER database (MTDB) 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. The Census Bureau added landmark features to the database on an as-needed basis and makes 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 2010 Census enumeration. The landmarks were not used as the basis for building or maintaining the address list used to conduct the 2010 Census. The Census Bureau systematically adds several types of point landmarks to the MAF/TIGER Database to provide additional locational reference points for census takers in the field. The landmarks include airports, cemeteries, locales, populated places, pillars and summits from the Geographic Names Information System (GNIS). Landmarks from this source have a GNIS ANSI Code to identify them. Area landmark and area water features can overlap; for example, a park or other special land-use feature may include 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; but these features 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 landmark has a unique area landmark identifier (AREAID) or point landmark identifier (POINTID) value.

5-38

5.11.1 Area Landmark State-based Shapefile Record Layout File Name: tl_2012_<state FIPS>_arealm.shp STATEFP ANSICODE AREAID FULLNAME MTFCC ALAND AWATER INTPTLAT INTPTLON 2 8 22 100 5 14 14 11 12 String String String String String Number Number String String State FIPS code Official code for the landmark for use by federal agencies for data transfer and dissemination Area landmark identifier 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 MAF/TIGER feature class code Land area Water area Latitude of the internal point Longitude of the internal point

5.11.2 Point Landmark State-based Shapefile Record Layout File Name: tl_2012_<state FIPS>_pointlm.shp STATEFP ANSICODE POINTID FULLNAME MTFCC 2 8 22 100 5 String String String String String State FIPS code Official code for the point landmark for use by federal agencies for data transfer and dissemination, if applicable Point landmark identifier Concatenation of expanded text for prefix type, base name, and suffix type with a space between each expanded text field MAF/TIGER feature class code

Linear elemental features are the spatial representation of 1-dimensional roads, hydrography, railroads and other miscellaneous features in the MAF TIGER database. A linear elemental feature can span one edge or multiple connecting edges that share a common name and feature classification (MTFCC) depending on the extent of the linear feature it represents. More than one linear elemental feature can share the same edge or group of connected edges. For example, an edge may be associated with a linear feature called Oak Street. This same edge may be one of several edges also associated with another linear feature called State Highway 57. The edge in question has two names, Oak Street and State Highway 57. One of these names will be designated as primary and the others alternate names. Usually the common street name (Oak Street) will be primary. The MAF/TIGER database breaks/ends linear elemental features when the feature name changes. All spelling differences are represented by a new feature. Features will also break at county boundaries, changes in primary/alternate designation, MTFCC, and gaps in the geometry. Linear features and attributes are available by the county, state and national extents in the following shapefiles. 5.12.1 All Lines Each All Lines shapefile describes the universe of edges that either bound or are included within a county or equivalent entity. The shapefile describes the geometry of each edge along with descriptive attributes and unique identification numbers. These identification numbers provide the means for linking the edges to alternate features their names, address ranges, and the adjacent faces. All Lines County-based Shapefile

5-39

The All Lines shapefile contains visible linear feature edges such as roads, railroads, and hydrography, as well as non-feature edges and non-visible boundaries. Additional attribute data associated with the linear feature edges found in the All Lines shapefiles are available in relationship files that users must download separately. The All Lines shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TLID (permanent edge identifier) value. The edges left and right faces can be identified by the TFIDL (permanent face identifier on the left side of the edge) and TFIDR (permanent face identifier on the right side of the edge) attributes which link to the TFID attribute in the Topological Faces shapefile. 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 (road feature indicator) and RAILFLG (rail feature indicator) set. Generally, certain feature types appear together on the same edge: Road and Railroads with adjacent tracks, tracks embedded in roadways or tracks located in the median Rail and Other Linear Featurerail features located on dams and levees Road and Other Linear Featureroad 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.

5-40

[Link] All Lines County-based Shapefile Record Layout File Name: tl_2012_<state-county FIPS>_edges.shp STATEFP COUNTYFP TLID TFIDL TFIDR MTFCC FULLNAME SMID LFROMADD LTOADD RFROMADD RTOADD ZIPL ZIPR FEATCAT HYDROFLG RAILFLG ROADFLG OLFFLG PASSFLG DIVROAD EXTTYP TTYP DECKEDROAD ARTPATH PERSIST GCSEFLG OFFSETL OFFSETR TNIDF TNIDT 5.12.2 Roads Linear road features and attributes are available in the following shapefiles: Primary Roads National Shapefile Primary and Secondary Roads State-based Shapefile All Roads County-based Shapefile Primary roads are generally divided, limited-access highways within the Federal interstate highway system or under state management. These highways are distinguished by the presence of interchanges and are accessible by ramps, and may include some toll highways. The Primary Roads shapefile contains all linear street features with MTFCC of S1100 in the MAF/TIGER database. The shapefiles are provided at a National geographic extent and in linear elemental feature geometry. 2 3 10 10 10 5 100 22 12 12 12 12 5 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 10 10 String String Integer Integer Integer String String String String String String String String String String String String String String String String String String String String String String String String Integer Integer State FIPS code County FIPS code Permanent edge ID Permanent face ID on the left of the edge Permanent face ID on the right of the edge MAF/TIGER feature class code of the primary feature for the edge 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 (as available) Spatial metadata identifier From house number associated with the most inclusive address range on the left side of the edge To house number associated with the most inclusive address range on the left side of the edge From house number associated with the most inclusive address range on the right side of the edge To house number associated with the most inclusive address range on the right side of the edge ZIP code associated with the most inclusive address range on the left side ZIP code associated with the most inclusive address range on the right side General feature classification category Hydrography feature indicator Rail feature indicator Road feature indicator Other linear feature indicator Special passage flag Divided road flag Extension type Track type Decked road indicator Artificial path indicator Hydrographic persistence flag Short lines flag for geographic corridors Left offset flag Right offset flag From TIGER node identifier To TIGER node identifier

5-41

The Primary and Secondary Roads shapefile contains all linear st reet features with MTFCC of S1100 and S1200 in the MAF/TIGER database. The shapefiles are provided at a State geographic extent and in linear elemental feature geometry. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not be divided, and usually have at-grade intersections with many other roads and driveways. They often have both a local name and a route number. The content of the All Roads shapefile includes primary roads, secondary roads, local neighborhood roads, rural roads, city streets, vehicular trails (4WD), ramps, service drives, walkways, stairways, alleys, and private roads. The All Roads shapefile contains all linear street features with S (Street) type MTFCCs in the MAF/TIGER database. The shapefiles are provided at a County geographic extent and in linear elemental feature geometry. The street MTFCC may be misclassified for some street features in MAF/TIGER. The default street type MTFCC S1400 was used in MAF/TIGER Accuracy Improvement Program (MTAIP) and other update operations if the data source used to update MAF/TIGER did not have a comparable classification code. Note that the LINEARID can be used to link the linear features back to the Featnames table and from there the TLID can relate the feature back to the all edges shapefile. [Link] Primary Roads National Shapefile Record Layout File Name: tl_2012_us_primaryroads.shp LINEARID FULLNAME RTTYP MTFCC 22 100 1 5 String String String String Linear identifier 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; display name. Route type code MAF/TIGER feature class code

[Link] Primary and Secondary Roads State-based Shapefile Record Layout File Name: tl_2012_<state FIPS>_prisecroads.shp LINEARID FULLNAME RTTYP MTFCC 22 100 1 5 String String String String Linear feature identifier 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 Route type code MAF/TIGER feature class code

[Link] All Roads County-based Shapefile Record Layout File Name: tl_2012_<state-county FIPS>_roads.shp LINEARID FULLNAME RTTYP MTFCC 5.12.3 Address Ranges Linear address range features and attributes are available in the following layer: Address Range Feature County-based Shapefile 22 100 1 5 String String String String Linear feature identifier 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 Route type code MAF/TIGER feature class code

5-42

The Address Range Feature Shapefile ([Link]) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure house numbers between the first structure house number to the last structure house number of a specified parity along an edge side relative to the direction in which the edge is coded. All of the TIGER/Line address range files contain potential address ranges, not individual addresses. Potential ranges include the full range of possible structure numbers even though the actual structures may not exist. Single-address address ranges are suppressed to maintain the confidentiality of the addresses they describe. The [Link] contains all of the address range to street name relationships in the Address Range Feature Name relationship file ([Link]). The [Link] also contains all possible relationships between the Address Range relationship table ([Link]) and the All Lines shapefile ([Link]). All of these address range to feature name and address range to edge relationships in the [Link] result in better geocoding match rates compared with using the [Link] for geocoding. The [Link] only contains the most inclusive address range associated to each side of a street edge and the primary street name assigned to the edge. [Link] Address Range Feature County-based Shapefile Record Layout File Name is: tl_2012_<state-county FIPS>_addrfeat.shp TLID TFIDL TFIDR ARIDL ARIDR LINEARID FULLNAME LFROMHN LTOHN RFROMHN RTOHN ZIPL ZIPR EDGE_MTFCC ROAD_MTFCC PARITYL PARITYR PLUS4L PLUS4R LFROMTYP 10 10 10 22 22 22 100 12 12 12 12 5 5 5 5 1 1 4 4 1 Integer Integer Integer String String String String String String String String String String String String String String String String String Permanent edge ID Permanent face ID on the left of the edge Permanent face ID on the right of the edge Left side Address range identifier Right side Address range identifier Linear feature identifier 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 From House Number associated with the address range on the left side of the edge; SIDE=L To House Number associated with the address range on the left side of the edge; SIDE=L From House Number associated with the address range on the right side of the edge; SIDE=R To House Number associated with the address range on the right side of the edge; SIDE=R ZIP code associated with the left address range ZIP code associated with the right address range Primary MAF/TIGER feature class code of related edge record MAF/TIGER feature class code of related linear feature record Left side Address Range Parity Right side Address Range Parity Left side ZIP+4 Code Right side ZIP+4 Code Left side From address range end type. This field will only be populated if the value is I and the address range is an imputed value calculated by the Census Bureau at a split point. If the value is anything other than I, the field shall be left blank. Left side To address range end type. This field will only be populated if the value is I and the address range is an imputed value calculated by the Census Bureau at a split point. If the value is anything other than I, the field shall be left blank.

LTOTYP

String

5-43

RFROMTYP

String

RTOTYP OFFSETL OFFSETR

1 1 1

String String String

Right side From address range end type. This field will only be populated if the value is I and the address range is an imputed value calculated by the Census Bureau at a split point. If the value is anything other than I, the field shall be left blank. Right side To address range end type. This field will only be populated if the value is I and the address range is an imputed value calculated by the Census Bureau at a split point. If the value is anything other than I, the field shall be left blank. Flag to designate if left side address range is on offset edge Flag to designate if right side address range is on offset edge

5.12.4 Railroads Linear railroad features and attributes are available in the following layer: Railroads National Shapefile The content of the Railroad shapefile includes spur lines, rail yards; mass transit rail lines such as carlines, streetcar track, monorail or other mass transit rail, and special purpose rail lines such as cog rail lines, incline rail lines and trams. The Railroad shapefile contains all linear rail features with R (Rail) type MTFCC in the MAF/TIGER database. The shapefiles are provided at a County geographic extent and in a linear elemental feature geometry (described in section 4.2). [Link] Railroads National Shapefile Record Layout File Name is: tl_2012_<US>_rails.shp LINEARID FULLNAME MTFCC 22 100 5 String String String Linear feature identifier 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 MAF/TIGER feature class code

Metropolitan and micropolitan statistical area and related statistical area geography and attributes are available in the following shapefiles: Combined New England City and Town Area (CNECTA) National Shapefile (Current) Combined Statistical Area (CSA) National Shapefile (Current) Metropolitan Division National Shapefile (Current) Metropolitan Statistical Area/Micropolitan Statistical Area (CBSA) National Shapefile (Current) New England City and Town Area (NECTA) National Shapefile (Current) New England City and Town Area (NECTA) Division National Shapefile (Current) 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

5-44

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 size. 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 2012 TIGER/Line Shapefiles are the updates to metropolitan and micropolitan statistical areas as of December 2009, announced by the OMB on December 1, 2009. The Office of Management and Budget (OMB) plans to announce delineations based on the 2010 standards and 2010 Census data in 2013. 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 are created when metropolitan statistical area containing a single core with a population of at least 2.5 million is subdivided to form smaller groupings of counties or equivalent entities. 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 5-45

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 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 are created when a NECTA containing a single core with a population of at least 2.5 million is to form smaller groupings of cities and towns. 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 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. All CBSAs have at least one principal city and there is one place-Holland City, MI-that is a principal city of two CBSAs (Allegan, MI and Holland-Grand Haven, MI). Core Based Statistical Area CodesThe 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 areas 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. Since CBSA codes are defined nationally, no additional codes are required to provide a unique entity identifier. Since lower level divisions nest within CBSA and CBSAs nest within combined areas, the higher level codes exist in the record layouts for the subordinate entity types.

5-46

5.13.1 Combined New England City and Town Area (CNECTA) National Shapefile Record Layout (Current) File Name: tl_2012_us_cnecta.shp CNECTAFP GEOID NAME NAMELSAD LSAD MTFCC ALAND AWATER INTPTLAT INTPTLON 3 3 100 100 2 5 14 14 11 12 String String String String String String Number Number String String Current combined New England city and town area code Current New England city and town area identifier, combined New England city and town area code Current combined New England city and town area name Current name and the translated legal/statistical area description for combined New England city and town area Current legal/statistical area description code for combined New England city and town area MAF/TIGER feature class code (G3200) Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5.13.2 Combined Statistical Area (CSA) National Shapefile Record Layout (Current) File Name: tl_2012_us_csa.shp CSAFP GEOID NAME NAMELSAD LSAD MTFCC ALAND AWATER INTPTLAT INTPTLON 3 3 100 100 2 5 14 14 11 12 String String String String String String Number Number String String Current combined statistical area code Combined statistical area identifier, combined statistical area code Current combined statistical area name Current name and the translated legal/statistical area description for combined statistical area Current legal/statistical area description code for combined statistical area MAF/TIGER feature class code (G3100) Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5.13.3 Metropolitan Division National Shapefile Record Layout (Current) File Name: tl_2012_us_metdiv.shp CSAFP CBSAFP METDIVFP GEOID NAME NAMELSAD LSAD 3 5 5 10 100 100 2 String String String String String String String Current combined statistical area code Current metropolitan statistical area/micropolitan statistical area code Current metropolitan division code Metropolitan division identifier; a concatenation of metropolitan statistical area/micropolitan statistical area code and metropolitan division code Current metropolitan division name Current name and the translated legal/statistical area description for metropolitan division Current legal/statistical area description code for metropolitan division

5-47

MTFCC ALAND AWATER INTPTLAT INTPTLON

5 14 14 11 12

String Number Number String String

MAF/TIGER feature class code (G3120) Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5.13.4 Metropolitan Statistical Area/Micropolitan Statistical Area (CBSA) National Shapefile Record Layout (Current) File Name: tl_2012_us_cbsa.shp CSAFP CBSAFP GEOID NAME NAMELSAD LSAD MEMI MTFCC ALAND AWATER INTPTLAT INTPTLON 3 5 5 100 100 2 1 5 14 14 11 12 String String String String String String String String Number Number String String Current combined statistical area code, if applicable Current metropolitan statistical area/micropolitan statistical area code Metropolitan statistical area/micropolitan statistical area identifier, metropolitan statistical area/micropolitan statistical area code Current metropolitan statistical area/micropolitan statistical area name Current name and the translated legal/statistical area description for metropolitan statistical area/micropolitan statistical area Current legal/statistical area description code for metropolitan statistical area/micropolitan statistical area Current metropolitan/micropolitan status indicator MAF/TIGER feature class code (G3110) Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5.13.5 New England City and Town Area (NECTA) Shapefile National Record Layout (Current) File Name: tl_2012_us_necta.shp Current combined New England city and town area code, if applicable Current New England city and town area code New England city and town area identifier, New England city and town area code Current New England city and town area name Current name and the translated legal/statistical area description for New England city and town area Current legal/statistical area description code for New England city and town area Current New England city and town area metropolitan/micropolitan status indicator MAF/TIGER feature class code (G3210) Current land area Current water area Current latitude of the internal point Current longitude of the internal point

CNECTAFP NECTAFP GEOID NAME NAMELSAD LSAD NMEMI MTFCC ALAND AWATER INTPTLAT INTPTLON 5-48

3 5 5 100 100 2 1 5 14 14 11 12

String String String String String String String String Number Number String String

5.13.6 New England City and Town Area (NECTA) Division Shapefile National Record Layout (Current) File Name: tl_2012_us_nectadiv.shp CNECTAFP NECTAFP NCTADVFP GEOID NAME NAMELSAD LSAD MTFCC ALAND AWATER INTPTLAT INTPTLON 3 5 5 10 100 100 2 5 14 14 11 12 String String String String String String String String Number Number String String Current combined New England city and town area code, if applicable Current New England city and town area code Current New England city and town area division code New England city and town area division identifier; a concatenation of New England city and town area code and New England city and town area division code Current New England city and town area division name Current name and the translated legal/statistical area description for New England city and town area division Current legal/statistical area description code for New England city and town area division MAF/TIGER feature class code (G3220) Current land area Current water area Current latitude of the internal point Current longitude of the internal point

Military installation geography and attributes are available in the following shapefile: Military Installation National 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 Section 5.10, Landmarks (Area and Point). This file does not include the three point landmarks identified as military installation features in the MAF/TIGER database. These point landmarks are included in the Point Landmark Shapefile. Although almost all military installations have assigned 8-character National Standard (ANSI) codes, the Census Bureau has not loaded any of this data into the MAF/TIGER database. The 2010 military shapefiles do not include this ANSICODE. 5.14.1 Military Installation National Shapefile Record Layout File Name: tl_2012_us_mil.shp ANSICODE AREAID FULLNAME MTFCC ALAND AWATER 8 22 100 5 14 14 String String String String Number Number Official code for the landmark for use by federal agencies for data transfer and dissemination Area landmark identifier 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 MAF/TIGER feature class code Land area Water area 5-49

INTPTLAT INTPTLON

11 12

String String

Latitude of the internal point Longitude of the internal point

Place geography and attributes are available by state in the following shapefile: Place State-based Shapefile (Current) 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 January 1, 2012, 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 (MCD), 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, but never across state 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 equivalents of counties) Towns in the New England states, New York, and Wisconsin (treated as MCDs) The boroughs in New York (treated as MCDs)

Census Designated Places (CDPs) are 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 partners as part of the Census Bureaus Participant Statistical Areas Program, or in cooperation with tribal officials as part of the Tribal Statistical Areas Program. The boundaries of CDPs, 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. In the nine states of the Northeast (Connecticut, Maine, Massachusetts, New Hampshire, New Jersey, New York, Pennsylvania, Rhode Island, and Vermont) as well as Michigan, Minnesota, and Wisconsin, a CDP may represent a densely settled concentration of population within a town or township; in other instances, an entire town or township may be defined as a CDP. Hawaii is the only state that has no incorporated places recognized by the Census Bureau. All places shown in 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 CDP's. Place CodesThe 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"). All places also have an eight-character ANSI code. Dependent and Independent PlacesDepending 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.

5-50

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 are always dependent within county subdivisions and all places are dependent within statistical county subdivisions. Independent Cities- Baltimore city, MD; St. Louis city, MO; Carson city, NV; and all 39 cities in Virginia are not part of any surrounding county and are treated as both equivalent to a county and an MCD (in MCD states). The FIPS code for St. Louis city is the same as the FIPS county subdivision code. All the others have differing FIPS place and county subdivision codes. At the county level, independent cities have a three-digit county code of 500 or higher. Geographic Corridors and Offset Geographic BoundariesA 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. Figures 5 and 6 depict geographic corridors and geographic offset limits. Geographic corridor address ranges are related by using the All Lines Shapefile and Address Ranges Relationship File permanent edge identifier (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. By assigning the address range to the geographic corridor edge rather than the road edge, structures will geocode 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.

5-51

5-52

5-53

5.15.1 Place State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_place.shp STATEFP PLACEFP PLACENS GEOID NAME NAMELSAD LSAD CLASSFP PCICBSA PCINECTA MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 5 8 7 100 100 2 2 1 1 5 1 14 14 11 12 String String String String String String String String String String String String Number Number String String Current state FIPS code Current place FIPS code Current place ANSI code Place identifier; a concatenation of the current state FIPS code and place FIPS code Current place name Current name and the translated legal/statistical area description for place Current legal/statistical area description code for place Current FIPS class code Current metropolitan or micropolitan statistical area principal city indicator Current New England city and town area principal city indicator G4110 (incorporated place) and G4210 (census designated place) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5-54

Public use microdata area geography and attributes are available by state in the following shapefile: Public Use Microdata Area (PUMA) State-based Shapefile (2010 Census) Public Use Microdata Areas (PUMAs) are decennial census areas that have been defined for the tabulation and dissemination of Public Use Microdata Sample (PUMS) data, American Community Survey (ACS), and ACS period estimates. For the 2010 Census, the State Data Centers (SDCs) in each state, the District of Columbia, and the Commonwealth of Puerto Rico were given the opportunity to delineate PUMAs within their state or statistically equivalent entity. All PUMAs must nest within states and have a minimum population threshold of 100,000 persons. 2010 PUMAs were built on census tracts, and cover the entirety of the United States, Puerto Rico, Guam, and the U.S. Virgin Islands. Because they do not meet the minimum population requirement, the Commonwealth of the Northern Mariana Islands and American Samoa do not contain any 2010 PUMAs. For more detailed information about PUMAs, please visit the 2010 Public Use Microdata Areas (PUMAs) website at [Link] 5.16.1 Public Use Microdata Area (PUMA) State-based Shapefile Record Layout (2010 Census) File Name: tl_2010_<state FIPS>_PUMA10.shp STATEFP10 PUMACE10 GEOID10 NAMELSAD10 MTFCC10 FUNCSTAT10 ALAND10 AWATER10 INTPTLAT10 INTPTLON10 2 5 7 100 5 1 14 14 11 12 String String String String String String Number Number String String 2010 Census state FIPS code 2010 Census Public Use Microdata Area code 2010 Census nation-based Public Use Microdata Area code; a concatenation of 2010 Census state FIPS code and Public Use Microdata Area code 2010 Census translated legal/statistical area description code and Public Use Microdata Area name MAF/TIGER feature class code 2010 Census functional status 2010 Census land area 2010 Census water area 2010 Census latitude of the internal point 2010 Census longitude of the internal point

School district geography and attributes are available by state in the following shapefiles: Elementary School District State-based Shapefile (Current) Secondary School District State-based Shapefile (Current) Unified School District State-based Shapefile (Current) School Districts are single-purpose administrative units within which local officials provide public educational services for the area's residents. The Census Bureau obtains school district boundaries, names, local education agency codes, grade ranges, and school district levels biennially from state school officials. The Census Bureau collects this information for the primary purpose of providing the U.S. Department of Education with annual 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 2012 TIGER/Line Shapefiles include separate shapefiles for elementary, secondary, and unified school districts. The 2012 shapefiles contain information from the 2011-2012 school year. The 2011-2012 school districts represent districts in operation as of January 1, 2012.

5-55

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 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 addition to regular functioning school districts, the TIGER/Line Shapefiles contain pseudo-school districts (see description below). The Census Bureaus representation of school districts is based on the grade ranges for which th e school district is financially responsible, which may or may not be the grade ranges that a school district operates. (The grade range that reflects financial responsibility is important for the allocation of Title 1 funds.) A typical example would be a school district that operates schools for children in grades Kindergarten (KG)-8, and pays for a neighboring school district to educate children in grades 912. The first school district is operationally responsible for grades K-8, but financially responsible for grades KG-12. Therefore, the Census Bureau would define the grade range for that school district as KG-12. If an elementary school district is financially responsible for grades KG-12 or Pre-Kindergarten (PK)12, there will be no secondary school district represented for that area. In cases, where an elementary school district is financially responsible for only lower grades, there is generally a secondary school district that is financially responsible for providing educational services for the upper grades. The following are exceptions to the above information: The Census Bureau depicts the State of Hawaii as one unified school district and the five counties that represent the five boroughs of New York city as one unified school district. In the school district shapefiles, California, Georgia, Illinois, Kentucky, Massachusetts, Oklahoma, South Carolina, Tennessee, Texas, and Vermont 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 financially responsible for less than the entire KG-12 grade range. In these areas, there were no regular functioning 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). A list of these pseudo-secondary school districts and their codes appears in Appendix B. School District CodesThe 2012 TIGER/Line Shapefiles contain 5-character numeric school district codes. The value 99997 is the school district code assigned to water or land, where no official school district is defined by a state. The school district codes are the local education agency codes used by the U.S. Department of Education and are unique within a state. School District Names The names of school districts include their description and no other field (NAMELSAD) is required. 5.17.1 Elementary School District State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_elsd.shp STATEFP ELSDLEA GEOID NAME LSAD LOGRADE 5-56 2 5 7 100 2 2 String String String String String String Current state FIPS code Current elementary school district local education agency code School district identifier; a concatenation of the current state FIPS code and elementary school district local education agency code Current elementary school district name Current legal/statistical area description code for elementary school district Current lowest grade covered by school district

HIGRADE MTFCC SDTYP FUNCSTAT ALAND AWATER INTPTLAT INTPTLON

2 5 1 1 14 14 11 12

String String String String Number Number String String

Current highest grade covered by school district MAF/TIGER feature class code (G5400) Current school district type Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5.17.2 Secondary School District State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_scsd.shp STATEFP SCSDLEA GEOID NAME LSAD LOGRADE HIGRADE MTFCC SDTYP FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 5 7 100 2 2 2 5 1 1 14 14 11 12 String String String String String String String String String String Number Number String String Current state FIPS code Current secondary school district local education agency code School district identifier; a concatenation of the current state FIPS code and secondary school district local education agency code Current secondary school district name Current legal/statistical area description code for secondary school district Current lowest grade covered by school district Current highest grade covered by school district MAF/TIGER feature class code (G5410) Current school district type Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5.17.3 Unified School District State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_unsd.shp STATEFP UNSDLEA GEOID NAME LSAD LOGRADE HIGRADE MTFCC SDTYP FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 5 7 100 2 2 2 5 1 1 14 14 11 12 String String String String String String String String String String Number Number String String Current state FIPS code Current unified school district local education agency code School district identifier; a concatenation of the current state FIPS code and unified school district local education agency code Current unified school district name Current legal/statistical area description code for unified school district Current lowest grade covered by school district Current highest grade covered by school district MAF/TIGER feature class code (G5420) Current school district type Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5-57

State and equivalent entity geography and attributes are available in the following shapefile: State and Equivalent Entity National Shapefile (Current) 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 U.S. Virgin Islands) as the statistical equivalents of states for the purpose of data presentation. Census regions and divisions consist of groupings of states and equivalent entities. The codes for these areas are included in the state shapefiles and the state records can be merged to form those areas. 5.18.1 State and Equivalent Entity National Shapefile Record Layout (Current) File Name: tl_2012_us_state.shp REGION DIVISION STATEFP STATENS GEOID STUSPS NAME LSAD MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 2 2 8 2 2 100 2 5 1 14 14 11 12 String String String String String String String String String String Number Number String String Current region code Current division code Current state FIPS code Current state ANSI code State identifier; state FIPS code Current United States Postal Service state abbreviation Current state name Current legal/statistical area description code for state MAF/TIGER feature class code (G4000) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

State legislative district geography and attributes are available by state in the following shapefiles: State Legislative District Lower Chamber (SLDL) State-based Shapefile (Current) State Legislative District Upper Chamber (SLDU) State-based Shapefile (Current) State legislative districts are the areas from which members are elected to state or equivalent entity legislatures. The state legislative district embodies the upper (senateSLDU) and lower (houseSLDL) chambers of the state legislature. The Census Bureau first reported data for state legislative districts as part of the 2000 Public Law (P.L.) 94-171 Redistricting Data File for the states that choose to submit them. State legislative districts (2010 Election Cycle) States participating in Phase 1 of the 2010 Census Redistricting Data Program, as part of P.L. 94-171, voluntarily provided the Census Bureau with the 2006 election cycle boundaries, codes, and in some cases names for their state legislative districts. All 50 states, plus the District of Columbia and Puerto Rico, participated in Phase 1. States subsequently provided legal changes and/or corrections to those plans through the Census Bureaus Redistricting Data Office or as part of Phase 2 of the 2010 Redistricting Data Program. 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 are no data by the lower house of the state legislative districts for either Nebraska or the District of Columbia.

5-58

State Legislative District Codes A unique 3-character census code, identified by state participants, is assigned to each state legislative district upper (senate) and lower (house) within a state. In Connecticut, Hawaii, Illinois, Louisiana, Maine, Maryland, Massachusetts, New Jersey, Ohio, and Puerto Rico, the state participant did not assign the current state legislative districts to cover all of the state or equivalent area. In states other than Maryland, the code ZZZ has been assigned to areas with no state legislative districts defined (usually large water bodies). These unassigned areas are treated within state as a single state legislative district 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 state legislative district defined. These unassigned areas are treated within county as a single state legislative district for purposes of data presentation. 5.19.1 State Legislative District Lower Chamber (SLDL) State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_sldl.shp STATEFP SLDLST GEOID NAMELSAD LSAD LSY MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 3 5 100 2 4 5 1 14 14 11 12 String String String String String String String String Number Number String String Current state FIPS code Current state legislative district lower chamber code State legislative district lower chamber identifier; a concatenation of the current state FIPS code and state legislative district lower chamber code Current name and the translated legal/statistical area description for state legislative district lower chamber Current legal/statistical area description code for state legislative district lower chamber Legislative session year MAF/TIGER feature class code (G5220) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5.19.2 State Legislative District Upper Chamber (SLDU) State-based Shapefile Record Layout (Current) File Name: tl_2012_<state FIPS>_sldu.shp STATEFP SLDUST GEOID NAMELSAD LSAD LSY MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 3 5 100 2 4 5 1 14 14 11 12 String String String String String String String String Number Number String String Current state FIPS code Current state legislative district upper chamber code State legislative district upper chamber identifier; a concatenation of the current state FIPS code and state legislative district upper chamber code Current name and the translated legal/statistical area description for state legislative district upper chamber Current legal/statistical area description code for state legislative district upper chamber Legislative session year MAF/TIGER feature class code (G5210) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

5-59

Subminor civil division (Sub-MCD) geography and attributes are available in Puerto Rico in the following shapefile: SubMinor Civil Division State-based Shapefile (Current) For the 2012 TIGER/Line Shapefiles, sub-MCDs are available in Puerto Rico. The sub-MCDs in Puerto Rico are termed subbarrios and are legally defined subdivisions of minor civil divisions (MCDs) named barriospueblo and barrios. Subbarrios do not exist within every MCD in Puerto Rico nor do they necessarily cover the entire area of an MCD where they do exist. The boundaries of the subbarrios are as of January 1, 2012 and were provided to the Census Bureau by the Puerto Rico Planning Board. The 2012 TIGER/Line Shapefiles contain the 5-character FIPS codes for sub-MCDs as well as 8-character ANSI codes. 5.20.1 Subminor Civil Division State-based Shapefile Record Layout (Current) File Name: tl_2012_72_submcd.shp STATEFP COUNTYFP COUSUBFP SUBMCDFP SUBMCDNS GEOID NAME NAMELSAD LSAD CLASSFP MTFCC FUNCSTAT ALAND AWATER INTPTLAT INTPTLON 2 3 5 5 8 15 100 100 2 2 5 1 14 14 11 12 String String String String String String String String String String String String Number Number String String Current state FIPS code Current county FIPS code Current county subdivision FIPS code Current subminor civil division FIPS code Current subminor civil division ANSI code Subminor civil division identifier; a concatenation of current state FIPS code, county FIPS code, county subdivision FIPS code, and subminor civil division FIPS code Current subminor civil division name Current name and the translated legal/statistical area description for subminor civil division Current legal/statistical area description code for subminor civil division Current FIPS class code MAF/TIGER feature class code (G4060) Current functional status Current land area Current water area Current latitude of the internal point Current longitude of the internal point

Topological face information is available in the following shapefile: Topological Faces (Polygons with All Geocodes) Shapefile The Topological Faces shapefile contains the attributes of each topological primitive face. 5.21.1 Topological Faces (Polygons with All Geocodes) Shapefile Record Layout File Name: tl_2012_<state-county FIPS>_faces.shp TFID 10 Integer Permanent face ID

5-60

STATEFP10 COUNTYFP10 TRACTCE10 BLKGRPCE10 BLOCKCE10 VTDST10 ZCTA5CE10 UACE10 UGACE10 PUMACE10 STATEFP COUNTYFP TRACTCE BLKGRPCE BLOCKCE SUFFIX1CE COUSUBFP SUBMCDFP ESTATEFP CONCTYFP PLACEFP AIANNHFP AIANNHCE COMPTYP TRSUBFP TRSUBCE ANRCFP TTRACTCE TBLKGPCE ELSDLEA SCSDLEA UNSDLEA CD112FP SLDUST SLDLST CSAFP CBSAFP METDIVFP CNECTAFP NECTAFP NCTADVFP LWFLAG OFFSET ATOTAL INTPTLAT INTPTLON

2 3 6 1 4 6 5 5 5 5 2 3 6 1 4 1 5 5 5 5 5 5 4 1 5 3 5 6 1 5 5 5 2 3 3 3 5 5 3 5 5 1 1 14 11 12

String String String String String String String String String String String String String String String String String String String String String Number String String Number String String String String String String String String String String String String String String String String String String Number String String

2010 Census state FIPS code 2010 Census county FIPS code 2010 Census census tract code 2010 Census block group number 2010 Census tabulation block number 2010 Census voting district code 2010 Census 5-digit ZCTA code 2010 Census urban area code 2010 Census urban growth area code 2010 Census public use microdata area code Current state FIPS code Current county FIPS code Current census tract code Current block group number Current tabulation block number Current Census block suffix 1 Current county subdivision FIPS code Current subminor civil division FIPS code Current estate FIPS code Current consolidated city FIPS code Current place FIPS code Current American Indian/Alaska Native/Native Hawaiian area FIPS code Current American Indian/Alaska Native/Native Hawaiian area census code Current American Indian/Alaska Native/Native Hawaiian area reservation/statistical area or offreservation trust land Hawaiian home land indicator Current American Indian tribal subdivision FIPS code Current American Indian tribal subdivision code Current Alaska Native Regional Corporation FIPS code Current tribal census tract code Current tribal block group letter Current elementary school district local education agency code Current secondary school district local education agency code Current unified school district local education agency code 112th congressional district FIPS code Current state legislative district upper chamber code Current state legislative district lower chamber code Current Combined statistical area code Current Metropolitan statistical area/micropolitan statistical area code Current Metropolitan division code Current Combined New England city and town area code (New England states only) Current New England city and town area code (New England states only) Current New England city and town area division code (New England states only) Land/water flag Geographic corridor/offset flag Total Area Latitude of the internal point Longitude of the internal point

5-61

Urban area geography and attributes are available in the following shapefile: Urban Area National Shapefile (2010 Census) For the 2010 Census, the Census Bureau classified as urban, all territory, population, and housing units located within urbanized areas (UAs) and urban clusters (UCs), both defined using the same criteria. The Census Bureau delineates UA and UC boundaries that represent densely developed territory, encompassing residential, commercial, and other non-residential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the u rban footprint. Rural consists of all territory, population, and housing units located outside of UAs and UCs. For the 2010 Census the urban and rural classification was applied to the 50 states, the District of Columbia and Puerto Rico. Per agreements with the Island Areas, minor modifications to the classification were implemented when applied to American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands. Urbanized Areas (UAs)An urbanized area consists of densely developed 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. The Census Bureau first introduced the urbanized area concept for the 1950 Census. Urban Clusters (UCs)An urban cluster consists of densely developed territory that has at least 2,500 people but fewer than 50,000 people. The Census Bureau first introduced the UC concept for Census 2000 to provide a more consistent and accurate measure of urban population, housing, and territory throughout the United States, Puerto Rico, and the Island Areas. Based on agreements with Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands, all qualifying urban areas are identified as urban clusters regardless of their final population counts. Thus urban clusters may exceed 50,000 people in these areas. Urban Area Titles and CodesThe title of each UA and UC may contain up to three incorporated place or census designated place (CDP) names, and will include the two-letter U.S. Postal Service abbreviation for each state or statistically equivalent entity into which the UA or UC extends. However, if the UA or UC does not contain an incorporated place or CDP, the urban area title will include the single name of a minor civil division or populated place recognized by the U.S. Geological Surveys 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. 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. 5.22.1 Urban Area (UA) National Shapefile Record Layout (2010 Census) File Name: tl_2010_<us>_uac10.shp UACE10 GEOID10 NAME10 NAMELSAD10 LSAD10 MTFCC10 UATYP10 FUNCSTAT10 5 5 100 100 2 5 1 1 String String String String String String String String 2010 Census urban area code 2010 Census urban area identifier, 2010 Census urban area code 2010 Census urban area name 2010 Census name and the translated legal/statistical area description for urban area 2010 Census legal/statistical area description code for urban area MAF/TIGER feature class code (G3500) 2010 Census urban area type 2010 Census functional status

5-62

ALAND10 AWATER10 INTPTLAT10 INTPTLON10

14 14 11 12

Number Number String String

2010 2010 2010 2010

Census Census Census Census

land area water area latitude of the internal point longitude of the internal point

Urban growth area geography and attributes are only available in the states of Oregon and Washington in the following shapefile: Urban Growth Area (UGA) State-based Shapefile (2010 Census) Urban growth areas are legally defined entities in Oregon and Washington that the Census Bureau includes in the MAF/TIGER database in agreement with the states. Urban Growth Areas, which are defined around incorporated places, are used to regulate urban growth. Urban growth area boundaries, which need not follow visible features, are delineated cooperatively by state and local officials in Oregon and Washington and then confirmed in state law. The Census Bureau collected boundaries for urban growth areas from the State of Oregon as part of a pilot project for Census 2000. The pilot project was extended to the State of Washington for the 2010 Census. Each urban growth area is identified by a 5-digit numeric census code, usually associated with the incorporated place for which the urban growth area is named. There have been updates to the urban growth area where spatial changes may have affected the Census 2000 data in minor instances; however; there have been significant changes to update Oregon and Washington urban growth areas prior to 2010. 5.23.1 Urban Growth Area (UGA) Shapefile Record Layout (2010 Census) File Name: tl_2010_<state FIPS>_uga10.shp STATEFP10 UGACE10 UGATYP10 GEOID10 NAME10 NAMELSAD10 LSAD10 MTFCC10 FUNCSTAT10 ALAND10 AWATER10 INTPTLAT10 INTPTLON10 2 5 1 7 100 100 2 5 1 14 14 11 12 String String String String String String String String String Number Number String String 2010 Census state FIPS code 2010 Census urban growth area code 2010 Census urban growth area type Urban growth identifier; a concatenation of state FIPS code and urban growth area code 2010 Census urban growth area name 2010 Census name and the translated legal/statistical area description for urban growth area 2010 Census legal/statistical area description code for urban growth area MAF/TIGER feature class code (G6330) 2010 Census functional status 2010 Census land area 2010 Census water area 2010 Census latitude of the internal point 2010 Census longitude of the internal point

Voting district geography and attributes are available by state in the following shapefile: Voting District (VTD) State-based Shapefile (2010 Census) Voting district is the generic name for geographic entities such as precincts, wards, and election districts established by state and local governments for the purpose of conducting elections. States participating in the Census 2010 Redistricting Data Programs as part of Public Law 94-171 (1975) provided the Census Bureau with boundaries, codes, and names for their voting districts.

5-63

Census 2010 Voting Districts For 2010, pseudo voting districts were identified in instances when participating sta tes chose to identify sub-areas within a voting district or when the VTD did not follow the legally described boundary (for example, in states that require that VTD boundaries follow visible features for purposes of tabulating and presenting census data). The Census Bureau identified these smaller areas as pseudo voting districts, with a P in the voting district indicator (VTDI10) field. Where the participating state indicated that the voting districts they submitted exactly match the precincts or other election districts in the state, the Census Bureau indicates the voting districts are actual by populating the VTDI10 field with an A. In cases where a participating state did not indicate to the Census Bureau whether the voting district was actual or pseudo, the VTDI10 field defaults to P. Rhode Island did not participate in Phase 2 of the 2010 Census Redistricting Data Program. Montana and Oregon participated in Phase 2, but did not provide voting districts for every county in their state. Kentucky participated in other aspects of Phase 2, but did not provide any voting districts for their state. 5.24.1 Voting District (VTD) Shapefile Record Layout (2010 Census) File Name: tl_2010_<state FIPS>_vtd10.shp STATEFP10 COUNTYFP10 VTDST10 GEOID10 VTDI10 NAME10 NAMELSAD10 LSAD10 MTFCC10 FUNCSTAT10 ALAND10 AWATER10 INTPTLAT10 INTPTLON10 2 3 6 11 1 100 100 2 5 1 14 14 11 12 String String String String String String String String String String Number Number String String 2010 Census state FIPS code 2010 Census county FIPS code 2010 Census voting district code Voting district identifier; a concatenation of the 2010 Census state FIPS code, county FIPS code, and voting district code 2010 Census voting district indicator 2010 Census voting district name 2010 Census name and the translated legal/statistical area description for voting district 2010 Census legal/statistical area description code for voting district MAF/TIGER feature class code (G5240) 2010 Census functional status 2010 Census land area 2010 Census water area 2010 Census latitude of the internal point 2010 Census longitude of the internal point

ZIP Code tabulation area geography and attributes are available in the following shapefile: 5-Digit ZIP Code Tabulation Area (ZCTA5) National Shapefile (2010 Census) ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) fivedigit ZIP Code service areas that the Census Bureau creates using whole blocks to present statistical data from censuses and surveys. The Census Bureau defines ZCTAs by allocating each block that contains addresses to a single Code Tabulation Area, usually to the ZCTA that reflects the most frequently occurring ZIP Code for the addresses within that tabulation block. Blocks that do not contain addresses but are completely surrounded by a single Code Tabulation Area (enclaves) are assigned to the surrounding ZCTA; those surrounded by multiple ZCTAs will be added to a single ZCTA based on limited buffering performed between multiple ZCTAs. The Census Bureau identifies five-digit ZIP Code Tabulation Areas using a five-character numeric code that represents the most frequently occurring USPS ZIP Code within that ZCTA, and this code may contain leading zeros.

5-64

There are significant changes to the 2010 Code Tabulation Areas delineation from that used in 2000. For 2010 only legitimate five-digit areas are defined so there is no longer full nation-wide coverage. The 2010 ZCTAs will better represent the actual Zip Code service areas because the Census Bureau initiated a process before creation of 2010 blocks to add block boundaries that split polygons with large numbers of addresses using different ZIP Codes. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Code Tabulation Areas process used primarily residential addresses and was biased towards ZIP Codes used for city-style mail delivery, thus there may be ZIP Codes that are primarily nonresidential or boxes only that may not have a corresponding ZCTA. ZIP Code Tabulation Area CodesThe Census Bureau identifies 5-digit ZCTAs using a five-character numeric code. 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. 5.25.1 5-Digit ZIP Code Tabulation Area (ZCTA5) National Shapefile Record Layout (2010 Census) File Name: tl_2010_us_zcta510.shp ZCTA5CE10 GEOID10 CLASSFP10 MTFCC10 FUNCSTAT10 ALAND10 AWATER10 INTPTLAT10 INTPTLON10 5 5 2 5 1 14 14 11 12 String String String String String Number Number String String 2010 Census 5-digit ZIP Code Tabulation Area code 2010 Census 5-digit ZIP Code Tabulation Area identifier, 2010 Census 5-digit ZIP Code Tabulation Area code 2010 Census FIPS 55 class code MAF/TIGER feature class code (G6350) 2010 Census functional status 2010 Census land area 2010 Census water area 2010 Census latitude of the internal point 2010 Census longitude of the internal point

5-65