Development committee presses ZoneCo for clearer rules on Cedar Road, Warrensville Center and residential standards

University Heights’ Development Committee met July 8 to review ZoneCo’s responses to the draft zoning-code matrix and to give the consultant clearer direction before the next draft, focusing on Cedar Road, the Warrensville Center Road corridor, residential setbacks and stormwater requirements.

Committee members discussed whether Cedar Road should be rezoned toward multifamily or remain commercial, noting technical constraints there compared with Warrensville Center Road. ZoneCo’s response in the matrix said Cedar Road’s lots average about 135 feet deep compared with roughly 175 feet on Warrensville Center Road, and that Cedar’s built environment is more auto-oriented and places sidewalks at the street edge, making it less comfortable for pedestrians and harder to buffer adjacent single-family homes. The matrix reported roughly 110 one- and two-family dwellings on Warrensville Center Road’s residential segment versus about 70 on Cedar Road.

The committee said those differences must inform any allowance for multifamily development on Cedar. Some members signaled they are “okay with multifamily” being permitted in parts of Cedar Road if design changes—such as moving sidewalks away from the street edge—improve the pedestrian environment. Others said Cedar should not be ignored and asked ZoneCo for concrete toolbox options to refresh that western end of the city rather than simply recommend more commercial zoning.

Warrensville Center Road dominated the discussion about the proposed mixed‑use corridor. Committee members reviewed several code items raised in ZoneCo’s responses: eliminating a 5/12 roof pitch to allow flat roofs and roof decks; rear setbacks (the draft ties a 35‑foot rear setback to the principal structure); maximum impervious coverage; required parking counts; and rear buffers. The draft currently shows a maximum impervious coverage for residential portions at 75% (an 85% figure applies to a mixed‑use category noted in presentation examples). The committee discussed alternatives such as on‑site underground storage or retention basins and porous paving; staff said underground storage and engineered storm systems are commonly used and can allow higher imperviousness if water is stored/treated on site.

Public commenters urged caution on height and intensity. “Would anybody be interested in having a 3‑story townhome in their backyard?” asked resident Joe Remy, reflecting neighborhood concern about scale. Julie Martinez, whose home backs to the corridor, told the committee: “Please be thoughtful in this process,” adding that residents want insulation from noise and activity and asked for explicit height limits in feet rather than just story counts. Micah Maliscus urged the city to reduce lane widths on Warrensville, add on‑street parking and pursue walkability so new retail serves nearby residents rather than generating cut‑through traffic.

The committee debated dimensional standards for townhouses and multifamily buildings. ZoneCo noted townhouses can be built at 16 feet but the draft retained a 20‑foot minimum lot width because townhouses are often developed as condominiums on a single lot. A persistent point of contention was side‑yard setbacks for multifamily: ZoneCo recommended 10 feet; some members proposed 5 feet to recoup units and reduce building height from four to three stories, while others said 10 feet provides meaningful buffering and sound reduction. The committee did not reach consensus and directed the consultant to keep the 10‑foot recommendation for the next draft while flagging the issue for public hearings and subsequent council action.

Other items the committee asked ZoneCo to address in draft two included: clarifying allowable uses in neighborhood commercial (to limit high‑intensity retail/autobody/autoshop uses and better define “local retail”), whether assembly/meeting places are permitted in neighborhood commercial (religious and institutional uses currently appear allowed in other districts), and how to treat educational uses (the draft limits educational facilities to the university district, which would grandfather existing schools but preclude new school sites in R‑1 unless changed).

On stormwater, staff and the committee discussed lowering the acreage threshold that triggers stricter stormwater controls (currently projects under one acre can avoid some requirements). One suggestion from the committee was to lower the threshold (for example, to three‑quarters of an acre) so smaller infill developments must include swales or other on‑site controls; staff cautioned engineers’ options vary and underground storage is costly but effective.

Process and public engagement were recurring themes. Multiple residents and committee members criticized the pace and clarity of outreach: the draft has been in process since mid‑2024 and elements of it trace back to a 2022 effort; speakers urged broader, earlier and clearer community sessions. The committee chair and staff said they plan a series of public hearings after the consultant hammers out a second draft that incorporates the feedback given at this meeting.

The committee closed the meeting by asking ZoneCo to prepare draft two with clearer parameters on the points above and to return for further committee review before community forums. The meeting adjourned on a motion from the committee chair, seconded by Councilmember Weiser.