U.S. Census Bureau TIGER/Line Files, 1990, 2000-2002, 2004-2009
Principal Investigator(s): View help for Principal Investigator(s) United States Department of Commerce. Bureau of the Census
Version: View help for Version V1
Name | File Type | Size | Last Modified |
---|---|---|---|
Documentation | 12/23/2021 02:23:PM | ||
|
application/zip | 21.6 GB | 01/03/2022 05:57:AM |
Login to generate citation for this folder.
To view the citation for the overall project, see http://doi.org/10.3886/E158022V1.
Folder Description
Summary:
View help for Summary
The 2007 TIGER/Line Shapefiles contain current geographic areas (boundaries of governmental units as of January 1, 2007) and Census 2000 vintage geography. The shapefiles also contain some additional post January 1, 2007 feature updates reported in the Boundary and Annexation Survey (BAS). The 2007 TIGER/Line Shapefiles contain realigned street feature coordinates as a result of the MAF/TIGER Accuracy Improvement Project. The Census Bureau is providing a list of counties that have not been realigned via the MTAIP process on their Web site, which is the source of the material included here.
The MAF/TIGER database provides support for the following:
2007 First Edition TIGER/Line Files
The TIGER/Line Shapefiles are extracts containing selected geographic and cartographic information from the Census Bureau's MAF/TIGER® (Master Address File / Topologically Integrated Geographic Encoding and Referencing) database. The MAF/TIGER database was developed at the Census Bureau to support a variety of geographic programs and operations including functions such as mapping, geocoding, and geographic reference files that are used in decennial and economic censuses and sample survey programs. Spatial data for geographic features such as roads, railroads, rivers, and lakes, as well as legal and statistical geographic areas are included in the product. Other information about these features, such as the name, the type of feature, address ranges, and the geographic relationship to other features, also are included. The TIGER/Line Shapefiles are made available to the public and are typically used to provide the digital map base for a Geographic Information System or for mapping software.The 2007 TIGER/Line Shapefiles contain current geographic areas (boundaries of governmental units as of January 1, 2007) and Census 2000 vintage geography. The shapefiles also contain some additional post January 1, 2007 feature updates reported in the Boundary and Annexation Survey (BAS). The 2007 TIGER/Line Shapefiles contain realigned street feature coordinates as a result of the MAF/TIGER Accuracy Improvement Project. The Census Bureau is providing a list of counties that have not been realigned via the MTAIP process on their Web site, which is the source of the material included here.
The MAF/TIGER database provides support for the following:
- Creation and maintenance of a digital geographic database that includes complete coverage of the United States, Puerto Rico, and the Island Areas
- Production of maps from the MAF/TIGER database for all Census Bureau enumeration and publication programs
- Assigning individual addresses to geographic entities and census blocks based on polygons formed by features such as roads and streams
Nation-Based Files
Entities that are defined independently from states and counties, such as American Indian Areas, are available in nation-based shapefiles that encompass the entire country. The following layers are included:
- American Indian/Alaska Native/Native Hawaiian Area (Census 2000 and current)
- American Indian Tribal Subdivision (Census 2000 and current)
- Combined New England City and Town Area (current)
- Combined Statistical Area (current)
- Metropolitan Division (current)
- New England City and Town Area (current)
- New England City and Town Area Division (current)
- State and Equivalent (Census 2000 and current)
- 3-Digit ZIP Code Tabulation Area (Census 2000)
- 5-Digit ZIP Code Tabulation Area (Census 2000)
State-Based Files
Entities such as school districts and congressional districts that are defined within states and can cross county boundaries are represented in state-based shapefiles. The following layers are included:
- Alaska Native Regional Corporation (Census 2000 and current)
- 110th Congressional District
- 108th Congressional District
- 106th Congressional District
- Consolidated City (Census 2000 and current)
- County and Equivalent (Census 2000 and current)
- Place (Census 2000 and current)
- 1-Percent Public Use Microdata Area (Census 2000)
- 5- or 10-Percent Public Use Microdata Area (Census 2000)
- Elementary School District (Census 2000 and current)
- Secondary School District (Census 2000 and current)
- Unified School District (Census 2000 and current)
- State Legislative District--Lower Chamber (Census 2000 and current)
- State Legislative District--Upper Chamber (Census 2000 and current)
- Urban Growth Area (Census 2000)
County-Based Files
Entities that are defined within counties and do not cross county or state lines such as census tracts, block groups, and blocks are represented in county-based shapefiles (i.e. one shapefile for each county). The following layers are included:
- All Lines (current)
- Area Hydrography (current)
- Area Landmark (current)
- Point Landmark (current)
- Block (Census 2000 and current)
- Block Group (Census 2000)
- Census Tract (Census 2000)
- County Subdivision (Census 2000 and current)
- Subbarrio (Census 2000 and current)
- Traffic Analysis Zone (Census 2000)
- Voting District (Census 2000)
- Address Range-Feature Name Relationship File (current)
- Address Ranges Relationship File (current)
- Feature Names Relationship File (current)
- Topological Faces (2-Cells With All Geocodes) Relationship File (current)
- Topological Faces-Area Landmark Relationship File (current)
- Topological Faces-Area Hydrography Relationship File (current)
American Indian Area-Based Files
The following layers are available by American Indian Area (see the AITS_BY_AIA folder):
- American Indian Tribal Subdivision (Census 2000 and current)
- .shp - the file that stores the feature geometry
- .shx - the file that stores the index of the feature geometry
- .dbf - the dBASE, or database, file that stores attribute information
- .prj - the file that stores the coordinate system information
- .shp.xml - the file that stores the metadata
- .dbf - the dBASE, or database, file that stores additional attribute information
- .dbf.xml - the file that stores the metadata
File Naming Conventions
The name of each file is:fe_2007_<extent>_<layer>.<ext> fe = internal US Census Bureau use 2007 = the version of the files <extent> = entity ID code, variable length The entity ID code identifies the geographic extent by specific entity for which the file contains data. It is of variable length depending on the type of file: Nation-based: 2-characters, "us" State-based: 2-digit numeric state FIPS code County-based: 5-digit numeric state-county FIPS code American Indian area-based: 4-digit American Indian area census code <layer> = layer tag, variable length The layer tag specifies the type of geography or feature the file contains. If '00' appears at the end of the layer tag, the file contains Census 2000 geography. If '00' does not appear, the file contains current geography. <ext> = the file extension
Examples
- Nation-based shapefile: Current New England City and Town Area (NECTA) shapefile
- fe_2007_us_necta.shp
- State-based shapefile: Census 2000 County and Equivalent shapefile for Maryland
- fe_2007_24_county00.shp
- County-based shapefile: Current Block shapefile for Worcester County, MA
- fe_2007_25027_tabblock.shp
- County-based shapefile: Point Landmark shapefile for Hughes County, OK
- fe_2007_40063_pointlm.shp
- American Indian Area-based Shapefile: Census 2000 American Indian Tribal Subdivision shapefile for Bois Forte Reservation
- fe_2007_0335_aitsaia00.shp
Related Publications
Published Versions
Report a Problem
Found a serious problem with the data, such as disclosure risk or copyrighted content? Let us know.
This material is distributed exactly as it arrived from the data depositor. ICPSR has not checked or processed this material. Users should consult the investigator(s) if further information is desired.