U.S. Department of Commerce

Geography

You are here: Census.gov › Geography › Maps & Data › TIGER Products › TIGER/Line® Shapefiles and TIGER/Line® Files
Skip top of page navigation
Skip top of page navigation

Maps & Data

Maps

Data

TIGER/Line® Shapefiles and TIGER/Line® Files

Tiger

  • Spatial extracts from the Census Bureau's MAF/TIGER database, containing features such as roads, railroads, rivers, as well as legal and statistical geographic areas.
  • 2007 & later are in shapefile format. 2006 & earlier are in TIGER/Line format.
  • Available to the public for no charge and are typically used to provide the digital map base for a Geographic Information System or for mapping software.
  • For use with geographic information system (GIS) software.
  • Do not include demographic data, but they contain geographic entity codes that can be linked to the Census Bureau’s demographic data, available on American FactFinder.
  • Frequently Asked Questions
  • Working with TIGER/Line Shapefiles How-To Guides

113th Congressional District Shapefiles

All legal boundaries and names are as of January 1, 2010, with the exception of the 113th Congressional Districts and the State Legislative Districts, which are as of January 1, 2013.

Download

Technical Documentation

File Availability

  • Shapefiles are released in one of three types of coverages:
    • Nation-based
    • State-based
    • County-based
  • The table below lists each type of geography and the coverage(s) at which each is available.

113th Congressional District TIGER/Line Shapefiles Availability
Layer
Nation-Based Files
State-Based Files
County-Based Files
Note that not all files exist for all states or all counties.
Alaska Native Regional Corporation   X  
American Indian/Alaska Native/Native Hawaiian Area X    
American Indian Tribal Subdivision X    
Block*   X  
Block Group   X  
Census Tract   X  
Congressional District--111th X X  
Congressional District--113th X X  
Consolidated City   X  
County   X  
County Subdivision   X  
Place   X  
School District--Elementary   X  
School District--Secondary   X  
School District--Unified   X  
State X X  
State Legislative District--Lower Chamber   X  
State Legislative District--Upper Chamber   X  
Subminor Civil Division   X  
Urban Area X    
Urban Growth Area   X  
Voting District     X
5-digit ZIP Code Tabulation Area X    
All Lines     X
All Roads     X
Area Hydrography     X
Area Landmark   X  
Linear Hydrography     X
Military Installation X    
Point Landmark   X  
Primary and Secondary Roads   X  
Topological Faces (Polygons with all Geocodes)     X
Address Range Relationship File     X
Address Range-Feature Name Relationship File     X
Faces-Area Hydrography Relationship File     X
Faces-Area Landmark Relationship File   X  
Feature Names Relationship File     X

*  County-based block shapefiles are available as part of the Partnership Shapefiles.

User Notes

User Note 1:

The state of New Hampshire uses floterial districts in their lower-chamber (SLDL) plan. Floterial districts are overlay districts made up of two or more discrete districts. These discrete or component districts are those represented in the New Hampshire SLDL shapefile. A text file of the New Hampshire floterials is also available for download.

The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.

2012 TIGER/Line Shapefiles

All legal boundaries and names are as of January 1, 2012. Released August 17, 2012.

Download

Technical Documentation

File Availability

  • Shapefiles are released in one of three types of coverages:
    • Nation-based
    • State-based
    • County-based
  • The table below lists each type of geography and the coverage(s) at which each is available.

2012 TIGER/Line Shapefiles Availability
Layer
Nation-Based Files
State-Based Files
County-Based Files
Note that not all files exist for all states or all counties.
Alaska Native Regional Corporation   X  
American Indian/Alaska Native/Native Hawaiian Area X    
American Indian Tribal Subdivision X    
Block*   X  
Block Group   X  
Census Tract   X  
Combined New England City and Town Area X    
Combined Statistical Area X    
Congressional District--112th X    
Consolidated City   X  
County X    
County Subdivision   X  
Estate   X  
Metropolitan Division X    
Metropolitan/Micropolitan Statistical Area X    
New England City and Town Area X    
New England City and Town Area Division X    
Place   X  
Public Use Microdata Area   X  
School District--Elementary   X  
School District--Secondary   X  
School District--Unified   X  
State X    
State Legislative District--Lower Chamber   X  
State Legislative District--Upper Chamber   X  
Subminor Civil Division   X  
Tribal Block Group X    
Tribal Census Tract X    
Urban Area X    
Urban Growth Area   X  
Voting District   X  
5-digit ZIP Code Tabulation Area X    
All Lines     X
All Roads     X
Address Range-Feature     X
Area Hydrography     X
Area Landmark   X  
Linear Hydrography     X
Military Installation X    
Point Landmark   X  
Primary Roads X    
Primary and Secondary Roads   X  
Rails X    
Topological Faces (Polygons with all Geocodes)     X
Address Range Relationship File     X
Address Range-Feature Name Relationship File     X
Faces-Area Hydrography Relationship File     X
Faces-Area Landmark Relationship File     X
Faces-Military Installation Relationship File X    
Feature Names Relationship File     X
Other Identifiers Relationship File     X

*  County-based block shapefiles are available as part of the Partnership Shapefiles.

User Notes

User Note 1:

The Current Tribal Census Tracts National Shapefile and Current Tribal Block Group National Shapefile were reposted on September 10, 2012. These files both contained duplicate records.

User Note 2:

A new incorporated place was added in Wisconsin (Bloomfield - 08265) during the 2012 Boundary and Annexation Survey (BAS). As part of the addition of this incorporated place, we failed to adjust the minor civil division (MCD) layer to account for addition of this incorporated place in Walworth County. In Wisconsin, all incorporated places are independent of MCDs. However, to maintain a seamless wall-to-wall coverage of county subdivision entities nationwide, we create false MCDs where this situation arises.

The following layers were reposted on September 10, 2012:

  • Current County Subdivision State-based Shapefile - (Wisconsin - 55 only)
  • Topological Faces (Polygons with All Geocodes) County-based Shapefile - (Walworth County - 55127 only)

The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.

2011 TIGER/Line Shapefiles

All legal boundaries and names are as of January 1, 2011. Released December 12, 2011.

Download

Technical Documentation

File Availability

2011 TIGER/Line Shapefiles Availability
Layer
Nation-Based Files
State-Based Files
County-Based Files
Note that not all files exist for all states or all counties.
Alaska Native Regional Corporation   X  
American Indian/Alaska Native/Native Hawaiian Area X    
American Indian Tribal Subdivision X    
Block   X  
Block Group   X  
Census Tract   X  
Combined New England City and Town Area X    
Combined Statistical Area X    
Congressional District--112th X    
Consolidated City   X  
County X    
County Subdivision   X  
Metropolitan Division X    
Metropolitan/Micropolitan Statistical Area X    
New England City and Town Area X    
New England City and Town Area Division X    
Place   X  
School District--Elementary   X  
School District--Secondary   X  
School District--Unified   X  
State X    
State Legislative District--Lower Chamber   X  
State Legislative District--Upper Chamber   X  
Subminor Civil Division   X  
Tribal Block Group X    
Tribal Census Tract X    
All Lines     X
All Roads     X
Address Range-Feature     X
Area Hydrography     X
Area Landmark     X
Linear Hydrography     X
Military Installation X    
Point Landmark     X
Primary Roads X    
Primary and Secondary Roads   X  
Rails X    
Topological Faces (Polygons with all Geocodes)     X
Address Range Relationship File     X
Address Range-Feature Name Relationship File     X
Faces-Area Hydrography Relationship File     X
Faces-Area Landmark Relationship File     X
Faces-Military Installation Relationship File X    
Feature Names Relationship File     X
Other Identifiers Relationship File     X

User Notes

User Note 1:  Topological Faces (Polygons with all Geocodes) Shapefiles Replaced on August 2, 2012

On August 2, 2012, the Topological Faces (Polygons with all Geocodes) Shapefiles were replaced in the download interface and FTP site for the following counties:

County FIPS
Colbert County, AL 01033
Lauderdale County, AL 01077
Arapahoe County, CO 08005
Denver County, CO 08031
New London County, CT 09011
Windham County, CT 09015
Boyle County, KY 21021
Lincoln County, KY 21137
Anne Arundel County, MD 24003
Calvert County, MD 24009
Osage County, MO 29151
Lorain County, OH 39093
Hamilton County, TX 48193
Rappahannock County, VA 51157

In files downloaded before this date, there are TFID records that are missing values for the following fields: STATEFP10, COUNTYFP10, TRACTCE10, BLKGRPCE10, BLOCKCE10, TRACTCE, BLKGRPCE, and BLOCKCE. 

Posted August 2, 2012

The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.

2010 TIGER/Line Shapefiles

All legal boundaries and names are as of January 1, 2010. Released beginning November 30, 2010. Last update March 26, 2012.

Download

Download by File Type

Web Interface

FTP Site


Download by State

FTP Site

Technical Documentation

File Availability

Available 2010 TIGER/Line Shapefiles
Layer
County-Based
Files
State-Based
Files
 Nation-Based Files American Indian Area-Based Files
Census 2000 Vintage
2010 Census Vintage

# Note that all files do not exist for all states, counties, or American Indian areas.
* No vintage indicated in title of file; no assigned vintage.
Alaska Native Regional Corporation
 
X
    
 X
X
American Indian Tribal Subdivision
 
X
 X X
X
X
American Indian/Alaska Native/Native Hawaiian Area
 
X
 X  
X
X
Block
X
X
    
X
X
Block Group
X
X
    
X
X
Census Tract
X
X
    
X
X
Combined New England City and Town Area   X X     X
Combined Statistical Area   X X     X
108th Congresional District
 
X
 X  
X*
 
111th Congressional District
 
X
 X  
 
X*
Consolidated City
 
X
    
X
X
County and Equivalent
 
X
 X  
X
X
County Subdivision
X
X
    
X
X
Metropolitan Division   X X     X
Metropolitan/Micropolitan Statistical Area   X X     X
New England City and Town Area   X X     X
New England City and Town Area Division   X X     X
Place
 
X
    
X
X
Public Use Microdata Areas
 
X
    
 
X
School District--Elementary
 
X
    
X
X
School District--Secondary
 
X
    
X
X
School District--Unified
 
X
    
X
X
State and Equivalent
 
X
 X  
X
X
State Legislative District--Lower Chamber
 
X
    
X
X
State Legislative District--Upper Chamber
 
X
    
X
X
Subbarrio
 X
 
    
X
 
Subminor Civil Division
 
X
    
 
X
Tribal Block Group     X X   X
Tribal Census Tract     X X   X
Urban Areas
 
 
 X  
 
X
Urban Growth Area
 
X
    
X
X
Voting District
X
 
    
X
X
ZIP Code Tabulation Area
 
X
 X  
X
X
All Lines
X
 
    
 
X*
All Roads
X
 
    
 
X*
Area Hydrography
X
 
    
 
X*
Area Landmark
X
 
    
 
X*
Linear Hydrography
X
 
    
 
X*
Military Installations   X X    
X*
Point Landmark
X
 
    
 
X*
Primary Roads     X     X*
Primary and Secondary Roads
 
X
    
 
X*
Rails     X    
X*
Topological Faces (Polygons With All Geocodes)
X
 
    
 
X*
Address Range-Feature Name Relationship File
X
 
    
 
X*
Address Ranges Relationship File
X
 
    
 
X*
Feature Names Relationship File
X
 
    
 
X*
Other Identifiers Relationship File
X
        
X*
Topological Faces-Area Hydrography Relationship File
X
 
    
 
X*
Topological Faces-Area Landmark Relationship File
X
        
X*
Topological Faces-Military Installation Relationship File  
 
 X  
 
X*

Special Release - Census Blocks with Population and Housing Unit Counts

We have produced a special version of shapefiles that incorporate the 2010 Census block geography and the 2010 Census population and housing unit counts. These shapefiles are available at the state level for the 50 states and the District of Columbia. At this time these shapefiles are not available for Puerto Rico or the Island areas.

These shapefiles were created for a special project so they do not contain all of the attributes of the TIGER/Line Shapefiles but contain the information necessary to identify the census blocks.

Download these files via our FTP site

Record Layout:

File Name: tabblock2010_<state FIPS>_pophu.shp

Field
Length
Type
Description
STATEFP10
2
String
2010 Census state FIPS code
COUNTYFP10
3
String
2010 Census county FIPS code
TRACTCE10
6
String
2010 Census census tract code
BLOCKCE
4
String
2010 Census tabulation block number
BLOCKID10
15
String
Block identifier; a concatenation of 2010 Census state FIPS code, county FIPS code, census tract code and tabulation block number.
PART
1
String
Part Flag Indicator – Y = partial block, N = whole block; Part Flag should always be N in these files
HOUSING10
100
Number
2010 Census Housing Unit Count
POP10
100
Number
2010 Census Population Count

User Notes

User Note 1:  Incorrect Voting District Names

The following voting disticts in Alaska are named incorrectly in the 2010 TIGER/Line Shapefiles:

21-415 Chugach Hills No. 2 Precinct in Anchorage Municipality (02020) should be Chugach Foothills No. 2 Precinct

06-610 Mcgrath Precinct in Bethel Census Area (02050) should be McGrath Precinct

37-710 Clarks Point Precinct in Dillingham Census Area (02070) should be Clark’s Point Precinct

04-410 Mendenhall Valley No. 1 District in Juneau City and Borough (02110) should be Mendenhall Valley No. 1 Precinct

34-870 Salamatoff Precinct in Kenai Peninsula Borough (02122) should be Salamatof Precinct

 

User Note 2:  Census 2000 Blocks

There is the possibility that some Census 2000 blocks are missing from this version of the shapefiles. If a state boundary was modified in our database a Census 2000 block may have moved from one state to the adjacent state. Due to the timing requirements for this version of the shapefiles these blocks will be missing from the Census 2000 block inventory. Complete coverage of Census 2000 blocks can be found in previous versions of the TIGER/Line Shapefiles.

NOTE: Please see User Note 18 for additional information.

 

User Note 3:  All Lines Shapefile and Feature Names Relationship File

The feature names in the All Lines shapefile may not be consistent from one edge to the next along the extent of a road feature. The All Lines shapefile identifies the primary street name for an edge, however some primary names and alternate names have been flipped resulting in a primary feature name for one edge being identified as an alternate name on another. All feature names (featname.dbf), whether primary or alternate, can be related to the All Lines shapefile (edges.shp) by matching the TLIDs.

 

User Note 4:   All Lines Shapefile - Permanent Face ID on the Right of the Edge (TFIDR) and Permanent Face ID on the Left of the Edge (TFIDL)

In the All Lines shapefile, the permanent face ID on the left of the edge (TFIDL) value or the permanent face ID on the right of the edge (TFIDR) value will be blank for edges on the outer boundary of a county and for edges on the outer boundary of the United States, Puerto Rico and the Island Areas. The TFID (either left or right side) that does not appear in the attribute table of the county file will appear in the adjacent county's attribute table. This may impact users who are creating layers and topologies from the All Lines Shapefiles.

 

User Note 5: All Lines Shapefile - Hancock, IL road name directionals

The Hancock County, IL TIGER county road name directions appear to be switched for the entire county.  This problem was confirmed by the Census Bureau Headquarter Geographers, Chicago Regional Office Geographers and Hancock County, IL officials.  Hancock County Road names are based on a Northing and Easting coordinate grid system.  County Roads with Northing directionals should have an East-West orientation and County Roads with Easting directionals should have a North-South orientation in Hancock County, IL.  The Hancock County Road name directionals are opposite in the MAF/TIGER Database (MTDB).  Northing directionals have an incorrect North-South orientation and the Easting County Roads have an incorrect East-West orientation in Hancock County. 

 

User Note 6:  Address Ranges Relationship File - Plus 4 (ZIP Plus 4 Code) Values

The ZIP plus 4 code values will not appear in the 2010 TIGER/Line Shapefiles.

 

User Note 7:  Topological Faces (Polygons With All Geocodes) Shapefile - AWATER and ALAND measurement field

Topological faces with the LWFLAG values: G (Glacier), I (Intermittent Water), L (Land) and S (Marsh/Swamp) are considered land areas for the calculation of the Areawater shapefile, ALAND measurement field.  Only topological faces with the LWFLAG value of P (Perennial Water) are used to calculate water areas in the Areawater shapefile, AWATER measurement field.  Glaciers, intermittent lakes, and marsh/swamp are considered water features although the area within them is classified as land for area measurement purposes.

 

User Note 8: Finding Roads, Railroads, and Other Linear Features

The 2010 TIGER/Line shapefiles include state-based files containing primary and secondary roads and county-based files containing all roads. Nation-based railroad and primary road files will be coming out in 2011 as part of the later phases of the 2010 TIGER/Line shapefile release.

The All Lines Shapefile (Edges) includes all linear feature geography such as roads (street features), railroads, hydrography, and other linear features.  The All Lines Shapefile is available at the county level only.  There are several attribute flags within the shapefile that indicate if the feature is a road, rail, or water.  Each edge has a unique TLID (TIGER/Line identifier) value.

More detailed information regarding these files can be found in the technical documentation.

 

User Note 9: Census 2000 Elementary School District Shapefiles and Census 2000 Unified School District Shapefiles

Spatial data are incorrect for a number of elementary and unified school districts, creating tiny holes in school district coverage. The state and county names, state and county FIPS codes, and school districts where this occurs are below:

Maricopa, AZ (04013)
between elementary school districts (ELSDs) 01380 and 04320

Yuma, AZ (04027) and Pima AZ (04109)
between ELSD 09600 in Yuma and unified school district (UNSD) 99997 (School District Not Defined) in Pima

Yuma, AZ (04027)
between ELSDs 05220 and 03900

Kern, CA (06029)
between ELSDs 04560 and 24330

Nevada, CA (06057)
between ELSDs 26820 and 00012

Orange, CA (06059)
between ELSD 14730 and UNSD 05880

San Bernardino, CA (06071)
between ELSDs 01710 and 41040

Santa Clara, CA (06085)
between ELSDs 22830 and 22350
between ELSD 22830 and UNSD 34590

San Mateo, CA (06081)
between ELSDs 17190 and 34920

Shasta, CA (06089)
between ELSD 27040 and UNSD 14950

Sonoma, CA (06097)
between ELSDs 32640 and 19410
between ELSDs 36180 and 40230

Ventura, CA (06111)
between ELSD 28170 and UNSD 09640
between ELSDs 29220 and 32760 (2)
between ELSD 30990 and UNSD 09640
between ELSDs 37140 and 30990

Clinton, IL (17027)
between ELSDs 37470 and 07010 (2)
between ELSD 07010 and UNSD 08460 (2)

Livingston, IL (17105)
between ELSDs 29520 and 00065

Ogle, IL, (17141)
between ELSDs 21130 and 14410
between UNSDs 25690 and 21300

Tazewell, IL (17179)
between ELSD 31080 and UNSD 26800

Union, IL (17181)
between ELSD 03750 and UNSD 12480

Washington, IL (17189)
between ELSDs 19740 and 27720
between ELSDs 19740 and 40680

Hancock, ME (23009)
between ELSD 14770 and UNSD 06260

Chouteau, MT (30015)
between ELSDs 03760 and 22750

Flathead, MT (30029)
Between ELSDs 15570 and 02850

Wheatland, MT (30107)
between ELSDs 13440 and 26790 (2),
between ELSDs 13440 and 15360

Cherry, NE (31031)
between ELSD 45270 and UNSD 74040

Hall, NE (31079)
within ELSD 19930
within ELSD 78930

Sheridan, NE (31161)
between ELSDs 60900 and 67290

Grant, WI (55043)
within UNSD 06870

Dodge, WI (55027)
between ELSD 10410 and UNSD 06780

 

User Note 10: 2000 Elementary School District Shapefile, 2000 Secondary School District Shapefile, 2000 Unified School District Shapefiles

The highrange and lorange grade ranges are missing from all 2000 elementary school districts. The lorange grade ranges are missing from all 2000 secondary and 2000 unified school districts.

 

User Note 11: Census 2000 American Indian Tribal Subdivision Shapefile for South Dakota

In the Census 2000 American Indian Tribal Subdivision Shapefile for South Dakota, a sliver of Porcupine District is missing the TRSUBFP00 code as this was not a valid state to tribal subdivision relationship.

 

User Note 12: Classification of Roads

The Primary and Secondary Roads shapefiles include all road segments with a MAF/TIGER Feature Classification Code (MTFCC) of S1100 (Primary Road) or S1200 (Secondary Road). Gaps in the primary and secondary road coverage may occur if a road segment is misclassified and assigned a different MTFCC. One example of where this has occurred is Attala County, MS. To obtain complete road coverage, download the 'All Roads' shapefiles, available by county.

 

User Note 13: Corrections to the 2010 Redistricting TIGER/Line Shapefile Technical Documentation

In addition to the correction of some minor typing errors, the following corrections have been made to the technical documentation. The corrected technical documentation is now available online.

1. File name correction for block group shapefiles:

tl_2010_<state FIPS>_bg10.shp
tl_2010_<state FIPS>_bg00.shp
tl_2010_<state-county FIPS>_bg10.shp
tl_2010_<state-county FIPS>_bg00.shp

2. File name correction for census tract shapefile:

tl_2010_<state FIPS>_tract10.shp (shown as “tl_2010_<state FIPS>_tract00.shp” for the 2010 Census layout)

3. Record Layouts added for the following shapefiles in both the body and appendices of the document:

Census Tract State-based Shapefile Record Layout (Census 2000)

File Name:  tl_2010_<state FIPS>_tract00.shp

Field

Length

Type

Description

STATEFP00

2

String

Census 2000 state FIPS code

COUNTYFP00

3

String

Census 2000 county FIPS code

TRACTCE00

6

String

Census 2000 census tract code

CTIDFP00

11

String

Census 2000 census tract identifier; a concatenation of state FIPS code, county FIPS code, and census tract code

NAME00

7

String

Census 2000 census tract name, including the decimal point and decimal digits if a non-zero census tract suffix exists, excluding trailing zeros unless the zeros are part of a non-zero census tract suffix, and excluding any leading zeros

NAMELSAD00

20

String

Census 2000 translated legal/statistical area description and the census tract name

MTFCC00

5

String

MAF/TIGER feature class code (G5020)

FUNCSTAT00

1

String

Census 2000 functional status

ALAND00

14

Number

Census 2000 land area

AWATER00

14

Number

Census 2000 water area

INTPTLAT00

11

String

Census 2000 latitude of the internal point

INTPTLON00

12

String

Census 2000 longitude of the internal point

Census Tract County-based Shapefile Record Layout (2010 Census)

File Name: tl_2010_<state-county FIPS>_tract10.shp

Field

Length

Type

Description

STATEFP10

2

String

2010 Census state FIPS code

COUNTYFP10

3

String

2010 Census county FIPS code

TRACTCE10

6

String

2010 Census census tract code

GEOID10

11

String

Census tract identifier; a concatenation of 2010 Census state FIPS code, county FIPS code, and census tract code

NAME10

7

String

2010 Census 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.

NAMELSAD10

20

String

2010 Census translated legal/statistical area description and the census tract name

MTFCC10

5

String

MAF/TIGER feature class code (G5020)

FUNCSTAT10

1

String

2010 Census functional status

ALAND10

14

Number

2010 Census land area

AWATER10

14

Number

2010 Census water area

INTPTLAT10

11

String

2010 Census latitude of the internal point

INTPTLON10

12

String

2010 Census longitude of the internal point

Census 2000 Block Group (State-based) Shapefile

File Name: tl_2010_<state FIPS>_bg00.shp

Field

Length

Type

Description

STATEFP00

2

String

Census 2000 state FIPS code

COUNTYFP00

3

String

Census 2000 county FIPS code

TRACTCE00

6

String

Census 2000 census tract code

BLKGRPCE00

1

String

Census 2000 block group number

BKGPIDFP00

12

String

Census 2000 census block group identifier; a concatenation of the Census 2000 state FIPS code, county FIPS code, census tract code, and block group number

NAMELSAD00

13

String

Census 2000 translated legal/statistical area description and the block group number

MTFCC00

5

String

MAF/TIGER feature class code (G5030)

FUNCSTAT00

1

String

Census 2000 functional status

ALAND00

14

Number

Census 2000 land area

AWATER00

14

Number

Census 2000 water area

INTPTLAT00

11

String

Census 2000 latitude of the internal point

INTPTLON00

12

String

Census 2000 longitude of the internal point

2010 Census Block Group (County-based) Shapefile

File Name: tl_2010_<state-county FIPS>_bg10.shp

Field

Length

Type

Description

STATEFP10

2

String

2010 Census state FIPS code

COUNTYFP10

3

String

2010 Census county FIPS code

TRACTCE10

6

String

2010 Census census tract code

BLKGRPCE10

1

String

2010 Census block group number

GEOID10

12

String

Census block group identifier; a concatenation of 2010 Census state FIPS code, county FIPS code, census tract code, and block group number

NAMELSAD10

13

String

2010 Census translated legal/statistical area description and the block group number

MTFCC10

5

String

MAF/TIGER feature class code (G5030)

FUNCSTAT10

1

String

2010 Census functional status

ALAND10

14

Number

2010 Census land area

AWATER10

14

Number

2010 Census water area

INTPTLAT10

11

String

2010 Census latitude of the internal point

INTPTLON10

12

String

2010 Census longitude of the internal point

4. Fields deleted from the Address Range Relationship File (addr.dbf):

FROMARMID
TOARMID

5. File name correction for subminor civil divisions:

tl_2010_72_submcd10.shp (previously shown as “tl_2010_<state (78)–county FIPS>_submcd10.shp”)

All corrections were made to the technical documentation and posted on the website on or after January 7, 2011. These changes will not be reflected in the technical documentation on the DVDs sent to the states.

 

User Note 14: Congressional Districts in Michigan and Ohio

Michigan's congressional district plan, as provided to the Census Bureau, did not provide congressional district assignments for water blocks within the Great Lakes for the 111th Congress. The 2010 TIGER/Line Shapefiles contain 633 water blocks that should be coded to no congressional district and are incorrectly assigned to congressional districts 1, 2, 5, 6, 9, 10, and 12-15. These changes occurred in the following 21 counties: Alger (003), Allegan (005), Alpena (007), Antrim (009), Bay (017), Benzie (019), Charlevoix (029), Chippewa (033), Huron (063), Iosco (069), Mackinac (097), Macomb (099), Manistee (101), Muskegon (121), Ottawa (139), Presque Isle (141), Sanilac (151), Schoolcraft (153), Tuscola (157), Van Buren (159), and Wayne (163).

Ohio's congessional district plan, as provided to the Census Bureau, did not provide congressional district assignments for water blocks within the Great Lakes for the 111th Congress. The 2010 TIGER/Line Shapefiles contain 118 water blocks that should be coded to no congressional district and are incorrectly assigned to congressional districts 5, 9, and 13. These changes occurred in the following five counties: Erie (043), Lorain (093), Lucas (095), Ottawa (123), and Sandusky (143).

See also User Note 21.

 

User Note 15: Joining TIGER/Line Shapefiles to demographic data from the new American FactFinder

The GEOID2 field no longer exists in the new American FactFinder data downloads. Users must now create this column using Microsoft Excel following these steps:

  1. Insert a column in between columns A- GEO ID and column B - Geography. Then highlight the column labeled ID.
  2. Click on "Data" tab at top.
  3. Choose "Text to Columns" from Data menu
  4. Select delimited, hit next:
  5. Set delimiter to other: S and click next.
  6. In the Data Preview box, select the second column. Then select "Text" in the Column Data Format box
  7. The resulting column B is equivalent to the GEO ID2 column in legacy AFF downloads

In addition, users must now create database compatible headers in the tables before using the data in a GIS. Users must remove the multiple lines of headers and replace it with a single, short name.

Users may wish to use the summary files instead of the tables from American FactFinder. The 2010 Census P.L. 94-171 Summary Files can be accessed on our ftp site. Additional data will be added as it becomes available.

Please direct any questions related to American FactFinder to (800) 923-8282 or ask a question. For questions about the TIGER/Line Shapefiles or other geographic products please e-mail us: geo.tiger@census.gov or call (301) 763-1128.

 

User Note 16: Re-release of Selected New York Shapefiles

On February 23, 2011, selected New York layers were replaced. Please see the list of affected layers for additional information.

 

User Note 17: Files Added to Download Sites

Some shapefiles and relationship files were inadvertently omitted from our website, and were then added in early February. The following have been added to our download interface and layer-based FTP site:

  • All files for Ballard County, KY
  • 2000 and 2010 block, 2000 and 2010 tract, and 2010 voting district shapefiles for Citrus County, FL
  • 2010 voting district shapefile for Jefferson County, IL

The following have been added to our state-based FTP site:

  • Some files for Vernon and all files for Vilas, Walworth, Washburn, Washington, Waukesha, Waupaca, Waushara, and Winnebago Counties, WI

One shapefile was replaced in the download interface and the layer-based FTP site after the original file was found to be damaged:

  • Roads shapefile for Citrus County, FL

NOTE: Other files in the affected states or counties listed above may have been re-copied to the FTP sites and download interface at the same time that the missing or corrected files were added. However, those files are identical to the original versions of the files.

 

User Note 18: Files Replaced on March 21, 2011

On March 21, 2011, the following files were replaced in the download interface, layer-based FTP site, and state-based FTP site:

  • Census 2000 shapefiles for Louisiana, Mississippi, New Jersey, and Virginia (to correct the potentially missing blocks described in User Note 2).
  • Topological Faces (Polygons With All Geocodes) Shapefiles for all counties

 

User Note 19: Inconsistent Name and Code Assignments in State Legislative Districts

There are inconsistent code and name assignments between state legislative districts, upper chamber (SLDU) and state legislative districts, lower chamber (SLDL) in coastal and water tributary areas in Louisiana, Maine, Massachusetts, and Puerto Rico. These SLDU/SLDL inconsistencies were introduced when land area was changed to water area or vice versa and not all of the corresponding SLDU or SLDL codes were updated. In some cases, one chamber may have been coded to the shore (land) while the other chamber, in the same area, was coded to the water. (Some states designated SLDU and SLDL assignments to “ZZZ” in water for area not defined by any SLDU or SLDL.) These inconsistencies are reflected in the 2010 Census geographic products but have been reconciled and will not appear in future products. The updated assignments are shown below.

Column header definitions:

STATEFP: State FIPS Code
COUNTYFP: County FIPS Code
TRACTCE: Census Tract
BLOCKCE: Census Block
SLDUST: State Legislative District--Upper Chamber
SLDLST: State Legislative District--Lower Chamber
AREALAND: Area Land
AREAWATER: Area Water
ASSIGNMENT UPDATE: Assignment Update

STATEFP COUNTYFP TRACTCE BLOCKCE SLDUST SLDLST AREALAND AREAWATER ASSIGNMENT UPDATE
22 051 020513 2002 010 ZZZ 0 14059 SLDUST 010 corrected to ZZZ
22 051 020502 3008 010 ZZZ 0 13847 SLDUST 010 corrected to ZZZ
23 029 955900 2058 ZZZ 030 0 417 SLDLST 030 corrected to ZZZ
23 029 955600 1094 ZZZ 031 0 598292 SLDLST 031 corrected to ZZZ
23 029 955900 2064 ZZZ 030 0 4310010 SLDLST 030 corrected to ZZZ
23 029 955900 2054 ZZZ 030 0 743306 SLDLST 030 corrected to ZZZ
23 029 955600 1114 ZZZ 031 0 13598 SLDLST 031 corrected to ZZZ
23 031 034001 4031 002 ZZZ 0 410733 SLDUST 002 corrected to ZZZ
25 001 014700 2052 047 ZZZ 0 1295 SLDUST 047 corrected to ZZZ
25 001 014700 1052 047 ZZZ 0 413 SLDUST 047 corrected to ZZZ
25 005 644101 2007 021 ZZZ 0 27219 SLDUST 021 corrected to ZZZ
25 005 644101 2013 021 ZZZ 0 10842 SLDUST 021 corrected to ZZZ
25 005 650300 2012 022 ZZZ 0 13607 SLDUST 022 corrected to ZZZ
25 021 416400 1001 044 ZZZ 0 816 SLDUST 044 corrected to ZZZ
25 021 416400 1004 044 ZZZ 0 11234 SLDUST 044 corrected to ZZZ
72 015 280201 4026 ZZZ 030 0 43344 SLDLST 030 corrected to ZZZ
72 017 590100 1000 ZZZ 013 0 1502416 SLDLST 013 corrected to ZZZ
72 027 320100 1001 ZZZ 015 0 243267 SLDLST 015 corrected to ZZZ
72 049 950500 1051 ZZZ 036 0 2004 SLDLST 036 corrected to ZZZ
72 057 270201 1109 ZZZ 030 0 5990 SLDUST ZZZ corrected to 006
72 057 270201 1115 ZZZ 030 0 6293 SLDUST ZZZ corrected to 006

 

User Note 20: Files Added to Download Site

We discovered that on our ftp site by entity type, data for counties that existed for Census 2000 but not for the 2010 Census were not available. This affects only the Census 2000 vintage geography. These counties were available on the ftp site by state. The counties that existed for Census 2000 and not for the 2010 Census are:

  • 02201 Prince of Wales-Outer Ketchikan Census Area, AK
  • 02232 Skagway-Hoonah-Angoon Census Area, AK
  • 02280 Wrangell-Petesrsburg Census Area, AK
  • 51560 Clifton Forge city, VA

 

User Note 21: Additional Congressional District Codes for Maryland, Michigan, Ohio, and Wisconsin

Maryland, Michigan, Ohio, and Wisconsin’s congressional district plans for the 111th Congress, as provided to the Census Bureau, did not provide congressional district assignments for water blocks within the Great Lakes and the Chesapeake Bay and its tributaries. Over the past decade and where appropriate, the Census Bureau has recoded some of these water blocks to land blocks. Also, many islands are now coded to individual Census 2010 tabulation land blocks. The result has been that some land blocks in the 2010 Census geographic and data products are not associated with a congressional district code. The Census Bureau has provided a CD code for each of these blocks in this table. These congressional district codes will be assigned to these blocks for future products and will be maintained until the new 113th Congressional plans are received and inserted into our geographic database.

See also User Note 14.

Posted March 30, 2011

 

User Note 22: ZIP Code Tabulation Area Shapefiles Released

On May 11, 2011, national and state-based ZIP Code Tabulation Area Shapefiles were released. Additionally, the Topological Faces (Polygons With All Geocodes) Shapefiles were replaced with versions that contain 2010 ZIP Code Tabulation Area codes.

Posted May 12, 2011

 

User Note 23: Island Area Shapefiles Released

On June 23, 2011, shapefiles for the Island Areas (American Samoa, Commonwealth of the Northern Mariana Islands, Guam, and the U. S. Virgin Islands) were released.

Posted June 23, 2011

 

User Note 24: New England City and Town Area Shapefiles Replaced

The state-based New England City and Town Area shapefiles for all six New England states were replaced on June 30, 2011. The new files include NECTAs that were inadvertently omitted from the original versions of the files.

Posted June 30, 2011

 

User Note 25: Error in New England City and Town Area Division Shapefile

The New England City and Town Area (NECTA) Division shapefile for New Hampshire erroneously contains some NECTA divisions that are located entirely in Massachusetts.

The following NECTA divisions exist in New Hampshire and should appear in the New Hampshire NECTA division shapefile: Haverhill-North Andover-Amesbury, MA-NH; Lawrence-Methuen-Salem, MA-NH; Lowell-Billerica-Chelmsford, MA-NH; and Nashua, NH-MA.

The following NECTA divisions exist only in Massachusetts and should not appear in the New Hampshire NECTA division shapefile: Boston-Cambridge-Quincy, MA; Brockton-Bridgewater-Easton, MA; Framingham, MA; Peabody, MA; and Taunton-Norton-Raynham, MA.

Posted September 8, 2011

 

User Note 26: Error in Metadata for PUMA Shapefiles

In the 2010 PUMA shapefiles, the <begdate> and <enddate> values in the metadata files are incorrect.  The correct dates for the delineation of the 2010 PUMAs are:

<begdate>201111<begdate>
<enddate>201204<enddate>

Posted June 19, 2012


The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.

2009 TIGER/Line Shapefiles

All legal boundaries and names are as of January 1, 2009. Released October 1, 2009.

Download

Technical Documentation

File Availability

2009 TIGER/Line Shapefiles Organizational Structure
Layer
Nation-Based Files
State-Based Files
County-Based Files
American Indian Area-Based Files
108th Congresional District (Congress elected in 2002)
 
X
 
 
111th Congressional District (Congress elected in 2008)
 
X
 
 
3-Digit ZIP Code Tabulation Area
X
X
 
 
5-Digit ZIP Code Tabulation Area
X
X
 
 
Address Range-Feature Name Relationship File
 
 
X
 
Address Ranges Relationship File
 
 
X
 
Alaska Native Regional Corporation
 
X
 
 
All Lines
 
 
X
 
American Indian Tribal Subdivision
X
X
 
X
American Indian/Alaska Native/Native Hawaiian Area
X
X
 
 
Area Hydrography
 
 
X
 
Area Landmark
 
 
X
 
Block
 
X
X
 
Block Group
 
X
X
 
Census Tract
 
X
X
 
Combined New England City and Town Area
X
X
 
 
Combined Statistical Area
X
X
 
 
Commercial Region
 
X
 
 
Consolidated City
 
X
 
 
County and Equivalent
X
X
 
 
County Subdivision
 
X
X
 
Elementary School District
 
X
 
 
Feature Names Relationship File
 
 
X
 
Metropolitan Division
X
X
 
 
Metropolitan/Micropolitan Statistical Area
X
X
 
 
Military Installation
X
X
 
 
New England City and Town Area
X
X
 
 
New England City and Town Area Division
X
X
 
 
Other Identifiers Relationship File
 
 
X
 
Place
 
X
 
 
Point Landmark
 
 
X
 
Public Use Microdata Area
 
X
 
 
State and Equivalent
X
X
 
 
State Legislative District--Lower Chamber
 
X
 
 
State Legislative District--Upper Chamber
 
X
 
 
Subbarrio
 
X
 
 
Super Public Use Microdata Area
 
X
 
 
Topological Faces (Polygons With All Geocodes) Shapefile
 
 
X
 
Topological Faces-Area Hydrography Relationship File
 
 
X
 
Topological Faces-Area Landmark Relationship File
 
 
X
 
Traffic Analysis Zone
 
 
X
 
Unified School District
 
X
 
 
Urban Area
X
 
 
 
Urban Growth Area
 
X
 
 
Voting District
 
 
X
 

User Notes

User Note 1:  Public Use Microdata Areas (PUMAs)

Census 2000 1-Percent Public Use Microdata Area (PUMA1) Shapefile & Census 2000 5- or 10-Percent Public Use Microdata Area (PUMA5) Shapefile

In the past the Public Use Microdata Areas have been named based on the sample size (1-percent, 5-percent, or 10-percent) but they have been renamed Super Public Use Microdata Area or Public Use Microdata Area.  The name Public Use Microdata Area refers to the areas formerly known as the 5-percent or 10-percent Public Use Microdata Area.  The name Super Public Use Microdata Area refers to the areas formerly known as the 1-Percent Public Use Microdata Area.  This change affects the naming convention of 2 shapefiles beginning with the 2009 Public TIGER/Line Shapefiles.

The Census 2000 1-Percent Public Use Microdata Area (PUMA1) Shapefile has been renamed Census 2000 Super Public Use Microdata Area (Super PUMA) Shapefile

The Census 2000 5- or 10-Percent Public Use Microdata Area (PUMA5) Shapefile has been renamed Census 2000 Public Use Microdata Area (PUMA) Shapefile

Due to the name change of the 1-Percent Public Use Microdata Area to Super PUMA, the full name of the Super PUMA does not appear in the attribute table.  The NAMELSAD00 field, which normally contains the full name, contains only “Super PUMA”.  The PUMA number can be obtained from the PUMA1CE00 field.  To create the fully qualified name, concatenate the NAMELSAD00 field and the PUMA1CE00 field.

 

User Note 2:  Topological Faces (2-Cells With All Geocodes) Relationship File

Topological Faces (2-Cells With All Geocodes) Relationship File is now a shapefile and has been renamed.  The new name is: Topological Faces (Polygons With All Geocodes) Shapefile
In addition, the following new fields have been added:

  • American Indian/Alaska Native/Native Hawaiian FIPS Codes (AIANNHFP00 and AIANNHFP)
  • Tribal Subdivision FIPS Codes (TRSUBFP00 and TRSUBFP)
  • Total Area (ATOTAL)
  • Internal Point Coordinates (INTPTLAT and INTPTLON)

 

User Note 3:  111th Congressional District Shapefile

The 111th Congressional District Shapefile has replaced the 110th Congressional District Shapefile.  There were no boundary changes between the 110th and 111th Congresses.

 

User Note 4: New State-based Shapefiles

For the 2009 TIGER/Line Shapefile release 15 new State-based Shapefiles have been added, they are as follows:

  • American Indian/Alaska Native/Native Hawaiian Area (AIANNH) State-based Shapefile (Census 2000 and Current)
  • American Indian Tribal Subdivision (AITS) State-based Shapefile (Census 2000 and Current)
  • Combined Statistical Area (CSA) State-based Shapefile (Current)
  • Metropolitan Statistical Area/Micropolitan Statistical Area (CBSA) State-based Shapefile (Current)
  • Metropolitan Division State-based Shapefile (Current)
  • Combined New England City and Town Area (CNECTA) State-based Shapefile (Current)
  • New England City and Town Area (NECTA) State-based Shapefile (Current)
  • New England City and Town Area (NECTA) Division State-based Shapefile (Current)
  • State and Equivalent State-based Shapefile (Census 2000 and Current)
  • Military Installation State-based Shapefile
  • 5-Digit ZIP Code Tabulation Area (ZCTA5) State-based Shapefile (2002) – not clipped (can extend beyond the state boundary)
  • 3-Digit ZIP Code Tabulation Area (ZCTA3) State-based Shapefile (2002) – not clipped (can extend beyond the state boundary)

 

User Note 5: Finding Roads, Railroads, and other Linear Features

The All Lines Shapefile (Edges) includes all linear feature geography such as roads (street features), railroads, hydrography, and other linear features.  The All Lines Shapefile is available at the county level only.  There are several attribute flags within the shapefile that indicate if the feature is a road, rail, or water.  Each edge has a unique TLID (TIGER/Line identifier) value.
More detailed information regarding the All Lines Shapefile can be found in the technical documentation located at URL: http://www.census.gov/geo/maps-data/data/pdfs/tiger/tgrshp2009/TGRSHP09.pdf

 

User Note 6:  All Lines Shapefile Metadata - Missing Spatial Metadata Identifiers (SMIDs)

The Spatial Metadata Identifier (SMID) in the All Lines shapefile identifies the source of the coordinates for the line segment when available (not every edge will have a SMID) and provides the link between the TIGER/Line Shapefile and the source and horizontal spatial accuracy information. There are a few occurrences where the SMIDs are missing from some All Lines metadata files; hence the spatial metadata elements are also missing. The Census Bureau is aware of this problem and is in the process of fixing this issue. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles.  See the list below of areas missing SMID information in the metadata.

Jefferson, Alabama (01073): SMID 932
Shelby, Alabama (01117): SMID 932
Fairbanks North Star Borough, Alaska (02090): SMID 3431
Faulkner, Arkansas (05045): SMID 4506
Brooks, Georgia (13027): SMID 113
Colquitt, Georgia (13071): SMID113
Mitchell, Georgia (13205): SMID 113
Thomas, Georgia (13275): SMID 113
Tift, Georgia (13277): SMID 113
Worth, Georgia (13321): SMID 113
Cook, Illinois (17031): SMID4625
Will, Illinois (17197): SMID 4625
Benton, Indiana (18007): SMID 4625
Elkhart, Indiana (18039): SMID 553
Fountain, Indiana (18045): SMID 4627
Fulton, Indiana (18049): SMID 553
Kosciusko, Indiana (18085): SMID 553
Lake, Indiana (18089): SMID 4625
Marshall, Indiana (18099): SMID 553
Montgomery, Indiana (18107): SMID 4627
Noble, Indiana (18113): SMID 553
Porter, Indiana (18127): SMID 4625
Tippecanoe, Indiana (18157): SMID 4627
Wabash, Indiana (18169): SMID 553
Warren, Indiana (18171): SMID 4627
White, Indiana (18181): SMID 4627
Whitley, Indiana (18183): SMID 553
Black Hawk, Iowa (19013): SMID 2734
Bremer, Iowa (19017): SMID 2734
Butler, Iowa (19023): SMID 2734
Chickasaw, Iowa (19037): SMID 2734
Fayette, Iowa (19065): SMID 2734
Cherokee, Kansas (20021): SMID581
Barton, Missouri (29011): SMID 581
Dade, Missouri (29057): SMID 581
Jasper, Missouri (29097): SMID 581
Lawrence, Missouri (29109): SMID 581
Newton, Missouri (29145): SMID 581
Cibola, New Mexico (35006): SMID 5346
Dona Ana, New Mexico (35013): SMID 2820
McKinley, New Mexico (35031): SMID 5346
Otero, New Mexico (35035): SMID 2820
Bertie, North Carolina (37015): SMID 4233
Archer, Texas (48009): SMID 234
Wichita, Texas (48485): SMID 120
Wichita, Texas (48485): SMID 234
Wilbarger, Texas (48487): SMID 120
Wilbarger, Texas (48487): SMID 234

 

User Note 7:  Windows XP Users May Experience Problems Unzipping the 2009 TIGER/Line Shapefiles

Windows XP users who are downloading multiple files at the same time from the 2009 TIGER/Line Shapefiles main download page who are also using the Windows extraction utility will be unable to unzip the files. The Census Bureau is looking into possible resolutions for this problem. In the interim, users can use one of the following options to work around this issue:

  • Use a different extraction utility other than the default Windows utility to unzip the files (i.e. WinZip or another similar tool).
  • Use the 2009 TIGER/Line Shapefiles main download page to download the files one at a time by clicking on the individual file names.
  • Use the ftp site to download the files.

 

User Note 8:  All Lines Shapefile and Feature Names Relationship File

The feature names in the All Lines shapefile may not be consistent from one edge to the next along the extent of a road feature. The All Lines shapefile identifies the primary street name for an edge, however some primary names and alternate names have been flipped resulting in a primary feature name for one edge being identified as an alternate name on another. All feature names (featname.dbf), whether primary or alternate, can be related to the All Lines shapefile (edges.shp) by matching the TLIDs.

 

User Note 9:   All Lines Shapefile - Permanent Face ID on the Right of the Edge (TFIDR) and Permanent Face ID on the Left of the Edge (TFIDL)

In the All Lines shapefile, the permanent face ID on the left of the edge (TFIDL) value or the permanent face ID on the right of the edge (TFIDR) value will be blank for edges on the outer boundary of a county and for edges on the outer boundary of the United States, Puerto Rico and the Island Areas. The TFID (either left or right side) that does not appear in the attribute table of the county file will appear in the adjacent county's attribute table. This may impact users who are creating layers and topologies from the All Lines Shapefiles.

 

User Note 10: All Lines Shapefile - Hancock, IL road name directionals

The Hancock County, IL TIGER county road name directions appear to be switched for the entire county.  This problem was confirmed by the BOC Headquarter Geographers, Chicago Regional Office Geographers and Hancock County, IL officials.  Hancock County Road names are based on a Northing and Easting coordinate grid system.  County Roads with Northing directionals should have an East-West orientation and County Roads with Easting directionals should have a North-South orientation in Hancock County, IL.  The Hancock County Road name directionals are opposite in the MAFTIGER Database (MTDB).  Northing directionals have an incorrect North-South orientation and the Easting County Roads have an incorrect East-West orientation in Hancock County.  BOC Geography Division is aware of this problem and steps are being taken to resolve this problem.

 

User Note 11:  Address Ranges Relationship File - Plus 4 (ZIP Plus 4 Code) Values

The ZIP plus 4 code values will not appear in the 2009 TIGER/Line Shapefiles.
 

 

User Note 12:  Census 2000 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile, 2002 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile, Topological Faces (2-Cells with All Geocodes) Shapefile

Both the Census 2000 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile and the 2002 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile will not contain values for areas without an actual ZCTA code. That is, areas with large amounts of land and no ZCTA code that were previously coded with nnnXX will not be included, and neither will areas with large amounts of water and no ZCTA code that were previously coded with nnnHH. As a result, there is no longer complete coverage of the United States and Puerto Rico by 5-digit ZCTAs, rather only those areas that have an actual ZCTA code will be included in the coverage. Also, the Topological Faces (2-cells with all Geocodes) Relationship File will not contain ZCTA5CE00 or ZCTA5CE codes where code is nnnXX or nnnHH. This means that only those faces that make up a ZCTA boundary will contain ZCTA codes.

 

User Note 13: American Community Survey 2009 (ACS09) Elementary School District, Secondary School District, and Unified School District Shapefiles

Spatial data are incorrect for a number of elementary, secondary, and unified school districts where tiny overlaps and holes in school district coverage can be found.  These problems were corrected in the Census Bureau’s source database for the 2009 American Community Survey and the Population Estimates Program.  We have not identified wide-spread issues, but it is possible there are additional counties with overlaps or holes.  The state and county names, state and county FIPS codes, and school districts where this occurs are below:

Overlaps:
Windham, CT (09015)
elementary school district (ELSD) 00720 and unified school district (UNSD) 05190

Middlesex, MA (25017)
ELSD 03330, secondary school district (SCSD) 03870, and UNSD 03510

Worcester, MA (25027)
ELSD 02910, SCSD 02580, and UNSD 10770

Gaps:
Lee, AL (01081)
between UNSDs 02070 and 02700

Hall, GA (13139)
between UNSDs 02610 and 02310

Burlington, NJ (34005)
between ELSD 10950, SCSD 08480 and UNSD 10710

Shelby, TN (47157)
between UNSDs 02940 and 03810

 

User Note 14:  Topological Faces (Polygons With All Geocodes) Shapefile - AWATER and ALAND measurement field

Topological faces with the LWFLAG values: G (Glacier), I (Intermittent Water), L (Land) and S (Marsh/Swamp) are considered land areas for the calculation of the Areawater shapefile, ALAND measurement field.  Only topological faces with the LWFLAG value of P (Perennial Water) are used to calculate water areas in the Areawater shapefile, AWATER measurement field.  Glaciers, intermittent lakes, and marsh/swamp are considered water features although the area within them is classified as land for area measurement purposes.

 

User Note 15:  Current American Indian/Alaska Native/Native Hawaiian Shapefiles

The NAMELSAD field in the current American Indian/Alaska Native/Native Hawaiian shapefiles lists the name of the area with AIANNH code 3280 as “Sac and Fox/Meskwaki Ranch Reservation”.  This is incorrect; it should be “Sac and Fox/Meskwaki Settlement”.

 

User Note 16: Understanding Vintage of Shapefiles

The 2009 TIGER/Line Shapefiles contain an extract from the MAF/TIGER database as of May 2009 and includes three vintages of geography. See Chapter 4 of the technical documentation for a detailed description of each file type and vintage.

Current Census Geography
Current geography is defined as the latest version of the geographic extent of legally defined geographic areas as reported, generally reflecting the boundaries of governmental units in effect as of January 1, 2009, or legal and statistical area boundaries that have been adjusted and/or corrected since Census 2000. This vintage enables users to see the most current boundaries of governmental units and they will match the data from the surveys that use 2009 geography, such as the 2009 Population Estimates. The layer names may be followed by (Current) or have no name in parentheses.

Census 2000 Geography
Census 2000 geography is the geographic extent of legally defined geographic areas or statistical areas in effect on January 1, 2000. This vintage enables users to work with Census 2000 data using boundaries as they existed in 2000. Since 2000, the Census Bureau initiated significant operations to improve the coordinate accuracy of our geographic database-the MAF/TIGER Accuracy Improvement Project or MTAIP. The MTAIP modified the base coordinates of virtually all the features in the database, thus the representation of Census 2000 geography will not match the representation depicted in the Census 2000 TIGER/Line files. The inventory and attributes of the 2000 census geography is, however, unchanged. The layer names are followed by (Census 2000) and the files have an "00" at the end of their name.

2007 Economic Census Geography
2007 Economic Census geography is defined as the version of the geographic extent of legally defined geographic areas in effect on January 1, 2007. The Economic Census is the major economic statistical program of the United States, and it provides a detailed portrait of the nation’s economy once every five years. The geographic entities used in an Economic Census can differ from those used in decennial censuses. The boundaries used for geographic entities for the 2007 Economic Census are those reported to the Census Bureau through the Boundary and Annexation Survey (BAS) to be legally in effect on January 1, 2007. The layer names are followed by (Economic Census) and the files have an "ec" at the end of their name.

 

User Note 17: 2010 Census Geography

Updates from participant programs directly related to the 2010 Census are not reflected in the 2009 TIGER/Line Shapefiles. We were continuing to process updates and verify changes when this version of the TIGER/Line Shapefiles were produced to support 2009 geographic programs and surveys. These updates will be part of the 2010 Census TIGER/Line Shapefiles, which will be released to the public beginning in early 2011. The 2010 Census TIGER/Line Shapefiles will include updated geographic areas such as census blocks, census tracts, school districts, and voting districts.

 

User Note 18: Omission from Technical Documentation

In Appendix A of the technical documentation, the record layout for the Topological Faces (Polygons With All Geocodes) Shapefile is missing the following field:

Field Length Type Description
CBSAFP 5 String Current metropolitan or micropolitan statistical area code

This field should appear between CSAFP and METDIVFP.

The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.

2008 TIGER/Line Shapefiles

All legal boundaries and names are as of January 1, 2008. Released December 8, 2008.

Download

Technical Documentation

File Availability

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. Though defined within states, county boundaries are available in nation-based as well as state-based shapefiles. The following layers are included:

  • American Indian/Alaska Native/Native Hawaiian Area (Census 2000 and current)
  • American Indian Tribal Subdivision (Census 2000 and current)
  • County and Equivalent (Census 2000 and current)
  • Combined New England City and Town Area (current)
  • Combined Statistical Area (current)
  • Metropolitan Division (current)
  • Metropolitan/Micropolitan Statistical Area (current)
  • New England City and Town Area (current)
  • New England City and Town Area Division (current)
  • State and Equivalent (Census 2000, current, and Economic Census)
  • Urban Areas (Census 2000 and corrected Census 2000)
  • 3-Digit ZIP Code Tabulation Area (Census 2000 and 2002)
  • 5-Digit ZIP Code Tabulation Area (Census 2000 and 2002)
  • Military Installation (current)

American Indian Area-Based Files

The following layers are available by American Indian Area:

  • American Indian Tribal Subdivision (Census 2000 and current)

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. Though defined within counties, blocks, block groups, census tracts, and county subdivisions are available in state-based as well as county-based shapefiles. Though defined within states, counties are available in state-based as well as nation-based shapefiles. The following layers are included:

  • Alaska Native Regional Corporation (Census 2000 and current)
  • Block (Census 2000 and current)
  • Block Group (Census 2000)
  • Census Tract (Census 2000)
  • Commercial Region (Economic Census)
  • 110th Congressional District (Congress elected in 2006)
  • 108th Congressional District (Congress elected in 2002)
  • Consolidated City (Census 2000, current, and Economic Census)
  • County and Equivalent (Census 2000, current, and Economic Census)
  • County Subdivision (Census 2000 and current)
  • Place (Census 2000, current, and Economic Census)
  • 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 and current)

County-Based Files

Entities that are defined within counties and do not cross county or state lines such as census tracts and voting districts are represented in county-based shapefiles. Though defined within counties, blocks, block groups, census tracts, and county subdivisions are available in state-based as well as county-based shapefiles. 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)
  • Other Identifiers 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)

User Notes

User Note 1:  All Lines Shapefile and Feature Names Relationship File

The feature names in the All Lines shapefile may not be consistent from one edge to the next along the extent of a road feature. The All Lines shapefile identifies the primary street name for an edge, however some primary names and alternate names have been flipped resulting in a primary feature name for one edge being identified as an alternate name on another. All feature names (featname.dbf), whether primary or alternate, can be related to the All Lines shapefile (edges.shp) by matching the TLIDs.

User Note 2:   All Lines Shapefile - Permanent Face ID on the Right of the Edge (TFIDR) and Permanent Face ID on the Left of the Edge (TFIDL)

In the All Lines shapefile, the permanent face ID on the left of the edge (TFIDL) value or the permanent face ID on the right of the edge (TFIDR) value will be blank for edges on the outer boundary of a county and for edges on the outer boundary of the United States, Puerto Rico and the Island Areas. The TFID (either left or right side) that does not appear in the attribute table of the county file will appear in the adjacent county's attribute table. This may impact users who are creating layers and topologies from the All Lines Shapefiles.

User Note 3:  Address Ranges Relationship File - Plus 4 (ZIP Plus 4 Code) Values

The ZIP plus 4 code values will not appear in the 2008 TIGER/Line Shapefiles.

User Note 4:  Census 2000 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile, 2002 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile, Topological Faces (2-Cells with All Geocodes) Relationship File

Both the Census 2000 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile and the 2002 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile will not contain values for areas without an actual ZCTA code. That is, areas with large amounts of land and no ZCTA code that were previously coded with nnnXX will not be included, and neither will areas with large amounts of water and no ZCTA code that were previously coded with nnnHH. As a result, there is no longer complete coverage of the United States and Puerto Rico by 5-digit ZCTAs, rather only those areas that have an actual ZCTA code will be included in the coverage. Also, the Topological Faces (2-cells with all Geocodes) Relationship File will not contain ZCTA5CE00 or ZCTA5CE codes where code is nnnXX or nnnHH. This means that only those faces that make up a ZCTA boundary will contain ZCTA codes.

User Note 5:  Census 2000 Place Shapefile Metadata and Current Place Shapefile Metadata

Both the Current Place Shapefile and the Census 2000 Place Shapefile metadata (place.shp.xml) files contain an incorrect MAF/TIGER Feature Class Code (MTFCC) for Census Designated Place. The MTFCC is incorrectly listed as G4120. The correct MTFCC code is G4210. The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years.

User Note 6:  Area Landmark and Point Landmark Shapefiles

In the Area Landmark and Point Landmark Shapefiles the MAF/TIGER Feature Class Code (MTFCC) of K2190 should be listed as one of the following MTFCC codes: K2180, K2183, K2184, K2185, K2186, or K2188. The Census Bureau is aware of this problem and is in the process of fixing them for the next release of the TIGER/Line shapefiles.

User Note 7:  All Lines Shapefile Metadata - Missing Spatial Metadata Identifiers (SMIDs)

The Spatial Metadata Identifier (SMID) in the All Lines shapefile identifies the source of the coordinates for the line segment when available (not every edge will have a SMID) and provides the link between the TIGER/Line Shapefile and the source and horizontal spatial accuracy information. There are a few occurrences where the SMIDs are missing from some All Lines metadata files; hence the spatial metadata elements are also missing. The Census Bureau is aware of this problem and is in the process of fixing this issue. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years.

User Note 8:  All Lines Shapefiles - Feature Distortion

In the 2008 TIGER/Line Shapefiles release we have identified 1,159 counties that contain new features that are distorted. These features appear to be pulled away from their position to a point and returned to their correct location forming a distorted edge. The problems are a result of the efforts to automatically integrate new data with existing positionally accurate features. We have not identified wide-spread issues in other counties but it is possible that there are additional counties with some distorted edges.

We are working diligently to correct these errors and anticipate a marked improvement in the 2009 TIGER/Line Shapefiles. We are continually working on updating our database and improvements will be seen with each subsequent release. In the meantime, depending on your needs, you may wish to use the prior version of the TIGER/Line Shapefiles or wait for the 2009 release which is scheduled for late summer.

List of 1,159 counties affected: [TXT]

User Note 9:  Current Elementary School District Shapefiles and Current Unified School District Shapefiles

Spatial data coverage for elementary and unified school districts is incomplete in one area, creating a tiny hole in school district coverage. This problem was corrected in the Census Bureau's source database after the 2008 TIGER/Line shapefile creation. The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years. The state and county names, state and county FIPS codes, and school districts where this occurs are below:

Monroe, TN 47123 and McMinn, TN 47107
between elementary school district (ELSD) 04050 in Monroe and unified school district (UNSD) 02820 in McMinn

User Note 10:  Census 2000 Elementary School District Shapefiles and Census 2000 Unified School District Shapefiles

Spatial data are incorrect for a number of elementary and unified school districts, creating tiny overlaps and holes in school district coverage. These problems were corrected in the Census Bureau's source database after the 2008 TIGER/Line shapefile creation. The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in the 2009 release of the TIGER/Line Shapefiles. The state and county names, state and county FIPS codes, and school districts where this occurs are below:

Overlaps:
Jackson, WI (55053)
unified school districts (UNSDs): 01260 and 00210

Gaps:
Maricopa, AZ (04013)
between elementary school districts (ELSDs) 01380 and 04320

Yuma, AZ (04027) and Pima AZ (04109)
between ELSD 09600 in Yuma and UNSD 99997 (School District Not Defined) in Pima

Yuma, AZ (04027)
between ELSDs 05220 and 03900

Kern, CA (06029)
between ELSDs 04560 and 24330

Nevada, CA (06057)
between ELSDs 26820 and 00012

Orange, CA (06059)
between ELSD 14730 and UNSD 05880

San Bernardino, CA (06071)
between ELSDs 01710 and 41040

Santa Clara, CA (06085)
between ELSDs 22830 and 22350
between ELSD 22830 and UNSD 34590

San Mateo, CA (06081)
between ELSDs 17190 and 34920

Shasta, CA (06089)
between ELSD 27040 and UNSD 14950

Sonoma, CA (06097)
between ELSDs 32640 and 19410
between ELSDs 36180 and 40230

Ventura, CA (06111)
between ELSD 28170 and UNSD 09640
between ELSDs 29220 and 32760 (2)
between ELSD 30990 and UNSD 09640
between ELSDs 37140 and 30990

Clinton, IL (17027)
between ELSDs 37470 and 07010 (2)
between ELSD 07010 and UNSD 08460 (2)

Livingston, IL (17105)
between ELSDs 29520 and 00065

Ogle, IL, (17141)
between ELSDs 21130 and 14410
between UNSDs 25690 and 21300

Tazewell, IL (17179)
between ELSD 31080 and UNSD 26800

Union, IL (17181)
between ELSD 03750 and UNSD 12480

Washington, IL (17189)
between ELSDs 19740 and 27720
between ELSDs 19740 and 40680

Hancock, ME (23009)
between ELSD 14770 and UNSD 06260

Chouteau, MT (30015)
between ELSDs 03760 and 22750

Flathead, MT (30029)
Between ELSDs 15570 and 02850

Wheatland, MT (30107)
between ELSDs 13440 and 26790 (2),
between ELSDs 13440 and 15360

Cherry, NE (31031)
between ELSD 45270 and UNSD 74040

Hall, NE (31079)
within ELSD 19930
within ELSD 78930

Sheridan, NE (31161)
between ELSDs 60900 and 67290

Grant, WI (55043)
within UNSD 06870

Dodge, WI (55027)
between ELSD 10410 and UNSD 06780

User Note 11:  Census 2000 State Legislative Districts (Upper Chamber) Shapefile - Incomplete Coverage in West Virginia

The state legislative districts (upper chamber) coverage is missing from Wetzel County, WV (54103) and Marion County, WV (54049). The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in the 2009 release of the TIGER/Line Shapefiles.

User Note 12:   All Lines Shapefile - Incorrect Permanent Face IDs (TFIDs) on Some Edges

There are approximately 400 small edges where the left and right TFID’s are transposed. This may impact users who are creating layers and topologies from the All Lines Shapefiles. The Census Bureau is aware of this issue and is in the process of correcting these errors. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years.

User Note 13:   County Subdivision Shapefiles - County Boundary Snapping Error

There are some instances in the Census 2000 and Current County Subdivision files where subdivision boundaries appear to bleed into the adjacent county, as opposed to snapping to the boundary line between the two counties. The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years. The following is a list of state and county names, state and county FIPS codes, and County Subdivision FIPS codes and names, respective to the listed counties, where this occurs.

Kings County, CA (06031)
Tulare County, CA (06107)
between County Subdivisions 93250 (Stratford CCD) and 92480 (Pixley CCD)

Delores County, CO (08033)
Montezuma County, CO (08083)
between County Subdivisions 91064 (Dove Creek CCD) and 92945 (Pleasant View CCD)

Brevard County, FL (12009)
Osceola County, FL (12097)
between County Subdivisions 93588 (West Brevard) and 93146 (South and East Osceola CCD)

Burk County, GA (13033)
Jefferson County, GA (13163)
between County Subdivisions 91644 (Keysville CCD) and 93444 (Wrens CCD)

Cook County, IL (17031)
Lake County, IL (17097)
between County Subdivisions 81100 (Wheeling township) and 77668 (Vernon township)

Ford County, IL (17053)
Iroquois County, IL (17075)
between County Subdivisions 78474 (Wall township) and 44277 (Loda township)

Logan County, IL (17107)
Sangamon County, IL (17167)
between County Subdivisions 36789 (Hurlburt township) and 81776 (Williams township)

Cheyenne County, KS (20023)
Dundy County, NE (31057)
between County Subdivisions 06850 (Bird City township) and 90210 (Benkleman No. 2 precinct)

Ramsey County, MN (27123)
Washington County, MN (27163)
between County Subdivisions 40382 (Maplewood city) and 71428 (Woodbury city)

Attala County, MS (28007)
Leake County, MS (28079)
between County Subdivisions 92988 (District 5) and 90360 (District 1)

Bronx County, NY (36005)
Westchester County, NY (36119)
between County Subdivisions 08510 (Bronx borough) and 49121 (Mount Vernon city)

Hughes County, OK (40063)
Seminole County, OK (40133)
between County Subdivisions 91378 (Holdenville CCD) and 93835 (Wewoka CCD)

Beaver County, PA (42007)
Lawrence County, PA (42073)
between County Subdivisions 27336 (Franklin township) and 59488 (Perry township)

Blair County, PA (42013)
Centre County, PA (42027)
Clearfield County, PA (42033)
among County Subdivisions 71624 (Snyder township), 66736 (Rush township), and 31752 (Gulich township)

Garza County, TX (48169)
Lynn County, TX (48305)
between County Subdivisions 93110 (Post Northwest CCD) and 94230 (Wilson CCD)

Shawano County, WI (55115)
Waupaca County, WI (55135)
between County Subdivisions 28825 (Germania town) and 32925 (Harrison town)

User Note 14:  Census 2000 Block County-based Shapefile and Census 2000 Block State-based Shapefile - Missing Urban/Rural

The Census 2000 urban/rural indicator (UR00) is null for block 1005 in census tract 9615, Mercer County, ND (38057). The field should show "R".

The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.

2007 TIGER/Line Shapefiles

All legal boundaries and names are as of January 1, 2007. Released March 31, 2008.

The 2007 TIGER/Line Shapefiles were the first release of TIGER spatial data from the modernized Census Bureau's MAF/TIGER database in shapefile format.

Download

Technical Documentation

File Availability

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)
  • Metropolitan/Micropolitan Statistical Area (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:

  • American Indian Tribal Subdivision (Census 2000 and current)

The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.

2006 Second Edition TIGER/Line Files

All legal boundaries and names are as of January 1, 2006.

The 2006 Second Edition TIGER/Line files are the last version of the TIGER/Line files the Census Bureau released.

Download

The TIGER/Line files are organized by county. In order to use these files in a GIS you will need to convert them from ASCII to a GIS compatible format using a translator.

FTP site

Technical Documentation

User Notes

Errata Note 1: Sioux County, North Dakota (FIPS code 38085)

An American Indian area can cross state lines. When this occurs, the same area can have more than one FIPS code. The Standing Rock Reservation (census code 3970) exists in two states. The North Dakota portion has a FIPS code of 75300. The South Dakota portion has a FIPS code of 61260. There was a county boundary change since 2000 between Sioux County, North Dakota (FIPS code 38085) and Corson County, South Dakota (FIPS code 46031).

In Record Type S, three polygons identified with a CENID of C5062 and POLYIDs of 1144, 1146, and 1736 are erroneously shown with a FIPS 55 Code (American Indian/Alaska Native Area/Hawaiian Home Land), 2000 code (AIANHHFP) of 75300 (Standing Rock Reservation). The correct AIANHHFP code for these polygons is 61260 (Standing Rock Reservation).

In Record Type S, two polygons identified with a CENID of C5062 and POLYIDs of 1144 and 1736 are erroneously shown with a Census Code (American Indian Tribal Subdivision), 2000 code (AITSCE) of 550 (Porcupine Tribal Subdivision, North Dakota). The correct AITSCE code for these polygons is 650 (Rock Creek Tribal Subdivision, South Dakota). These two polygons also are erroneously assigned a FIPS 55 Code (American Indian Tribal Subdivision), 2000 code (AITS) of 63710 (Porcupine Tribal Subdivision, North Dakota). The correct AITS code for these polygons is 55360 (Rock Creek Tribal Subdivision, South Dakota).

In Record Type S, 62 polygons identified with a CENID of C5062 and POLYIDs of 251, 252, 257, 263, 266, 269, 270, 271, 272, 277, 280, 281, 282, 283, 284, 285, 895, 970, 1007, 1174, 1175, 1176, 1179, 1266, 1267, 1268, 1269, 1270, 1271, 1272, 1273, 1274, 1275, 1276, 1277, 1360, 1361, 1362, 1363, 1364, 1365, 1366, 1367, 1368, 1413, 1414, 1415, 1416, 1417, 1418, 2057, 2058, 2075, 2076, 2077, 2078, 2095, 2096, 2097, 2118, 2119, and 2330 are erroneously shown with a FIPS 55 Code (American Indian Tribal Subdivision), 2000 code (AITS) of 33550. The correct AITS code for these polygons is 42000 (Kenel Tribal Subdivision).

The FIPS 55 Code (FIPS) for Kenel Tribal Subdivison is erroneously shown in Record Type C, Entity Type Code (ENTITY) X as 33550 for two records. The correct FIPS 55 Code is 42000.

As a result of the errors appearing in Record Type S described above, six records are missing from Record Type C. We are providing the missing Record Type C records using the Record Type C layout. Using the file in Record Type C format, users can insert the missing records into Record Type C.

User Note 1: Same State and County Codes on Both Sides of a Current County Boundary

To avoid one of the major difficulties data users had last decade with the mixing of "current" state and county codes with decennial census tract and block numbers which are uniquely identified only by the decennial census state and county codes, the Census Bureau is continuing to provide Census 2000 codes on Record Type 1 even though the distribution unit for the 2006 Second Edition TIGER/Line files is current county or statistically equivalent entity. Since some county or statistically equivalent entity boundaries have changed since Census 2000, the current boundaries may not match those used in Census 2000. Thus it is possible to find some territory that was in County A in the Census 2000 versions of the TIGER/Line files in the 2006 Second Edition TIGER/Line file for County B.

In counties or statistically equivalent entities that have gained territory, it is possible to have a line segment that is a current county boundary and has the single-side source code (field name SIDE1) set, but has the same state and code codes on both sides of the line segment. This occurs because a polygon that was, for example, in the Census 2000 TIGER/Line file for County A now is in the 2006 Second Edition TIGER/Line file for County B. Since Record Type 1 displays the Census 2000 geography, the state and county code for County A (the county or statistically equivalent entity that lost territory) appears on this line segment even though it currently is part of County B. The other side of this line segment is in an adjacent TIGER/Line file and the Census Bureau appends the state and county code of the adjacent county (County A) to this line segment. The result is a line segment that is a current county boundary yet has the same state and county codes on both sides of the line segment.

The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.

2000 TIGER/Line Files

All legal boundaries and names are as of January 1, 2000.

108th Congressional District Census 2000

Urban Area Census 2000

Census 2000

Redistricting Census 2000

Released December 2000 - March 2001. The Island Areas are not included in this release.


Download - FTP Site

Technical Documentation [PDF]

ReadMe File [TXT]

Metadata [TXT]

Errata and User Notes

The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.

1992 TIGER/Line Files

The 1992 TIGER/Line Files serve as a link between 1980 and 1990 geography. These files are in an early TIGER/Line format that generally does not work with shapefile conversion software.

Technical support is not available for these files.

The boundaries shown are for Census Bureau statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement.


Legal Disclaimer: No warranty, expressed or implied, is made with regard to the accuracy of the data in the TIGER/Line Shapefiles, and no liability is assumed by the United States Government in general, or the Census Bureau specifically, as to the positional or attribute accuracy of the data. The boundary information in the TIGER/Line Shapefiles is for statistical data collection and tabulation purposes only. Their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions.


[PDF] or PDF denotes a file in Adobe’s Portable Document Format. To view the file, you will need the Adobe® Reader® Off Site available free from Adobe. [Excel] or the letters [xls] indicate a document is in the Microsoft® Excel® Spreadsheet Format (XLS). To view the file, you will need the Microsoft® Excel® Viewer Off Site available for free from Microsoft®. This symbol Off Site indicates a link to a non-government web site. Our linking to these sites does not constitute an endorsement of any products, services or the information found on them. Once you link to another site you are subject to the policies of the new site.
Source: U.S. Census Bureau | Geography | (301) 763-1128 |  Last Revised: March 04, 2013