Lifetime Citizen Portal Access — AI Briefings, Alerts & Unlimited Follows
Lafayette residents press council over land‑use rewrite; questions linger on ‘missing‑middle,’ corner shops and building heights
Loading...
Summary
Hundreds of public commenters and a lengthy staff presentation focused debate Wednesday on Lafayette’s proposed land‑use code rewrite — especially whether to allow missing‑middle housing on corner/collector lots, limited neighborhood‑serving businesses, and targeted height incentives — with council asking staff for clearer maps, definitions and safeguards before adoption.
Hundreds of residents and volunteers packed the speaking roster at Lafayette City Council’s April 7 meeting to press officials for changes to a proposed land‑use code rewrite that would convert large parts of the city to form‑based districts.
Speakers from neighborhoods across the city urged council to preserve existing patterns and curtail what they called aggressive reclassification of streets and lots. "The survey is biased toward a favored plan by consultants," said Susan Curtis, who told council she walked Lafayette daily and urged staff not to treat the questionnaire as a definitive measure of community input. Other residents from Indian Peaks, Annas Farm and Old Town raised particular concerns about street classifications, legal covenants and the risk that new rules could permit commercial uses on corner lots where homeowners and covenants currently prohibit them.
Why it matters: The land‑use rewrite implements the Legacy Lafayette comprehensive plan and will rezone large areas to districts that aim to encourage walkability and mixed uses. That shift can accelerate redevelopment, but residents, neighborhood groups and councilors asked for more precise boundaries and protections so change does not outpace neighborhood character or private covenants.
City staff summarized engagement for the code project: 38 public meetings, about 2,700 comments and roughly 1,000 survey responses. Staff said the highest‑level tension centers on three topics: allowing “missing‑middle” housing (duplexes, triplexes and other small multiunit types) on corner and collector streets, permitting limited neighborhood‑serving commercial uses (cafés, small retail) in some residential areas, and whether to offer limited height increases (four stories) on major corridors in exchange for community benefits such as affordable units or public space.
Council direction and next steps: Councilors broadly signaled they want staff to return with clearer, evidence‑based definitions and maps before the code moves forward. Specifically they asked for: - A firm definition and map for “collector” and “major corridor” streets so residents can see where changes might apply. - An inventory of HOA/PUD covenants that would legally bar some conversions and a map showing likely impact areas. - A more explicit live‑work approach if the council wants to enable small owner‑operated businesses without removing housing stock. - Quantified, enforceable standards for any incentive program that would permit additional height in exchange for community benefits (for example, how many affordable units at what AMI level would be required).
Quotes that frame the debate: "We need safe connections in this city," Susan Curtis said, urging staff to prioritize transportation safety and water treatment over retrofitting neighborhoods. "I would strongly urge you…to declare this a water emergency this year," Mike Watson told council, linking planning decisions to drought concerns. On process and protections, Barbara Patton of Indian Peaks warned the council that "our covenants run with the land" and argued that N2 zoning is incompatible with her neighborhood’s PUD and HOA restrictions.
What’s next: Staff will return with an adoption‑draft that incorporates public and working‑group feedback, plus the requested maps and definitions; council asked that any changes be monitored after adoption and reviewed within a year so any negative consequences can be corrected.
Ending: Council did not adopt the full code at Wednesday’s meeting; it provided direction on key policy questions and required staff to supply more precise maps, covenant overlays and community‑benefit metrics before a formal adoption hearing.
