Sidewalks are part of the transportation network, and should be repaired as such

California Streets and Highways Code (SHC) Division 7, Part 3, Chapter 22, Article 2: Repairs, states that the responsibility for repairing sidewalks lies with the adjacent property owner. This is, on its face, unconstitutional, regardless of state code. The state is saying that a government agency can require a property owner to maintain property that belongs to the government, without any compensation. It has long been hoped that a public interest entity would sue the state to declare this code unconstitutional, but so far that has not happened. The ability of the public to sue is overmatched by the power of the cities and counties to fight any such lawsuit. Therefore, it is imperative that the legislature remove this unconstitutional requirement from state law.

It is worth noting that this code dates from 1941. Society’s view of the responsibility of governments to its citizens, what characterizes a livable and walkable place, and equitable transportation systems, have evolved considerably since that time. State law, on the topic of sidewalks, has not.

Code defines sidewalk (paragraph 5600): “As used in this chapter “sidewalk” includes a park or parking strip maintained in the area between the property line and the street line and also includes curbing, bulkheads, retaining walls or other works for the protection of any sidewalk or of any such park or parking strip.” The lack of a definition for ‘parking strip’ is concerning. Is it the buffer area, or does it include parking areas on the roadway? Does the use of this term allow people to park motor vehicles in the buffer? The code is vague.

It is not clear that state code should require, or not require, adjacent property owners to maintain the ‘park or parking strip’, most commonly called sidewalk buffers. These buffers are not part of the transportation network, but they are a key part of enhancing walkability and overall livability through provision of shade trees.

Note that this does not address the day-to-day maintenance of sidewalks in the sense of removal of leaf fall and snow. However, neither does existing code. This is left to policy of the individual city or county, as it probably should be.

The replacement language would be very simple. Chapter 22 would read:

“Sidewalks and curbs are an integral part of the transportation network, and will be maintained for the benefit of all citizens using all modes of transportation, in a state of good repair, under the same requirements that apply to adjacent roadways.”

It is worth noting that the most poorly repaired sidewalks are often adjacent to government-owned property. Governments seem to view this code as applying to private property owners, and not to themselves.

Nothing in state law precludes a local government, city or county, from taking on responsibility for repairing sidewalks. They generally have not done so, because by shifting the responsibility for maintaining part of the transportation network onto private citizens, they can spend more money on infrastructure for motor vehicles. That is the real reason for this state law, and its continuance into modern times.

it’s not just transportation infrastructure

It has been increasingly common to refrain from blaming traffic violence on drivers, and instead to point to transportation infrastructure which encourages drivers to speed and to act in such a way as to create crashes. There is truth in this, and equity to some degree. But I think the pendulum has swung too far in that direction, and it is time to bring back driver responsibility.

We have invested trillions of dollars to create a transportation system that kills and mains countless people, with an emphasis on harming people who walk and bicycle. This was not an ‘accident’. Traffic engineers knew that their roadway designs would kill people, but absolved themselves of responsibility by pointing to the ‘standards’, which promote these designs, but are based on nothing but speculation and bias. It is always easier to blame crashes on driver behavior than to design safe roadways. Well, here we are. It will cost trillions to fix. We don’t have that money. That is not to say we should not be fixing what we can, with a priority on those designs and locations that have killed the most people, or seem most likely to.

But there are two very, very common driver behaviors which are not really an infrastructure problem. Red light running, and failure to yield to walkers in the crosswalk, both of which I’ve written about before. See ‘how to stop red light running‘ and the list of other posts there, and ‘Yield to walkers? Nah.‘.

Could we move signals to upstream instead of downstream of intersections? Yes, but that is very unlikely in a transportation profession that values tradition over observation and innovation. Could we install raised crosswalks (also known as continuous sidewalks) or raised intersections to let drivers know that they are guests on the roadway, not the hegemony. Yes, and that would cost a lot of money.

Let me say up front that I am not in favor of in-person law enforcement of traffic law. However, we have an epidemic of traffic violence, perpetrated by drivers, which could be greatly reduced with a limited and guardrailed period of enforcement. Automated enforcement of red light running will come to City of Sacramento, probably within five years, and to the entire county, probably within 10 years, but a lot of people are going to be killed and severely injured in the meanwhile. Would law enforcement use this as a pretext for racial and income bias? Yes, they will. It is in their nature. But I want to save lives. Police could write hundreds of tickets a day to red light runners. No, it isn’t about citation income, it is about saving lives.

Automated enforcement of failure by drivers to yield to walkers in the crosswalk is even further away, and may never happen. Nothing short of direct law enforcement may correct this problem. Again, police could write hundreds of tickets a day on failure to yield.

It is not just traffic violence, death and injury, that is the problem. It is that both of these driver behaviors intimidate people who would like to walk and bicycle from doing so. People stay home, or drive instead, or go ahead and walk and bicycle, but live in fear. Of course this is the desired outcome for politicians who support a cars-first transportation system, and oppression of those who don’t participate in the automative paradigm whether by choice or necessity. People who walk and bicycle are truly second-class citizens in our society, and many of them are further so due to racism, income bias, age, and disability.

As you will notice from past posts, I’m not a supporter of the police, and most particularly, not CHP. But police in the City of Sacramento could be forced to actually do something useful. The police work for the Chief, the Chief works for the City Manager, and the City Manager works for the City Council. The council could direct the police to pay attention to traffic violence. If the City Manager doesn’t support, fire her. If the Chief doesn’t support, fire her. And on down the line. The police spend almost all their time responding to things after they’ve gone wrong. Though they give lip service to community policing, prevention is a tiny part of what they do. And so with traffic violence. They respond to crashes, when they could be preventing crashes through targeted enforcement. They document the carnage, and almost alway blame it on the person walking and bicycling, though that is rarely the case. CHP is harder to rein in. It is an agency largely out of the control of the rest of state government. It goes its own way, ignoring laws it doesn’t like, interpreting laws to absolve drivers, and putting its thumb on corrective legislation by encouraging the windshield bias of our governor.

SacCity Vision Zero Update

There are three opportunities for commenting on the City of Sacramento Vision Zero Action Plan update.

In person: Vision Zero Action Plan Community Workshop Thursday, January 29 at 5:30 pm, Sacramento City College, 3835 Freeport Boulevard registration

Virtual: Vision Zero Action Plan Virtual Workshop, Wednesday, February 4 at 5:30 pm registration

Survey

The city’s Vision Zero webpage for general information, and links for the above.

For prior Getting Around Sacramento posts on Vision Zero, see category: City of Sacramento: Vision Zero, and the more general calegory: Vision Zero.

The city’s Vision Zero effort has failed. We are still the highest traffic fatality city in the state. I believe the reason to be primarily that there were flaws in the original approach to Vision Zerio. Though I’ve written about this before, I will post again, soon.

If you are not already following Slow Down Sacramento, please do. It is the best source of information on safety from traffic violence and the city’s Vision Zero effort.

City of Sacramento Vision Zero Action Plan update graphic

Sac City abandons separated bikeways

The City of Sacramento has installed a number of separated, parking-protected bikeways, including P St, Q St, 19th St, 21st St, 9th St, 10th St, and J St. It is failing FAILING to maintain these bikeways. They have not been swept by the city since the beginning of leaf season, early November.

You can find several blocks, or portions of blocks that have been cleared, but these have not been cleared by the city. They have been cleared by landscape services contracted by adjacent property management companies, mostly for multi-family housing. It is not the responsibility of these companies to clear the bikeways, but they do so both as a community service, and to maintain a higher level of appearance for their housing and businesses.

The city should be ashamed of itself. It has created a hazard of its own making.

It would probably be better if the city returned these streets to their previous configuartion, with traditional bike lanes. At least these could be swept by the city, and to some degree are swept by the wind of passing motor vehicles.

photo of SacCity P St separated bikeway; yes there is a bikeway under the leaf piles and leaf slime
SacCity P St separated bikeway; yes there is a bikeway under the leaf piles and leaf slime

SacATC 2025-11-20

The Sacramento Active Transportation Commission (SacATC) will meet Thursday, November 20, 2025, at 5:30 PM. The meeting will be at Sacramento City Hall, council chambers. The meeting is livestreamed from the Upcoming Meetings Materials page at the time of the meeting. Comments may be made in-person, or via eComment on the Upcoming Meetings Materials page up to the time of the meeting, but should be submitted well ahead of time if you wish the commission members to see the comment before the meeting. No comments are taken online.


Agenda (pdf)

Open Session

Roll Call

Land Acknowledgement

Pledge of Allegiance

Welcome New Commissioner – Justine Recio-Patel

Consent Calendar

  1. Approval of Active Transportation Commission Meeting Minutes
  2. Active Transportation Commission Log File ID: 2025-00201 Location: Citywide Recommendation: Pass a Motion adopting the Active Transportation Commission Log.

Discussion Calendar

  1. Franklin Boulevard Complete Street Informational Update
  2. Transportation Planning Current and Planned Projects
  3. Active Transportation Commission 2025 Annual Report

Commission Staff Report

Commissioner Comments – Ideas and Questions

Public Comments-Matters Not on the Agenda

Adjournment


SACOG Board 2025-11-20

The SACOG Board of Directors will meet on November 20, 2025, at 9:30 AM.

  • Attend: SACOG’s offices, 1415 L Street, Suite 300, Sacramento, CA
  • Watch: https://www.sacog.org/meetings/meetingagendas, at the time of the meeting
  • Comment: In-person, or submit via email to the clerk at lespinoza@sacog.org at least 24 hours prior to the meeting. (see agenda for details)

Agenda (pdf)

Pledge of Allegiance

Roll Call

Public Communications

Disclosures

Consent:

  1. Approve Minutes of the October 16, 2025, Board Meeting
  2. Approve the Transportation Development Act Claims for City of West Sacramento, County of Yolo and Yuba-Sutter Transit Authority
  3. May is Bike Month Contract Extension
  4. SACOG Flexible Funding Program Grant Extension Request and Funding Transfer for the City of Isleton
  5. 511 Traveler Information Systems Consultant Services — Contract Terms Standardization

Action:

  1. Approve 2026 Meeting Schedule
  2. 2025 Blueprint Adoption: Certification of the Final Environmental Impact Report and adoption of Findings of Fact, Statement of Overriding Considerations, and Mitigation Monitoring and Reporting Program; Approval of Amendment #11 to the 2025-28 Metropolitan Transportation Improvement Program (MTIP) and Conformity Analysis, associated with the proposed Metropolitan Transportation Plan/Sustainable Communities Strategy (MTP/SCS); and Adoption of the 2025 Blueprint (MTP/SCS); there are 10 attachements, which can be viewed in the html agenda or meeting packet at https://www.sacog.org/meetings/meetingagendas

Information:

  1. Tracking Blueprint Implementation through the Regional Monitoring Program

Reports:

  1. Chair’s Report, Board Members’ Reports and Executive Director’s Report

Receive & File:

  1. 2026 Regional Trail Implementation Strategy Update – Governance and Funding
  2. Quarterly Report on Contracts
  3. Land Use Implementation Activities for October 2025

SACOG Transportation Committee 2025-11-06

The SACOG Transportation Committee meets today, Thursday, November 6, 2025, starting at 10:00 AM. This is a thin agenda, but may still be of interest for the trails strategy.


Agenda (pdf)

Consent:

  1. Approval of the October 2, 2025, Transportation Committee Meeting
  2. May is Bike Month Contract Extension
  3. SACOG Flexible Funding Program Grant Extension Request and Funding Transfer for the City of Isleton
  4. 511 Traveler Information Systems Consultant Services — Contract Terms Standardization

Information:

  1. 2026 Regional Trail Implementation Strategy Update – Governance and Funding (Summer Lopez) (Est. Time: 30) • Governance and funding options for trails

Other Matters

Adjournment


SacATC 2025-10-16

Yes, very late post, but better late than never.

The Sacramento Active Transportation Commission (SacATC) will meet Thursday, October 16, 2025, at 5:30 PM. The meeting will be at Sacramento City Hall, council chambers. The meeting is livestreamed from the Upcoming Meetings Materials page at the time of the meeting. Comments may be made in-person, or via eComment on the Upcoming Meetings Materials page up to the time of the meeting, but should be submitted well ahead of time if you wish the commission members to see the comment before the meeting. No comments are taken online.


Agenda (pdf)

Open Session Roll Call Land Acknowledgement Pledge of Allegiance Consent Calendar All items listed under the Consent Calendar are considered and acted upon by one Motion.

  1. Approval of Active Transportation Commission Meeting Minutes
  2. Active Transportation Commission Log

Discussion Calendar

  1. SacAdapt Transportation Adaptation Plan staff | presentation
  2. Connecting Howe Avenue: Safety and Mobility Plan Phase 3 Public Engagement staff | presentation
  3. Norwood Mobility Project Phase 3 Public Engagement: Public Draft Plan staff | presentation
  4. Active Transportation Commission 2025 Annual Report staff | report | presentation

Commission Staff Report

Commissioner Comments – Ideas and Questions

Public Comments-Matters Not on the Agenda

Adjournment


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