12.07.2015 Views

Baltimore-Washington Parkway Widening Feasibility Study

Baltimore-Washington Parkway Widening Feasibility Study

Baltimore-Washington Parkway Widening Feasibility Study

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Baltimore</strong>-<strong>Washington</strong> <strong>Parkway</strong> <strong>Widening</strong> <strong>Feasibility</strong> <strong>Study</strong>Traffic and Transportation Impacts5.4.2.42040No-Buildto2040Full-BuildFigure 5.9 documents the projected change in the peak hour level-of-service from 2040 No-Buildscenario to the 2040 Full-Build scenario. Key observations include the following: Results are similar to the comparison between the 2040 No-Build and 2040 Partial-Build north ofthe Capital Beltway. Thus, peak hour level-of-service is anticipated to improve under the 2040Full-Build scenario on widened segments south of MD 175, but degrades on the three-lanesegments north of MD 175. This reflects additional traffic seeking the benefits of a widenednorth-south commuter link which has an adverse effect on operations for segments north ofMD 175 where widening has already taken place under the 2040 No-Build scenario. The PM peak hour level-of-service conditions south of the MD 450 interchange to U.S. Route 50are generally worse as these segments are three lanes under existing conditions and will notexperience any widening under the 2040 Full-Build scenario despite experiencing an increase indemand resulting from widening elsewhere along the <strong>Parkway</strong>. The AM peak hour level-ofserviceconditions are expected to remain essentially unchanged from those observed in the2005 Existing Conditions and the 2040 No-Build and 2040 Partial-Build scenarios.Figure 5.9. Change in Level-of-Service from 2040 No-Build to 2040 Full-Build52 November 2012

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!