U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
Chapter 3 provided a detailed description of the catalogs and datasets that comprise the HPMS data model. This chapter provides in-depth information on the data collection and reporting requirements for the Sections and Sample Panel Identification datasets, which the States are responsible for providing to FHWA. In addition, this chapter contains information on the datasets that are developed and maintained by FHWA, and the datasets that are gathered by FHWA from other sources.
Upon submittal to FHWA, the Sections and Sample Panel Identification datasets will be stored in the Sections Catalog. These datasets will then be linked to the respective State's Linear Referencing System (LRS) network for data management and analysis purposes, as shown in Figure 4.1 below. Furthermore, the data in the Sections catalog will be spatially linked to the Routes dataset (in the Shapes Catalog) via the Route ID field, which serves as the unique identifier that is embedded in each of these datasets (as discussed in Chapter 3).
This chapter also specifies the fields of information that are to be reported for the Sections and Sample Panel Identification datasets. Also included in this chapter are the detailed requirements, as well as any applicable guidance for the various data items that are to be reported in the Sections dataset.
In addition to the data items that the States are responsible for collecting and reporting, there are also data items that FHWA is responsible for coding, as well as data items that are calculated by the HPMS software. Each of these types of data is also described in this chapter.
The data fields listed in Table 4.1 are to be submitted as part of the Sections dataset which will be stored in the Sections Catalog (discussed in Chapter 3) within FHWA's system.
|Field Number||Field Name|
are used to report values and additional
information pertaining to the data item (in Field 6).
The next section describes the detailed specifications for the fields identified in Table 4.1, in terms of their Descriptions, Usage, Data Formats, Coding instructions, and Guidance (where applicable) for each Field.
|Field 1: Year_Record|
|Description:||The calendar year for which the data are being reported.|
|Use:||For identifying the representative year of the data.|
|Coding:||Enter the four digits for the calendar year that the data represents.|
|Guidance:||The value that is coded must reflect the calendar year for which the data is being reported, not the year that the data is being submitted.|
|Field 2: State_Code|
|Description:||The State Federal Information Processing Standard (FIPS) code.|
|Use:||For identifying the State for which the data is being reported.|
|Coding:||Enter up to two digits for the State FIPS code.|
|Guidance:||See Appendix C for a complete list of FIPS codes.|
|Field 3: Route_ID|
|Description:||The unique identifier for a given roadway (i.e., route).|
|Use:||For identifying the specific route for which the data is being reported.|
|Coding:||Enter an alphanumeric sequence consisting of no more than 60 characters.|
|Guidance:||The Route ID is to be developed per the States' preference. However, the ID schema must be consistent with the Route ID schema that is contained in the State's LRS network attribute data.|
|Field 4: Begin_Point|
|Description:||The point of origin for a given section of road|
|Use:||For identifying the beginning point of a section for spatial referencing purposes.|
|Coding:||Enter a decimal value to the nearest thousandth of a mile|
|Field 5: End_Point|
|Description:||The terminus point for a given section of road.|
|Use:||For identifying the ending point of a section for spatial referencing purposes|
|Coding:||Enter a decimal value to the nearest thousandth of a mile.|
|Field 6: Data_Item|
|Description:||The attribute being reported for a given section of road.|
|Use:||For specifying the particular attribute being reported for a given section of road.|
|Coding:||Code the database-specific data item name for each data item listed in Section 4.4 of this chapter.|
|Guidance:||Guidance for each data item is discussed in Section 4.4 of this chapter.|
|CAUTION: The States must use the database-specific data item names that are listed in Table 4.2. Failure to use the database-specific data item names as they are specified will cause the States ' records to fail validation when the records are uploaded for HPMS submittal purposes.|
|Field 7: Section_Length|
|Description:||The true length (i.e., measured length) for a given section of road.|
|Use:||For analysis and comparison of various data items for apportionment, administrative, legislative, analytical, and national highway database purposes.|
|Coding:||Code the length in decimal format to the nearest thousandth of a mile.|
Report either the inventory or LRS-based length for a given section of road, per the States’ preference. This length should be consistent with the length that is reported in the State’s Certified Public Road Mileage. Furthermore, the reported length must be consistent with the difference between Field 5 (End_Point) and Field 4 (Begin_Point). For undivided facilities, the inventoried length should be measured along the centerline in the designated inventory direction (i.e., cardinal direction). For divided highways, the length should be measured in accordance with the designated inventory direction, for both the cardinal and non-cardinal sides of the roadway.
For “one-way pairs” (i.e., divided non-Interstate roadway sections located along a given route (see Fig. 4.4b)), measure and report the length of each roadway section independently; do not average the length of the two roadways.
When measuring the length between at-grade intersections, use the center point of the intersecting roadways as the points of reference (i.e., origin, or terminus) for the section as shown in Figure 4.2.
If the intersection is grade-separated, measure to the theoretical center-most point of the intersecting roadways.
When a route terminates at an interchange, such as a "T" interchange (as shown in Figure 4.3A), measure the length as the average of the directional connecting roadway segment's lengths to the first point of intersection with the perpendicular mainline route.
For ramps, the length should be measured either from gore to gore, or from taper to taper, and should be noted as such in the metadata for ramp reporting. Figures 4.3B, 4.3C, and 4.3D provide examples of begin and end taper points for grade-separated interchanges.
Source: Google Maps.
Figure 4.3C: Begin Taper Point
Source: Google Maps.
Figure 4.3D: End Taper Point
Source: Google Maps.
The begin taper point (Figure 4.3C) is the point at which the exit (deceleration) lane separates from the outermost lane of the mainline roadway, becoming a separate lane.
The end taper point (Figure 4.3D) is the point at which the entrance (acceleration) lane joins the outermost lane of the mainline roadway to become one lane.
Metadata: See Chapter 3 for a description of the metadata reporting requirements for ramps.
|Field 8: Value_Numeric|
|Description:||The numeric value that is associated with a particular data item.|
|Use:||For identifying the corresponding numeric value for a particular data item, for a given section of road.|
|Coding:||Must be coded in accordance with the individual data item descriptions discussed in Section 4.4 of this chapter.|
|Field 9: Value_Text|
|Description:||The text value that is associated with a particular data item.|
|Use:||For identifying the corresponding text value for a particular data item, for a given section of road.|
|Coding:||Must be coded in accordance with the individual data item descriptions discussed in Section 4.4 of this chapter. This field is available for State use where text data is not required for a particular data item. This field is limited to 50 characters.|
|Field 10: Value_Date|
|Description:||The date value that is associated with a particular data item.|
|Use:||For identifying the corresponding date value for a particular data item, for a given section of road.|
|Coding:||Must be coded in accordance with the individual data item descriptions discussed in Section 4.4 of this chapter. This field is available for State use where date data is not required for a particular data item.|
|Field 11: Comments (Optional)|
|Description:||Additional information for State use (formerly referred to as the "State Control Field").|
|Use:||For storing supplemental information provided by the States which is used to manage their various databases.|
|Coding:||This item can be coded as variable text up to 100 characters, in accordance with the State's needs|
|Guidance:||The information provided in this field is not required by FHWA.|
Example records: The following example shows a potential arrangement of records for various data items (e.g., AADT, IRI, Through Lanes, etc.) for the State of Oregon, based on the file structure described in Table 4.1. This file is to be developed by the States and submitted to FHWA in a Character Separated Value (CSV) file format as shown below. This file should not contain any records that have either a zero (0) or null value for the fields that require an entry, for any given Data Item. The Value Text and Value Date fields can be used by the States to enter additional information, when data for these fields are not required for a particular data item (e.g., AADT). Furthermore, the Comment field is not required for FHWA purposes, but is available as an optional field for State-use. The States can either submit one aggregate CSV file containing all records for all of the required data items, or submit a series of individual CSV files. Upon submittal, this data will be stored in the Sections Catalog within FHWA's system.
NOTE: This file should not contain any records that have either a zero (0) or null value for the fields that require an entry (Value_Numeric, Value_Text, Value_Date), as specified in Section 4.4.