Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Zoning Code Rewrite topic
No spam. Unsubscribe anytime.
Zoning subcommittee reviews town-hall feedback on Warrensville Center Road, raises infrastructure and parking concerns
Summary
Members of the University Heights zoning subcommittee on Oct. 13 reviewed resident feedback from a Sept. 30 town hall about a September 2025 draft zoning code, focusing on retail viability, building height, parking, stormwater and utility capacity, and neighborhood engagement.
Get email alerts on the Zoning Code Rewrite topic
No spam. Unsubscribe anytime.
The University Heights economic development committee's zoning subcommittee met Oct. 13 to review resident feedback from a Sept. 30 citywide town hall and the September 2025 draft of a proposed comprehensive zoning code rewrite. Committee members said they want to fold public comments into the next draft and to pursue further technical studies before moving forward.
"For today, what I'd like to really focus on is...read through what we heard, discuss what we heard, and see if there are...potential changes to the code," said John Rock, a member of the zoning subcommittee, opening the meeting and identifying the committee's intent to address town-hall concerns.
The subcommittee and members of the public discussed several recurring themes from the town hall and written notes: whether small corner retail shown in the draft would be economically viable; the visual scale and height of new multifamily buildings; the amount and location of parking; risks to aging storm and sewer systems from increased impervious surface; and the need for traffic, streetscape and utility data to guide design decisions.
Residents and speakers said the zoning map’s pattern of mixed-use “red squares” interspersed between multifamily blocks could place small retail mid-block, where several speakers questioned whether those spaces would attract customers beyond the immediate neighborhood. The subcommittee noted ZoneCo (the consultant referenced in the presentation materials) did not provide a localized market or demographic study specific to University Heights backing the retailers-on-corners concept.
"There was no study to back up that idea of those corners," one subcommittee member summarized of the presentation materials, and the group discussed whether the code should require or merely allow first-floor retail. The September draft caps building heights at 50 feet in some districts, the subcommittee noted, and members debated whether a numeric cap or a story-based standard would better manage scale adjacent to single-family lots.
Infrastructure concerns were a prominent thread. A consulting engineer in the audience warned that "density means high stormwater" and urged the city to reassess the sanitary and storm systems before adopting standards that could increase runoff. Committee members said current stormwater and sewer infrastructure in parts of the city dates to the mid-20th century and that upgrades would likely be required if density increases.
The subcommittee reported ongoing conversations with Cuyahoga County agencies and the Cuyahoga Soil and Water Conservation District about stormwater management and said it expects a proposal from the conservation district. Members also said the city previously considered using ARPA funds for sewer work and noted existing constraints on municipal funding.
Traffic and streetscape also came up repeatedly. The committee reviewed an older ODOT traffic study cited by a speaker — approximately 1,000 vehicles during peak hour and about 13,000 average daily traffic on sections of Warrensville Center Road — and members said up-to-date traffic data and a streetscape plan are needed before decisions about lane configurations, parking, protected bike lanes or a mid-block retail pattern are finalized.
On parking, the group discussed front-yard parking and the effects of high parking demand from rentals. The draft zoning’s multifamily parking assumptions — discussed in the meeting as roughly 1 space per bedroom and a 1.5-space rule for some two-bedroom units — do not address the localized problem of vehicles parked on residential lawns, subcommittee members said.
Speakers also raised housing types and affordability tools. Attendees encouraged expanding options such as accessory dwelling units (ADUs) to provide incremental housing and income for owners, while the subcommittee stressed existing ADU provisions require the owner to occupy one of the units and limit unit size. Committee members said they will revisit how ADUs are defined and whether long-term rentals that meet owner-occupancy rules should be explicitly allowed.
Residents pressed for stronger design and enforcement tools to prevent poorly maintained landscaping, unshielded dumpsters, and other site-level impacts. Several speakers said planning and design-review standards need to be clearer so that new development fits neighborhood expectations; the subcommittee discussed options including a focused neighborhood design review or a streetscape/charrette process to generate visual prototypes for affected blocks.
Committee members emphasized process and engagement as much as code language. The group discussed organizing focused meetings or neighborhood workshops to show prototypical designs, gather affected homeowners’ input and produce materials developers can use to propose projects consistent with community goals. The subcommittee also noted another city-organized town hall on Oct. 30 and its next subcommittee meeting on Nov. 10, when members expect to begin detailed review of the September 2025 draft available online.
No formal zoning votes or ordinance adoptions were taken at the Oct. 13 meeting; the committee adjourned after discussing next steps.
Looking ahead, the subcommittee said it will: seek updated traffic and market studies where needed; continue coordination with county stormwater partners and utilities on capacity and standards; consider landscaping, dumpster enclosure and covered-parking requirements to reduce visual and nuisance impacts; and design additional resident engagement sessions to create shared visuals and tradeoffs before finalizing code language.

