Get email alerts on the Split Zoning topic
No spam. Unsubscribe anytime.
Panel supports changing ‘split zoning’ rule so applicants pick a single code for projects
Summary
Staff proposed deleting a sentence that forced adjacent properties into a different zone; members agreed the change reduces split-zone confusion and recommended clarifying language before sending the package to the city attorney.
Staff described a proposed fix to the draft development code’s split‑zoning language so applicants would select a single district at project start rather than being bound by adjacent zoning lines. The staff memo explained the change would keep the requirement to choose one district but remove text that effectively forced an adjacent parcel to the T5 UC standard.
A committee member said removing the ‘forced pick’ sentence would help eliminate split‑zone ambiguity, and a public commenter supported the change as “constructively good.” The board asked staff to summarize the proposed replacement language and return with a redline and clean version for the city attorney to review before any public hearing.
AI generated
The text on this page is AI generated. Summaries, highlights, analysis, and video transcripts are all produced from the original source material.
AI can make mistakes, so if you spot one, and we will fix it for everyone.
Note: the source content is unaltered by us. Any content source we link to, be it a video, an audio recording, or a document, is presented exactly as its publisher released it. That publisher is usually a government body, sometimes an individual official or another organisation.
