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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Baltimore</strong>-<strong>Washington</strong> <strong>Parkway</strong> <strong>Widening</strong> <strong>Feasibility</strong> <strong>Study</strong>Traffic and Transportation Impacts5.4.2.32040No-Buildto2040PartialBuildFigure 5.8 documents the anticipated change in the AM and PM peak hour level-of-service for the 2040Partial-Build scenario relative to the 2040 No-Build Scenario. Key observations associated with thiscomparison include the following:Level-of-service improves under the 2040 Partial-Build Scenario on widened segments south ofMD 175, but degrades on the three-lane segments north of MD 175. This reflects additionaltraffic seeking the benefits of a widened north-south commuter link which has an adverse effecton operations for segments north of MD 175 where widening has already taken place under the2040 No-Build scenario.A reduction in the projected peak-hour level-of-service is also noted for the B-W <strong>Parkway</strong>segment from the Capital Beltway to MD 193 on which the auxiliary lanes between the closelyspacedinterchanges provide three lanes in each direction under existing conditions. Thissection of the <strong>Parkway</strong> is not anticipated to experience any widening under the 2040 Partial-Build scenario compared to either the 2005 Existing Conditions or 2040 No-Build Scenarios.The PM peak hour conditions on those <strong>Parkway</strong> segments south of the Capital Beltway aregenerally worse as these segments are assumed to remain two lanes in each direction under the2040 Partial-Build scenario.Figure 5.8. Change in Level-of-Service from 2040 No-Build to 2040 Partial Build51 November 2012

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

Saved successfully!

Ooh no, something went wrong!