VaDOT is working on an update to the 2003 NOVA Regional Bikeway and Trail Network Study, and they released a draft version of that update last month. After studying how much latent demand there was, what level of service cyclists were receiving and what the public expressed as priorities, they've created a draft of a new network that is " more extensive than that of 2003 and reflects the region’s progress in improving bicycle connectivity through on-road and off-road bicycle infrastructure."
20% of the bike network (108 miles in total) identified in 2003 has since been added in the region.
The 2015 Network includes 367 miles of off-road shared-use paths and trails, 61 miles of on-road bicycle lanes, 72 miles of “other notable existing” facilities, and 530 miles of proposed regional corridors.
Most of the places they've identified with latent demand are urban and already bike-friendly.
The study of bicycle level of service found that only 19% of Virginia's Regional Roadway Network was "generally considered comfortable bicycle facilities".
These comfortable cycling facilities are typically characterized by low-volume neighborhood streets or roadways with parallel shared use paths. Patrick Henry Drive (Arlington County), below, is a great example of a BLOS “A” facility, as it is predominately residential and equipped with bidirectional bicycle lanes.
58% is considered "tolerable" and the remaining 23% is "uncomfortable."
The study recommends 34 additions to the Regional Bikeway and Trails Network, with several of those being in the Alexandria and Arlington area. Many of these facilities already exist and are just being added to the map.
Alexandria
- In Alexandria, the study recommends adding facilities to Edsall Road between I-395 and Pickett Street and to Eisenhower Avenue from S. Van Dorn Street to Holmes Run as "proposed" in the 2015 Eisenhower West Small Area Plan.
- It also "adds" the existing sharrows on Braddock Road from W. Windsor Avenue (end of existing bike lanes) to King Street.
- On Janneys Lane / Seminary Road / N. Pickett Street / N. Pegram Road the study adds the existing bike lanes as "on-road" and the "proposed" ones from N. Quaker Road to N. Pickett Street and then continuing on N. Pickett and N. Pegram Road.; and then connecting this "proposed segment" with the existing bike lanes on N. Pegram Road, which ultimately connect to the Holmes Run Trail.
- On Braddock Road from Commonwealth Avenue to Mount Vernon Avenue it "adds" the existing sharrows.
Alexandria and Arlington
- Valley Drive/Preston Road/Martha Custis Drive - Add as "other notable existing" along W. Glebe Road, Valley Drive, and Preston Road. Existing shared lane markings. Also add "other notable existing" along Martha Custis Drive/ Shirlington Bridge/ Quincy Street to the Four Mile Run Trail
Arlington
- Army-Navy Driver from Memorial Drive to S. Glebe Drive at the Four Mile Run Trail - Add as "proposed", connecting the existing Army Navy Drive bike lanes to S. Glebe Drive via S. Adams Street and 26th Road
- Boundary Channel Drive from S. Washington Boulevard to the Mount Vernon Trail via LBJ Park - Add connection in Lady Bird Johnson Memorial Park as "other notable existing" and add connection from LBJ Park to S. Washington Boulevard as "proposed"
- Key Boulevard from N. Veitch Street to Kirkwood Road - Add as "other notable existing" since Key Boulevard operates as a bike boulevard, with various traffic calming measures (bulb outs, chokers, and traffic circles). Connect to Kirkwood Road on the west end via N. Jackson Street and 13th Street
- S. Washington Boulevard from US 50 (Arlington Boulevard) to Columbia Pike (Towers Park) - Add as "on-road, existing" from US 50 to S. Courthouse Road and as "proposed" from S. Courthouse Road to S. Quinn Street / Columbia Pike
- S. Abingdon Street/ 34th / S. Stafford / 33rd from 31st Street to N. Quaker Lane - Add as "on-road, existing" from 31st Street to N. Quaker Lane (existing bike lanes). Recommend that S. Wakefield Street become a signed bicycle route
Thanks for posting this. As a bike commuter for ten years in a more hostile part of Fairfax County, I have to say that this is depressing. I'm supposed to be happy about 61 miles of on-road bike lanes in a huge, wealthy county? I guess I should celebrate every victory, but I would like to see it read 610 miles rather than 61. VDOT is all about cars. Maybe someone can point me to the bright side.
Posted by: Damien | December 01, 2015 at 07:59 AM
The biggest problem is that once VDOT slaps down a sidepath they congratulate themselves and never think about it again. E.g., the FFX county parkway trail, which hasn't been fully repaved in 30 years, is often covered with debris and has low-hanging trees and other maintenance issues gets an A. There is no way that VDOT would give an A rating to a road in the same shape. The parkway itself, running right next to the badly paved trail, gets repaved at least every 5 years. (To be fair, VDOT did finally repave some parts of the trail a couple of years ago, but only the very worst parts--and that was done with leftovers from the road work.)
Posted by: Mike | December 01, 2015 at 08:32 AM
Isn't that 61 miles over the whole region? So it's even worse than that for Fairfax.
I used to commute from Arlington to Fairfax City. Fairfax does have some good trails, but if they don't go where you're going, it gets difficult. The cloverleafs around I-66 are especially problematic. VDOT plans them for cars, as it probably should, but leaves little realistic accommodation for pedestrians or cyclists.
Posted by: DE | December 01, 2015 at 08:38 AM
"Propsed corridors" mileage should under no circumstances be included in the "Total Network" mileage.
There is no cost to propose facilities and put them down on paper. There is a cost to actually designing, building, and implementing them.
I don't consider anything as part of the network until the pavement/paint/barriers are in place.
Posted by: Alexandria Cyclist | December 01, 2015 at 11:20 AM
@DE
"VDOT plans them for cars, as it probably should, but leaves little realistic accommodation for pedestrians or cyclists"
The "T" in VDOT stands for transportation, not cars.
Posted by: Alexandria Cyclist | December 01, 2015 at 11:21 AM
A brief look at their website would tell you that the T might as well stand for Cars.
Posted by: DE | December 01, 2015 at 11:30 AM
I second Mike's comments on the FFX county side paths. The Braddock Road side path is a death trap from the Fairfax county parkway all the way to the Cross County Connector. This could be made a well usable corridor with pretty reasonable investment.
Posted by: Chris | December 01, 2015 at 06:32 PM
I have been a resident of Fairfax County for 25 years, and have biked all over. I'm a regular bike commuter from my house in Springfield to Fort Belvoir, I've also bike commuted to a previous job in Alexandria, and I've ridden all over Alexandria, Arlington, and other counties in the region.
IMO FFX county has the worst biking infrastructure in the area. The path along the FFX County Parkway and the Franconia Springfield Parkway meanders, is hard to follow, and is frequently in poor shape, with sand, mud, uneven pavement, and often with overgrown trees. I know of several examples of paths that lead nowhere - these are just put in place with no thought to an overall plan. I'm sure the county pats themselves on the back for these, but they really don't add much of a real capability.
I've heard lots of plans, and plans for plans, over the years, but have seen little action. They keep revising the master plan and worrying about little things, when many improvements are obvious and don't need exhaustive study. For example, a major road near my house would benefit simply from a shoulder or a side path (both for bikes and pedestrians) and would enable non-motorized access to a shopping center, and might help enable kids to ride their bike or walk to school. (I submitted a request for a sidewalk to the county years ago, and received a vague response that they'd look into it.) Instead, it remains very dangerous to anything but cars, and my community is isolated.
Posted by: happy rider | December 01, 2015 at 08:14 PM
A few more comments:
It looks like they give themselves credit for proposed corridors, and furthermore, these are the majority of the network. That's silly. A proposal doesn't do me any good now - it's just a proposal on paper.
Another metric in the report is that they've only built 20 percent of the trails that were planned in 2003. That's not very encouraging.
Their color coding of latent demand, BLOS, and so on, misses some obvious things, like where are trail doesn't connect. For example, the path along the FFX county parkway from where the parkway splits into the FFX county parkway and the Franconia Springfield parkway TO I-95, does not connect with either the path on the south side of I-95, nor to the FFX county parkway or the Franconia Springfield parkway. A path is only useful if it is contiguous. Again, it doesn't take a deep analysis, a hired consulting firm, and a long, drawn-out equation in the appendix to define BLOS: it's just common sense!
Fort Belvoir was increased in the latest BRAC, but none of the proposals are near Fort Belvoir. The only change in the southern part of the county is for Gunston Road. That's a nice road to ride on to get to Mason Neck, but I'm surprised that that made it as a priority, and that it's the only proposal for the southern part of the county. How about a good way to take the FFX county parkway over I-95?
Posted by: happy rider | December 01, 2015 at 08:43 PM