9th Street Separated Bikeway at SacATC

At last night’s Sacramento Active Transportation Commission (SacATC) meeting, the 9th Street Separated Bikeway was item 3 on the agenda. As is usual, I did not have a chance to review the item until shortly before the meeting, so did not post comments ahead of time, but did make comments during the meeting. I’ve broken the agenda item into staff report, plans, and presentation slides for easier access.

This was the preliminary presentation on this project, and it will be revised and come back to the commission at least once more.


My comments text, thought some particulars were left out due to the two-minute time limit:

I am glad to see the project, since it closes one of the gaps that makes the existing separated bikeways less useful.

Widths

The six-foot bikeway width does not meet NACTO recommendations (preferred width) of 8 feet or more for separated bikeways. Six feet does not allow for passing or wider bicycles, and is NOT a best practice.

NACTO table of Unidirectional Protected Bike Lane Widths

I support bin/leaf zones, but the entire buffer should be wide enough to accommodate bins, as has been implemented on some blocks of P and Q streets. I am not sure how wide this is, but it is more than 3 feet.

In order to gain the necessary width for bicycles and buffers, the street right-of-way needs to be reallocated:

  • One of the two general purpose lanes should be 9 feet (the left lane), the other 10.5 feet (the right lane), which gains 2.5 feet. The wider lane would be used by buses on SacRT Route 51. The wider lane should be marked as such, with the width painted on the pavement at every intersection to inform drivers.
  • Similarly, one of the two parking lanes should be 7.5 feet, which gains 0.5 feet, and signed or marked as a narrower parking lane. The city does not need to accommodate car bloat on every street and every parking lane.

Bikeway Protection

I support turn wedges, but they should be concrete, not solely paint and posts. Though the paint and post turn wedges provide some safety for bicyclists, and particularly for walkers, they are less safe than concrete, which the city calls ‘rolled curb turn wedge’.

SacCity photo of a rolled curb turn wedge
SacCity photo of a rolled curb turn wedge

Any block with only an alley break in the separated bikeway should be protected by concrete curbs, not simply by paint and posts. Where driveways occur, it may be better to use paint and posts.

Marking

Whenever a bikeway crosses general purpose lanes, as it does approaching Broadway, the merge zone must be marked with green backed sharrows. Anything less is unsafe for bicyclists.

Any place where a bikeway transitions from one side to the other side is designed, there must be a bike signal to control motor vehicle traffic. In general, bicyclists need an exclusive bike phase, where no motor vehicles are turning. The side-to-side transitions on 19th Street (from left to right, just past W Street), and 21st Street (from right to left at W Street) are NOT safe for bicyclists, and as a result, there are many fewer bicyclists using these streets than was intended or is desirable. The city has resisted using bike signal faces, though the expense is a fraction of what the city routinely spends replacing functional signals and signal boxes.

Any time a bikeway is between two general purpose lanes, as it is approaching Broadway, the bikeway must be marked with continuous green paint. Somehow the plans dropped green paint between W Street and Broadway, the most confusing and potentially deadly part of the entire project.


Commissioners made a few comments:

  • Generally supportive of the project intent
  • Moore commented on green paint approaching Broadway, and asked if the transition could be earlier to reduce conflicts at the W intersection; staff response it that right-turning vehicles at W Street are the biggest conflict, other than X Street and Broadway
  • Hodel supported the red paint daylighting, and asked for green paint approaching Broadway

Apparently there were a large number of eComments on the agenda items, though I’m unsure how many related to this agenda item or the other three main items. When the meeting is over, all the eComments disappear, apparently into the ether. This is not just a problem for SacATC, but for all city meetings. Unless a citizen takes care to capture the eComments before the meeting ends, they will never know what others commented online.

The NACTO Urban Bicycle Design Guide (3rd edition, 2024) includes the diagram below within the ‘Designing Protected Bike Lanes‘ section.

diagram of NACTO One-Way Protected Bike Lanes Design Guidance
NACTO One-Way Protected Bike Lanes Design Guidance

disconnected bike network

A recent article on CapRadio: Sacramento’s bike network received a failing grade. City officials disagree was also reference on Streetsblog California.

The People for Bikes analysis on Sacramento is at https://cityratings.peopleforbikes.org/cities/sacramento-ca. Note that only cities are rated, not counties, so there is no rating for unincorporated Sacramento County. Sacramento’s score was 36, Rancho Cordova’s 29, Folsom 37, Elk Grove 23, West Sacramento 25, and Citrus Heights not scored.

The lead photo on CapRadio is a concrete-separated bikeway on Broadway. But it is only one block long, and is the only one in the city.

A quote from Jennifer Donlon Wyant is revealing of exactly the problem with Sacramento bike facilities:

“M Street from Sac State to Midtown through East Sacramento is known to be an all-ages and abilities bikeway connecting schools and health care and retail, and that is shown as a high-stress facility,” she noted. “When known low-stress facilities like this are showing up as high stress, that concerns me.” 

Yes, parts of M Street are great, and should be recognized with a neighborhood or greenway status. Though it is an overly wide street along much of its length, traffic is slow and light, and it meets the definition of a low-stress bikeway.

However, what happens at either end? Approaching Alhambra, M Street ends, with no bike lanes on Alhambra, and no wayfinding for how to shift to a low-stress route to continue westward. At the east end is Elvas Avenue, one of the most hazardous bike routes in the city. Bicyclists exiting onto Elvas Avenue from 62nd Street must cross four lanes of high-speed, high volume motor vehicle traffic to reach the safety of the Hornet Tunnel and SacState. Most bicyclists cross early and ride against traffic. It is slightly less hazardous to go westbound to M Street. There is no wayfinding for how to best deal with this situation.

The city has been aware of the Elvas problem for years. Nothing has been done. This blog has written about it many times: tag:Elvas-Ave.

All of the parking-protected, separated bikeways in the city are discontinuous:

  • 10th Street northbound: starts at W Street with an awkward transition from east side to west side; ends at I Street
  • 9th Street southbound: starts at I Street; ends at Q Street; design is very inconsistent with bike lane-only blocks
  • P Street westbound: starts at 21st Street; ends of 9th Street
  • Q Street eastbound: starts at 9th Street; ends at 21st Street
  • J Street eastbound: starts at 19th Street; ends at 28th Street
  • 19th Street southbound: starts at H Street; ends at W Street with an awkward transition from east side to west side; at Broadway the route transitions to Freeport Blvd with no bike facilities
  • 21st Street northbound: starts at W Street with an awkward transition from east side bike lane to west side separated bikeway; ends at H Street with a semi-protected bike signal

For few of these routes do the separated bikeways take you to a final destination. There are transitions to regular bike lanes, or no bike lanes at all, at the ends of each segment. That is not a connected network. It is disconnected!

Almost every advocate in the city is supportive of Jennifer Donlon Wyant and all she has accomplished to make the city more bikeable, more walkable, more livable. However, the city policy, by staff at a higher level, and city council, to spend almost none of its general fund on transportation safety, and to rely only on state and federal grants. means that the city will continue to rank low on any assessment of bicycle friendly.

Sacramento needs a connected network, and we are far from that.

Google map of Elvas Ave from 62nd St to Hornet Tunnel
Google map of Elvas Ave from 62nd St to Hornet Tunnel

Bike Advocacy Workshop

I attended a Bike Advocacy Workshop hosted by the League of American Bicyclists in late March in Santa Monica. This was the third time the League had hosted the workshop, so it is evolving. It is intended to provide professional development for advocates in a similar way to that League Cycling Instructor (LCI) seminar. Though many LCIs and LCI Coaches have been requesting for many years that the League either add advocacy information to the LCI seminar, or create a separate track, apparently this was developed on the initiative of a League staff member, not on those requests.

I took this workshop, not because I necessarily think I need training in advocacy, or need the certification, but curiosity about the League’s approach to advocacy. Most League activities are at the national level, not at the state or local level, with that role taken on by other bicycle advocacy organizations. Santa Monica Spokes, the local advocacy organization, co-lead the workshop.

The workshop was a combination of presentations by advocates, field trips to look at bike facilities in Santa Monica, or which there are many, some role-playing exercises, and of course evenings outings for beer and pizza. Many of the participants work for bicycle advocacy organizations, mostly local in southern California, but with others not directly affiliated and from other regions.

The workshop was good. It would benefit from more role-playing and discussion to address the objections to bicycle facilities that often crop up, not just from an infrastructure perspective but from a livability perspective.

Santa Monica does have a lot of bicycle facilities, focusing now on physically separated bikeways on arterials and collector streets. There is a multi-use paths associated with the E/Expo light rail line. In a few places there are bicycle-only connections between streets. Some of the separated bikeways feel squeezed in, installed on relatively narrow streets without removing parking. It is better, in my view, to either remove parking from one side to create enough space for a comfortable bikeway, or just do a regular bike lane. The new NACTO Urban Bikeway Design Guide makes clear the importance of wider separated bikeways to accommodate all types of bikes, and to allow safe and comfortable passing of wider bikes such as cargo bikes and three-wheeled bikes.

A few times during the workshop the ghost of John Forrester, Effective Cycling, and vehicular cycling was trotted out to beat the dead horse. This horse has been beat for so long by so many that it is not recognizable as a horse. Advocates of bicycle infrastructure keep bringing this up, though I know of no advocates who advocate against infrastructure, though there are still, and should be, voices for the right to use the roadway.

photo of Bike Advocacy Workshop role-playing exercise
Bike Advocacy Workshop role-playing exercise
photo of Bike Advocacy Workshop field trip on multi-use path
Bike Advocacy Workshop field trip on multi-use path

Caltrans D3 says ‘fuck you’ to Yolo bicyclists

The bike path along I-80 along the Yolo causeway is closed this afternoon (Tuesday, 2:00 PM). The sign at the east entry to the bike paths says:

Bike Path Closed sign on east entry to Yolo causeway bike path
Bike Path Closed sign on east entry to Yolo causeway bike path

Note that this sign indicates that the path will not be closed until 8 PM on Tuesday, March 18.

This is what the Caltrans website says (UPDATE: Extended 79-hour Closure for Eastbound U.S. Highway 50 in Yolo County Postponed due to Weather Forecast, 2025-03-13, retrieved 2025-03-18 3:00 PM):

screen capture from Caltrans D3 website
screen capture from Caltrans D3 website

Note that this press release says that the path will be open again by 6:00 AM on Tuesday, March 18.

And this is the reality is:

construction on Yolo causeway bike path
construction on Yolo causeway bike path

Construction is completely blocking the path, at this location and several others. The work to remove the concrete barrier from the freeway is ongoing along the western section of the causeway. Some parts of the freeway are also torn up, awaiting reconstruction.

I talked to the supervisor at this construction location, and he said they are just a subcontractor, not responsible for Caltrans signing, or lack thereof. He called the general contractor, who apparently said it is my problem, not theirs. After exiting at the I-80 off-ramp (the normal entry to the path north to Yolo County 32A is not accessible), I saw a CHP officer, and reported the issue to him. He said he would pass it along. He probably will, but I doubt that either CHP nor Caltrans will do anything about it.

This is an active construction project which was not properly signed for construction. This is a violation of Caltrans procedure, and state law, and federal law.

It is absolutely typical of Caltrans District 3 (which includes Yolo and Sacramento counties) to not care about the travel or safety of bicyclists. What would it take to correct the signing, and to correct the website? Not much, but it is beyond the care and interest of Caltrans D3.

Caltrans has said that as a result of the Yolo 80 project, there would be an improved bike path. I’ve previously written about why that is very likely to be a lie: Yolo causeway bike path. Note that though Caltrans claims the current construction is just bridge rehabilitation and has nothing to do with the Yolo 80 project, that is a lie. It is safe to assume that everything Caltrans D3 says is a lie. Caltrans is a highway department, not a transportation department. They care about motor vehicles. They do not care about walkers or bicyclists or air quality or the state budget. In fact, given the high fatality rate on both under-construction and completed highway projects, they don’t really care about motor vehicle drivers either.

I will also note that the California Transportation Commission (CTC) is complicit in Caltrans D3 malfeasance, as they continue to fund projects no matter what the behavior or violation of the law. And above CTC, California State Transportation Agency, which is intended to oversee both CTC and Caltrans, but does not.

CalBike’s Agenda for 2025

A number of organizations have come out with agenda’s for next year, and I’ll cover a few of those in several posts. First, CalBike. I participated in CalBike’s agenda reveal on December 3, and it was disappointing. Mostly videos of talking heads about the past, not much about the future. The breakout I participated in was dominated by a single person who wanted to talk about specific locations and wouldn’t let anyone get a word in edgewise about policy. But CalBike now has a page dedicated to CalBike’s Agenda for 2025, which is clearly presented. CalBike has organized support statewide for progressive legislation which encourages bicycling and makes it safer, and has supported legislation for walkers as well. There isn’t an active statewide organization for walking, unfortunately.

The agenda lists:

  • bicycle highways
  • shared streets
  • quick-build pilot
  • bike omnibus #2
  • bicycle safety stop
  • new bike boulevard classification
  • e-bike policy

Though e-bikes modified to be (illegal) motorcycles is not a big problem in Sacramento area, yet, it is in other places. San Francisco, where I am right now, is full of deliveristas on bikes that have pedals and chains, but top out about 40 mph. In the Lake Tahoe region, it is rich high school students. I’d like to see legislation to clearly define what is and is not an e-bike, and make sure high speed devices are banned from bike lanes and bike facilities. It is already illegal (AB 1774 Dixon, 2024) to modify an e-bike for higher speeds, or to sell devices which bypass design speed, but of course enforcement is uncertain.

The bicycle safety stop should be a no-brainer, except of course that Newsom and CHP probably don’t have brains. Treating stop signs as yield signs, slowing and yielding when necessary, is what almost all bicyclists already do, and there is nothing unsafe about it. Research has indicated that the rate of full and complete stops at stop signs is nearly the same for bicyclists and drivers, but when bicyclists stop, then are in danger of getting hit from behind by drivers not stopping, and the energy to get started again is significant, not just a press of the gas pedal.

Shared street standards are a good idea. Many locations have implemented shared streets, with different designs. As a new idea to be experimented with, wide variation was OK, but enough is known about designs now to create a standard. Some cities have continually lessened the protection and messaging on shared streets (or removed them completely, in the case of Sacramento), and standards would help prevent this erosion. I think shared streets should be more common that ‘regular’ streets. Shared streets are where people live, regular streets are where people drive.

I’m not sure whether state-recognized quick-build designs would help much. Cities are already doing these projects, and the best thing Caltrans could do is get out of the way.

photo of Sacramento 26th St slow & active street, since terminated
Sacramento 26th St slow & active street, since terminated

Elvas Ave and Hornet Tunnel update

Re-upping the Elvas Ave and Hornet Tunnel post from earlier this year. It has been reported to me by a number of bicyclists, and I have experienced it myself, that this section of Elvas between the Hornet Tunnel and the signal at 62nd Street has become significantly more hazardous due to the motor vehicle traffic generated by The Line (a collection of various food vendors, opened 2022) and Garden at the Line (an outdoor eating and drinking area adjacent to The Line, opened this December). There is a lot more come and go parking on Elvas, and a lot more motor vehicle traffic in and out of the parking lots. Most bicyclists ride on the sidewalk to avoid the fast-moving traffic, otherwise the crash rate would be higher. The M Street to Elvas Avenue to Hornet Tunnel route is probably the busiest in the city.

In addition to the previous post (reblog below) about the hazards for bicyclists, this area is now hazardous for walkers along and crossing Elvas.

I was there last night for the SABA social gathering, and the place was packed. People were parking along the west side of Elvas as well as on 63rd Avenue and 64th Avenue, and then trying to cross Elvas to Garden at the Line. It was nearly impossible to cross, as there are no marked crosswalks over Elvas at either street, drivers are going fast, and Elvas is not well lit. The speed limit in this section is 40 mph, which almost guarantees that walkers hit by cars will die. Sidewalks on both sides of Elvas are in poor condition, and rolled curbs are common, which are less safe for people walking than vertical curbs. There are no sidewalk buffers. While this section of Elvas is not one of the top 5 or top 10 Vision Zero corridors, it will quickly become so. In the last five years, there have been two injury crashes on this stretch, one bicyclist and one walker, both in the vicinity of Hornet Tunnel.

The city has no plans to improve safety for bicyclists or walkers on this stretch of Elvas.

SacCity is not sweeping separated bikeways

The City of Sacramento is not sweeping its separated bikeways, as it promised to do when it installed them. The separated bikeways, on I St, P St, Q St, 9th St, 10th St, 19th St, and 21st St have not been swept by the city. The city has a sweeper designed specifically for these bikeways. It may be broken down, or the city may be choosing not to sweep. Some of the bikeways are being swept by landscape maintenance services associated with adjacent properties, a few spots are being swept by individual owners or residents, and even the parks department is cleaning up, but not consistently.

photo of Q St at 14th St, separated bikeway, not swept by city
Q St at 14th St, separated bikeway, not swept by city

In a few places that have heavier bicycle and scooter traffic, such as P St between 15th and 14th, the leaves have turned into leaf slime, which is extremely hazardous for anyone on two wheels. I’ve seen people almost spin out here, and I have as well.

Most people seem to have realized that the place for piled leaves is NOT in the bikeway, but in the adjacent buffer, and in some locations that buffer is labeled as such. But some people are still piling in the bikeway.

Regular bike lanes are an issue as well. Most are not swept. Dry leaves are sometimes swept away be motor vehicle traffic, but once they are wet, they don’t move. If there is motor vehicle traffic across or along the bike lane, such as approaching an intersection, the leaves are quickly turned into slime. Very slippery! Be cautious anywhere there are leaves.

Palm trees – ack!

And just in case you need to be reminded, palm trees and the fronds they drop are an ongoing hazard to people walking and bicycling. A single frond can block a sidewalk from use by anyone with a mobility device. A single frond can block a bikeway or bike lane, and can throw a bike rider off their bike. With every wind storm or heavy rain storm, palm trees drop huge numbers of fronds. Why do we continue to allow this hazard for walkers and bicyclists? In a few locations where they have historic value, such as Capitol Park, they might be justifiable. But nowhere else. They need to be removed!

photo of palm fronds on Q St
palm fronds on Q St

Yolo causeway bike path

Caltrans and Yolo County Transportation District are proposing to widen a section of Interstate 80 from Sacramento to the Yolo/Solano county line, a project called Yolo 80. This is not just a future project, subject to funding shortfalls and lawsuits, but is actually underway, as Caltrans illegally spends funds for highway maintenance on highway widening. I have written a number of posts on Yolo 80 and managed lanes, but today is just about the bike path that parallels Interstate 80 from the west edge of West Sacramento to Davis.

I am not a commuter or regular rider on the causeway path, but I do average riding it about once a week (I like concerts and beer and Mishka’s tea), and have been doing so for about 13 years.

Caltrans, in the Final Environmental Impact Statement (FEIR), Chapter 2, proposes a number of mitigation measures or policies, including the rehabilitation of the existing bike path, and extension of the bike path to county road 105, where a bicyclist can either use an existing though poorly maintained bike path along the freeway, or surface streets into Davis. In selling the project to the public, Caltrans and Yolo TD have promoted the mode shift potential of an improved and extended bike path, and in fact it seems a major part of the project.

However, this and all other mitigation measures are dependent upon excess tolling revenue, income above that necessary to maintain the section of freeway. It is not at all clear that there will be any excess funds, and Caltrans has made no promises that any mitigation measures will be implemented if there is no excess. Freeway maintenance is expensive!

To take Caltrans at their word, that they really want to do the bike path improvements and extension (if you take Caltrans District 3 at their word, you haven’t been reading this blog), it is instructive to look as the existing path and route.

First, the part along county road 32A, from where the path joins the road, to county road 105, where 32A crosses to the north of the railroad tracks, and the path along the freeway to Olive Drive begins. After a patch of gravel on the shoulder that gets worse over time, the bike ‘route’ is on the shoulder of road 32A, with a posted 55 mph speed limit (which means, in a practical sense, 65-75 mph). There is frequently trash on the shoulder, which is the responsibility of the county, but I have never seen trash picked up or the shoulder swept. This is not horrible for experienced bicyclists, I have ridden it a number of times, but replacing the shoulder with with an actual Class 1 bikeway would be an immense improvement. However, if the path is between 32A and the freeway, the noise and auto pollution will still be horrible. Could it be on the other side of the railroad tracks? Perhaps, but having the path pass under the railroad tracks to the north side would raise the issue of blocked access during flooding episodes, which are not uncommon in the Yolo Bypass (that is why it exists).

The second mitigation is rehabilitation of the existing bike path along Yolo causeway. I think it is useful to see how Caltrans is taking care of the existing path to see how they might rehabilitate it, and take care of it in the future. Preview: They don’t give a shit.

Trash coming off vehicles accumulates on the path. I don’t know how often it is cleaned, but I can tell you it is not often. Maybe twice a year. A lot of the trash eventually gets blown off into the Yolo bypass rather than getting picked up. This Wednesday, there were large accumulations of leaves shed from the trees along the path.

The path itself has not been maintained in the 13 years I’ve been riding on it. There are cracks that have been there so long tree sprouts are coming up in them. The asphalt parts of the path, where the path is on fill rather than bridge, are becoming unrideable. Many of these cracks are parallel linear, presenting the danger of wheel capture and falls for narrow-tired bikes.

When it rains, the path has large and persistent puddles. It was not well designed to drain. Note that the photo below was two days after the rain, and there is still standing water.

The path has been narrowed in several places for construction of the widened section of the freeway. This makes everything worse, removing the width that allows bicyclists to navigate around hazards.

There is a fence along the concrete barrier between the freeway and the path. This fence is not only intended to keep people from crossing (though it does have gaps from time to time, presumably to allow people from disabled motor vehicles to exit the freeway), it protects bicyclists on the path from flying debris from cars. Not only the trash they lose, but actual car parts. You can find a variety of car parts along the path, and I’m sure far more is prevented from getting onto the path by the fence. Cars lose a lot of parts! But construction has removed the fencing along a number of sections. In some cases there is wood fencing on top of the K-rail temporary barriers, but it is flimsy and only half the height of the fencing. And in several locations, there is no fencing at all, it has simply been removed. For no reason, so far as I can see.

At the western end of the causeway section, where the path turns north to connect to road 32A, there should be a permanent barrier to make sure that bicyclists don’t continue onto the freeway. But the barrier, created with leftover materials, is frequently damaged, probably by construction crews, and has several times been missing completely. Imagine riding here at night!

What Does It Mean?

It means that Caltrans cannot be trusted to construct, rehabilitate, or maintain a bike path along the route of Interstate 80 through the Yolo Causeway and into Davis. They are lying that they have, they are lying that they will. Do not, under any circumstances, trust Caltrans District 3 to serve or protect bicyclists. This is criminal neglect by Caltrans.

more on Broadway-Land Park bike signal

I have written before about the problematic bike signal for Broadway eastbound at Land Park Drive (dangerous bike signal on Broadway, Broadway bicyclist press the button). Now some more detail, from a full hour of observation on the signal and driver behavior.

I had hoped to observe bicyclists reacting to the signal, but unfortunately there were no bicyclists. Despite the city devoting much of the street right-of-way to bike lanes (not protected, on only sometimes buffered), it appears that no one is riding their bicycle on Broadway. I’m not surprised. Broadway continue to be an unpleasant place for bicyclists and walkers, and regular bike lanes are unlikely to change that.

The last post I had noted that there was a required beg button for bicyclists to trigger the bike signal, but had failed to look up and notice that there was a complete set of regular signal, bike signal, and blank-out no-right-turn sign on the same post. It looks like:

photo of Broadway eastbound at Land Park Dr, signal, bike signal, blank-out no right turn
Broadway eastbound at Land Park Dr, signal, bike signal, blank-out no right turn

For those unfamiliar with the blank-out signs, which are relatively uncommon in the city, it illuminates when turns are prohibited, and is blank when not prohibited. See photo below for the blank-out phase.

This signal array is definitely mis-communicating to drivers. When the bicycle signal is on, the no-right-turn sign should be on, and the regular signal red. This is mounted close to the right hand turn lane, and drivers see it as applying to that lane.

Most of the time, it is necessary to press the pedestrian beg button to trigger the bike signal. But then sometimes it is triggered without any press, and not due to the presence of bicyclists, as there were no bicyclists. Most signal cycles the bike signal remains red.

When the bike signal is on, there is a period of time when the no-right-turn sign is not on (blanked out), as below.

photo of Broadway eastbound at Land Park Dr, signal, bike signal, blanked-out no-right-turn
Broadway eastbound at Land Park Dr, signal, bike signal, blanked-out no-right-turn

Do drivers follow the no-right-turn sign? In an hour of observation, I did not see one driver follow the sign. Every driver turned across the no-right-turn sign and across the green bike signal. Every. Though I did not observe it at this time, I have experienced drivers yelling at me, and other bicyclists have reported being yelled at, by drivers who think they have the right of way and wonder why bicyclists are proceeding and interfering with cars. The photo below shows just one of about 70 drivers who turned against the no-right-turn sign.

photo of Broadway eastbound at Land Park Dr, driver turning against no-right-turn sign
Broadway eastbound at Land Park Dr, driver turning against no-right-turn sign

Solutions

  1. The regular signal should remain red while the bike signal is green. The placement of this signal is interpreted by drivers as applying to the right hand turn lane, so it must be red.
  2. The bike signal must have an exclusive phase where all other vehicle movements are prohibited. A properly designed intersection with a properly designed signal system probably would not need an exclusive phase, but this is NOT a properly designed intersection and NOT a properly designed signal system.
  3. The pedestrian beg button should be removed from the bike lane, and automatic detection of bicyclists installed. The city knows how to do this, and has done it at a few other intersections, but chose not to here.

Bicyclists will be fatally or severely injured here, and the cause of the crash will be mis-designed roadways, for which city engineers are directly responsible. Drivers are just responding to a mis-designed roadway, the guilty party is the traffic engineers.

The design document for Broadway Complete Streets, and as built, has a through lane, a dedicated left hand turn lane, and a dedicated right hand turn lane. This right hand turn lane is the source of the conflict, the source of the danger. The roadway as built prioritizes motor vehicle throughput over safety.

a trip to San Rafael

Dan Allison, author of this blog, took a trip to San Rafael, California, in north bay Marin County, on Monday of Week Without Driving. To be transparent, I have been car-free for over 13 years, and car-light for about 7 years before that, so a trip on bicycle and public transportation is just the way I live life, not an exploration of the challenge that people who can’t drive face. My income is lower middle income, so I have enough money to travel, at least locally. I went to San Rafael to retrieve my phone charger and battery pack that I’d left on a Marin Transit bus last Wednesday. It took three days for Marin Transit to find the item and get it to lost and found. It was entertaining, and sad, to watch the included AirTag travel around on multiple bus routes. AirTags are bluetooth, so only report when they are close to a modern iPhone, but they do keep showing up in new locations.

So, the Monday trip:

  • bicycle from home to Sacramento Valley Station
  • Capitol Corridor train from Sacramento Valley Station to Richmond Station, $22.95
  • BART from Richmond to El Cerrito del Norte, $0.85
  • Golden Gate Transit bus 580 from El Cerrito del Norte to San Rafael Transit Center, $3.50
  • bicycle to a local coffee shop, where I worked on Week Without Driving communication
  • bicycle to Sprouts Farmers Market for lunch supplies
  • bicycle to Larkspur Ferry
  • Golden Gate Larkspur Ferry to San Francisco, $7
  • bicycle to San Francisco Bay Ferry gate G1
  • San Francisco Bay Ferry to Oakland Ferry, $2.30
  • bicycle to Oakland Jack London Station
  • Capitol Corridor from Oakland to Sacramento, $24.65
  • bicycle from Sacramento Valley Station to home

All of the public transportation was using my senior Clipper Card, on my watch. Capitol Corridor train travel was pre-purchased tickets through the app. The total was $61.25, which is rather expensive for a none day trip, but is quite a bit less than I would have spent driving. At about 83 miles there, and about 105 miles back, using the IRS rate of $0.67 per mile, driving would have cost $126. Plus $17.25 for Golden Gate Bridge and Carquinez Bridge tolls. Most people think only about gas costs, or charging costs, and forget about depreciation, insurance, maintenance, parking, and tolls.

Travel time is hard to compare, since I made so many stops along the way, and did not travel by the most direct route. Looking at the simpler Sacramento to San Rafael trip, driving would be 1 hour 20 minutes, whereas I spent about 2 hours 20 minutes on public transportation.

This is a trip that I’ve taken many times, so there was very little planning involved, and in fact I changed my plans for the leg back home several times on the fly, without problems. Less familiar trips would take more planning.

A few photos from my trip are below, but many parts are missing. I’m not used to documenting my public transportation travels, and even less for selfies.