Beavercreek council advances landscape code revision after extensive public comment; council asks staff to clarify grandfathering and erosion exceptions

Beavercreek City Council on Monday advanced Ordinance 25-05 to a second reading after a lengthy public hearing and council discussion about how the proposed landscaping rules would treat native plantings, mailbox plantings, erosion-prone areas and existing large front-yard gardens.

The ordinance would repeal the current Section 97.1 (“weeds and grass”) of the Beavercreek Codified Ordinances and add a new Section 97.10 to clarify yard maintenance and landscaping rules. Staff presented the draft language and said the changes focus on defining what “managed and maintained” means and on drawing clearer lines between lawns and landscape beds. In the staff presentation, a planning staff member said the proposed code would limit landscape beds in required front yards to 50% of the required front-yard area, require landscape beds to have “obvious shapes and edges,” and call for a three-foot setback between landscape beds and side/rear property lines unless a fence protects a neighbor’s yard.

The council opened the ordinance for public comment. Ten speakers requested time; most were residents who voiced support for native-plant and managed-natural landscapes but raised concerns about the 50% cap, grandfathering of existing plantings, the definition of the public right-of-way, and how enforcement and complaints would work.

Deborah Whitaker (1375 Bills Drive) said several right-of-way strips near her street would not meet some of the proposal’s standards and asked for clarity on how the city would treat obstructions in roadway sight lines. Debbie Carr (2889 Lance Road), who identified herself as part of a group of native-plant gardeners, thanked staff for meeting with the group and said the draft ordinance is improved but still ambiguous. Carr urged clearer language to protect established plantings and suggested expressly allowing mailbox plantings where they do not obstruct visibility.

Several speakers urged flexibility. "This ordinance recognizes that native plants are not weeds," said Molly Finch, who identified herself as owner of a landscape business, praising the draft for progress but calling the 50% cap "unnecessary and arbitrary." Seth Wagman described a heavily shaded front yard that cannot support turf and said the city should not require turf where native landscaping is appropriate. Antoinette Marlowe, whose property abuts a park, asked whether tall native grasses used for erosion control would be treated as decorative plantings and whether they would be legal if they exceed the three-foot setback.

Staff and council members repeatedly emphasized the code’s intent to balance safety and neighbor concerns with flexibility for managed, defined natural landscapes. Staff said the code would not distinguish between native and nonnative species so long as plantings were managed and not listed as state noxious weeds; the city will use the State of Ohio list of noxious weeds for that determination. Planning staff also said existing plantings that are in place in 2023–2024 and are well managed would not be required to be removed; council asked staff to add explicit grandfathering language for large established plantings.

Council members asked staff to add clearer exceptions for erosion-control plantings (for example, where engineering or county approvals preclude a standard remedy) and to clarify how the city will determine the 50% calculation using GIS/aerial imagery and how complaints would be handled. Several council members suggested a possible third reading to allow more public input and time for staff to draft amendments.

After discussion, a council member moved to send the ordinance to a second reading; the motion passed. Council directed staff to prepare language addressing: (1) grandfathering of existing, well-managed plantings in front yards that exceed the 50% cap; (2) clear exceptions for erosion-control plantings and where ditch/engineered solutions make plantings necessary; and (3) clarified language on mailbox plantings and right-of-way definitions.

The ordinance will return for a subsequent council reading with staff-proposed clarifications. Council did not adopt the ordinance at this meeting; it advanced to the next formal reading for further editing and public input.