Highway Performance Monitoring System Field Manual

Chapter 4 Data Requirements and Specifications

4.1 Overview

This chapter provides in-depth information on the data collection and reporting requirements for the Sections and Sample Panel Identification datasets, which comprise the linear features of HPMS. 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.

The Sections and Sample Panel Identification datasets will be stored in the Sections Catalog. These datasets relate to each other through the states Linear Reference System (LRS) as described in Chapter 3.

This chapter specifies the data items that are to be reported for the Sections and Sample Panel Identification datasets. Included in this chapter are the detailed requirements, along with applicable guidance for the data items that are to be reported in the Sections dataset.

Based on the data reported by the State DOT, FHWA will derive other data items. These derived data is described in this chapter.

4.2 Sections Data Reporting Requirements

Data Fields Required for Section Reporting Purposes

The data fields listed in Table 4.1 are to be reported as part of the Sections dataset which will be stored in the Sections Catalog (discussed in Chapter 3) within FHWA’s system.

• Field Number is the number assigned to each data field for reference purposes.
• Field Name specifies the type of information that shall be reported for each field. The Data Item field (Field No. 6) in Table 4.1 stores the name of the Data Item that is being reported. A complete list of these data items is shown in Table 4.2.

Table 4.1: HPMS Sections File Structure

	Field Number	Field Name
Section	1	Year_Record
	2	State_Code
	3	Route_ID
	4	Begin_Point
	5	End_Point
	6	Data_Item
	7	Section_Length
	8	Value_Numeric
	9	Value_Text
	10	Value_Date
	11	Comments (Optional)

Italicized fields 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.

Data Type: Numeric (Integer)

Coding: Enter the four digits for the calendar year that the data represents.

Guidance: The value that is coded shall 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.

Data Type: Numeric (Integer)

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.

Data Type: Text

Coding: Enter an alphanumeric sequence consisting of no more than 120 characters.

Guidance: The Route ID is to be developed per the States’ preference. However, the ID schema shall 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.

Data Type: Numeric (Decimal (8,3))

Coding: Enter a decimal value to the nearest thousandth of a mile.

Guidance: N/A

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.

Data Type: Numeric (Decimal (8,3))

Coding: Enter a decimal value to the nearest thousandth of a mile.

Guidance: N/A

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.

Data Type: Text

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 shall 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.

Data Type: Numeric (Decimal (8,3))

Coding: Code the length in decimal format to the nearest thousandth of a mile.

Guidance: Report either the inventory or LRS-based length for a given section of road, per the States’ preference. This length shall be consistent with the length that is reported in the State’s Certified Public Road Mileage. Furthermore, the reported length shall be consistent with the difference between Field 5 (End_Point) and Field 4 (Begin_Point). For undivided facilities, the inventoried length shall be measured along the centerline in the designated inventory direction (i.e., cardinal direction). For divided highways, the length shall 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.

For ramps, the length should be measured from taper to taper, and should be noted as such in the metadata for ramp reporting. Figures 4.3A, 4.3B, and 4.3C provide examples of begin and end taper points for grade-separated interchanges.

Source: Google Maps.

Figure 4.3B: Begin Taper Point Source: Google Maps.

Figure 4.3C: End Taper Point Source: Google Maps.

The begin taper point (Figure 4.3B) 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.3C) 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.

Data Type: Numeric (Decimal (8,3))

Coding: Shall be coded in accordance with the individual data item descriptions discussed in Section 4.4 of this chapter.

Guidance: N/A

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.

Data Type: Text

Coding: Shall 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.

Guidance: N/A

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.

Data Type: Date

Coding: Shall 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.

Guidance: N/A

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.

Data Type: Text

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., Annual Average Daily Travel (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. In most cases, the Value Numeric field shall be used to report the primary information for each 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: The Value Numeric field should contain a value of zero (0) only when it is representative of the condition or performance indicator for a given data item (see Section 4.4 for a description of valid values by data item).

Year_Record|State_Code|Route_ID|Begin_Point|End_Point|Data_Item|Section_Length|Value_Numeric|
Value_Text|Value_Date|Comments

2009|41|000100200S00|0|0.75|AADT|0.75|14800|Factored ‘06 AADT||

2009|41|000100200S00|0.75|5.32|AADT|4.57|14700||4/21/2009|

2009|41|000100200S00|0|0.75|IRI|0.75|118||3/2009|

2009|41|000100200S00|0.75|5.32|IRI|4.57|94|||

2009|41|000100200S00|5.32|5.69|IRI|0.37|66||4/2008|

2009|41|000100200S00|0|0.75|Through_Lanes|0.75|4|||

2009|41|000100200S00|0.75|5.32|Through_Lanes|4.57|4|||Widened in ‘08

4.3 Data Items to be Reported

The States shall report the data items as listed in Table 4.2. Five types of data items that are to be reported are as follows: Inventory, Route, Traffic, Geometric, and Pavement data. Table 4.2 also lists the Item Numbers for each Data Item, the specific name for each Data Item, and the Extent for which the Data Item is to be reported. Detailed information on coding instructions, extent requirements, and additional guidance for each Data Item is contained in Section 4.4.

The Table of Potential Samples (TOPS) (discussed in Section 6.2) is developed based on the spatial intersection of the following five data items: Functional System, Urban Code, Facility Type, Through Lanes, and AADT. Accordingly, the length of these data items are used as control totals for system extent. Each of these data items shall be reported for the entire extent of all Federal-aid highways for a given State.

The HPMS is an inventory system that requires reported data to represent the condition and operation for all public roadways. As a result, directional conflicts in coding may arise for specific data items under certain reporting conditions. The following provides some guidance on how these conflicts can be addressed.

Data items may differ in shape or dimension on either side of a roadway. For reporting purposes, one side of the facility shall be designated for inventory purposes, and the applicable data items shall be coded for the designated side of the roadway. The “inventory direction” should be applied on a statewide basis (i.e., always South to North, East to West, or vice versa) and should never change once it has been designated.

Information reported for certain data items (e.g., AADT and Through Lanes) must reflect attributes associated with both directions of travel (i.e., inventory and non-inventory direction) on two-way roadways, regardless of whether or not these roadways are divided facilities. Caution should be exercised when reporting this information, as these data are used for Federal-aid apportionment purposes.

For pavement performance analysis purposes, a State can opt to report specified pavement data items for its divided Interstate roadway sections either solely for the inventory direction, or for both directions of travel (i.e., inventory and non-inventory directions). The selected reporting method shall be specified in the Metadata accordingly (see Chapter 3, Sec. 3.3, Tables 3.18 and 3.19 for specifications). NOTE: If this data is reported for both directions of travel, then FHWA will use this information to compute metrics (for all divided Interstate roadways sections) that will ultimately be used for assessing pavement performance. Please see Table 4.2 for the full list of items that can be reported for both directions of travel associated with divided Interstate roadway sections. Additionally, please see the data item descriptions in this chapter for detailed coding guidance.

Table 4.2: Data Items, Related Submission Deadlines and Required Reporting Formats

Data Item Type	Data Item No.	Database-Specific Data Item Name	Data Item Name	Extent		Due Date	LRS Reporting Req. for Divided Highways
Inventory	1	F_System	Functional System	FE + R		April 15#	I&NI
	2	Urban_Code	Urban Code	FE + R		April 15#	I or I&NI*
	3	Facility_Type	Facility Type	FE + R		April 15#	I&NI
	4	Structure_Type	Structure Type	FE**		April 15#	I or I&NI*
	5	Access_Control	Access Control	FE*	SP*	June 15	I
	6	Ownership	Ownership	FE		June 15	I&NI
	7	Through_Lanes	Through Lanes	FE + R		April 15#	I or I&NI*
	8	HOV_Type	Managed Lane Operations Type	FE**		June 15	I
	9	HOV_Lanes	Managed Lanes	FE**		June 15	I
	10	Peak_Lanes	Peak Lanes		SP	June 15	I
	11	Counter_Peak_ Lanes	Counter Peak Lanes		SP	June 15	I
	12	Turn_Lanes_R	Right Turn Lanes		SP	June 15	I
	13	Turn_Lanes_L	Left Turn Lanes		SP	June 15	I
	14	Speed_Limit	Speed Limit	FE*	SP	June 15	I
	15	Toll_Charged	Toll Charged	FE**		June 15	I
	16	Toll_Type	Toll Type	FE**		June 15	I
Route	17	Route_Number	Route Number	FE*		June 15	I or I&NI*
	18	Route_Signing	Route Signing	FE*		June 15	I
	19	Route_Qualifier	Route Qualifier	FE*		June 15	I
	20	Alternative_Route_Name	Alternative Route Name	FE		June 15	I
Traffic	21	AADT	Annual Average Daily Traffic	FE + R		June 15	I
	22	AADT_Single_Unit	Single Unit Truck and Bus AADT	FE*	SP*	June 15	I
	23	Pct_Peak_Single	Percent Peak Single-Unit Trucks and Buses		SP	June 15	I
	24	AADT_Combination	Combination Truck AADT	FE*	SP*	June 15	I
	25	Pct_Peak_Combination	Percent Peak Combination Trucks		SP	June 15	I
	26	K_Factor	K-factor		SP	June 15	I
	27	Dir_Factor	Directional Factor		SP	June 15	I
	28	Future_AADT	Future AADT		SP	June 15	I
	29	Signal_Type	Signal Type		SP	June 15	I
	30	Pct_Green_Time	Percent Green Time		SP	June 15	I
	31	Number_Signals	Number of Signalized Intersections		SP	June 15	I
	32	Stop_Signs	Number of Stop Sign-Controlled Intersections		SP	June 15	I
	33	At_Grade_Other	Number of Intersections, Type - Other		SP	June 15	I
Geometric	34	Lane_Width	Lane Width		SP	June 15	I
	35	Median_Type	Median Type		SP	June 15	I
	36	Median_Width	Median Width		SP	June 15	I
	37	Shoulder_Type	Shoulder Type		SP	June 15	I
	38	Shoulder_Width_R	Right Shoulder Width		SP	June 15	I
	39	Shoulder_Width_L	Left Shoulder Width		SP	June 15	I
	40	Peak_Parking	Peak Parking		SP	June 15	I
	41	Widening_Obstacle	Widening Obstacle		SP	June 15	I
	42	Widening_Potential	Widening Potential		SP	June 15	I
	43	Curves_A through Curves_F	Curve Classification		SP*	June 15	I
	44	Terrain_Type	Terrain Type		SP	June 15	I
	45	Grades_A through Grades_F	Grade Classification		SP*	June 15	I
	46	Pct_Pass_Sight	Percent Passing Sight Distance		SP	June 15	I
Pavement	47	IRI	International Roughness Index	FE***	SP*	April 15#	I or I&NI*
	48	PSR	Present Serviceability Rating	FE***#	SP*	April 15#	I or I&NI*
	49	Surface_Type	Surface Type	FE***	SP*	April 15#	I or I&NI*
	50	Rutting	Rutting	FE***	SP*	April 15#	I or I&NI*
	51	Faulting	Faulting	FE***	SP*	April 15#	I or I&NI*
	52	Cracking_Percent	Cracking Percent	FE***	SP*	April 15#	I or I&NI*
	54	Year_Last_Improv	Year of Last Improvement		SP	June 15	I
	55	Year_Last_Construction	Year of Last Construction		SP	June 15	I
	56	Last_Overlay_Thickness	Last Overlay Thickness		SP	June 15	I
	57	Thickness_Rigid	Thickness Rigid		SP	June 15	I
	58	Thickness_Flexible	Thickness Flexible		SP	June 15	I
	59	Base_Type	Base Type		SP	June 15	I
	60	Base_Thickness	Base Thickness		SP	June 15	I
	61	Climate_Zone**	Climate Zone**		SP	June 15	I
	62	Soil_Type**	Soil Type**		SP	June 15	I
Inventory	63	County_Code	County Code	FE		June 15	I
Special Networks	64	NHS	National Highway System	FE**		April 15#	I&NI
	65	STRAHNET_Type	Strategic Highway Network	FE**		June 15	I
	66	Truck	National Truck Network	FE**		June 15	I
	67	Future_Facility	Future National Highway System	FE**		June 15	I
Inventory	68	Maintenance_Operations	Maintenance & Operations	FE		June 15	I
Traffic	69	Capacity	Capacity		SP	June 15	I
Inventory	70	Dir_Through_Lanes	Directional Through Lanes	FE****#		April 15	I or I&NI*

FE = Full Extent for all functional systems (including State and non-State roadways)

FE* = Full Extent for some functional systems, see Sec. 4.4 for more details

FE** = Full Extent wherever data item is applicable, see Sec. 4.4 for more details

FE*** = Full Extent for all NHS roadways (including State and non-State roadways)

FE***# = (Optional) Full Extent for NHS roadways (including State and non-State roadways)

FE****# = (Optional) Full Extent for Interstate roadways (including State and non-State roadways)

FE + R = Full Extent including ramps located within grade-separated interchanges

SP = All Sample Panel Sections (as defined by HPMS)

SP* = Some Sample Panel Sections, see Sec. 4.4 for more details

** = States have the option to override initial codes assigned by FHWA

# = This data item is required to be submitted for Interstate roadways by April 15^th; conversely, this data item is required to be submitted for all non-Interstate roadways by June 15^th.

I = Inventory direction reporting required (i.e., one directional approach associated with both undivided facilities and divided facilities (dual carriageways), see Sec. 4.4 for more details)

I&NI = Inventory and Non-inventory direction reporting required (i.e., both directional approaches associated with divided facilities (i.e., dual carriageways), see Sec. 4.4 for more details)

I&NI* = Inventory and Non-inventory direction reporting optional. For example, International Roughness Index (IRI) data can be reported independently for both the inventory and non-inventory directional approaches associated with all divided Interstate roadway sections, per the States’ discretion.

NOTE: For pavement performance analysis purposes, if a State opts to report pavement distress items (i.e., IRI, PSR, Surface Type, Rutting, Faulting, and Cracking Percent) for both directions of travel associated with its divided Interstate roadway sections, then the following data items shall also be reported for both the inventory and non-inventory directions associated with these roadway sections:

• Urban Code (Data Item 2)
• Structure Type (Data Item 4)
• Route Number (Data Item 17)
• Directional Through Lanes (Data Item 70)

The States shall submit their section-level data for certain data items (Data Items 1-3, 7, and 21) as homogenous sections. For most other data items, this submittal format is optional. By definition, a homogenous section is a section that has the same value for a given data item over its entire extent. A homogenous section has a natural beginning and ending point where the value for a given data item changes beyond the limits of that section.

If preferred, the States may structure and submit their non-homogenous section-level data in accordance with the limits of the TOPS sections (i.e. section limits shall be equivalent to TOPS section limits). However, the States shall submit their section-level data for Data Items 31-33, 43, and 45 in accordance with the limits of TOPS sections. If a State submits section-level data that matches the limits of the TOPS sections, then, they shall apply one of the following calculation methods (per the data item specifications listed in Table 4.3) to ensure that the values reported provide the required representation of those sections:

1. No Calculation Required – Reported value shall be consistent within the limits of the section.
2. Combination – Reported value shall consist of a concatenation of multiple (text) values within the limits of the section.
3. Minimum Value – Reported value shall be the lowest value in a range of values within the limits of the section.
4. Predominance – Reported value shall be based on the most prevalent value within the limits of the section.
5. Weighted Averaging – Reported value shall be based on an averaging of values within the limits of the section, weighted by the length of the sub-section for each value.

The calculation method to be applied depends on the particular data item being reported. Table 4.3 provides a summary of the data items and their applicable calculation method:

Table 4.3: Calculation Method by Data Item

Item Number	Data Item Name	Method
1	Functional System *	No Calculation Required
2	Urban Code *	No Calculation Required
3	Facility Type *	No Calculation Required
4	Structure Type	No Calculation Required
5	Access Control	Predominance
6	Ownership	Predominance
7	Through Lanes *	No Calculation Required
8	Managed Lane Operations Type	Predominance
9	Managed Lanes ***	Predominance
10	Peak Lanes	Predominance
11	Counter-Peak Lanes	Predominance
12	Right Turn Lanes	Predominance
13	Left Turn Lanes	Predominance
14	Speed Limit	Predominance
15	Toll Charged	Predominance
16	Toll Type	Predominance
17	Route Number	Predominance
18	Route Signing	Predominance
19	Route Qualifier	Predominance
20	Alternative Route Name	Predominance
21	AADT *	No Calculation Required#
22	Single-Unit Truck and Bus AADT	Weighted Averaging
23	Percent Peak Single-Unit Trucks and Buses	Weighted Averaging
24	Combination Truck AADT	Weighted Averaging
25	Percent Peak Combination Trucks	Weighted Averaging
26	K-factor	Weighted Averaging
27	Directional Factor	Weighted Averaging
28	Future AADT	Weighted Averaging
29	Signal Type	Predominance
30	Percent Green Time	Weighted Averaging
31	Number of Signalized Intersections **	No Calculation Required
32	Number of Stop Sign-Controlled Intersections **	No Calculation Required
33	Number of Intersections, Type – Other **	No Calculation Required
34	Lane Width	Predominance
35	Median Type	Predominance
36	Median Width	Predominance
37	Shoulder Type	Predominance
38	Right Shoulder Width	Predominance
39	Left Shoulder Width	Predominance
40	Peak Parking	Predominance
41	Widening Obstacle	Combination
42	Widening Potential	Minimum Value
43	Curve Classification **	No Calculation Required
44	Terrain Type	Predominance
45	Grade Classification **	No Calculation Required
46	Percent Passing Sight Distance	Minimum Value
47	International Roughness Index	Weighted Averaging
48	Present Serviceability Rating	Weighted Averaging
49	Surface Type	Predominance
50	Rutting	Weighted Averaging
51	Faulting	Weighted Averaging
52	Cracking Percent	Weighted Averaging
54	Year of Last Improvement	Predominance
55	Year of Last Construction	Predominance
56	Last Overlay Thickness	Predominance
57	Thickness Rigid	Predominance
58	Thickness Flexible	Predominance
59	Base Type	Predominance
60	Base Thickness	Predominance
61	Climate Zone	Predominance
62	Soil Type	Predominance
63	County Code	Predominance
64	National Highway System	No Calculation Required
65	Strategic Highway Network	No Calculation Required
66	National Truck Network	No Calculation Required
67	Future National Highway System	No Calculation Required
68	Maintenance & Operations	Predominance
69	Capacity	Weighted Averaging
70	Directional Through Lanes *	No Calculation Required

*Data items shall be reported as homogenous sections (used to define the TOPS)

**Values for these data items shall be reported for the defined limits of the TOPS sections

***Section limits for this data item shall be consistent with those associated with Data Item 8

#Weighted Averaging may be used if multiple traffic counts are combined to comprise a homogenous section

4.4 Data Item Requirements

NOTE: The following descriptions for each Data Item include an “English” name (in parenthesis) for clarification purposes. However, the States shall use the database-specific data item names shown in bold gray to populate Field 6 in their Sections datasets.

Item 1: F_System (Functional System)

Description: The FHWA approved Functional Classification System.

Use: For querying and analysis of data (e.g., transportation performance management (TPM) metrics, Federal-aid project information, etc.) by functional system.

Extent: All Public highways including ramps located within grade-separated interchanges as identified in 23 U.S.C 101.a(27)

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R
Urban	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R
FE + R = Full Extent & Ramps

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Code the value that represents the FHWA approved functional system. These following codes are to be used for all rural and urban sections:

Code	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

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: For LRS purposes, this Data Item shall be reported independently for both directions of travel associated with divided highway sections, for which dual carriageway GIS network representation is required per guidance in Chapter 3, Section 3.3 and Table 3.5.

This Data Item shall also be reported for all ramp sections contained within grade separated interchanges. If a section is defined as a ramp (i.e., Data Item 3 = Code ‘4’), then it shall be coded the same as the highest order Functional System roadway that traverses the interchange.

Codes ‘6’ and ‘7’ shall be reported for all National Highway System (NHS) sections.

Additional guidance on functional systems and the coding of this item can be found in Chapter 5.

Item 2: Urban_Code (Urban Code)

Description: The U.S. Census Urban Area Code.

Use: For the querying and analysis of data (e.g., transportation performance management (TPM) metrics, Federal-aid project information, etc.) by the unique identification of a State’s urbanized areas, and generically by small urban or rural areas.

Extent: All Public highways including ramps located within grade-separated interchanges as identified in 23 U.S.C. 101.a(27).

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R
Urban	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R
FE + R = Full Extent & Ramps

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Enter up to five digits for the Census urban area code. Leading zeroes are not required.

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: Code ‘99998’ for small urban sections and ‘99999’ for rural area sections. A small urban area shall be derived from Census Urban Clusters that are not located within an urbanized area, with a Census defined population of at least 5,000.Coding for this Data Item shall match the Urban Area boundaries

Appendix I lists the U.S. Census Urban Area Codes that are currently in use. FHWA may issue interim guidance when Urban Codes change.

This Data Item shall also be reported for all ramp sections contained within grade separated interchanges.

A Census Urbanized Area can be expanded for transportation purposes. This Adjusted Urbanized Area, once approved by FHWA, shall be identified using the Census Urban Area Code for the Urbanized Area upon which the adjusted area is based upon. For more information and guidance on the FHWA Urban Boundary adjustment and approval process, see the FHWA publication, “Highway Functional Classification Concepts and Criteria and Procedures, 2013 Edition”.

For LRS purposes, this Data Item can be reported independently for both directions of travel associated with divided highway sections, for which dual carriageway GIS network representation is required per guidance in Chapter 3, Section 3.3 and Table 3.5. NOTE: This data item is required to be reported for both the inventory and non-inventory directional approaches associated with all divided Interstate roadway sections where the following pavement data items have been reported in the same manner (as specified in the Metadata; see Chapter 3, Sec. 3.3, Tables 3.18 and 3.19):

• Data Item 47 (IRI)
• Data Item 48 (PSR)
• Data Item 49 (Surface Type)
• Data Item 50 (Rutting)
• Data Item 51 (Faulting)
• Data Item 52 (Cracking Percent)

Item 3: Facility_Type (Facility Type)

Description: The operational characteristic of the roadway.

Use: For determining public road mileage, for investment requirements modeling to calculate capacity and estimate roadway deficiencies and improvement needs, in the cost allocation pavement model, and in the national highway database; for the querying and analysis of data (e.g., transportation performance management (TPM) metrics, Federal-aid project information, etc.) by facility type.

Extent: All Public highways including ramps located within grade-separated interchanges as identified in 23 U.S.C 101.a(27).

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R
Urban	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R
FE + R = Full Extent & Ramps

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Use one of the following codes as applicable regardless of whether or not the section is on a structure. The definition for each code is as follows:

Code	Description
1	One-Way Roadway	Roadway that operates with traffic moving in a single direction during non-peak period hours.
2	Two-Way Roadway	Roadway that operates with traffic moving in both directions during non-peak period hours.
4	Ramp	Non-mainline junction or connector facility contained within a grade-separated interchange.
5	Non Mainline	All non-mainline facilities excluding ramps.
6	Non Inventory Direction	Individual road/roads of a multi-road facility that is/are not used for determining the primary length for the facility.
7	Planned/Unbuilt	Planned roadway that has yet to be constructed.

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: General

Public road mileage is based only on sections coded ‘1,’ or ‘2’. This includes only those roads that are open to public travel regardless of the ownership or maintenance responsibilities. Ramps are not included in the public road mileage calculation.

Frontage roads and service roads that are public roads shall be coded either as one-way (Code ‘1’) or two-way (Code ‘2’) roadways.

Use Code ‘7’ to identify a new roadway section that has been approved per the State Transportation Improvement Plan (STIP), but has yet to be built.

”One-way Pairs” (See Figure 4.5)

Characteristics:

• Divided roadway sections that have the same route designation (e.g., Route 1), but different street names (e.g., West Avenue, and East Avenue);
• Typically located in an urban area or a city/town;
• Usually connects to roadways with two-way traffic;
• Are typically separated by some physical or visual element other than a curb or barrier, such as buildings, landscaping, or terrain;
• Parallel roadway sections which complement each other in providing access at both termini; and
• Not designated as an Interstate

Ramps

Ramps may consist of directional connectors from either an Interstate to another Interstate, or from an Interstate to a different functional system. Moreover, ramps allow ingress and egress to grade separated highways. Ramps may consist of traditional ramps, acceleration and deceleration lanes, as well as collector-distributor lanes.

Ramps shall be coded with the highest order functional system within the interchange that it functions. A mainline facility that terminates at the junction with another mainline facility is not a ramp and shall be coded ‘1.’

Non-Mainlines

Non-mainline facilities include roads or lanes that provide access to and from sites that are adjacent to a roadway section such as bus terminals, park and ride lots, and rest areas. These may include: special bus lanes, limited access truck roads, ramps to truck weigh stations, or a turn-around.

For LRS purposes, this Data Item shall be reported independently for both directions of travel associated with divided highway sections, for which dual carriageway GIS network representation is required per guidance in Chapter 3, Section 3.3 and Table 3.5.

Figure 4.4 shows an example of a street (E. Baltimore St.), for which traffic is only permitted to move in the eastbound direction. In this particular case, this data item shall be assigned a Code ‘1’ for a given section (Section “X”) along this stretch of road.

Source: Bing Maps

Figure 4.5 shows an example of a street (MD 198), for which traffic moves in the east and westbound directions along a set of one-way pairs (i.e., divided sections located along a given route). In this particular case, this data item shall be assigned a Code ‘1’ for section “X”, and section “Y”.

Source: Bing Maps

Figure 4.6 shows an example of a street (7^th St. NW), for which traffic is permitted to move in both the north and southbound directions. In this particular case, this data item shall be assigned a Code ‘2’ for a given section (Section “X”) along this stretch of road.

Source: Bing Maps

Figure 4.7 shows an example of ramps contained within a grade-separated interchange located on a highway (Interstate 495). In this particular case, this data item shall be assigned a Code ‘4’ for all applicable ramp sections (denoted as “Ramps” in the figure).

Source: Bing Maps

Figure 4.8 shows an example of a highway (Interstate 270), which consists of express and local lanes in both the north and southbound directions. In this particular case, this data item shall be assigned a Code ‘5’ for Sections “X” and “Y” to indicate that they are non-mainline facilities.

Source: Bing Maps

Figure 4.9 shows an example of a highway (Interstate 270), for which an inventory direction is defined (northbound). In this particular case, this data item shall be assigned a Code ‘6’ for Section “X”, as the southbound side of the roadway would be defined as the non-inventory direction.

Source: Bing Maps

Item 4: Structure_Type (Structure Type)

Description: Roadway section that is a bridge, tunnel or causeway.

Use: For analysis in the national highway database and pavement performance analysis/reporting

Extent: All Federal-aid highways.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE**	FE**	FE**	FE**	FE**	FE**
Urban	FE**	FE**	FE**	FE**	FE**	FE**	FE**
FE** = Full Extent wherever data item is applicable

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Use the following codes:

Code	Description
1	Section is a Bridge
2	Section is a Tunnel
3	Section is a Causeway

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: Code this data item wherever a bridge, tunnel, or causeway exists.

Bridges shall meet a minimum length requirement of more than 20 feet (per the National Bridge Inventory (NBI) guidelines in accordance with 23 CFR 650.305) in order to be deemed a “structure.” Per NBI guidelines, bridge-sized culverts shall be reported for this data item; all other culverts are to be excluded.

A tunnel is a roadway below the surface connecting to at-grade adjacent sections.

A causeway is a narrow, low-lying raised roadway, usually providing a passageway over some type of vehicular travel impediment (e.g. a river, swamp, earth dam, wetlands, etc.).

In accordance with 23 CFR 490.309(c), this data shall be collected and reported on an annual cycle for the Interstate roadways and on a 2-year maximum cycle for all other required sections.

The begin and end points for this data item shall be coded in accordance with the points of origin and terminus for the associated bridge, tunnel or causeway. Furthermore, the points of origin and terminus for structures shall exclude approach slabs.

For LRS purposes, this Data Item can be reported independently for both directions of travel associated with divided highway sections, for which dual carriageway GIS network representation is required per guidance in Chapter 3, Section 3.3 and Table 3.5. NOTE: This data item is required to be reported for both the inventory and non-inventory directional approaches associated with all divided Interstate roadway sections where the following pavement data items have been reported in the same manner (as specified in the Metadata; see Chapter 3, Sec. 3.3, Tables 3.18 and 3.19):

• Data Item 47 (IRI)
• Data Item 48 (PSR)
• Data Item 49 (Surface Type)
• Data Item 50 (Rutting)
• Data Item 51 (Faulting)
• Data Item 52 (Cracking Percent)

Source: PennDOT

Source: PennDOT

Source: PennDOT Video-log.

Item 5: Access_Control (Access Control)

Description: The degree of access control for a given section of road.

Use: For investment requirements modeling to calculate capacity and estimate type of design, in truck size and weight studies, and for national highway database purposes.

Extent: All principal arterials and Sample Panel sections; optional for other non-principal arterial sections beyond the limits of the Sample Panel.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE	FE	FE	FE	SP	SP
Urban	FE	FE	FE	FE	SP	SP	SP
FE = Full Extent SP = Sample Panel Sections

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Use the following codes:

Code	Description
1	Full Access Control	Preference given to through traffic movements by providing interchanges with selected public roads, and by prohibiting crossing at-grade and direct driveway connections (i.e., limited access to the facility).
2	Partial Access Control	Preference given to through traffic movement. In addition to interchanges, there may be some crossings at-grade with public roads, but, direct private driveway connections have been minimized through the use of frontage roads or other local access restrictions. Control of curb cuts is not access control.
3	No Access Control	No degree of access control exists (i.e., full access to the facility is permitted).

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Source: TxDOT, Transportation Planning and Programming Division.

Source: https://upload.wikimedia.org/wikipedia/commons/a/a9/Ohio_13_and_Possum_Run_Road.JPG

Figures 4.15 and 16: No Access Control (Code ‘3’)

Source for Figures 4.15 and 4.16: FDOT RCI Field Handbook, Nov. 2008.

Item 6: Ownership (Ownership)

Description: The entity that has legal ownership of a roadway.

Use: For apportionment, administrative, legislative, analytical, and national highway database purposes, and in cost allocation studies; for the querying and analysis of data (e.g., transportation performance management (TPM) metrics, Federal-aid project information, etc.) by ownership.

Extent: All Public highways as identified in 23 U.S.C 101.a(27).

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE	FE	FE	FE	FE	FE	FE	FE
Urban	FE	FE	FE	FE	FE	FE	FE	FE
FE = Full Extent SP = Sample Panel Sections

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Code the level of government that best represents the highway owner irrespective of whether agreements exist for maintenance or other purposes. If more than one code applies, code the lowest numerical value using the following codes:

Code	Description	Code	Description
1	State Highway Agency	60	Other Federal Agency
2	County Highway Agency	62	Bureau of Indian Affairs
3	Town or Township Highway Agency	63	Bureau of Fish and Wildlife
4	City or Municipal Highway Agency	64	U.S. Forest Service
11	State Park, Forest, or Reservation Agency	66	National Park Service
12	Local Park, Forest or Reservation Agency	67	Tennessee Valley Authority
21	Other State Agency	68	Bureau of Land Management
25	Other Local Agency	69	Bureau of Reclamation
26	Private (other than Railroad)	70	Corps of Engineers
27	Railroad	72	Air Force
31	State Toll Road	73	Navy/Marines
32	Local Toll Authority	74	Army
40	Other Public Instrumentality (i.e., Airport)	80	Other
50	Indian Tribe Nation

Value_Text: Optional. Code secondary ownership information, if applicable.

Value_Date: No entry required. Available for State Use.

Guidance: “State” means owned by one of the 50 States, the District of Columbia, or the Commonwealth of Puerto Rico including quasi-official State commissions or organizations;

“County, local, municipal, town, or township” means owned by one of the officially recognized governments established under State authority;

“Federal” means owned by one of the branches of the U.S. Government or independent establishments, government corporations, quasi-official agencies, organizations, or instrumentalities;

“Other” means any other group not already described above or nongovernmental organizations with the authority to build, operate, or maintain toll or free highway facilities.

Only private roads that are open to public travel (e.g., toll bridges) are to be reported in HPMS.

In cases where ownership responsibilities are shared between multiple entities, this item shall be coded based on the primary owner (i.e., the entity that has the larger degree of ownership), if applicable. Information on additional owners shall be entered in Data Field 9 for this item.

For LRS purposes, this Data Item shall be reported independently for both directions of travel associated with divided highway sections, for which dual carriageway GIS network representation is required per guidance in Chapter 3, Section 3.3 and Table 3.5.

Item 7: Through_Lanes (Through Lanes)

Description The number of lanes designated for through-traffic.

Use: For apportionment, administrative, legislative, analytical, pavement performance analysis/reporting and national highway database purposes.

Extent: All Federal-aid highways including ramps located within grade-separated interchanges.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R
Urban	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R	FE+R
FE = Full Extent & Ramps

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Enter the number of through lanes in both directions carrying through traffic in the off-peak period.

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: This Data Item shall also be reported for all ramp sections contained within grade separated interchanges.

Code the number of through lanes according to the striping, if present, on multilane facilities, or according to traffic use or State/local design guidelines if no striping or only centerline striping is present.

For one-way roadways, two-way roadways, and couplets, exclude all ramps and sections defined as auxiliary lanes, such as:

• Collector-distributor lanes
• Weaving lanes
• Frontage road lanes
• Parking and turning lanes
• Acceleration/deceleration lanes
• Toll collection lanes
• Truck climbing lanes
• Shoulders

When coding the number of through lanes for ramps (i.e., where Data Item 3 = Code ‘4’), include the predominant number of (through) lanes on the ramp. Do not include turn lanes (exclusive or combined) at the termini unless they are continuous (turn) lanes over the entire length of the ramp.

Managed lanes (e.g., High Occupancy Vehicle (HOV), High Occupancy Toll (HOT), Express Toll Lanes (ETL)) operating during the off-peak period are to be included in the total count of through lanes.

This data shall be collected and reported on an annual cycle for all required sections.

For LRS purposes, this Data Item can be reported independently for both directions of travel associated with divided highway sections, for which dual carriageway GIS network representation is required per guidance in Chapter 3, Section 3.3 and Table 3.5.

Source: TxDOT, Transportation Planning and Programming Division.

Item 8: HOV_Type (Managed Lane Operations Type)

Description: The type of managed lane operations (e.g., HOV, HOT, ETL, etc.).

Use: For administrative, legislative, analytical, and national highway database purposes.

Extent: All sections where managed lane operations exist. This shall correspond with the information reported for Data Item 9 (Managed Lanes).

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE**	FE**	FE**	FE**	FE**	FE**
Urban	FE**	FE**	FE**	FE**	FE**	FE**	FE**
FE** = Full Extent wherever data item is applicable

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Use the following codes:

Code	Description
1	Full-time Managed Lanes	Section has 24-hour exclusive managed lanes (e.g., HOV use only; no other use permitted).
2	Part-time Managed Lanes	Normal through lanes used for exclusive managed lanes during specified time periods.
3	Part-time Managed Lanes	Shoulder/Parking lanes used for exclusive managed lanes during specified time periods.

Value_Text: No Entry Required. Available for State Use.

Value_Date: No Entry Required. Available for State Use.

Guidance: Code this data item only when managed lane operations exist.

Code this Data Item for both directions to reflect existing managed lane operations. If more than one type of managed lane is present for the section, code the lesser of the two applicable Managed Lane Type codes (e.g., if Codes ‘2’ and ‘3’ are applicable for a section, then the section shall be coded as a Code ‘2’).

Alternatively, if more than one type of managed lane operation exists, the secondary Managed Lane Type may be indicated in the Value_Text field.

This information may be indicated by either managed lane signing (e.g., the presence of a large diamond-shaped marking (HOV symbol) on the pavement, or both).

Source: FDOT RCI Field Handbook, Nov. 2008.

Item 9: HOV_Lanes (Managed Lanes)

Description: Maximum number of lanes in both directions designated for managed lane operations.

Use: For administrative, legislative, analytical, and national highway database purposes.

Extent: All Sections where managed lanes exist. This should correspond with the information reported for Data Item 8 (Managed Lane Operations Type).

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE**	FE**	FE**	FE**	FE**	FE**
Urban	FE**	FE**	FE**	FE**	FE**	FE**	FE**
FE** = Full Extent wherever data item is applicable

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Enter the number of managed lanes in both directions.

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: Code this data item when Data Item 8 (Managed Lane Operations Type) is coded.

If more than one type of managed lane operation exists on the section, code this data item with respect to all managed lanes available, and indicate (in the Value_Text field) how many lanes apply to the Managed Lane Operations Type reported in Data Item 8.

Item 10: Peak_Lanes (Peak Lanes)

Description: The number of lanes in the peak direction of flow during the peak period.

Use: For investment requirements modeling to calculate capacity, and in congestion analyses, including estimates of delay. Also used in the Highway Capacity Manual (HCM)-based capacity calculation procedure.

Extent: All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	SP	SP	SP	SP	SP	SP
Urban	SP	SP	SP	SP	SP	SP	SP
FE = Full Extent SP = Sample Panel Sections

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Code the number of through lanes used during the peak period in the peak direction.

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: Include reversible lanes, parking lanes, or shoulders that are legally used for through-traffic for both non-HOV and HOV operation.

• For urban roads, code based on the peak direction of travel;
• For rural 2 or 3-lane roads, code both directions; and
• For rural roads with 4 or more lanes, code based on the peak direction of travel.

The peak period is represented by the period of the day when observed traffic volumes are the highest.

Source: Mike Kahn/Green Stock Media

Item 11: Counter_Peak_Lanes (Counter-Peak Lanes)

Description: The number of lanes in the counter-peak direction of flow during the peak period.

Use: For investment requirements modeling to calculate capacity, and in congestion analyses, including estimates of delay. It is used in the Highway Capacity Manual (HCM)-based capacity calculation procedure.

Extent: All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	SP	SP	SP	SP	SP	SP
Urban	SP	SP	SP	SP	SP	SP	SP
SP = Sample Panel Sections

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Code the number of through lanes used during the peak period (per Data Item 10) in the counter-peak direction of flow.

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: Include reversible lanes, parking lanes, or shoulders that are legally used for through-traffic for both non-HOV and HOV operation.

• For urban roads, code based on the counter-peak (i.e. opposite-peak) direction of travel;
• For rural 2 or 3-lane roads, do not code this data item

Visual inspection should be used as the principle method used to determine the number of peak lanes and counter-peak lanes.

The number of peak and counter-peak lanes should be greater than or equal to the total number of through lanes (i.e., Peak Lanes + Counter-Peak Lanes >= Through Lanes). The number of peak and counter-peak lanes can be greater than the number of through lanes if shoulders, parking lanes, or other peak-period-only lanes are used during the peak period.

The peak period is represented by the period of the day when observed traffic volumes are the highest.

Item 12: Turn_Lanes_R (Right Turn Lanes)

Description: The presence of right turn lanes at a typical intersection.

Use: For investment requirements modeling to calculate capacity and in congestion analyses, including estimates of delay.

Extent: All Sample Panel sections located in urban areas, optional for all other urban sections beyond the limits of the Sample Panel.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural
Urban	SP	SP	SP	SP	SP	SP	SP
SP = Sample Panel Sections

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Enter the code from the following table that best describes the peak-period turning lane operation in the inventory direction.

Code	Description
1	No intersection where a right turning movement is permitted exists on the section.
2	Turns permitted; multiple exclusive right turning lanes exist. Through movements are prohibited in these lanes. Multiple turning lanes allow for simultaneous turns from all turning lanes.
3	Turns permitted; a continuous exclusive right turning lane exists from intersection to intersection. Through movements are prohibited in this lane.
4	Turns permitted; a single exclusive right turning lane exists.
5	Turns permitted; no exclusive right turning lanes exist.
6	No right turns are permitted during the peak period.

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: Include turning lanes that are located at entrances to shopping centers, industrial parks, and other large traffic generating enterprises as well as public cross streets.

Where peak capacity for a section is governed by a particular intersection that is on the section, code the turning lane operation at that location (referred to as most controlling intersection); otherwise code for a typical intersection.

Through movements are prohibited in exclusive turn lanes.

Use codes ‘2’ through ‘6’ for turn lanes at a signalized or stop sign intersection that is critical to the flow of traffic; otherwise enter the code that best describes the peak-hour turning lane situation for typical intersections on the sample.

Code a continuous turning lane with painted turn bays as a continuous turning lane. Code a through lane that becomes an exclusive turning lane at an intersection as a shared (through/right turn) lane; however, if through and turning movements can be made from a lane at an intersection, it is not an exclusive turning lane.

Roundabouts (as shown in Figure 4.20) should be considered as an intersection where turns are permitted with no exclusive lanes. Use a Code ‘5’ for this item since traffic can either turn or go through the roundabout from the same lane. However, if an exclusive turning lane exists (as indicated by pavement markings), use a Code ‘4’. Code if the roundabout controls the capacity of the entire HPMS section. If there is not a controlling intersection, then code for a typical intersection.

Source: SRA Consulting Group, Nov. 2008

This Data Item shall be coded based on the same intersection that is used for identifying the percent green time for a given roadway section.

Painted islands (Figure 4.21) located in the center of a roadway should be considered a median, for the purpose of determining whether or not a turn lane exists.

Slip-ramp movements should not be considered for the purpose of determining turn lanes.

On-ramps and off-ramps which provide access to and from grade-separated, intersecting roadways are to be excluded from turn lane consideration.

Source: TxDOT, Transportation Planning and Programming Division.

Right Turn Lanes Coding Examples:

Source: FDOT RCI Field Handbook, Nov. 2008.

Source: Minnesota Dept. of Transportation (MnDOT).

Source: MoveTransport.com

Source: FDOT RCI Field Handbook, Nov. 2008.

Source: TxDOT, Transportation Planning and Programming Division.

Item 13: Turn_Lanes_ L (Left Turn Lanes)

Description: The presence of left turn lanes at a typical intersection.

Use: For investment requirements modeling to calculate capacity and in congestion analyses, including estimates of delay.

Extent: All Sample Panel sections located in urban areas, optional for all other urban sections beyond the limits of the Sample Panel.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural
Urban	SP	SP	SP	SP	SP	SP	SP
SP = Sample Panel Sections

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Enter the code from the following table that best describes the peak-period turning lane operation in the inventory direction.

Code	Description
1	No intersection where a left turning movement is permitted exists on the section.
2	Turns permitted; multiple exclusive left turning lanes exist. Through movements are prohibited in these lanes. Multiple turning lanes allow for simultaneous turns from all turning lanes.
3	Turns permitted; a continuous exclusive left turning lane exists from intersection to intersection. Through movements are prohibited in this lane.
4	Turns permitted; a single exclusive left turning lane exists.
5	Turns permitted; no exclusive left turning lanes exist.
6	No left turns are permitted during the peak period.

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: Where peak capacity for a section is governed by a particular intersection that is on the section, code the turning lane operation at that location (referred to as most controlling intersection); otherwise code for a typical intersection.

Include turning lanes that are located at entrances to shopping centers, industrial parks, and other large traffic generating enterprises as well as public cross streets.

Through movements are prohibited in exclusive turn lanes.

Use codes ‘2’ through ‘6’ for turn lanes at a signalized or stop sign intersection that is critical to the flow of traffic; otherwise enter the code that best describes the peak-hour turning lane situation for typical intersections on the sample.

Code a continuous turning lane with painted turn bays as a continuous turning lane. Code a through lane that becomes an exclusive turning lane at an intersection as a shared (through/left turn) lane; however, if through and turning movements can be made from a lane at an intersection, it is not an exclusive turning lane.

Roundabouts (as shown in Figure 4.20) should be considered as an intersection where turns are permitted with no exclusive lanes. Use a Code ‘5’ for this item since traffic can either turn or go through the roundabout from the same lane. Code if the roundabout controls the capacity of the entire HPMS section. If there is not a controlling intersection, then code for a typical intersection.

On-ramps and off-ramps which provide access to and from grade-separated, intersecting roadways are to be excluded from turn lane consideration.

Source: SRA Consulting Group, Nov. 2008

Jug handle configurations (as shown in Figure 4.27), or lanes on either side of the roadway should be considered as an intersection with protected (exclusive) left turn lanes. Although a jug handle may be viewed as a right turn lane, it is intended for left turn movements, therefore it should not be coded as a right turn lane; instead use Code ‘6.’

This Data Item shall be coded based on the same intersection that is used for identifying the percent green time for a given roadway section.

Painted islands located in the center of a roadway should be considered a median, for the purposes of determining whether or not a turn lane exists.

Permitted U-turn movements are not to be considered for the purpose of determining turn lanes.

Left Turn Lanes Coding Examples:

Source: FDOT RCI Field Handbook, Nov. 2008.

Source: Unavailable

Source: Kentucky Transportation Cabinet

Example for Coding Turn Lanes and Through Lanes:

For an intersection that has a single left turn lane and no right turn lane with turns permitted in the peak period (as shown in Figure 4.31), use a code ‘4’ for this Data Item, and a code ‘5’ (turns permitted; no exclusive right turning lane exists) for Data Item 12 (Right Turn Lanes). Additionally, this intersection has four through-lanes (Data Item 7), and two peak-lanes (Data Item 10).

Item 14: Speed_Limit (Speed Limit)

Description: The posted speed limit.

Use: For investment requirements modeling to estimate running speed and for other analysis purposes, including delay estimation.

Extent: All Sample Panel sections, optional for all other sections beyond the limits of the Sample Panel.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE	FE	SP	SP	SP	SP
Urban	FE	FE	SP	SP	SP	SP	SP
SP = Sample Panel Sections

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Enter the daytime speed limit for automobiles posted or legally mandated on the greater part of the section. If there is no legally mandated maximum daytime speed limit for automobiles, code ‘999’.

Value_Text: No entry required. Available for State Use.

Value_Date: No entry required. Available for State Use.

Guidance: If the speed limit changes within the limits of a section, the State shall determine and report the predominant speed limit.

Baseline speed limit data for the National Highway System (NHS) will be provided by FHWA. The State shall validate or update this information annually as needed.

Item 15: Toll_Charged (Toll Charged)

Description: Identifies sections that are toll facilities regardless of whether or not a toll is charged.

Use: For administrative, legislative, analytical, and national highway database purposes.

Extent: All roadways that are toll facilities, whether public or privately-owned / operated.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE**	FE**	FE**	FE**	FE**	FE**	FE**	FE**
Urban	FE**	FE**	FE**	FE**	FE**	FE**	FE**	FE**
FE** = Full Extent wherever data item is applicable

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Use the following codes:

Code	Description
1	Toll charged in one direction only.
2	Toll charged in both directions.
3	No toll charged

Value_Text: Assign the appropriate Toll ID. See Appendix D for the list of IDs.

Value_Date: No entry required. Available for State Use.

Guidance: Code this data item only when a toll facility is present.

Code each toll and non-toll portion of contiguous toll facilities as separate sections.

If tolls are charged in both directions, but only one direction at a given time, then use Code ‘1’.

Include High Occupancy Toll (HOT) lanes and other special toll lanes. Use Code ‘3’ for subsections of a toll facility that do not have tolls.

Source: FDOT RCI Field Handbook, Nov. 2008.

Item 16: Toll_Type (Toll Type)

Description: Indicates the presence of special tolls (i.e., High Occupancy Toll (HOT) lane(s) or other managed lanes).

Use: For administrative, legislative, analytical, and national highway database purposes.

Extent: All roadways where special tolls exist.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE**	FE**	FE**	FE**	FE**	FE**	FE**	FE**
Urban	FE**	FE**	FE**	FE**	FE**	FE**	FE**	FE**
FE** = Full Extent wherever data item is applicable 7

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Use the following codes:

Code	Description
1	This section has toll lanes but no special tolls (e.g., HOT lanes).
2	This section has HOT lanes.
3	This section has other special tolls.

Value_Text: Assign the appropriate Toll ID. See Appendix D for the list of IDs.

Value_Date: No entry required. Available for State Use.

Guidance: This may not be an HOV facility, but has special lanes identified where users would be subject to tolls.

High Occupancy Toll (HOT) lanes are HOV lanes where a fee is charged, sometimes based on occupancy of the vehicle or the type of vehicle. Vehicle types may include buses, vans, or other passenger vehicles.

Item 17: Route_Number (Route Number)

Description: The signed route number.

Use: Used along with route signing and route qualifier to track information by specific route.

Extent: All principal arterials, minor arterials, and the entire NHS.

Functional System		1	2	3	4	5	6	7
	NHS	IH	OFE	OPA	MiA	MaC	MiC	Local
Rural	FE	FE	FE	FE	FE
Urban	FE	FE	FE	FE	FE
FE = Full Extent

Coding Requirements for Fields 8, 9, and 10:

Value_Numeric: Code the appropriate route number (leading zeroes shall not be used), e.g., Interstate 81 shall be coded as ‘81’; Interstate 35W shall be coded as ‘35’.

Value_Text: Enter the full route number, e.g., “35W” or “291A.”

Value_Date: No entry required. Available for State Use.

Guidance: This shall be the same route number that is identified for the route in Data Items 18 and 19 (Route Signing and Route Qualifier).

If two or more routes of the same functional system are signed along a roadway section (e.g., Interstate 64 and Interstate 81), code the lowest route number (i.e., Interstate 64).

If two or more routes of differing functional systems are signed along a roadway section (e.g., Interstate 83 and U.S. 32), code this Data Item in accordance with the highest functional system on the route (in this example, Interstate).

For the official Interstate route number, enter an alphanumeric value for the route in Data Field 9.

If Data Items 18 or 19 (Route Signing or Route Qualifier) are coded ‘10,’ code a text descriptor (in Field 9) for this Data Item.

If the official route number contains an alphabetic character (e.g. “32A”), then code the numeric portion of this value in Field 8, and the entire value in Field 9.

Where a route is designated with alphabetic characters only (e.g. “W”), then don’t code the Value_Numeric field for this item and use the Value_Text field for the route name.

For LRS purposes, this Data Item can be reported independently for both directions of travel associated with divided highway sections, for which dual carriageway GIS network representation is required per guidance in Chapter 3, Section 3.3 and Table 3.5. NOTE: This data item is required to be reported for both the inventory and non-inventory directional approaches associated with all divided Interstate roadway sections where the following pavement data items have been reported in the same manner (as specified in the Metadata; see Chapter 3, Sec. 3.3, Tables 3.18 and 3.19):

• Data Item 47 (IRI)
• Data Item 48 (PSR)
• Data Item 49 (Surface Type)
• Data Item 50 (Rutting)
• Data Item 51 (Faulting)
• Data Item 52 (Cracking Percent)