Among the additions and changes to projects proposed to the Transportation Planning Board for inclusion in the 2015 Financially Constrained Long-Range Transportation Plan (CLRP), is an addition of ten dedicated bike lane projects requested by DDOT. These projects will remove one or more lanes for vehicular traffic on approximately 9 miles of streets throughout the city.
Though these are not protected bike lanes, this is still pretty big news, primarily because it demonstrates a transition point for DDOT on two issues.
First, it means they're moving from the low-hanging fruit of bike lanes that can be added without removing traffic lanes or parking to projects that will get more push back from motorists. DDOT has always known that to get to their mileage goal they'd have to do that, but the fact they're initiating this means that they think they have the political cover to move forward with it. Capitol Hill has always had an abundance of bike lanes because they could be added without losing vehicle lanes, and it's telling that none of these proposed lanes are on Capitol Hill.
Second, it means that DDOT is viewing diagonal streets as appropriate places for cyclists. Several years ago there was a discussion about diagonals at a BAC meeting in which DDOT representatives stated that they didn't think cyclists wanted to ride on those streets and that they were going to try to give them other options, and the BAC disagreed. But now they're proposing putting bike lanes on three key diagonals (Pennsylvania Ave NW, Florida Avenue NE and New Jersey Ave NW). I've ridden on all three, and bike lanes will be a welcome addition. In case you're wondering, all 9 miles only cost $480,000. You can see the map and list below.
Update from DDOT: The CLRP is mostly a process step, and there is a lot more design that goes into any of these bike lane installations. Some of these could be protected bike lanes. Some they have started some preliminary design on, some they have not. Some are easy, some are hard. But all have to go through this step before installation.
All of these are “funded” in some form or another, but not all are necessarily funded in the current 6-year budget. And while this is a regional process step, they also still have some outreach/engagement/procedural steps to take as they advance the design on these, and those have to be done before installation. But they have the “build” year as 2015 for almost all of these so that they have the flexibility to install these sooner without going through this annual CLRP process again.
Also, Virginia is proposing improvements to the I-66 Corridor inside the Beltway that includes completion of unspecified elements of the bicycle and pedestrian network around the corridor.
And both Northern Virginia and DC made the removal of streetcar lines official. Update: In DC's case, the small “spur” from Benning Road to Minnesota Avenue station is being removed, since that is not being pursued further as part of the ongoing EA, but there is still active environmental work on the whole of the extension from Oklahoma Avenue to the Benning Road Metro station.
"And both Northern Virginia and DC made the removal of streetcar lines official."
???
Posted by: DaveS | January 22, 2015 at 12:37 PM
Most likely bike projects (none of this is guaranteed, but they are the "regionally significant" project identified in the study this I-66 project is based on):
Project 13 – Custis Trail Widening
This project will widen the trail to 12 feet, where feasible (e.g., right of way is available and
there are no utility conflicts); smooth cracked and heaved pavement; and upgrade trail lighting
between Lynn Street in downtown Rosslyn and the intersection with the Washington and Old
Dominion Trail (in Bluemont Park) near the western edge of Arlington County. This project
supports bicycle commuter travel along the I-66 corridor parallel to the interstate providing
access to many key destinations. These trail improvements will also help accommodate
increased levels of reverse commuting (east to west) by bicycle that may occur in conjunction
with increased development in Tysons and Merrifield.
Project 27 – Fairfax Drive Connector
This project will improve connectivity between the Custis Trail and the Bluemont Junction
Trail, and the western edge of the Rosslyn-Ballston Corridor through wider sidewalks,
improved signal timing, ramps and signage on N. Fairfax Drive west of N. Glebe Road.
Improving access will enable more bicyclists and pedestrians to make commuting and recreational
trips through the area. It will also increase safety for all users by clearly designating the
location of a sidepath to motor vehicles, bicyclists, and pedestrians.
Project 34.A – Arlington Boulevard Trail (Glebe to Beltway)
This project will create a trail along Arlington Boulevard through a combination of constructing
an off-road sidepath, on-street infrastructure, and signage. The project will continue the
existing Arlington Boulevard sidepath west from Glebe Road to the I-495 interchange. The trail
will enable bicyclists to travel from western Arlington County, and eastern/central portions of
Fairfax County to locations in the Rosslyn-Ballston corridor, Crystal City, and east into the
District of Columbia. The improvements will enhance bicyclist comfort through either a separated
bicycle facility, or an on-road bicycle facility on a relatively low-speed, low-volume frontage
road. Alternative alignments will need to be explored around challenging areas, such as
Seven Corners.
Project 34.B – Arlington Boulevard Trail at I-495 Interchange
This project will construct bicycle and pedestrian accommodations across I-495 (Capital
Beltway) in the vicinity of Arlington Boulevard. The ultimate facility will likely be a gradeseparated
crossing, and include overpass crossings of the interchange ramps, Fairview Park
Drive (east of interchange), Gallows Road (west of interchange), as well as the 16 lanes of I-495.
Constructing a crossing of the Beltway at this location will allow for bicycle and pedestrian
traffic on the Arlington Boulevard trail to continue uninterrupted.
Project 34.C – Arlington Boulevard Trail (Beltway West to City of Fairfax)
This project will create a trail along Arlington Boulevard through a combination of constructing
an off-road sidepath, on-street infrastructure, and signage from the I-495/Arlington Boulevard
interchange to the City of Fairfax border at Fairfax Boulevard. The construction of this trail
would make an important connection for cyclists between Fairfax/central Fairfax County and
Arlington County.
Project 51 – West Falls Church Connector Trail
This project will construct a trail between the West Falls Church Metro station and the Pimmit
Hills neighborhood to the northwest. The project will travel through VDOT and WMATA right
of way. This connection has the potential to significantly improve access to the Metro station
from the north.
Project 52 – VA 7 Tysons to Falls Church
This project will construct an off-road connection between the Washington and Old Dominion
Trail in Falls Church and Tysons, running parallel to VA 7 (Leesburg Pike). Shorter-term
improvements may use existing frontage roads to expedite initial implementation. The project
will significantly improve connectivity between major regional destinations (Tysons, Falls
Church) and existing facilities for nonmotorized traffic (Washington and Old Dominion Trail),
and is part of the Fairfax County Bicycle Master Plan.
Posted by: Chris Slatt | January 22, 2015 at 12:47 PM
The smoothing of Custis will be most welcome. They did two different portions over two years a bit back, but left a couple of places that'll really knock the components off your bike.
Posted by: DE | January 22, 2015 at 01:06 PM
DaveS, Arlington cancelled its streetcar this fall and DC decided to "postpone" the extension of the H Street line east.
Posted by: washcycle | January 22, 2015 at 01:18 PM
Nice that they're adding a bike lane on a road crossing RCP. Though I might note that once you get north of M Street, there is not a single road with a bike lane across RCP in DC--and RCP itself runs all the way to Maryland. Porter Street and Military Road clearly need bike accomodation.
Posted by: Crickey7 | January 22, 2015 at 01:59 PM
Bike lanes on diagonals are needed. They are the main connecting routes throughout the city.
Though per the recent discussion on GGW if these aren't protected lanes then greater effort should be made to reduce speeding on these streets.
Posted by: Jeffb | January 22, 2015 at 06:17 PM
Though maybe the lane reduction will accomplish that all by itself?
Posted by: Jeffb | January 22, 2015 at 06:19 PM
If we are going to reduce a lane or lanes on Florida Avenue I would like to see them converted to a bus only lane. Travel on the 90 buses is exceedingly slow.
Posted by: Dave | January 22, 2015 at 08:04 PM
If we are going to lose a lane or two on Florida Ave I would much rather see that lane go to buses. Travel on the 90s line is exceedingly slow.
Posted by: Dave | January 22, 2015 at 08:06 PM
Forgive my lack of understanding, but how do these new projects fit into the scheme of the plans we've seen from DDOT in the past. There is already a FY 2015 plan. Let's face it, many of those have been sitting around for years and have not gotten done. Are these new plans extra special and funded to be done sooner? And does this have any effect on those other plans? For goodness sake, it cannot take that much time expenditure to wrap those up fairly quickly - it is just paint and signs.
Also, why are these not protected bike lanes? Sure, it is great that DDOT has the stones to take out a car lane, but why not go all the way? Don't get me wrong, I will use them and I think other will too.
I find it ironic to see the 7th Street lanes completed after Bicycle Space moved off the block.
Posted by: Steve Seelig | January 22, 2015 at 09:21 PM
Steve, this is sort of the first step in any project. "The CLRP identifies all regionally significant transportation projects and programs that are planned in the Washington metropolitan area between 2014 and 2040. Over 600 projects are included, ranging from simple highway landscaping to billion-dollar highway and transit projects. Some of the projects will be completed in the near future, while others are only in the initial planning stage."
These plans are not funded and won't necessarily happen soon.
I will say that bike lanes aren't always a matter of just painting. There are designs and such that have to be done. That takes time.
Posted by: washcycle | January 22, 2015 at 09:25 PM
I'll echo Steve's apprehension. DDO Tseems great at announcing plans and proposals year after year.
But come next January will we see anything?
Posted by: Jeffb | January 22, 2015 at 11:26 PM
On this list? Probably not. I believe this is long term planning.
Posted by: washcycle | January 22, 2015 at 11:39 PM
Sadly, due to an interpretation of air quality conformity federal regulations, MWCOG requires projects that either increase or decrease the number of lanes to go through air quality modeling. It is a lengthy process, so putting these on the CLRP allows the modeling to go forward, and will likely result in a finding of no impact.
The gist of it is that there is a possibility that in reducing the number of car lanes, DDOT will increase congestion, i.e. idling, and air quality would suffer. Our models are getting better and taking into account mode shifts, but it's still unfortunate that we have to clear this hurdle to deliver projects that will actually make air quality better and facilitate healthier lifestyles.
Also, Steve, give DDOT some credit, while in 2014 they scoped a huge bike network for the MoveDC plan, they also delivered over 9 miles of lanes, including a bunch of cycletrack. I'd give them an A+ for their recent work, and while I'd love to see more too, the obstacles and delays are many.
Posted by: Will | January 23, 2015 at 04:21 AM
Will,
I give the DDOT huge credit, both to the bike folks in planning for bike lanes and in getting the GoDC thing done before the end of Gray's tenure. Note: I said planning. The execution from the engineering folks in actually getting installations done is appallingly bad.
Let's see how the new guy does in creating an agency where the laziest person does not get to stop bike lane installation, as it has been for many years.
Posted by: Steve Seelig | January 23, 2015 at 09:22 AM
6th St. NE already has bike lanes between K St and Florida. I last rode in those lanes about a month ago.
Posted by: rsn | January 23, 2015 at 11:28 AM
The post has been updated with new information from DDOT.
Posted by: washcycle | January 23, 2015 at 11:40 AM
I thought new jersey was going to get rebuilt between k and new york ave. whatever happened to that?
Posted by: neb | January 23, 2015 at 02:56 PM
@neb, I think the major plans for NJ Ave reconstruction are the blocks just north of NY Ave, not south of it, but I could be wrong.
Posted by: Jacques | January 26, 2015 at 12:30 PM
A member of the Virginia General Assembly has introduced a bile to require cyclists to ride on a path instead of the road if one is available. This is a horrible idea that should be stamped down wherever it rears its ugly head.
Quoting from the Coalition for Smarter Growth:
"A Delegate from outside of Richmond has introduced a bill (HB1746) that would require people on bikes to use any available sidepath or bike lane, and prohibit their riding in the roadway. Obviously, this bill could have major negative impacts on the many Northern Virginia cyclists who use bicycles for transportation."
http://salsa3.salsalabs.com/o/2041/p/dia/action3/common/public/?action_KEY=15475
Posted by: DE | January 28, 2015 at 02:25 PM
bile = bill, but maybe I meant it, subconsciously.
Posted by: DE | January 28, 2015 at 02:25 PM