Errata and User Notes for the 2003 TIGER/Line® Files
Errata Note 1: Montgomery County, Ohio (FIPS code 39113)
The Place Description Code (PDC) for the county subdivision of Union (FIPS code 78470) is erroneously shown as 0 in Record Type C, Entity Type M, DATAYR 2003. The correct PDC is 9.
Errata Note 2: Green County, Wisconsin (FIPS code 55045)
The census feature class code (CFCC) for TLID 48533689 is incorrectly shown as "B a". The correct CFCC is B11.
Errata Note 3: Urban/Rural Indicator in Record Type B
In Record Type B, the Urban/Rural Indicator, 2000 Corrected (field name URCC) is erroneously shown as U where the Urban Area, 2000 Corrected (field name UACC) is blank. The Urban/Rural Indicator in Record Type B should be blank for records where the UACC field is blank.
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 2003 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 2003 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 2003 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: March 5, 2004
Last revised: January 10 2005
