Errata and User Notes for the 2002 TIGER/Line® Files
Errata Note 1: Jackson County, Kansas (FIPS code 20085)
The name of an American Indian Reservation is erroneously shown in Record Type C, Entity Type I as the "Prairie Band Potawatomi Nation." The correct name is "Prairie Band of Potawatomi Nation."
Errata Note 2: Aroostook County, Maine (FIPS code 23003)
In Record Type S, the polygon identified with a CENID of C3352 and POLYID of 8838 is erroneously shown with an MSACMSA code of 0730. This polygon is not part of the Bangor, Maine Metropolitian Statistical Area (MSA) and no MSA code should appear in this field. All the polygons in Aroostook County are erroneously shown with a New England County Metropolitan Area (NECMA) code of 0733 in Record Type S. Aroostook County is not part of the Bangor, Maine NECMA and no NECMA code should appear in the NECMA field.
Errata Note 3: Independent Cities in Virginia (FIPS codes 51510 through 51840)
The Place Description Code (PDC) for all Independent Cities in Virginia is erroneously shown as 0 in Record Type C, Entity Type C for those records with a DATAYR = CQR0. The correct PDC is 9. The FIPS Class Code (FIPSCC) is erroneously shown as Z7 in Record Type C, Entity Type M for those records with a DATYR = 2000. The correct FIPS Class Code is C7.
Errata Note 4: Prince William County (FIPS code 51153) and Manassas City (FIPS code 51683) Virginia
All polygons in Prince William County and Manassas City, Virginia 2002 TIGER/Line released in January 2003 are erroneously shown with a blank Consolidated Metropolitan Statistical Area/Metropolitan Statistical Area Code, Current (MSACMSACU) and a blank Primary Metropolitan Statistical Area Code, Current (PMSACU) in Record Type A. The correct MSACMSACU code for all polygons in these counties or statistically equivalent entities is 8872. The correct PMSACU code for all polygons in these counties or statistically equivalent entities is 8840. The Census Bureau regenerated and rereleased the 2002 TIGER/Line files for these counties or statistically equivalent entities in June 2003. The correct codes appear in the MSACMSACU and PMSACU fields in the files released in June 2003.
Errata Note 5: Pierce (FIPS code 13229) and Ware (FIPS code 13299) Counties Georgia
The Pierce County 2002 TIGER/Line file erroneously contains a detached polygon identified by CENID c1994 and POLYID 43 which actually belongs in Ware County. This problem has been resolved in the Census TIGER database and the 2003 TIGER/Line files will contain the correct county boundaries.
Errata Note 6: Typographical Error in the Technical Documentation for Record Type I
In Chapter 6 of the 2002 TIGER/Line Technical Documentation the record layout for Record Type I erroneously indicates that blank values are not valid for the TIGER 1-Cell Source Code field (field name SOURCE). Blank values are valid for this field in the 2002 TIGER/Line files.
User Note 1: Areal Landmarks
Many areal (polygon) landmarks that appeared in the Census 2000 and earlier versions of the TIGER/Line files do not appear in the 2002 TIGER/Line files. The majority of these missing landmarks are water landmarks. The Census Bureau has identified and fixed the problem that resulted in these areal landmarks not appearing in the 2002 TIGER/Line files and they should appear in the 2003 and subsequent versions of the TIGER/Line files.
User Note 2: 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 2002 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 2002 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 2002 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.
Source: U.S. Census Bureau, Geography Division
Created: January 8, 2003
Last revised: August 14 2003
