Errata and User Notes for the 2004 First Edition TIGER/Line®
Errata Note 1: Eagle County, Colorado (FIPS code 08037)
In Record Type E, the polygon identified with a CENID of C1522 and a
POLYID of 3751 is erroneously shown with a FIPS55 Economic Census Place code
(PLACEEC) of 99999 (Balance of County). The correct PLACEEC code is 04935
Errata Note 2: Caddo Parish, Louisiana (FIPS code 22017)
In Record Type E, the polygons identified with a CENID of C3238 and
POLYIDs of 4921 and 4932 are erroneously shown with a FIPS55 Economic Census
Place code (PLACEEC) of 70000 (Shreveport). The correct PLACEEC code for both
polygons is 99999 (Balance of Parish).
Errata Note 3: Lac Qui Parle County, Minnesota (FIPS code 27073)
In Record Type E, six polygons identified with a CENID of C3696) and
POLYIDs of 122, 255, 381, 458, 479, and 480 are erroneously shown with a FIPS
Economic Census County code (COUNTYEC) of 011 (Big Stone County). The correct
COUNTYEC code for all these polygons is 073 (Lac Qui Parle County).
Errata Note 4: 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: Metropolitan Statistical Areas, Micropolitan Statistical
Areas, Combined Statistical Areas,and New England City and Town Areas
The Metropolitan Statistical Area, Micropolitan Statistical Area,
Combined Statistical Area (CSA), and New England City and Town Area (NECTA)
boundaries, names, and codes appearing in the 2004 First Edition TIGER/Line
files are those in effect at the time of the Office of Management and Budget's
(OMB's) announcement on June 6, 2003. The OMB announced updates in OMB Bulletin No.
04-03 in December 2003.
User Note 2: Same State and County Codes on Both Sides of a Current
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.
[PDF] or denotes a file in Adobe’s Portable Document Format. To
view the file, you will need the Adobe® Acrobat®
available free from Adobe.
Source: U.S. Census Bureau
Last revised: Friday, 28-Jan-2005 16:20:23 EST