Proximity Home Page




TIGER/Line Main

DMD Main

  DMD Sections
    Edges/Roads (this page)
    Faces
    Feature Names

    Points/Locations

    Feature Class Codes

    Scope of Files

    Applications
 
Decision-Making Information
  ProximityOne
  information resources & solutions
  (888) DMI-SOLN
  (888) 364-7656


Accessing & Using TIGER/DMD Files
  -- Edges/Roads Shapefile Attributes

The Edges, or all lines, shapefile (edges.dbf) contains basic attributes of all roads and related lines (e.g., railroads). See Edges table/record layout below. Each edge has a unique TLID (TIGER/Line Identifier) value. The left and right faces for an edge can be determined by linking on the TFIDL (left) or TFIDR (right) attribute to the TFID attribute in the Topological Faces relationship table (faces.dbf).

The Address Ranges relationship table (addr.dbf) contains the attributes of each address range. Each address range has a unique ARID value. The edge to which an address range applies can be determined by linking to the edges shapefile on the TLID attribute. Multiple address ranges can apply to the same edge (an edge can have multiple address ranges).

The Address Range-Feature Name relationship table (addrfn.dbf) contains a record for each address range-linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can have multiple feature names). The address range is identified by the ARID attribute, which can be used to link to the Address Ranges relationship table. The linear feature name is identified by the LINEARID attribute that relates the address range back to the featnames.dbf table.

The Feature Names relationship table (featnames.dbf) contains a record for each feature name-edge combination, and includes the feature name attributes. The edge to which a Feature Names relationship table record applies can be determined by linking to the All Lines shapefile on the TLID attribute. Multiple Feature Names relationship table records can link to the same edge, for example, a road edge could link to US Hwy 22 and Rathburn Road. The linear feature to which the feature name applies is identified by the LINEARID attribute. Multiple feature names may exist for the same edge (linear features are not included in the data set, but could be constructed using the All Lines shapefile and the relationship tables).

The Faces table (faces.dbf) contains the attributes of each face (side of edge). Each face has a unique TFID value. The face geometries can be built from the All Lines/Edges shapefile using the edge left and right face relationships. Each edge contains a TFIDL (left-side) and TFIDR (right-side) that can be used to link to the Faces TFID value.

The Area Landmark shapefile (arealm.shp) contains the geometry and attributes of each area landmark. Each area landmark has a unique AREAID value.

The Topological Faces-Area Landmark relationship table (facesal.dbf) contains a record for each face-area landmark relationship. The face to which a Topological Faces-Area Landmark relationship table record applies can be determined by linking to the Topological Faces relationship table on the TFID attribute. The area landmark to which a Topological Faces-Area Landmark relationship table record applies can de determined by linking to the Area Landmark shapefile on the AREAID attribute. A face may be part of multiple area landmarks. An area landmark may consist of multiple faces.

The Area Hydrography shapefile contains the geometry and attributes of each area hydrography feature. Each area hydrography feature has a unique HYDROID value.

The Topological Faces-Area Hydrography relationship table contains a record for each face-area hydrography feature relationship. The face to which a Topological Faces-Area Hydrography relationship table record applies can be determined by linking to the Topological Faces table on the TFID attribute. The area hydrography feature to which a Topological Faces-Area Hydrography relationship table record applies can be determined by linking to the Area Hydrography shapefile on the HYDROID attribute. A face may be part of multiple area water features. An area water feature may consist of multiple faces.

Edges Table Structure
The Edges table structure presented below. Fields with ** are not part of the TIGER structure and are unique to the DMD structure. The TIGER Editor can be used to derive the original TIGER data/records from this DMD version.
FieldNameWidthTypeDescription
STATEFP2StringState FIPS code
COUNTYFP3StringCounty FIPS code
DLID ** 10IntegerDMD permanent edge ID
DFIDL **10IntegerDMD permanent face ID on the left of the edge
DFIDR **10IntegerDMD permanent face ID on the right of the edge
STATUS ** 1StringDMD review status
TLID10IntegerTIGER permanent edge ID
TFIDL10IntegerTIGER permanent face ID on the left of the edge
TFIDR10IntegerTIGER permanent face ID on the right of the edge
MTFCC5StringMAF/TIGER feature class code of the primary feature for the edge
FULLNAME100StringConcatenation of expanded text for prefix qualifier, prefix direction, prefix type, base name, suffix type, suffix direction, and suffix qualifier with a space between each expanded text field (as available)
SMID22StringSpatial metadata identifier
LFROMADD12StringFrom house number associated with the most inclusive address range on the left side of the edge
LTOADD12StringTo house number associated with the most inclusive address range on the left side of the edge
RFROMADD12StringFrom house number associated with the most inclusive address range on the right side of the edge
RTOADD12StringTo house number associated with the most inclusive address range on the right side of the edge
ZIPL5StringZIP code associated with the most inclusive address range on the left side
ZIPR5StringZIP code associated with the most inclusive address range on the right side
FEATCAT1StringGeneral feature classification category
HYDROFLG1StringHydrography feature indicator
RAILFLG1StringRail feature indicator
ROADFLG1StringRoad feature indicator
OLFFLG1StringOther linear feature indicator
PASSFLG1StringSpecial passage flag
DIVROAD1StringDivided road flag
EXTTYP1StringExtension type
TTYP1StringTrack type
DECKEDROAD1StringDecked road indicator
ARTPATH1StringArtificial path indicator
PERSIST1StringHydrographic persistence flag
GCSEFLG1StringShort lines flag for geographic corridors
OFFSETL1StringLeft offset flag
OFFSETR1StringRight offset flag
TNIDF10IntegerFrom TIGER node identifier
TNIDT10IntegerTo TIGER node identifier
DNIDF **10IntegerFrom DMD node identifier
DNIDT **10IntegerTo DMD node identifier

Additional Information
ProximityOne develops geographic-demographic-economic data and analytical tools and helps organizations knit together and use diverse data in a decision-making and analytical framework. We develop custom demographic/economic estimates and projections, develop geographic and geocoded address files, and assist with impact and geospatial analyses. Wide-ranging organizations use our tools (software, data, methodologies) to analyze their own data integrated with other data. Follow ProximityOne on Twitter at www.twitter.com/proximityone. Contact ProximityOne (888-364-7656) with questions about data covered in this section or to discuss custom estimates, projections or analyses for your areas of interest.


Copyright © . Proximity. All Rights Reserved.
Sitemap | Contact Us | News