In Record Type E, the polygon identified with a CENID of c3238 and POLYID of 4932 is erroneously shown with a FIPS55 Economic Census Place code (PLACEEC) of 99999 (Balance of Parish). The correct PLACEEC code for this polygon is 70000 (Shreveport).
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.
The FIPS Class Code (FIPSCC) for Baltimore city, Maryland is erroneously shown in Record Type C, Entity Type Code (ENTITY) M as C7. The correct FIPSCC is Z7. The FIPS 55 Code (FIPS) for Baltimore city, Maryland is erroneously shown in Record Type C, ENTITY M as 04000. The correct FIPS 55 Code is 90002.
The FIPS Class Code (FIPSCC) for the Independent Cities in Virginia are erroneously shown in Record Type C, Entity Type Code (ENTITY) M as C7. The correct FIPSCC is Z7. The FIPS 55 Code (FIPS) for the Independent Cities in Virginia are erroneously shown in Record Type C; ENTITY M; FIPS Code, Name, and/or Attribute Data Applicable Year (DATAYR) 2004 with codes below the 90000 code range. The correct FIPS 55 Code appears in Record Type C; ENTITY M; DATAYR 2000. Data users should correct the FIPS 55 Code on the ENTITY M records with a DATAYR of 2004 to match the FIPS 55 Code on the ENTITY M records with a DATAYR of 2000.
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 2004 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 2004 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 2004 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.
denotes a file in Adobe’s Portable Document Format.
To view the file, you will need the
Adobe® Acrobat® Reader
available free from Adobe.
