Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Use topic
No spam. Unsubscribe anytime.
Council delays Halsey Gateway code changes, schedules work session to revisit height and parking rules
Summary
City planner presented a proposed Halsey Gateway Overlay that would allow height bonuses up to 50 feet (four stories) in MU‑1/MU‑2 zones in exchange for community benefits; council set a September work session and continued final action to October after residents and councilors raised concerns about height, parking and transit assumptions.
Get email alerts on the Land Use topic
No spam. Unsubscribe anytime.
City planning staff presented the second reading of a development‑code amendment (case file LUD‑0007‑2026) to add a Halsey Gateway Overlay District (HGO) for downtown mixed‑use zones. The proposal would add design standards, building massing rules, and a height‑bonus framework that allows developments taller than the existing 35‑foot limit to go to 50 feet (capped at four stories) if an applicant provides four community benefits from a seven‑option menu.
Dakota Meyer, the associate planner, said the height bonus is contingent on planning commission review and listed community benefits that can include parking options (for which 65% or 75% of required parking would count toward the benefit matrix). Meyer emphasized step‑back requirements and design standards intended to reduce corridor canyoning as buildings rise above 35 feet.
Public speakers and councilors questioned whether allowing automatic height bonuses would result in out‑of‑scale buildings, whether incentivized parking would function under state C‑FACT guidelines, and how transit frequency assumptions used in C‑FACT mapping might change. Paul Wilcox and several council members argued the automatic allowance of 50‑foot structures was problematic; planning commission members urged additional review.
Outcome: The council declined to adopt the ordinance at tonight’s meeting. Instead it scheduled a council work session on September 22 and continued deliberation with a date‑certain council action set for October 27 so members can review the materials and receive additional briefings on parking, design standards, and transit assumptions.
Next steps: Staff will prepare targeted materials for the council work session outlining the incentive mechanics, example designs, parking calculations and how C‑FACT transit classifications affect parking requirements.

