Name File Type Size Last Modified
  Documentation 12/23/2021 02:15:PM
2002vX.zip application/zip 7.2 GB 12/23/2021 07:02:AM
2002vY.zip application/zip 7.2 GB 12/23/2021 07:08: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

2002 TIGER/Line Files

The current boundaries represented in the 2002 TIGER/Line files are those reported to the Census Bureau by April 1, 2002 as being in effect as of January 1, 2002.The 2002 TIGER/Line files contain few, if any, updates to street features or address ranges from the Census 2000 versions of the TIGER/Line files. Some additional features may have been added in the 20 counties where the Census Bureau improved the street feature coordinates.

About the Files

The Census Bureau has made major changes to the structure, field definitions, and contents for the 2002 TIGER/Line files. New record types have been added, two record types were deleted, and several record types were expanded and substantially revised. The Census Bureau has removed the 1990 geography from the 2002 TIGER/Line files replacing it with current geography. Also new for the 2002 TIGER/Line files is a permanent zero-cell (or node) identification number (TZID) for each node.

To improve the ability of data users to merge multiple counties, the Census Bureau is adding the state and county codes to those Record Type 1 records for the adjacent county (these are the Record Type 1 records that have the single-sided segment flag set, and until this version, all the data elements for the side of the record "outside" the county have been blank). The Census Bureau also is making the TLIDs and TZIDs for these records the same. Thus the county boundary segments and zero-cells in adjacent counties will now have the same TLID and TZID. The Census 2002 TIGER/Line data dictionary contains a complete list of all the fields in the 19 record types which are listed below.

  • Record Type 1 Complete Chain Basic Data Record
  • Record Type 2 Complete Chain Shape Coordinates
  • Record Type 4 Index to Alternate Feature Identifiers
  • Record Type 5 Complete Chain Feature Identifiers
  • Record Type 6 Additional Address Range and ZIP Code Data
  • Record Type 7 Landmark Features
  • Record Type 8 Polygons Linked to Area Landmarks
  • Record Type A Polygon Geographic Entity Codes: Current Geography
  • Record Type B Polygon Geographic Entity Codes: Corrections
  • Record Type C Geographic Entity Names
  • Record Type E Polygon Geographic Entity Codes: Economic Census
  • Record Type H TIGER/Line ID History
  • Record Type I Link Between Complete Chains and Polygons
  • Record Type P Polygon Internal Point
  • Record Type R TIGER/Line ID Record Number Range
  • Record Type S Polygon Geographic Entity Codes: Census 2000
  • Record Type T TIGER Zero-Cell ID
  • Record Type U TIGER/Line ID Overpass/Underpass Identification
  • Record Type Z ZIP+4AE Codes
The TIGER/Line data is stored in compressed format in subdirectories by state name. There is one TIGER/Line file (in a compressed format) for each county or county equivalent. The file names consist of TGR + the 2-digit state FIPS (Federal Information Processing Standards) code + the 3-digit county FIPS code (i.e. TGR01031.ZIP for Coffee County, Alabama.) Each state folder contains individual county files.

The individual county files include one file for each record type included for that county with the following name convention: tgr01031.rt1. The convention follows the order described above with each file having a suffix which includes 'rt' (record type) followed by its designation (in this case record type 1). Each county file also contains its own metadata record.

All documentation files for the TIGER/Line data are stored in a directory named '0docs' which is located in the 'Parent Directory'. This directory appears at the top of the index of state subdirectories for each edition of the TIGER/Line files. The documentation includes a complete list of FIPS state and county codes.



Related Publications

Published Versions

Export Metadata

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.