Arbitrary and Capricious: City Only Applying Fire Clearance Rule to Bike Projects

Nearly 10 months ago, rumbling began over the proposed width of the car travel lane in the redesign of Potomac Street that included a protected bike lane. Neighbors cited a portion of the Baltimore City adopted International Fire Code, which states that Fire Apparatus Access Roads must maintain 20 feet of clear width, and that Aerial Fire Apparatus Access Roads must maintain 26 feet of clear width. 

Our existing street network analyzed for clear width. Purple streets would need parking removed on both sides of the street to be compliant. Red streets would need parking removed on one side of the street to be compliant.

Our existing street network analyzed for clear width. Purple streets would need parking removed on both sides of the street to be compliant. Red streets would need parking removed on one side of the street to be compliant.

We've written about that battle extensively. It received national attention. We filed suit against the city since we felt this fire code ruling was being applied in an arbitrary and capricious manner to one street. We were granted a temporary restraining order to halt removal of the bike lane while we negotiated a solution with the city that worked for all parties.

In those negotiations, we were told by the Mayor's Office and the Baltimore City Department of Transportation (DOT) that, at the time, Potomac Street was the only project under consideration for re-design or re-evaluation, and that a clear protocol for Baltimore City Fire Department review and approval of city street redesign would apply going forward. 

Weeks later, in a Mayor's Bicycle Advisory Commission meeting, we learned from now departed Bike Share Coordinator Jay Decker that all bicycle construction projects were on hold citywide pending review of the "entire bike plan."

Along with that news, we also knew of many ongoing resurfacing projects throughout the city that didn't involved bicycle projects, and that many of these projects failed to meet the Baltimore City adopted IFC clearance standards. So we decided to investigate.

On September 29, we requested a list of resurfacing and reconstruction projects occurring in Baltimore City. On October 11, DOT provided us with their Orange Code list for 2017, which details all resurfacing and reconstruction projects planned, ongoing, or completed for the year.

That very day, we evaluated all street resurfacing and reconstruction underway or planned for July 2017 or later, giving a few months of leeway after the Potomac Street issue was raised, and we were told, addressed.

Using GIS centerline data for city streets, we determined the streets highlighted above failed a 20 foot clearance if the street contained parking. In total, at the time of our evaluation:

  • 40 of 62 streets completed since July 2017 failed clearance.

  • 12 of 33 streets currently under construction failed clearance

  • 24 of 55 streets to be completed failed clearance.

On October 11, we immediately reported this information to the new Director of DOT, Michelle Pourciau. We requested an urgent meeting to discuss the inconsistency of moving forward with what appeared to be every resurfacing and reconstruction project in the city except for those with bike lanes.

We were not given a list of available meeting times until November 6, and the available times were at the end of November. Knowing this would allow all seasonal paving to be completed before our meeting occurred, we immediately filed a Public Information Act request with DOT and Baltimore City Fire Department. 

In lieu of a timely meeting with DOT, our goal with this request was to get clarity on the fire clearance policy that the Mayor's Office and Baltimore City Department of Transportation said was developed in response to the Potomac Street fight, and better understand why exceptions were granted and signed for resurfacing and reconstruction of some non-compliant streets but not others. Maryland state law requires receipt of disclosable records within 30 days.

Immediately after submission of the PIA request, we received an email granting us a meeting with Director Pourciau on November 16. At that meeting, we had not yet received the results of our Public Information Act request, and were told that the City Solicitor's office had advised against disclosing any information that may be a part of the official PIA request. Regardless, we learned the following:

  • All construction work had been stopped on the Downtown Bike Network, even on streets where the re-striping would not affect clear width.

  • No construction work had been stopped on resurfacing of streets without bicycle infrastructure. DOT claimed that "resurfacing of existing conditions" was not a part of the new fire clearance policy.

  • No construction work had been stopped on reconstruction of streets without bicycle infrastructure, even ones like Preston Gardens and Saint Paul Street, which are total reconstructions that provide a new clear width identical to Potomac Street, but are adjacent to skyscrapers instead of two story row homes.

We were told at this meeting that over the winter, DOT would evaluate these projects and their road width policies and fire clearance access rules. This seemed to imply that these things had not already been done, which was a departure from our discussion around Potomac Street. We asked why bike lanes couldn't also continue non-conforming construction like other projects, and were given no answer.

Today, we received the response to our PIA request, 60 days after the request and 30 days after the legal deadline for disclosure of records. The paving season is completed, the non-compliant projects we questioned were installed.

The response to our PIA request verifies what we suspected.

  • Since the Potomac Street debacle, DOT and Baltimore City Fire Department have created no tool to evaluate streets for compliance with Baltimore City adopted fire code.

  • No fire apparatus access road classification map exists.

  • No single list of project evaluations exists, and no promised written exemptions are available.

  • And, the only record of an evaluation of a street was a single bike lane striping.

Both Chief Niles Ford's affidavit and the City Solicitor's argument in our Potomac Street suit clearly state that a lack of 20 foot clearance is a life safety issue and severely hampers fire access operations. If this sworn testimony is true, the city is grossly negligent in not using resurfacing as an opportunity to improve clear width to fire code standards, particularly when we experienced a 5-year high in fatal fires in 2017. If we accept that the testimony was hyperbolic to prove a point, we must acknowledge that it was simply a vendetta against a bicycle lane. Neither of these possibilities is acceptable.

We are encouraged that DOT has committed to developing a standard for road clearance over the winter, and we hope it will result in uniform application of law.

And, since other existing major reconstruction projects have continued, we expect the Downtown Bicycle Network to be installed in the first week of the spring paving season without fire clearance based redesign. 

If this doesn't happen? Well, we're familiar with the terms arbitrary and capricious.
 

Support our #fightforbikes? Donate today!
 

North Avenue Rising: Take the Survey

In November, kick-off meetings were held for the North Avenue Rising project, a $27,330,000 project to improve transit stops, install bus lanes, and make targeted streetscape improvements to North Avenue. The project is a federally funded Transportation Investment Generating Economic Recovery grant, or TIGER grant. The project has additional financial support from MDOT MTA and Baltimore City. 

Our Ask

Take the project survey available here. 

In questions #6 and #10, please state that you would like to see dedicated, separated transit and bike lanes throughout the corridor, and that you would like to see a center-running transit option.

Background

We wrote a detailed post in July of 2016 about how to make this project better. It is available here. In short:

The red bus lane stops and starts throughout the corridor.

For dedicated transit lanes to be successful, they should be contiguous and ideally separated, or at minimum, curbside. The project as planned currently has parking-adjacent bus lanes, which stop and start throughout the corridor depending on traffic volume. This will result in conflict between buses and cars during every parallel parking attempt and abuse of the lanes by stopped cars and delivery vehicles. 

"Parallel" bike facilities, blocks away.

For bicycling to be comfortable for people of all ages on the North Avenue corridor, and for the planned bike share stations to be utilized safely and effectively, separated bike lanes must also be present on North Avenue, at least along the wider section where buses are most frequent. Presently, bikes are relegated to "parallel facilities," which are not parallel. Worse, there is no connection across the bridge, requiring bicyclists to dismount and walk or illegally ride on the sidewalk. 

These constraints mean we're going to spend millions of dollars on a project that still prioritizes moving and storing private cars over moving people via foot, bike, and transit. The end result will be a street with only moderately improved transit travel times, a street with no safe place to bike, and a street that will still be dangerous to cross as a pedestrian. 

According to NACTO's figures on person throughput, North Avenue today can move 6,000 people per hour. The TIGER grant as designed may improve this to 11,200 people per hour. Our fix can move 34,100 people per hour.

The Fix

The fix is easy, it just costs more money. Based on costs of other dedicated alignment bus corridors, an additional $20-30 million could elevate North Avenue from the flawed project outlined above to a truly transformative corridor.

Wider Section of North Ave

The wider section of North Avenue that has the highest bus volume could have a center-running, separated busway. This would allow for curbside protected bike lanes, parking, and a single travel lane for personal automobiles.

North Avenue wide segment at a bus stop, with center running transit way, protected bike lanes, and parking.

North Avenue wide segment at a bus stop, with center running transit way, protected bike lanes, and parking.

Narrower Sections of North Ave

If we removed on-street parking on one side of the street in the narrower sections, areas furthest east and west on North Avenue, we could continue the center-running, separated transit lane by making it bi-directional. Bus frequency is low enough along this segment that oncoming buses would rarely encounter each other, but if they did, they could merge into the regular car travel lane to pass each other.  This design is being used in Indianapolis with the IndyGo Red Line Bus Rapid Transit project, which has similar bus timing to these parts of North Avenue. 

North Avenue narrow segment, where buses share a bi-directional lane and pass each other in the regular travel lane. Parking is restricted on one side of the street to allow for the bus lane and protected bike lanes.

North Avenue narrow segment, where buses share a bi-directional lane and pass each other in the regular travel lane. Parking is restricted on one side of the street to allow for the bus lane and protected bike lanes.

North Avenue narrow segment at a bus stop. Parking is further restricted to make width for the bus stop and allow for protected bike lanes.

North Avenue narrow segment at a bus stop. Parking is further restricted to make width for the bus stop and allow for protected bike lanes.

While parking would need to be reduced on these edges of the corridor where the street is narrower, this is exactly where neighborhoods have zero-car household rates far above the city average, and where adjacent streets have very low on-street parking utilization. Many buildings also have alley garages and rear parking access. Removing parking would be a challenge, but it would be in line with focusing on the majority of road users in these segments, who lack access to a car and instead walk, bike, or take transit.

Perspective on Cost

$20-30 million is a fraction of the money Governor Hogan reallocated away from Baltimore and to rural highways with his cancelation of the Red Line. Baltimore City could also come up with this money over the several year project timeline. In just the few months since Councilman Dorsey passed legislation to increase the fine for parking in bus lanes and bus stops to $250, the city has already failed to collect nearly $500,000 because they haven't updated their ticketing software to the new amount. 

We can afford a project that gets this right the first time, and sets up a future on North Avenue that could easily be upgraded to real Bus Rapid Transit or Light Rail Transit. We can't afford to spend $27,330,000 on the existing project. North Avenue and the people of Baltimore deserve better than this. 
 

> Take the project survey available here.
 

24 hours, 24 Bikemore wins, 24 reasons to give.

While there's no doubt we've been faced with a lot of challenges this year, we try not to forget to celebrate our accomplishments big and small.

In the 24 hours of #GivingTuesday, we're sharing 24 Bikemore wins from this year. That's 24 reasons to give. What's your reason for giving?

Whether you want to be able to bike safely with your kids, want to improve access to jobs for those without cars, or want to feel safe walking to your neighborhood grocery store — donate to Bikemore today and tag us in an unselfie to let your friends know your reason for giving. 

Donate to Bikemore to create a safer, healthier, and more livable bicycling city!

We're grateful for your support that has helped us accomplish so much this far, and grateful for your continued support today!

And don't forget to follow along all day on FacebookTwitter, or Instagram!

 

What the heck is Cranksgiving?

Cranksgiving 2017 poster.jpg

Cranksgiving is on Saturday, November 18th, and it's one of our favorite days of the year! 
 

So, what the heck is Cranksgiving?

Cranksgiving is a national event that combines bike riding and giving back. It's a mix of a scavenger hunt, food drive, and bike ride. We'll give you a list of food items and grocery stores, and then you'll have a set amount of time to ride to as many of the stores to collect as many of the food items as you can. And all of the food goes to Moveable Feast. Basically, it's all about food for people in need and riding bikes with friends, new and old.

What does the day look like?

12:30pm | Registration at Peabody Heights Brewery
1:45pm | Pre-ride rules and kick-off
2:00pm | Biking food scavenger hunt throughout Baltimore
4:00pm | Receipts and food due at Peabody Heights Brewery
4:00pm - 6:00pm | Awards and after party at Peabody Heights Brewery

Do I need to register beforehand?

No, just show up! Registration is from 12:30-1:45pm. It's helpful if you RSVP on Facebook, but there's no formal registration beforehand.  

Do I need a team?

Because riding with friends is more fun, all riders participate in teams of 3 or 4. If you don't have a team beforehand, we'll help "free agents" find folks to ride with during registration, or you can post in the Facebook event and get one going beforehand. 

How does the ride/scavenger hunt work?

When you register, teams will be handed their manifests. On the manifest is a list of grocery stores and food items to purchase, each worth a certain number of points. The way to get the most points is to hit all the grocery stores and purchase all the unique foods. The ride begins at 2pm and only teams who check in at Peabody Heights by 4pm will be considered for prizes. Then stick around for the after party, where we'll announce the winners and prizes, and for beer, food and celebration!

How do we win? What are the prize categories?

The winners are 1st, 2nd, and 3rd (the teams that have the most points, if there's a tie, the team that checks in first win) and — our favorite category — BEST COSTUME/TEAM SPIRIT! 

How much does it cost to participate?

By design, Cranksgiving is and always will be a free event — meaning Bikemore will never charge registration to participate. We ask that each person on a team bring $10-15 to help purchase food items on the list. But how much you are able to spend is entirely up to you! 

What should I bring?

- Working bike
- Bag to carry purchases (backpacks, panniers, baskets — whatever you have!) 
- $10-15 for purchasing food to donate
- Water bottle
- Flat kit (Bikemore doesn't provide any ride support)
- (Optional) Smartphone to take photos and upload to social media for additional points! 

Is it a race? I don't ride very fast. Will I still have fun? 

Kinda. That's Ok! Absolutely! Cranksgiving is designed to be a team event (because what's more fun that riding through the city with some friends?!) While prizes are awarded to teams with the highest number of points, you can also win Best Costume & Team Spirit!

CAn I bring my kids?

Yes, we have had family teams in the past! The ride is set up so you pick your own route and pick which stores to go to depending on your own judgement and comfort level. And our Team Spirit/Best Costume prize category is a great one for younger riders! And either way, it's a great way to have fun riding together and give back.

What happens if it rains?

Unless it's a serious safety hazard, this is a rain or shine event. Riding in the rain/cold/wind makes you tough, so show up and ride! Plus, people in need still need food when it's raining.

>> Check the Facebook event for all updates, and to invite your friends!

Tonight, speak up about North Ave Rising!

Tonight is the first meeting about North Avenue Rising. We hope you'll make it out, even if you can't make it until after work!

Here are the main points we'd like you to make:

  1. North Avenue Rising must have separated, dedicated transit lanes throughout the entire project corridor.

  2. North Avenue Rising must have separated, dedicated bicycle lanes at minimum between Pennsylvania Avenue and Broadway, where there is high density, frequent bus service, and a wider right-of-way.

  3. North Avenue Rising must have a road diet, calming the street and allowing space for high quality bike and transit lanes while maintaining parking for businesses.

  4. These requirements should lead to North Avenue Rising including center-running transit, which will further spur economic development and transit growth on North Avenue, and allow for a potential rail transit future for North Avenue once that growth demands it.

There are community meetings Monday through Thursday this week for you to attend. We're encouraging folks to #filltheroom at Monday night's meeting, but we encourage you to attend whichever meeting you're able to.

Monday, November 13, 2017
4:00 PM - 5:30 PM
Impact Hub
10 East North Avenue

Tuesday, November 14, 2017
6:00 PM - 8:00 PM
Bluford/KASA at Walbrook
2000 Edgewood Street

Wednesday, November 15, 2017
6:00 PM - 8:00 PM
Rita R. Church Community Center
2101 Saint Lo Drive

Thursday, November 16, 2017
6:00 PM - 8:00 PM
Parkview Recreation Center
2610 Francis Street

>> Want to know more about North Ave Rising? More about the project and our take.