2004 First Edition TIGER/Line(R) Files Technical Documentation Chapter 2: Version Code and Identification Numbers The vintage of the TIGER/Line(R) files is reflected in its name, not in the version code. The year noted in the name of the TIGER/Line files, the 2003 TIGER/Line files for example, normally represents the vintage of the boundaries in the file while the version code reflects the creation date of the TIGER/Line files. Version Code The version code is a numeric code that uniquely identifies a record with a specific release version of the TIGER/Line files. All record types have a 4-character field for the version code. The version code of the TIGER/Line files is assigned as "MMYY" which represents the month and year that the data in the file was extracted from the TIGER(R) database. This means that county files created for the same program are likely to have different version codes. Adjacent counties in a state may have different version codes if they were extracted at different points in time. This will make it easier for users to determine the latest version of the data if they have several versions of the TIGER/Line files for a county. The version codes for earlier releases of the TIGER/Line files are as follows: 1000 to 1100 - TIGER/Line Files, Redistricting Census 2000 0301 to 0801 - TIGER/Line Files, Census 2000 0302 to 0502 - TIGER/Line Files, UA Census 2000 1002 to 0603 - TIGER/Line Files, 2002 0203 to 0303 - TIGER/Line Files, 108th CD Census 2000 1203 to 0304 - TIGER/Line Files, 2003 TIGER/Line Identification Number (TLID) The TIGER/Line files use a permanent 10-digit TIGER/Line record identification number (TLID) to uniquely identify a complete chain for the Nation. TLID Codes The 10-digit TLID will not exceed the value 2^31 - 1 (2,147,483,647) and will represent the same complete chain in all versions of this file, beginning with the TIGER/Line Precensus Files, 1990. The minimum value is 100,001. Topological changes to the complete chain will cause the TLIDs to change. For instance, when updates split an existing complete chain, each of the new parts receives a new TLID; the old TLID is not reused. For those Record Type 1 records that are county boundaries (those records that have the single-side source code-SIDE1-set), the U.S. Census Bureau is making the TLIDs for these records the same so that the complete chain representing a segment of the boundary between two neighboring counties will have the same TLID code in both counties. To make the TLIDs for these complete chains identical in both files, the U.S. Census Bureau is replacing the original TLID of one of the line segments with the TLID from the other file. Record Type R contains the range of unique complete chain record numbers assigned to a census file in a nationwide scheme. Record Type R has the lowest (minimum) and the highest (maximum) record numbers for the range. Permanent record numbers are assigned within each partition of the Census TIGER(R) database. Numbers are assigned to complete chains beginning at the minimum value and increasing the current value by one until it reaches the maximum value. For those complete chains that represent a segment of the boundary between two neighboring counties, the TLID will not appear in Record Type R for one of the counties. This occurs when the TLID for the complete chain is from the adjoining county and would be outside of the numeric range for this county. Users will need to reference Record Type R from that adjoining county for the Record Type R information for these TLIDs. Record Type H shows the history of a particular TLID, whether combined or split, and its predecessors or successors. For those complete chains that represent a segment of the boundary between two neighboring counties, the complete history for a TLID may not appear in Record Type H for one of these counties. Where the TLID is from the adjoining county only the most current TLID history record will appear in a TIGER/Line file. Users will need to reference Record Type H from the adjoining county to find the entire history for that TLID. TLID Record Locations The TLID field appears in columns 6 through 15 of the following record types: Record Type 1 Record Type 6 Record Type 2 Record Type Z Record Type 4 The TLID field appears in columns 11 through 20 of the following record types: Record Type H Record Type I In Record Type U, the TLID field appears in columns 22 through 31, 32 through 41, 42 through 51, and 52 through 61. TLID Record Linkages The TLID field provides a key for linking records containing primary attributes describing the complete chain or the geographic entity codes associated with the left and the right sides of the complete chain. Record Type I contains the key fields required to link the TLID and the GT-polygon identification fields, CENID and POLYID. Record Type I also contains the key fields required to link the TIGER zero-cell identification numbers (TZIDs) identifying the start node and end node of each complete chain to the TLID of that complete chain. TLID Sort Sequence Each record type is a separate file. The records in each record type do not have an overall sort sequence. Data users may wish to sort the file by TLID in order to facilitate record linkages. TIGER Zero-Cell Identification Number (TZID) The post-Census 2000 TIGER/Line files use a permanent 10-digit TIGER zero-cell identification number (TZID) to uniquely identify a zero-cell (node) for the Nation. TZID Codes The 10-digit TZID will not exceed the value 2^31 - 1 (2,147,483,647) and will represent the same zero-cell in all versions of this file, beginning with the 2002 TIGER/Line. The minimum value is 100,001. For those zero-cells along the boundary between two neighboring counties, the U.S. Census Bureau is making the TZIDs for these zero- cells the same so that the zero-cell will have the same TZID code in both counties. To make the TZIDs for these zero-cells identical in both files, the U.S. Census Bureau is replacing the original TZID of one of the zero-cells with the TZID from the other file. Record Type R contains the range of unique zero-cell record numbers assigned to a census file in a nationwide scheme. Record Type R has the lowest (minimum) and the highest (maximum) record numbers for the range. Permanent record numbers are assigned within each partition of the Census TIGER database. Numbers are assigned to zero-cells beginning at the minimum value and increasing the current value by one until it reaches the maximum value. For those zero-cells along the boundary between two neighboring counties, the TZID will not appear in Record Type R for one of the counties. This occurs when the TZID for the zero- cell is from the adjoining county and would be outside of the numeric range for this county. Users will need to reference Record Type R from that adjoining county for the Record Type R information for these TZIDs. TZID Record Locations The TZID field appear in the following record types: Record Type I - Contains start and end TZIDs in columns 21 through 30 (start) and columns 31 through 40 (end) Record Type T - Appears in columns 11 through 20 Record Type U - Appears in columns 11 through 20 TZID Record Linkages The TZID field provides a key that can be used for sequentially linking complete chains. Record Type I contains the key fields required to link the start and end TZIDs to the TLID and the GT-polygon identification fields, CENID and POLYID. TZID Sort Sequence Each record type is a separate file. The records in each record type do not have an overall sort sequence. Data users may wish to sort the file by TZID in order to facilitate record linkages. User-Defined Changes to the TIGER/Line Files TLID and TZID as Standard Identification Numbers Users should store the record number and the version code associated with each complete chain and zero-cell in their local systems to ensure their ability to match records with earlier or later versions of the TIGER/Line files. The record and version numbers of each complete chain and zero-cell provide an important link to the corresponding complete chain and zero-cell in the Census TIGER database. This key will allow users to transfer new information from later U.S. Census Bureau TIGER/Line releases into their database. Feature Changes If users choose to assign a new record number (TLID) to each new complete chain they create and a new record number (TZID) to each new zero-cell they create the U.S. Census Bureau recommends assigning a version number with a value greater than 5000 in order to avoid duplicating a U.S. Census Bureau-assigned record number that may appear elsewhere in the national file. Users should create a new record for each new complete chain and zero-cell, including those formed when a new intersection splits an existing complete chain. If a complete chain has been assigned different feature identifiers, attributes, and/or coordinate positions without being merged with or split from another complete chain, it is a modified complete chain and does not need a new TLID. Users should assign a version code equal to 4999 for all deleted complete chain, zero-cell, and landmark records. Users may assign or reassign polygon and landmark identification numbers in any manner that uniquely identifies each within a file. TIGER/Line Polygon Identification Numbers (CENID, POLYID) The U.S. Census Bureau uses two fields, the census file identification code (CENID) and the polygon identification code (POLYID), to uniquely identify GT-polygons. The CENID is a U.S. Census Bureau alphanumeric identifier used to uniquely number the GT-polygons within its TIGER partitions. Since the partitions may include only a portion of a county, the TIGER/Line files may contain multiple CENIDs. The polygon identification number (POLYID) is a temporary number assigned to every polygon in the Census TIGER database. Although this number is part of the database design, it is a dynamic number and can change between different versions of the TIGER/Line files. The Census TIGER database does not contain permanent identifiers for GT-polygons as it does for complete chains. POLYID is unique only within CENID; in cases where a TIGER/Line file contains more than one CENID, the POLYID may not be unique within that file. Within each CENID, the value for the POLYID starts with "1" and increments sequentially until all GT-polygons are numbered. CENID and POLYID Codes The CENID is a 5-character alphanumeric code. Record Type R contains a list of all valid CENIDs used in each county TIGER/Line file. The POLYID code is an integer identification number, without leading zeros, applied to each GT-polygon. The POLYID with a value of 1 refers to the universal polygon, the polygon that refers to all space outside a county coverage area and is excluded from Record Types A, B, E, I, P, and S. The range of POLYID numbers in a county file may contain gaps or skipped numbers resulting from the use of one partition (CENID) for more than one TIGER/Line county file. POLYID numbers also may duplicate in a single TIGER/Line (R) file as they are unique only within CENID. A single TIGER/Line file may contain CENID information from many other census files. Either the CENIDL and POLYIDL, or CENIDR and POLYIDR fields in Record Type I will have a blank value where the complete chain is a county boundary. CENID and POLYID Record Locations The CENID and POLYID fields appear in the following record types: Record Type 8 - Records exist only for area landmark GT-polygons Record Type A - Records exist for all GT-polygons Record Type B - Records exist for GT-polygons with Count Question Resolution changes Record Type E - Records exist for all Economic Census GT-polygons Record Type I - Contains left- and right-side CENIDs and POLYIDs associated with each complete chain Record Type P - Records exist for all GT-polygons Record Type R - Contains only CENID; Record Type R lists the minimum and maximum possible TLIDs and TZIDs, and the highest TLID and TZID from each census file (CENID) used to generate the current version of the TIGER/Line files. Record Type S - Records exist for all GT-polygons CENID and POLYID Record Linkages The TIGER/Line files use both the CENID and POLYID fields to link all of the polygon record types together (Record Types A, B, E, P, and S), to link the GT-polygons to the associated complete chains, and to link area landmarks to GT-polygons. The CENID and POLYID fields link the geographic area codes in Record Types A, B, E, and S to Record Type P which contains the coordinates for an internal point in the GT-polygon. The TIGER/Line files include a Type A and a Type S record for each Type P record. Record Type I provides a link between the GT-polygon records and the record types containing complete chain attributes (Record Types 1, 2, 4, and 6). Each Type I record identifies a complete chain by TLID with a left- and right-side GT-polygon. Here CENIDL and POLYIDL contain the CENID and POLYID codes for the GT-polygon on the left side of the line. Likewise, CENIDR and POLYIDR contain the CENID and POLYID codes for the GT-polygon on the right side of the line. There is a Type I record for each Type 1 record. All CENID and POLYID codes appear in Record Type I. To find all of the complete chains that form the boundary of a specific GT-polygon, search Record Type I for a match with either the left or the right CENID and POLYID. Where the left and the right CENID and POLYID codes are the same, the complete chain is internal to the GT-polygon (e.g., a dead-end street). Record Type 8 provides a link between the GT-polygons and the landmark feature records. See the section, TIGER/Line Landmark Identification Numbers, in this chapter. CENID and POLYID Sort Sequence The POLYID codes appear in numeric sequence by alphanumeric CENID in Record Types A, B, E, P, and S. There is no systematic CENID or POLYID sequence in Record Type I. TIGER/Line Landmark Identification Numbers (LAND) The landmark feature identification number (LAND) is a 10-digit number that uniquely identifies both point and area landmarks within each county file. LAND is not a permanent number; the U.S. Census Bureau assigns LANDs each time a new version of the TIGER/Line files is produced. Within each county, LANDs are assigned beginning with "1" and are incremented sequentially until all features are numbered. In rare situations, Record Type 7 may list the same LAND number more than once if the landmark has more than one feature name. Each name appears as a separate data record in Record Type 7. These data records describe the same landmark and have the same LAND. Overlapping landmarks (e.g., a pond located in a park) may cause more than one name to be assigned to a GT-polygon. However, overlapping landmarks are separate features with different LANDs. LAND Codes The LAND is an integer number that does not contain leading zeros. It is assigned during the extraction of the data and is not a permanent number. There may be gaps in the sequence of the LANDs in Record Type 7 because of the way this information is extracted. LAND Record Locations The LAND field appears in the following record types: Record Type 7 - Landmark attributes Record Type 8 - Linkage record containing the LAND and the CENID and POLYID fields LAND Record Linkages Record Type 8 links each area landmark's LAND with a CENID and POLYID. Each area landmark will have one or more Type 8 records that together identify all of the GT-polygons that make up the landmark. LAND Sort Sequence Record Type 7 and 8 contain records sorted in ascending order by LAND. In Record Type 8, each LAND is repeated for each GT-polygon covered by the area landmark.