Fwd: City Council CIP tomorrow, 5:00 PM: Standard Details update (Item 3.1) — safer bike lanes & tree canopy
Mountain View MVCSP
From: April Webster <apri...@gmail.com>
Date: Mon, Apr 13, 2026 at 7:31 PM
Subject: [mvcsp-discuss] Re: City Council CIP tomorrow, 5:00 PM: Standard Details update (Item 3.1) — safer bike lanes & tree canopy
This is literally one of the most important documents the City has. It dictates, literally, how your streets look. Right down to driveway lips, street trees, and bike ways.Don't sleep on this one!BrandonOn Mon, Apr 13, 2026, 18:49 April Webster <apri...@gmail.com> wrote:Hi folks — City Council is reviewing the Capital Improvement Program (CIP) tomorrow — this is an even year where projects get added, removed, and reprioritized, so it’s one of the key opportunities to weigh in.
One of the items that could really benefit from support is the staff recommended Mountain View Standard Detail Update (27-27) (Agenda Item 3.1, Attachment 5).
It might sound technical and has a relatively small price tag ($54k), but it has an outsized impact on what actually gets built across the city.
Standard Details are the default engineering templates used for street design — things like cross-sections, driveway visibility requirements, and landscape strips. Because they’re the starting point for most projects, they end up shaping outcomes like bike facilities, street trees, and small open space opportunities (e.g., linear and pocket parks).
While the Standards were last updated in 2019, some of the most influential pieces — including the street cross-sections (A-4 and A-5 — see diagram attached below) — date back to around 2001. Those set the baseline for how street space is allocated, so when they’re out of date, many current best practices don’t show up unless they’re pushed for project-by-project. Other cities have already started aligning their design guidance with more recent Complete Streets practices (e.g., San José’s Complete Streets Design Guidelines), which highlights the opportunity to do the same here at the implementation level.
In practice, that often shows up during project design and public outreach as efforts to bring projects in line with current expectations:
- gaps between policy goals and what gets built
- conflicts (e.g., visibility requirements vs. tree canopy
- and more back-and-forth during design and outreach
A concrete example is driveway visibility requirements (e.g., pedestrian safety triangles, A-22 — see diagram attached below), which can limit where street trees are allowed. Without updated guidance, that can lead to unnecessary tree removal or missed opportunities for canopy in both public and private development projects — even when broader City goals support it.
Updating Standard Details is a relatively small investment, but it’s one of the most direct ways to:
- set clearer, up-to-date defaults aligned with current design guidance from the past three years (e.g., DIB-94, NACTO, CA MUTCD)
- reduce redesign and project-by-project negotiation between planning and engineering
- reduce ambiguity in design decisions, which can help limit risk and avoid project-by-project uncertainty
- make it easier to consistently deliver on things like safe streets and healthy canopy
If you’re interested in weighing in:
📅 Tuesday, April 14
🕔 5:00 PM
📍 Council Chambers, 500 Castro St (or via Zoom), Agenda
🗣️ Agenda item 3.1 (CIP) - first item on the agendaEven a short comment supporting this as a way to better align policy with implementation — especially around street trees and usability — could be helpful.
Happy to chat if it would be useful, please just reach out.
Cheers,
April
Standard Detail A-4: Standard Geometric Street Cross Sections (2001) - note car lane widths (wider than state standards), shared bike lane parking (no parking protected bike lane option), no planting strip (for tree canopy + GSI)
Standard Detail A-22: Side Street / Driveway Pedestrian & Vehicular Triangle of Safety (2001) - this standard would benefit from review. In some cases, the visibility triangles may be overly conservative, which can limit where street trees are placed and has contributed to tree removal or missed opportunities for canopy in both public and private projects.
This is the Mountain View Coalition for Sustainable Planning's discussion list. To join our low-traffic announcement-only list, please visit https://groups.google.com/d/forum/mvcsp
---
You received this message because you are subscribed to the Google Groups "mvcsp-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mvcsp-discus...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/mvcsp-discuss/CAMANeTVwdiV3NC0nxojHOKnZvBRvYBo798a3DA0TQFCpzaLx-w%40mail.gmail.com.