Can't bike into town, because of all the rallies mucking things up. Can't take Metro anywhere, between rally-goers and trackwork on the Yellow Line. Can't go east cause 50 is all ripped up. Can't go west cause 66 is single-lane at the Beltway. Can't go north cause it's too late to get out. Can't go south cause 95 is...95.
So I guess I'll stay home and laugh at all the lunacy...
Adam's blog is now roaming the dirt roads of Vermont, chronicling transportation and travels one hill at a time...
August 28, 2010
August 11, 2010
New contraflow bike lanes on New Hampshire Ave NW
Greater Greater Washington has a post this morning about the new contraflow bike lanes on New Hampshire Ave NW, for a block or so on either side of the 16th/U St intersection.
But there's a curious twist to them...the contraflow lane is between the opposing travel lane and the parking lane, as is suggested on the edges of the below graphic:

I don't see anything wrong with the intersection layout itself, with dedicated bicycle signals and the bike boxes on 16th St. But the contraflow lanes on the adjacent blocks are some cause for concern. I easily see this creating a higher potential for bike-vehicle collisions given that vehicles will have to cross the bike lane in order to park or depart from the parking lane. There's also nothing really stopping vehicles from using the bike lane as a staging area or outright parking in the bike lane.
There's a better overall solution for this case. There appears to be enough width on New Hampshire Ave to implement a full-width bike lane curbside, moving the parking lane back to the "opposing flow side" of the street, with the two sides then being separated by a raised curb or bollards.
Though there are a couple disadvantages to this solution...:
...there are some noteable advantages:
Either way, I'm reminded of last year's implementation of bike lanes on 1st Ave N in downtown Minneapolis, MN, which has a little bit of both the new New Hamsphire Ave configuration and my proposed re-configuration. These 1st Ave N bike lanes are curbside, between the parking lane and the curb. But they are also on the passenger side of parked vehicles, with a lower chance of "doorings" than if the bike lane were on the driver's side.
I'm off tomorrow, so I may have to take a bike ride up to check it out...
But there's a curious twist to them...the contraflow lane is between the opposing travel lane and the parking lane, as is suggested on the edges of the below graphic:

I don't see anything wrong with the intersection layout itself, with dedicated bicycle signals and the bike boxes on 16th St. But the contraflow lanes on the adjacent blocks are some cause for concern. I easily see this creating a higher potential for bike-vehicle collisions given that vehicles will have to cross the bike lane in order to park or depart from the parking lane. There's also nothing really stopping vehicles from using the bike lane as a staging area or outright parking in the bike lane.
There's a better overall solution for this case. There appears to be enough width on New Hampshire Ave to implement a full-width bike lane curbside, moving the parking lane back to the "opposing flow side" of the street, with the two sides then being separated by a raised curb or bollards.
Though there are a couple disadvantages to this solution...:
- Greater bike-ped conflict potential.
- Greater "dooring" potential (since the bike lane would be on the driver's side and not the passenger's side).
...there are some noteable advantages:
- Parking vehicles no longer need to cross the bike lane, reducing potential bike-vehicle conflicts.
- Physical separation of the bike lane from vehicle lanes (parking or travel) further reduces potential bike-vehicle conflicts, plus the possibility of a vehicle using the bike lane for parking or "staging".
- Full-width bike lane reduces the chance of a "dooring" incident, plus it still allows for snow removal in winter (similar to the 15th St contraflow lane).
- Bike-ped and "dooring" incidents are generally less severe than bike-"moving vehicle" incidents.
Either way, I'm reminded of last year's implementation of bike lanes on 1st Ave N in downtown Minneapolis, MN, which has a little bit of both the new New Hamsphire Ave configuration and my proposed re-configuration. These 1st Ave N bike lanes are curbside, between the parking lane and the curb. But they are also on the passenger side of parked vehicles, with a lower chance of "doorings" than if the bike lane were on the driver's side.
I'm off tomorrow, so I may have to take a bike ride up to check it out...
July 31, 2010
Why drivers hate us bikes...
My curmudgeonly associate had this to say on Twitter last night:
To which I'll add red light runners (REGARDLESS of mode) and those who don't even bother to slow down at 4-way stops...both of which I see all the time in Old Town. I'll admit that I don't always stop at 4-ways, but I'll at least slow down to see if cars are coming, because if a car gets there first, they have the right-of-way. Period.
dear fellow cyclists on H street—cutting other cyclists off & then riding down the wrong side of the road epitomizes why drivers hate us.
To which I'll add red light runners (REGARDLESS of mode) and those who don't even bother to slow down at 4-way stops...both of which I see all the time in Old Town. I'll admit that I don't always stop at 4-ways, but I'll at least slow down to see if cars are coming, because if a car gets there first, they have the right-of-way. Period.
July 20, 2010
Complete Streets for Alexandria, next phase
A bit late on this, but the big news out of last week's Alexandria Transportation Commission meeting was that Complete Streets was approved by the Commission, with a draft resolution and a draft ordinance being forwarded to City Council to be placed on the docket sometime this fall. There was concern from one Commission member about the lack of a public hearing by the Commission on Complete Streets, but it was explained that City Council will be holding their own public hearing on the subject, and this was acceptable to the Commission member.
The other big news from the meeting was BRAC-133, as the meeting doubled as the Public Hearing on the draft BRAC-133 TMP. There were only three commenters at the meeting, though several more citizens were in attendence.
One commenter was convinced of the need for BRAC-133 shuttle service to include the Eisenhower Ave Metro station, going so far as to comment that it would serve both the Blue and Yellow Lines (Yellow, yes...Blue, no). Another commenter wanted complete separation between the BRAC-133 shuttles and DASH buses that serve Southern Towers. This second commenter also thought that emphasis on bicycle routes and bicycle usage to/from Mark Center is not worthwhile. Unfortunately, I didn't catch much from the third speaker.
The Draft TMP is due to NCPC on July 30.
Last bit from the meeting was an update on some reports and studies. An Environmental Assessment is about to be initiated for the proposed Potomac Yard Metro Station. Traffic analysis for the Beauregard Corridor study is underway, with some findings due out this fall...this study also includes Van Dorn St. A report on Old Town Parking is due out in September. And staff are in the process of starting a 13-month Transitway Feasibility Study on the 3 primary transit corridors in the city's Transportation Master Plan, with the intial study focus on the Beauregard/Van Dorn corridor.
No August meeting for the Commission...next meeting is September 1.
The other big news from the meeting was BRAC-133, as the meeting doubled as the Public Hearing on the draft BRAC-133 TMP. There were only three commenters at the meeting, though several more citizens were in attendence.
One commenter was convinced of the need for BRAC-133 shuttle service to include the Eisenhower Ave Metro station, going so far as to comment that it would serve both the Blue and Yellow Lines (Yellow, yes...Blue, no). Another commenter wanted complete separation between the BRAC-133 shuttles and DASH buses that serve Southern Towers. This second commenter also thought that emphasis on bicycle routes and bicycle usage to/from Mark Center is not worthwhile. Unfortunately, I didn't catch much from the third speaker.
The Draft TMP is due to NCPC on July 30.
Last bit from the meeting was an update on some reports and studies. An Environmental Assessment is about to be initiated for the proposed Potomac Yard Metro Station. Traffic analysis for the Beauregard Corridor study is underway, with some findings due out this fall...this study also includes Van Dorn St. A report on Old Town Parking is due out in September. And staff are in the process of starting a 13-month Transitway Feasibility Study on the 3 primary transit corridors in the city's Transportation Master Plan, with the intial study focus on the Beauregard/Van Dorn corridor.
No August meeting for the Commission...next meeting is September 1.
July 12, 2010
"Let's make a deal", Mississippi style
Mississippi recently passed a 3-foot passing law for vehicles to give bicyclists at least 3 feet of space when passing. Quite impressive, given Mississippi's near-complete rule-by-car mentality.
So yesterday, the SunHerald (Mississippi Gulf Coast newspaper) writes an article about the new law. The comment section, as expected, has some negative comments...many of which have been heard before in the DC region, including on TheWashCycle.
My favorite has to be "Let's Make a Deal":
Perhaps someone should take him up on that deal...though I'd throw in a counterproposal: when drivers themselves learn to stop at red lights and stop signs, we'll deal.
So yesterday, the SunHerald (Mississippi Gulf Coast newspaper) writes an article about the new law. The comment section, as expected, has some negative comments...many of which have been heard before in the DC region, including on TheWashCycle.
My favorite has to be "Let's Make a Deal":
When cyclists learn to stop at red lights, stop signs and buy tags I give them 3 feet. The cyclists that ride in Woolmarket stay in the traffic lane, go around cars at stop signs and are not equipped to ride in dusk hours. Rural roads that are barely wide enough for 2 cars to pass and have no sidewalk or curd and gutter just screams for an accident. Are riders required to wear helments in this law?
Why is a cyclist allowed to ride on the roads I have to buy a tag to drive on but a 4 wheeler can not?
Perhaps someone should take him up on that deal...though I'd throw in a counterproposal: when drivers themselves learn to stop at red lights and stop signs, we'll deal.
I'll catch it after all...
Transportation Commission meeting apparently got moved to this Thursday, so I'll be able to make it after all. It's also the Public Hearing on the BRAC-133 Transportation Management Plan, so if you're interested in speaking, be sure to be there.
July 02, 2010
On vacation
On vacation for the next week and a half or so, so I'll be missing next week's Alexandria Transportation Commission meeting where they're expected to approve the draft Complete Streets ordinance and send it to the City Manager (for eventual approval by City Council, expected this fall). Also, don't miss the public hearing part of the commission meeting, covering the BRAC-133 Transportation Management Plan.
Side note, no city-sponsored Ped/Bike Citizens Group meetings until September. Thinking BikeWalk Alexandria will still have their normal meeting in August.
Hopefully when I get back, we'll have a better timeline on the new deck drains for the Route 1 ATL. At least they cleared the dirt piles off the section prone to flooding. Now if VDOT could just clear off the rest of the trail down to Huntington Ave.
Side note, no city-sponsored Ped/Bike Citizens Group meetings until September. Thinking BikeWalk Alexandria will still have their normal meeting in August.
Hopefully when I get back, we'll have a better timeline on the new deck drains for the Route 1 ATL. At least they cleared the dirt piles off the section prone to flooding. Now if VDOT could just clear off the rest of the trail down to Huntington Ave.
June 15, 2010
Route 1 ATL to get new drains
Got a bit of a surprise over the weekend. I've received a few E-mails from the Wilson Bridge public affairs team E-mailed me regarding my complaint about debris on the Route 1 ATL and the clogged drains near the start of the bridge.
First off, right after I sent my original E-mail, a team was dispatched to clear the drains of the debris I had noted. This has been done, though the rest of the sand/dirt along the trail has yet to be cleared up (another E-mail to VDOT/WWB is being sent this morning).
As for the drains themselves, the Wilson Bridge team has known of their tendency to clog for some time. The drain grates that were installed (with the narrow slots) are apparently the ones that meet Federal design standards. The bridge team has been working, and recently received approval from FHWA and VDOT, on a design exemption to install grates with wider slots (so as to reduce the chances of them clogging). Now they're just waiting for manufacture of the new grates so they can be installed, with the goal of having them installed by the end of July.
So this should hopefully eliminate our recurring Active Transportation LAKE. I also hope they don't run into the same problem that DDOT did recently with installing grates in the wrong direction... (i.e. parallel to the travel path)
First off, right after I sent my original E-mail, a team was dispatched to clear the drains of the debris I had noted. This has been done, though the rest of the sand/dirt along the trail has yet to be cleared up (another E-mail to VDOT/WWB is being sent this morning).
As for the drains themselves, the Wilson Bridge team has known of their tendency to clog for some time. The drain grates that were installed (with the narrow slots) are apparently the ones that meet Federal design standards. The bridge team has been working, and recently received approval from FHWA and VDOT, on a design exemption to install grates with wider slots (so as to reduce the chances of them clogging). Now they're just waiting for manufacture of the new grates so they can be installed, with the goal of having them installed by the end of July.
So this should hopefully eliminate our recurring Active Transportation LAKE. I also hope they don't run into the same problem that DDOT did recently with installing grates in the wrong direction... (i.e. parallel to the travel path)
June 10, 2010
Route 1 ATL update
Checked earlier this afternoon...still the leftover mudpuddle, so no cleanup yet. If there's nothing by tomorrow, I'll be calling VDOT back (and sending out another E-mail)...
June 04, 2010
The Route 1 Active Transportation LAKE
Yes, lake. Not lane. Lake. But first, an update on another issue.
The other issue being the traffic signal at Route 1 and Fort Hunt Rd, just south of the Beltway. The pedestrian signals here have been hiding behind black plastic bags for months. It got to the point where Turbineblade (coincidentally a neighbor of mine who's a bicycle enthusiast) complained on TheWashCycle on Tuesday.
So I did a quick walkabout after the storms yesterday evening to check on both the signal and the "lake".

Of course, no walk/bike ride would be complete without some driver stopping halfway into the crosswalk. No excuse for this guy...the light on Huntington Ave was red for a full 20 seconds before he got down here.

Then there's the dirt/silt piles. Not just the sidewalk here on this side, but the ATL (bike/ped path) on the other side of Route 1 have had these dirt/silt piles ever since the February snowstorms. Nobody has bothered to clear them off yet. More on that later.
Then I got down to the intersection at Fort Hunt Rd, where I happily saw that the plastic bags were removed and the pedestrian signals were operational:

I did notice two problems with the signals, though. First, and this is the same issue at Huntington Ave, they're not automatic...you have to push the button in order to get the walk signal. While I could see doing this late at night for crossing Route 1, I see no reason why the pedestrian signals can't be automatic during the normal daytime cycles...especially on Route 1 itself. Also, the daytime cycle lengths for cross-traffic crossing Route 1 are long enough to where they could also easily be automatic for the pedestrian signals.
The second problem is that the walk phase on the northbound Route 1 side changes to "don't walk" way too quickly, especially since the green phase for northbound Route 1 is quite long.
Now, moving on to our Active Transportation Lake, which "Whiteknuckled" complained about on TheWashCycle on Wednesday. I've noticed this one too in recent weeks, especially after it rains (like it did yesterday evening). Here's one of the culprits:

This is one of two drains (the other is hidden under the "lake") that have been clogged with dirt and debris ever since the storm. Because they're clogged, we get this "lake" forming every time it rains.
So last night, I sent out an E-mail about both the "lake" and the dirt/silt on the paths/sidewalks. I addressed it mainly to VDOT and the Wilson Bridge team, but also CCed several others, including the Fairfax County Supervisor for the district, the two State Delegates for the area...their district line goes right through the Route 1/Fort Hunt Rd intersection, and the State Senator for the area. Below is the E-mail I sent, verbatim:
Before I even got to bed, I had an E-mail from Delegate Surovell, saying "This is ridiculous" and directing his legislative assistant to get an answer from VDOT. Early this morning, I got an E-mail from Bob Driscoll, manager for VDOT's Fairfax Maintenance district, stating he wasn't sure if his maintenance district was responsible for this section, but he'd direct it to the proper maintenance district if it isn't Fairfax.
So we'll see. Hopefully, it'll get to the right person, get to them soon, and we'll have cleared out drains and an "empty lake" before too long.
The other issue being the traffic signal at Route 1 and Fort Hunt Rd, just south of the Beltway. The pedestrian signals here have been hiding behind black plastic bags for months. It got to the point where Turbineblade (coincidentally a neighbor of mine who's a bicycle enthusiast) complained on TheWashCycle on Tuesday.
So I did a quick walkabout after the storms yesterday evening to check on both the signal and the "lake".

Of course, no walk/bike ride would be complete without some driver stopping halfway into the crosswalk. No excuse for this guy...the light on Huntington Ave was red for a full 20 seconds before he got down here.

Then there's the dirt/silt piles. Not just the sidewalk here on this side, but the ATL (bike/ped path) on the other side of Route 1 have had these dirt/silt piles ever since the February snowstorms. Nobody has bothered to clear them off yet. More on that later.
Then I got down to the intersection at Fort Hunt Rd, where I happily saw that the plastic bags were removed and the pedestrian signals were operational:

I did notice two problems with the signals, though. First, and this is the same issue at Huntington Ave, they're not automatic...you have to push the button in order to get the walk signal. While I could see doing this late at night for crossing Route 1, I see no reason why the pedestrian signals can't be automatic during the normal daytime cycles...especially on Route 1 itself. Also, the daytime cycle lengths for cross-traffic crossing Route 1 are long enough to where they could also easily be automatic for the pedestrian signals.
The second problem is that the walk phase on the northbound Route 1 side changes to "don't walk" way too quickly, especially since the green phase for northbound Route 1 is quite long.
Now, moving on to our Active Transportation Lake, which "Whiteknuckled" complained about on TheWashCycle on Wednesday. I've noticed this one too in recent weeks, especially after it rains (like it did yesterday evening). Here's one of the culprits:

This is one of two drains (the other is hidden under the "lake") that have been clogged with dirt and debris ever since the storm. Because they're clogged, we get this "lake" forming every time it rains.
So last night, I sent out an E-mail about both the "lake" and the dirt/silt on the paths/sidewalks. I addressed it mainly to VDOT and the Wilson Bridge team, but also CCed several others, including the Fairfax County Supervisor for the district, the two State Delegates for the area...their district line goes right through the Route 1/Fort Hunt Rd intersection, and the State Senator for the area. Below is the E-mail I sent, verbatim:
I'm writing regarding the Active Transportation Lane (bike/ped path) along Route 1 in eastern Fairfax County, between Huntington Ave and the bridge over Hunting Creek on the south side of the 95/495 Beltway (constructed as part of the Wilson Bridge project).
Ever since the February snowstorms, the path/lane has been covered with piles of dirt and silt leftover from snow clearing operations. This dirt and silt has still not been swept up/removed. Also, at the south end of the Hunting Creek bridge, there are two deck drains that have been clogged with dirt/silt/debris, which in recent weeks has resulted in this section of the lane flooding over every time it rains, as can be seen in the attached photograph (taken after this evening's thunderstorms). I'm not sure if this is still under the Wilson Bridge contractor or if it's under VDOT maintenance now, but this situation is unsatisfactory and these dirt piles and drains should be cleared out as soon as possible.
Thank you for your time. If you have any questions for me, please E-mail me.
Before I even got to bed, I had an E-mail from Delegate Surovell, saying "This is ridiculous" and directing his legislative assistant to get an answer from VDOT. Early this morning, I got an E-mail from Bob Driscoll, manager for VDOT's Fairfax Maintenance district, stating he wasn't sure if his maintenance district was responsible for this section, but he'd direct it to the proper maintenance district if it isn't Fairfax.
So we'll see. Hopefully, it'll get to the right person, get to them soon, and we'll have cleared out drains and an "empty lake" before too long.
Subscribe to:
Posts (Atom)