The feature names in the All Lines shapefile may not be consistent from one edge to the next along the extent of a road feature. The All Lines shapefile identifies the primary street name for an edge, however some primary names and alternate names have been flipped resulting in a primary feature name for one edge being identified as an alternate name on another. All feature names (featname.dbf), whether primary or alternate, can be related to the All Lines shapefile (edges.shp) by matching the TLIDs.

In the All Lines shapefile, the permanent face ID on the left of the edge (TFIDL) value or the permanent face ID on the right of the edge (TFIDR) value will be blank for edges on the outer boundary of a county and for edges on the outer boundary of the United States, Puerto Rico and the Island Areas. The TFID (either left or right side) that does not appear in the attribute table of the county file will appear in the adjacent county's attribute table. This may impact users who are creating layers and topologies from the All Lines Shapefiles.

The ZIP plus 4 code values will not appear in the 2008 TIGER/Line Shapefiles.

Both the Census 2000 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile and the 2002 5-Digit ZIP Code Tabulation Area (ZCTA5) Shapefile will not contain values for areas without an actual ZCTA code. That is, areas with large amounts of land and no ZCTA code that were previously coded with nnnXX will not be included, and neither will areas with large amounts of water and no ZCTA code that were previously coded with nnnHH. As a result, there is no longer complete coverage of the United States and Puerto Rico by 5-digit ZCTAs, rather only those areas that have an actual ZCTA code will be included in the coverage. Also, the Topological Faces (2-cells with all Geocodes) Relationship File will not contain ZCTA5CE00 or ZCTA5CE codes where code is nnnXX or nnnHH. This means that only those faces that make up a ZCTA boundary will contain ZCTA codes.

Both the Current Place Shapefile and the Census 2000 Place Shapefile metadata (place.shp.xml) files contain an incorrect MAF/TIGER Feature Class Code (MTFCC) for Census Designated Place. The MTFCC is incorrectly listed as G4120. The correct MTFCC code is G4210. The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years.

In the Area Landmark and Point Landmark Shapefiles the MAF/TIGER Feature Class Code (MTFCC) of K2190 should be listed as one of the following MTFCC codes: K2180, K2183, K2184, K2185, K2186, or K2188. The Census Bureau is aware of this problem and is in the process of fixing them for the next release of the TIGER/Line shapefiles.

The Spatial Metadata Identifier (SMID) in the All Lines shapefile identifies the source of the coordinates for the line segment when available (not every edge will have a SMID) and provides the link between the TIGER/Line Shapefile and the source and horizontal spatial accuracy information. There are a few occurrences where the SMIDs are missing from some All Lines metadata files; hence the spatial metadata elements are also missing. The Census Bureau is aware of this problem and is in the process of fixing this issue. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years.

n the 2008 TIGER/Line Shapefiles release we have identified 1,159 counties that contain new features that are distorted. These features appear to be pulled away from their position to a point and returned to their correct location forming a distorted edge. The problems are a result of the efforts to automatically integrate new data with existing positionally accurate features. We have not identified wide-spread issues in other counties but it is possible that there are additional counties with some distorted edges.

We are working diligently to correct these errors and anticipate a marked improvement in the 2009 TIGER/Line Shapefiles. We are continually working on updating our database and improvements will be seen with each subsequent release. In the meantime, depending on your needs, you may wish to use the prior version of the TIGER/Line Shapefiles or wait for the 2009 release which is scheduled for late summer.

Spatial data coverage for elementary and unified school districts is incomplete in one area, creating a tiny hole in school district coverage. This problem was corrected in the Census Bureau's source database after the 2008 TIGER/Line shapefile creation. The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years. The state and county names, state and county FIPS codes, and school districts where this occurs are below:

Monroe, TN 47123 and McMinn, TN 47107
between elementary school district (ELSD) 04050 in Monroe and unified school district (UNSD) 02820 in McMinn

Spatial data are incorrect for a number of elementary and unified school districts, creating tiny overlaps and holes in school district coverage. These problems were corrected in the Census Bureau's source database after the 2008 TIGER/Line shapefile creation. The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in the 2009 release of the TIGER/Line Shapefiles. The state and county names, state and county FIPS codes, and school districts where this occurs are below:

Overlaps:
Jackson, WI (55053)
unified school districts (UNSDs): 01260 and 00210

Gaps:
Maricopa, AZ (04013)
between elementary school districts (ELSDs) 01380 and 04320

Yuma, AZ (04027) and Pima AZ (04109)
between ELSD 09600 in Yuma and UNSD 99997 (School District Not Defined) in Pima

Yuma, AZ (04027)
between ELSDs 05220 and 03900

Kern, CA (06029)
between ELSDs 04560 and 24330

Nevada, CA (06057)
between ELSDs 26820 and 00012

Orange, CA (06059)
between ELSD 14730 and UNSD 05880

San Bernardino, CA (06071)
between ELSDs 01710 and 41040

Santa Clara, CA (06085)
between ELSDs 22830 and 22350
between ELSD 22830 and UNSD 34590

San Mateo, CA (06081)
between ELSDs 17190 and 34920

Shasta, CA (06089)
between ELSD 27040 and UNSD 14950

Sonoma, CA (06097)
between ELSDs 32640 and 19410
between ELSDs 36180 and 40230

Ventura, CA (06111)
between ELSD 28170 and UNSD 09640
between ELSDs 29220 and 32760 (2)
between ELSD 30990 and UNSD 09640
between ELSDs 37140 and 30990

Clinton, IL (17027)
between ELSDs 37470 and 07010 (2)
between ELSD 07010 and UNSD 08460 (2)

Livingston, IL (17105)
between ELSDs 29520 and 00065

Ogle, IL, (17141)
between ELSDs 21130 and 14410
between UNSDs 25690 and 21300

Tazewell, IL (17179)
between ELSD 31080 and UNSD 26800

Union, IL (17181)
between ELSD 03750 and UNSD 12480

Washington, IL (17189)
between ELSDs 19740 and 27720
between ELSDs 19740 and 40680

Hancock, ME (23009)
between ELSD 14770 and UNSD 06260

Chouteau, MT (30015)
between ELSDs 03760 and 22750

Flathead, MT (30029)
Between ELSDs 15570 and 02850

Wheatland, MT (30107)
between ELSDs 13440 and 26790 (2),
between ELSDs 13440 and 15360

Cherry, NE (31031)
between ELSD 45270 and UNSD 74040

Hall, NE (31079)
within ELSD 19930
within ELSD 78930

Sheridan, NE (31161)
between ELSDs 60900 and 67290

Grant, WI (55043)
within UNSD 06870

Dodge, WI (55027)
between ELSD 10410 and UNSD 06780

The state legislative districts (upper chamber) coverage is missing from Wetzel County, WV (54103) and Marion County, WV (54049). The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in the 2009 release of the TIGER/Line Shapefiles.

There are approximately 400 small edges where the left and right TFID’s are transposed. This may impact users who are creating layers and topologies from the All Lines Shapefiles. The Census Bureau is aware of this issue and is in the process of correcting these errors. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years.

There are some instances in the Census 2000 and Current County Subdivision files where subdivision boundaries appear to bleed into the adjacent county, as opposed to snapping to the boundary line between the two counties. The Census Bureau is aware of this issue and is in the process of correcting it. These corrections will be reflected in subsequent releases of the TIGER/Line Shapefiles over the next two years. The following is a list of state and county names, state and county FIPS codes, and County Subdivision FIPS codes and names, respective to the listed counties, where this occurs. Kings County, CA (06031)
Tulare County, CA (06107)
between County Subdivisions 93250 (Stratford CCD) and 92480 (Pixley CCD)

Delores County, CO (08033)
Montezuma County, CO (08083)
between County Subdivisions 91064 (Dove Creek CCD) and 92945 (Pleasant View CCD)

Brevard County, FL (12009)
Osceola County, FL (12097)
between County Subdivisions 93588 (West Brevard) and 93146 (South and East Osceola CCD)

Burk County, GA (13033)
Jefferson County, GA (13163)
between County Subdivisions 91644 (Keysville CCD) and 93444 (Wrens CCD)

Cook County, IL (17031)
Lake County, IL (17097)
between County Subdivisions 81100 (Wheeling township) and 77668 (Vernon township)

Ford County, IL (17053)
Iroquois County, IL (17075)
between County Subdivisions 78474 (Wall township) and 44277 (Loda township)

Logan County, IL (17107)
Sangamon County, IL (17167)
between County Subdivisions 36789 (Hurlburt township) and 81776 (Williams township)

Cheyenne County, KS (20023)
Dundy County, NE (31057)
between County Subdivisions 06850 (Bird City township) and 90210 (Benkleman No. 2 precinct)

Ramsey County, MN (27123)
Washington County, MN (27163)
between County Subdivisions 40382 (Maplewood city) and 71428 (Woodbury city)

Attala County, MS (28007)
Leake County, MS (28079)
between County Subdivisions 92988 (District 5) and 90360 (District 1)

Bronx County, NY (36005)
Westchester County, NY (36119)
between County Subdivisions 08510 (Bronx borough) and 49121 (Mount Vernon city)

Hughes County, OK (40063)
Seminole County, OK (40133)
between County Subdivisions 91378 (Holdenville CCD) and 93835 (Wewoka CCD)

Beaver County, PA (42007)
Lawrence County, PA (42073)
between County Subdivisions 27336 (Franklin township) and 59488 (Perry township)

Blair County, PA (42013)
Centre County, PA (42027)
Clearfield County, PA (42033)
among County Subdivisions 71624 (Snyder township), 66736 (Rush township), and 31752 (Gulich township)

Garza County, TX (48169)
Lynn County, TX (48305)
between County Subdivisions 93110 (Post Northwest CCD) and 94230 (Wilson CCD)

Shawano County, WI (55115)
Waupaca County, WI (55135)
between County Subdivisions 28825 (Germania town) and 32925 (Harrison town)

The Census 2000 urban/rural indicator (UR00) is null for block 1005 in census tract 9615, Mercer County, ND (38057). The field should show "R".