University Heights committee debates 30-inch hedge rule, sightlines and tree‑service registration

The University Heights City Council joint Service & Utilities and Building & Housing Committee continued its review of ordinance 2024‑65, the rewrite of Chapter 10.72 (trees, hedges and shrubbery), focusing on sight‑line rules, enforcement and contractor registration.

The committee discussed retaining a 30‑inch maximum height where vegetation could obstruct drivers’ or pedestrians’ views and whether that single height standard fits narrow, densely built lots. Councilwoman Win Weiser said she had repeatedly seen hedges that “come all the way to the sidewalk,” blocking visibility for children, bikes and drivers pulling from driveways. Service Director Allen Pennington described the engineering basis the committee referenced: “In regards to, the site triangle you’re talking about, that’s from the Ohio location design manual,” which sets sight‑triangle distance based on approaching traffic speed and assumptions about vehicle position off the travel lane.

Why it matters: the ordinance change would consolidate and update several sections of the city code, clarify when the building commissioner can order trimming or removal, and add registration and qualification requirements for commercial tree services. Committee members said clearer rules could make enforcement and contractor oversight more consistent, while several members warned against overreaching into established plantings.

Key points from the discussion

- Sightlines and measurements: Committee members reviewed the rationale for a 30‑inch clear‑view standard near intersections and corners and debated whether to add a horizontal distance (for example, a 30‑foot corner zone) in addition to a height limit. Several members described a local intersection where large shrubs reduce visibility. Participants noted that sight‑triangle practice commonly assumes the driver’s bumper or eye point is a fixed distance from the travel lane (the transcript cited 10–17 feet as typical engineering assumptions).

- Existing code and discretion: Members reported that some 30‑inch language exists in the municipal code in other sections (for example, weed control) but that 10.72 currently places discretionary authority with the building commissioner to determine a hazard. Several members said that discretion is helpful to avoid turning the city into an HOA‑style regime, while others said discretion must be backed by clearer criteria so enforcement is evenhanded.

- Fences vs. hedges: The committee discussed how the code treats hedges similarly to fences for some purposes — for example, higher fences along streets are separate from the corner/triangle rule — and whether the 25% open visibility rule that applies to some fence types should be referenced for hedges.

- Contractor registration and qualifications: The draft ordinance would require tree services that work in the city to register, carry insurance and workers’ compensation, and meet competence criteria. The committee debated whether the registration should require an on‑staff ISA (International Society of Arboriculture) certification or allow contractors to demonstrate competence with references, equipment lists and other documentation. Mr. Malaskis, a participant who has worked with tree services, summarized the committee’s intent: “to be clear, the noxious prohibition is already on the books,” and said the registration requirement is intended to make contractor competence and insurance verifiable to protect residents.

- Homeowner work and permits: Committee members clarified that homeowners may still take down or trim trees on their own property and, in Ohio, may obtain a homeowner permit; registration/licensing requirements apply when a contractor is hired or when a permit triggers licensing rules.

- Notification for public‑street impacts: The draft requires that firms notify the building commissioner at least one business day before work that will block a public street; Service Director Allen Pennington said “1 day is usually adequate” to coordinate police, fire and traffic control. Some members proposed increasing notice to two or three days and adding a permit condition that contractors use “best efforts” to notify immediate neighbors.

- Enforcement and penalties: The committee reviewed options for enforcement when owners or contractors ignore orders. Members described civil remedies — placing unpaid abatement costs on the tax duplicate — and limited criminal penalties reserved for egregious noncompliance. Law Director Brad Bridal and others said the city should preserve options to recoup costs and to pursue criminal charges only when appropriate; members stressed hazardous‑tree provisions merit stronger remedies because of public‑safety risk.

What the committee directed or decided

- The committee asked the law director and staff to revise the draft to: clarify which provisions remain discretionary, harmonize cross‑references (for example sections being moved or merged), and add clearer options for contractor registration, documentation requirements and neighborhood notification. No final vote or ordinance adoption occurred during the meeting.

Background and next steps

- The discussion continued an item the committee had reviewed at earlier meetings. Committee members asked staff to circulate an updated draft that incorporates the clarifications discussed and to return the ordinance to a future joint committee meeting. Several members said they want a public hearing once the revised ordinance is published so residents can comment.

Ending note

- Committee members emphasized balancing public safety, neighbors’ rights and reasonable administrative burden on residents and contractors. Staff and the law director were asked to prepare a revised draft for committee review and a public hearing schedule.