U.S. Census Bureau TIGER/Line Feature Representation
In addition to the generic FME feature attributes that FME Workbench adds to all features (see About Feature Type Attributes), this format also adds format-specific attributes (Format Attributes).
With a few exceptions, an FME feature is created for each record of a TIGER/Line data file. Each file, that is, .RT1, .RTA, is translated to an appropriate FME feature type, with attribute names matching those in the TIGER/Line product manual.
The TIGER/Line RT (record type) and VERSION attributes are generally discarded, but the MODULE attribute is added to each feature. The MODULE attribute contains the file base name, for example, TGR26001, of the county from which the feature originated. For some keys, such as LAND, POLYID, and CENID, this MODULE attribute is needed to make the key unique when the Dataset folder consists of more than one logical file, i.e. more than one county of data.
The table below lists feature types and their relationship to the TIGER/Line product.
|
Feature Type |
Relationship to TIGER/Line Product |
|---|---|
|
AltName |
These features are derived from the type 4 record (Index to Alternate Feature Identifiers), and relate a TLID to 1 to 4 alternate feature name numbers (the The standard reader pipeline attaches the names from the FeatureIds feature attributes ALT_FEDIRS, ALT_FEDIRP, ALT_FENAME, and ALT_FETYPE to the CompleteChain features. The ALT_FENAME is a list of feature names associated with the TLID on the AltName feature, with the alternate names separated by commas. Note that 0, 1, or more AltName records may exist for a given TLID and that each AltName record can contain between one and four alternate names. Currently CompleteChains will only be updated with the alternate names from one of the related AltName records, potentially resulting in the loss of some alternate names. Future versions of the TIGER/Line reader will add support for multiple AltName records. These features have no associated geometry. |
|
AreaLandmarks |
These features are derived from type 8 (Polygons Linked to Area Landmarks) records. Each associates a Landmark feature (attribute LAND) with a Polygon feature (attribute POLYID). This feature has a many-to-many relationship with Polygon features. These features have no associated geometry. |
|
CompleteChain |
A CompleteChain is a polyline with an associated TLID (TIGER/Line ID). The CompleteChain features are established from a type 1 record (Complete Chain Basic Data Record) and, if available, its associated type 3 record (Complete Chain Geographic Entity Codes). As well, any type 2 records (Complete Chain Shape Coordinates) available are used to fill in intermediate Shape points on the arc. The TLID is the primary key and is unique within the entire national TIGER/Line coverage. These features always have a line geometry. |
|
EntityNames |
These features are derived from type C (Geographic Entity Names) records and have no associated geometry. |
|
FeatureIds |
These features are derived from type 5 (Complete Chain Feature Identifiers) records. Each feature contains a feature name (FENAME), and its associated feature ID code (FEAT). The FEAT attribute is the primary key and is unique within the county module. FeatureIds have a one-to-many relationship with AltName features, and KeyFeatures features. These features have no associated geometry. |
|
IDHistory |
These features are derived from type H (TIGER/Line ID History) records. They can be used to trace splitting, merging, creating and deleting of CompleteChain features. These features have no associated geometry. |
|
KeyFeatures |
These features are derived from type 9 (Polygon Geographic Entity Codes) records. They may be associated with a FeatureIds feature by way of the FEAT attribute and a Polygon feature by way of the POLYID attribute. These features have no associated geometry. |
|
Landmarks |
These features are derived from type 7 (Landmark Features) records. They relate to point or area landmarks. For area landmarks, there is a one-to-one relationship with an AreaLandmark record. The LAND attribute is the primary key and is unique within the county module. These features may have an associated point geometry. Landmarks associated with polygons do not have the polygon geometry attached. It needs to be collected by way of the AreaLandmark feature from a Polygon feature. |
|
PIP |
These features are derived from type P (Polygon Internal Point) records. They relate to a Polygon feature by way of the POLYID attribute and can be used to establish an internal point for Polygon features. These features have a point geometry. |
|
PolyChainLink |
These features are derived from type I (Link Between Complete Chains and Polygons) records. They are normally all consumed by the standard reader pipeline while attaching CompleteChain geometries to Polygon features to establish their polygon geometries. PolyChainLink features have a many-to-one relationship with Polygon features, and a one-to-one relationship with CompleteChain features. These features have no associated geometry. |
|
Polygon |
These features are derived from type A (Polygon Geographic Entity Codes) records and, if available, the related type S (Polygon Additional Geographic Entity Codes) records. The POLYID attribute is the primary key, uniquely identifying a polygon within a county module. These features have an associated polygon geometry, automatically collected by the standard reader pipeline. It is collected from CompleteChain geometries based on the type I (PolyChainLink) records. |
|
ZipCodes |
These features are derived from type 6 (Additional Address Range and ZIP Code Data) records. These features are intended to augment the ZIP Code information kept directly on CompleteChain features. There is a many-to-one relationship between ZipCodes features and CompleteChain features. These features have no associated geometry. |
|
ZipPlus4 |
These features are derived from type Z (ZIP+4 Codes) records. ZipPlus4 features have a many-to-one relationship with CompleteChain features. These features have no associated geometry. |