Roadway Elements | Non-Metropolitan Area | Metropolitan Area |
Document characteristics within the project limits of known roadway projects that will be moved into the updated TSP and that will be subject to an enhanced review process based on OAR 660-012-0830 (see
Enhanced Review of Select Roadway Projects for more information) |
Could |
Shall |
Location of all publicly owned, operated, or supported streets |
Shall |
Shall |
Identification of roadway ownership by jurisdiction |
Shall |
Shall |
Identification of roadway classifications by jurisdiction, including federal, state, regional, and local classifications, as applicable |
Shall |
Shall |
Identification of primary uses, and whether they serve local, regional, pass-through, or freight traffic |
Should |
Shall |
Identification of primary users of a facility, including whether users are primarily on foot, bicycle, transit, freight, or personal vehicle |
Should |
Shall |
Identification of land use context for each segment of a facility, including types of planned land uses surrounding the facility |
Should |
Shall |
Identification of the location of key destinations |
Should |
Shall |
Identification of roadway characteristics: - For local streets include location
- For collector streets include location, condition, and number of general-purpose travel lanes and turn lanes
- For arterial streets include location, condition, and number of general-purpose travel lanes, turn lanes, and lane width
- For expressways and other limited-access highways include location, condition, and number of general-purpose travel lanes, turn lanes, and lane width, as well as the locations and types of interchanges
|
Shall |
Shall |
Identification of lane configurations and traffic control devices at study intersections |
Shall |
Should |
Identification of area-wide traffic signals and ownership responsibility |
Shall |
Should |
Identification and type of intelligent transportation systems facilities |
Shall |
Should |
An overview of pricing strategies in use, including specific facility pricing, area or cordon pricing, and parking pricing |
Should |
Shall |
Collection of weekday evening peak-period traffic counts at the identified study intersections |
Shall |
Should |
Identification of bridge location, condition (bridge sufficiency rating), and ownership responsibility |
Shall |
Should |
Identification of pavement type and conditions through a windshield survey |
Should |
Shall |
Location of all reported serious injuries and deaths of people related to vehicular crashes from the most recent 5 years of available data |
Should |
Shall |
Quantify average annual daily traffic volumes on all paved public roads |
Should |
Should |
Safety analysis (e.g., crash data, Safety Priority Index System locations, off-ramp queuing) |
Should |
Should |
Collection of weekday morning and/or weekday mid-afternoon peak period traffic counts at the identified study intersections |
Could |
Could |
Identification of existing right-of-way widths for all collector and arterial roadways and where the right-of-way may be insufficient to accommodate future buildout |
Could |
Could |
Identification of the number and locations of points-of-access to state facilities |
Could |
Could |
Identification of on-street parking locations |
Could |
Could |
Collection of 16-hour full-classification traffic counts at the identified study intersections or select locations
|
Could |
Should |
Identification of detailed pavement conditions of all federal-aid-eligible roadways using pavement conditions index |
Could |
Could
|