Minnesota Department of Transportation

511 Travel Info

Corridor Planning Guidebook

Step 2. Background and Context

The purpose of Step 2 is to develop an understanding of the corridor and its broader context and history prior to conducting detailed data collection and analysis in Step 3.

Step 2 focuses on the following information:

  • Studies, Plans and Projects. Relevant prior transportation studies and plans that should be considered as background when preparing the corridor plan.
  • Context. Description of the existing and future built environment, transportation origins and destinations, corridor function, Complete Streets assessment, and community demographics.
  • Roadway Characteristics. Documentation of existing roadway functions and features, including geometric and modal elements, designations, and aesthetic considerations.

Step 2 Engagement Activities

  • Conduct project kickoff meeting with agency and partner staff as appropriate
  • Prepare Engagement Plan
  • Share draft Step 2 results with MnDOT, partner agencies and public
    • Typically, combined with sharing and input on Step 3 results
  • Document input and adjust Step 2 results and Engagement Plan as needed
  • Review Engagement Plan against results to date and adjust as needed See additional guidance in Appendix B: Public and Agency Engagement.

Information to Review

Studies, Plans and Projects

MnDOT and/or other agencies may have previously prepared plans or studies relevant to the corridor, intersecting facilities (roads, trails, transitways), or adjacent areas. These plans and studies may provide important information relevant to the corridor context, such as community needs, transportation challenges, proposed projects, alignment with other efforts, or other information which can support the corridor plan.

The list of plans in Table 3 is intended to be used as a prompt for consideration not a directive to review all listed plans. Guidebook users should review the list, identify relevant plans, and summarize relevant information in narrative, tables or charts, maps, etc., as appropriate. Level of detail for Regional Corridor Vision plan may be less, depending on corridor length.

Item 

Source 

Information to Review 

Prior Corridor-Related Studies or Projects 

Input from MnDOT, District staff, MPO and/or local agency staff 
MnDOT, regional or local agency corridor plans or studies, including transitways where relevant 
MnDOT construction projects, plans and studies webpage 

Purpose of the study or project, year conducted/constructed, agencies involved, key findings related to needs and recommended improvements. 

MnDOT Statewide or District Planning Documents 

State Aviation System Plan 
Statewide Bicycle System Plan 
State Freight Plan 
Statewide Ports and Waterways Plan 
Minnesota Walks (Statewide Pedestrian System Plan) 
State Rail Plan  
Greater MN Transit Investment Plan 
District Freight Plan 
District Safety Plan 
District Bicycle Plan 
District Manufacturers’ Perspective Study 
District Community Conversations reports  
Resilience Improvement Plan 
Carbon Reduction Strategy 
EV Infrastructure Needs Assessment 
Transportation Systems Management and Operations (TSMO) Strategic Plan 
Other Districtwide Plans (example: District 8 Shoulder Widening Prioritization) 
National Hazardous Materials Route Registry 

Scan relevant documents for identified needs and recommended projects, designations (e.g., freight routes, bike routes, emergency evacuation/hazardous materials, etc.), identified modal networks or network gaps in the corridor area.  

Regional and Local Planning Documents 

Area Transportation Partnerships (ATP) relevant studies or other documents  
Regional Development Organizations (RDOs) plans (on the relevant ATP website linked above), as relevant 
MPO metropolitan transportation plan (on the MPO website), as relevant 
City or County transportation plans, Safe Routes to School plans, pedestrian/bicycle plans 
Comprehensive Plans (see also Table 4 below) 
City or county emergency management offices 

Scan relevant documents for identified needs and recommended projects, designations (e.g., freight routes, bike routes, emergency evacuation/hazardous materials, etc.), identified modal networks or network gaps in the corridor area. 

Programmed and Planned Projects 

State Transportation Improvement Program (STIP) 
MnDOT Capital Highway Improvement Plan (CHIP) and  
CHIP Mapping Application 

Planned and programmed projects in the STIP and CHIP in the corridor area. Include description of the project, links to published plans or websites, timeline for construction, and location in or near the corridor area.  

Context

Understanding community context helps identify needs and opportunities of communities along the corridor. The intent of this section is to describe the built environment of the community, the purpose of the corridor, and demographics of communities along the corridor. This review can also help identify any concerns or potential conflicts between local land use plans and existing or future highway infrastructure, such as right-of-way preservation or issues regarding future municipal consent.

Information collected through desk research in this task will be supplemented with information gathered through detailed data collection on Step 3 and through public engagement to develop a holistic view of the corridor and the community.

Item 

Source 

Information to Review 

Corridor Purpose and Function  

MnDOT Functional Classification Map  

Functional classification of road(s) 

Land Use Context Categories and Transportation Hierarchy  

Access Management Category Interactive Map (for internal MnDOT access only) 
MnDOT Complete Streets Handbook 

Documentation of the following for the corridor: 

  • Land Use Context Categories (these can be found in MnDOT’s Access Management Category Interactive Map, which is consistent with Chapter 3 of the Facility Design Guide) 
  • Transportation Hierarchy (which can be found in MnDOT’s Complete Streets Handbook and uses roadway characteristics and land use context to determine user priorities along a road segment)  

Community, Land Use, and Economic Development Context 

Local (city/county) or regional comprehensive plans  

Input from city/county staff regarding pending/proposed developments 

Existing and future land use, relevant land use policies (including Travel Demand Management), local zoning, development patterns, built environment characteristics, key industries, airports, key origins and destinations by mode (vehicle, freight, bike/ped/transit/micromobility), employment centers, schools, housing, parks, and other descriptive information about development within the community. 

Community Demographics 

U.S. Census  
Minnesota Compass 

Comparison of demographics within corridor area to City, County, State.  
Demographics include but are not limited to race and ethnicity, persons with disabilities, persons with limited English proficiency, household income, low-wage workers, age, vehicle ownership.  

Roadway Characteristics

This section describes the key physical features and characteristics of the roadway or roadways that are the subject of the corridor plan.  

Item 

Source 

Information to Review 

Average Annual Daily Traffic (AADT) and Heavy Commercial Average Annual Daily Traffic (HCAADT) 

MnDOT Transportation Data Management System 

Obtain and report most recent daily vehicle volumes as reported for relevant corridor segments 

Roadway Geometry, Design and Modal Elements 

Aerial maps and/or field walk 

Number and purpose of lanes, lane widths, turn lanes, intersection controls, curb cuts, transit elements, sidewalk and bicycle lane widths and design, presence of frontage roads and bridges.  

Right-of-Way 

GIS or other mapping 

Identify existing MnDOT roadway right-of-way if this data is readily available.   

Roadway Designations 

National Highway System (NHS) on FHWA Minnesota’s NHS Webpage 
Oversize/Overweight (OSOW) Superload Corridors map on MnDOT's Freight Webpage 
MnDOT Historical Segments of Trunk Highways in Minnesota Storymap 
MnDOT Scenic Byways Webpage 

Identify whether the corridor is on the NHS system, is an OSOW corridor, is a historical segment of trunk highway, or is a scenic byway. 

Aesthetics and Visual Quality  

Aerial maps and/or field walk 

Presence of street trees and landscaping, lighting, street furniture, wayfinding, etc., and contribution to visual quality or aesthetics of the corridor