U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
202-366-4000
The Highway Performance Network is a newly created geospatial network based on FHWA’s 2016 HPMS network and the 2017 NPMRDS network. Through spatial integration, all TMC data contained in the NPMRDS data are transferred to the 2016 HPMS network. The goal and objective of this effort is to enable more in-depth analysis of travel time data along with highway capacity data and other public defined data items such as the federally defined highway functional classification system. State highway agencies and other users can take advantage of what have been accomplished here for the integration of NPMRDS data to the native HPMS system through a relatively simple geospatial tagging process.
Data definitions are based on HPMS Field Manual and various FHWA guidance and documents on NPMRDS at: http://www.ops.fhwa.dot.gov/freight/freight_analysis/perform_meas/vpds/npmrdsfaqs.htm
FHWA Performance Network Geodatabase Data Files - User Guide (PDF 553 kb)
Attribute Field | Attribute Name | Attribute Description |
---|---|---|
YEAR_RECORD_HPMS | Representative Year of Data (HPMS Sample Panel Section Field #1) |
The calendar year for which the data is applicable according to source data. |
STATE_CODE | State FIPS Code (HPMS Sample Panel Section Field #2) |
The State Federal Information Processing Standard (FIPS) code of the state to which the TMC segment is assigned. |
ROUTE_ID | Location Reference ID (HPMS Sample Panel Section Field #3) |
Location Reference ID for the linear feature matched with the TMC Segment. If multiple HPMS linear features with different IDs are matched with a single TMC path, the predominant ID by length is assigned. |
ROUTE_NUMBER | Route Number (HPMS Data Item #17) |
The signed route number. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
ROUTE_NAME | Alternative Route Name (HPMS Data Item #20) |
A familiar, non-numeric designation for a route. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
ROUTE_QUALIFIER | Route Qualifier (HPMS Data Item #19) |
Code for the route signing descriptive qualifier. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1: No qualifier or Not Signed 2: Alternate 3: Business Route 4: Bypass Business 5: Spur 6: Loop 7: Proposed 8: Temporary 9: Truck Route 10: None of the Above |
ROUTE_SIGNING | Route Signing (HPMS Data Item #18) |
Code for the type of route signing. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1: Not Signed 2: Interstate 3: U.S. 4: State 5: Off-Interstate Business Marker 6: County 7: Township 8: Municipal 9: Parkway Marker or Forest Route Marker 10: None of the Above |
F_SYSTEM | Functional System (HPMS Data Item #1) |
The FHWA approved Functional Classification System code. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the value for the highest functional class (minimum code value) is assigned. Attribute Value: Description 1: Interstate 2: Principal Arterial – Other Freeways and Expressways 3: Principal Arterial – Other 4: Minor Arterial 5: Major Collector 6: Minor Collector 7: Local |
FACILITY_TYPE | Facility Type (HPMS Data Item #3) |
The operational characteristic of the roadway. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1: One-Way Roadway 2: Two-Way Roadway 4: Ramp 5: Non Mainlane 6: Non Inventory Direction 7: Planned/Unbuilt |
URBAN_CODE | Urban Code (HPMS Data Item #2) |
The U.S. Census Urban Area Code. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description <99998: Refer to U.S. Census Urban Area Code 99998: Small Urban Sections 99999: Rural Area Sections |
NHS | National Highway System (HPMS Data Item #64) |
Code for a roadway that is a component of the National Highway System (NHS). If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value length is assigned. Attribute Value: Description 1: Non Connector NHS 2: Major Airport 3: Major Port Facility 4: Major Amtrak Station 5: Major Rail/Truck Terminal 6: Major Inter City Bus Terminal 7: Major Public Transportation or Multi-Modal Passenger Terminal 8: Major Pipeline Terminal 9: Major Ferry Terminal |
STRAHNET | Strategic Highway Network (HPMS Data Item #65) |
Code for a roadway section that is a component of the Strategic Highway Network (STRAHNET). If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1: Regular STRAHNET 2: Connector |
OWNERSHIP | Ownership (HPMS Data Item #6) |
The entity that has legal ownership of a roadway. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1=State Hwy Agency. 2=County Hwy Agency. 3=Town or Township Hwy Agency. 4=City or Municipal Hwy Agency. 11=State Park, Forest, or Reservation Agency. 12=Local Park, Forest, or Reservation Agency. 21=Other State Agency. 25=Other Local Agency. 26=Private (other than Railroad). 27=Railroad. 31=State Toll Authority. 32=Local Toll Authority. 40=Other Public Instrumentality (e.g., Airport, School, University). 50=Indian Tribe Nation. 60=Other Federal Agency. 62=Bureau of Indian Affairs. |
TRUCK | National Truck Network (HPMS Data Item #66) |
Code for a roadway section that is a component of the National Truck Network (NTN) as defined by 23 CFR 658. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1: Section is on the National Network (NN) 2: Other State-designated truck route (optional) |
THROUGH_LANES | Through Lanes (HPMS Data Item #7) |
The number of lanes designated for through-traffic. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
PEAK_LANES | Peak Lanes (HPMS Data Item #10) |
The number of lanes in the peak direction of flow during the peak period. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
COUNTER_PEAK_LANES | Counter-Peak Lanes (HPMS Data Item #11) |
The number of lanes in the counter-peak direction of flow during the peak period. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
SHOULDER_TYPE | Shoulder Type (HPMS Data Item #37) |
The type of shoulder. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1=None. 2=Surfaced shoulder exists – bituminous concrete (AC). 3=Surfaced shoulder exists – Portland Cement Concrete surface (PCC). 4=Stabilized shoulder exists – (stabilized gravel or other granular material with or without admixture) 5=Combination shoulder exists (shoulder width has two or more surface types; e.g., part of the shoulder width is surfaced and a part of the width is earth). 6=Earth shoulder exists. 7=Barrier curb exists; no shoulder in front of curb. |
SHOULDER_WIDTH_L | Left Shoulder Width (HPMS Data Item #39) |
The existing left shoulder width. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
SHOULDER_WIDTH_R | Right Shoulder Width (HPMS Data Item #38) |
The existing right shoulder width. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
LANE_WIDTH | Lane Width (HPMS Data Item #34) |
The measure of existing lane width. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
MEDIAN_TYPE | Median Type (HPMS Data Item #35) |
The type of median. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1=None. 2=Unprotected. 3=Curbed. 4=Positive barrier-unspecified. *5=Positive barrier-flexible. *6=Positive barrier-semi-rigid. *7=Positive barrier – rigid. *Codes 5, 6, and 7 are optional. |
MEDIAN_WIDTH | Median Width (HPMS Data Item #36) |
The existing median width. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
ACCESS_CONTROL | Access Control (HPMS Data Item #5) |
The degree of access control for a given section of road. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1=Full Access Control. 2=Partial Access Control. 3=No Access Control. |
WIDENING_OBSTACLE | Widening Obstacle (HPMS Data Item #41) |
Obstacles that prevent widening of the existing roadway for additional through lanes. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description X=No obstacles. A=Dense development. B=Major transportation facilities. C=Other public facilities D=Terrain restrictions. E=Historic and archeological sites. F=Environmentally sensitive areas. G=Parkland. |
WIDENING_POTENTIAL | Widening Potential (HPMS Data Item #42) |
The number of through lanes that could be potentially added. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
HOV_LANES | Managed Lanes (HPMS Data Item #9) |
Maximum number of lanes in both directions designated for managed lane operations. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
HOV_TYPE | Managed Lane Operations Type (HPMS Data Item #8) |
The type of managed lane operations (e.g., HOV, HOT, ETL, etc.). If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1=Full-time: Section has 24-hr. exclusive HOV lanes (HOV use only; no other use permitted). 2=Part-time: Normal through lanes used for exclusive HOV during specified time periods. 3=Part-time: Shoulder/Parking lanes used for exclusive HOV during specified time periods. |
SPEED_LIMIT | Speed Limit (HPMS Data Item #14) |
The posted speed limit. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
TOLL_CHARGED | Toll Charged (HPMS Data Item #15) |
Identifies sections that are toll facilities regardless of whether or not a toll is charged. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1=Toll charged in one direction only. 2=Toll charged in both directions. 3=No toll charged |
TOLL_ID | Toll ID (Appendix D. Toll-ID Table) |
If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
TOLL_TYPE | Toll Type (HPMS Data Item #16) |
Indicates the presence of special tolls (i.e., High Occupancy Toll (HOT) lane(s) or other managed lanes). If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1=This section has toll lanes but no HOT lanes. 2=This section has HOT lanes. |
AADT | Annual Average Daily Traffic (HPMS Data Item #21) |
Annual Average Daily Traffic. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
AADT_COMBINATION | Combination Truck AADT (HPMS Data Item #24) |
Annual Average Daily Traffic for Combination Trucks. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
AADT_SINGLE_UNIT | Single-Unit Truck & Bus AADT (HPMS Data Item #22) |
Annual Average Daily Traffic for single-unit trucks and buses. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
PCT_PEAK_COMBINATION | Percent Peak Combination Trucks (HPMS Data Item #25) |
Peak hour combination truck volume as a percentage of total AADT. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
PCT_PEAK_SINGLE | Percent Peak Single-Unit Trucks and Buses (HPMS Data Item #23) |
Peak hour single-unit truck and bus volume as a percentage of total AADT. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
K_FACTOR | K-factor (HPMS Data Item #26) |
The design hour volume (30th largest hourly volume for a given calendar year) as a percentage of AADT. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
DIR_FACTOR | Directional Factor (HPMS Data Item #27) |
The percent of design hour volume (30th largest hourly volume for a given calendar year) flowing in the higher volume direction. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
IRI | International Roughness Index (HPMS Data Item #47) |
IRI is the road roughness index most commonly used worldwide for evaluating and managing road systems. Road roughness is the primary indicator of the utility of a highway network to road users. IRI is defined as a statistic used to estimate the amount of roughness in a measured longitudinal profile. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
PSR | Present Serviceability Rating (HPMS Data Item #48) |
Present Serviceability Rating (PSR) for pavement condition. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
SURFACE_TYPE | Surface Type (HPMS Data Item #49) |
Surface type on a given section. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1=Unpaved. 2=Bituminous. 3=JPCP-Jointed Plain Concrete Pavement. 4=JRCP-Jointed Reinforced Concrete Pavement. 5=CRCP-Continuously Reinforced Concrete Pavement. 6=Asphalt-Concrete (AC) Overlay over Existing AC Pavement. 7=AC Overlay over Existing Jointed Concrete Pavement. 8=AC (Bitum. Overlay over Existing CRCP). 9=Unbonded Jointed Concrete Overlay on PCC Pavements. 10=Bonded PCC Overlays on PCC Pavements. 11=Other. |
CRACKING_PERCENT | Cracking Percent (HPMS Data Item #52) |
Cracking is defined as a fissure or discontinuity of the pavement surface not necessarily extending through the entire thickness of the pavement. Cracking Percent is defined as the percentage of pavement surface exhibiting cracking as follows:
|
FAULTING | Faulting (HPMS Data Item #51) |
Faulting is defined as a vertical misalignment of pavement joints in Portland Cement Concrete Pavements (Jointed Concrete Pavement). Jointed Concrete Pavements is defined as pavements where the top-most surface is constructed of Portland cement concrete with joints (Item 49 codes ‘3’, ‘4’, ‘9’, ‘10’, and ‘11’). It may be constructed of either reinforced or unreinforced (plain) concrete.If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
RUTTING | Rutting (HPMS Data Item #50) |
Average depth of rutting. A rut is defined as longitudinal surface depressions in the asphalt pavement derived from measurements of a profile transverse to the path of travel on a highway lane. It may have associated transverse displacement. Asphalt pavement (Item 49 codes ‘2’, ‘6’, ‘7’, and ‘8’) is defined as pavements where the top-most surface is constructed with asphalt materials.If multiple HPMS segments with different attribute values are assigned to a single TMC path, the length-weighted average is assigned. |
STRUCTURE_TYPE | Structure Type (HPMS Data Item #4) |
Code for roadway section that is a bridge, tunnel or causeway. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 1: Bridge 2: Tunnel 3: Causeway |
YEAR_LAST_IMPROV_VD | Year of Last Improvement (HPMS Data Item #54) |
The year in which the roadway surface was last improved. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
YEAR_LAST_CONSTRUCTION_VD | Year of Last Construction (HPMS Data Item #55) |
The year in which the roadway was constructed or reconstructed. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
IS_SAMPLE | Is Sample | Code to indicate whether the TMC Segment is a Sample Panel section. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. Attribute Value: Description 0: Is not a sample panel section 1: Is a sample panel section |
SAMPLE_ID | Sample ID (HPMS Sample Panel Sections Field #7) |
A unique identifier for the section. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
EXPANSION_FACTOR | Expansion Factor (HPMS Software-Calculated Items) |
The ratio of the total length in a volume group to the total sampled volume group length. If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
National_Route_ID | National Route ID | The unique identifier, combining FIPS code with the Route ID, for a given roadway (i.e., route). If multiple HPMS segments with different attribute values are assigned to a single TMC path, the predominant value by length is assigned. |
TMC | TMC Path Identifier (NPMRDS Attribute #1) |
The unique 9-digit value identifying the TMC Segment. |
TMC_Type | Type of TMC Code (NPMRDS Attribute #2) |
“P1” is the typical TMC Code. “P3” indicates national, state, and county boundaries, rest areas, toll plazas, major bridges, etc. “P4” is for ramps. |
TMC_RoadNumber | Common name or route number (NPMRDS Attribute #3) |
The roadway number, for TMC Segments on numbered roadways. |
TMC_RoadName | Associated Road Name (NPMRDS Attribute #4) |
Name of Roadway according to source data. |
TMC_FirstName | Associated Street (NPMRDS Attribute #5) |
The cross street and/or interchange associated with the internal segment of 5-digit Location ID. |
TMC_Country | Country (NPMRDS Attribute #7) |
The country in which the TMC Segment is located. |
TMC_State | State (NPMRDS Attribute #8) |
The postal abbreviation of the state to which the TMC Segment is assigned. |
TMC_County | County (NPMRDS Attribute #9) |
The county to which the TMC Segment is assigned. |
TMC_Zip | Postal Code (NPMRDS Attribute #10) |
The 5-digit zip code to which the TMC Segment is assigned. |
TMC_Direction | Direction (NPMRDS Attribute #11) |
The overall direction of the roadway. |
TMC_StartLat | Beginning Latitude (NPMRDS Attribute #12) |
The latitude of the beginning of the TMC Segment. |
TMC_StartLong | Beginning Longitude (NPMRDS Attribute #13) |
The longitude of the beginning of the TMC Segment. |
TMC_EndLat | Ending Latitude (NPMRDS Attribute #14) |
The latitude of the end of the TMC Segment. |
TMC_EndLong | Ending Longitude (NPMRDS Attribute #15) |
The longitude of the end of the TMC Segment. |
TMC_Miles | Length of Segment (NPMRDS Attribute #16) |
The length of the TMC Segment along the road in miles. |
Attribute Field | Attribute Name | Attribute Description |
---|---|---|
year_record | Representative Year of Data | The calendar year for which the data is applicable according to source data which is NHPMS 2017 dataset. |
state_code | State FIPS Code | Up to two digits for the FIPS code. |
route_id | Location Reference ID | Location Reference ID for the linear feature matched with the TMC Segment. |
begin_point | Beginning Milepost | The beginning milepost of a route section. |
end_point | Ending Milepost | The ending milepost of a route section. |
data_item | The calendar year for which the data is applicable according to source data. | |
section_length | Length of Route Section | The length of a route section, calculated by subtracting beginning milepost from ending milepost. |
value_numeric | Numeric Value | Numeric value for data item. |
value_text | Text Value | Text value for data item and here it is referred to the TMC path identifier |
value_date | Date Value | Date value for data item. |
comments | Comment for State use | Comment for State use. |