Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Rezoning General Plan Amendment topic

No spam. Unsubscribe anytime.

Hooper council discusses opening general plan for developer's subdivision proposal

2522240 · March 7, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

At a March 6 work meeting the Hooper City Council discussed whether to open its general plan to consider a developer's request to amend the land-use map for a proposed subdivision with two alternative layouts; councilmembers emphasized using a developer's agreement and planning-commission review before any rezoning.

Hooper City Council members spent the bulk of their March 6 work meeting discussing a developer's request to open the city's general plan to consider amending the land-use map for a proposed subdivision.

Council members and staff said the developer has presented two alternative plans: a higher-yield "blended" layout the transcript describes as a 53‑lot configuration that would reserve a large park, and a lower‑yield option of roughly 100 half‑acre lots. Council members raised concerns about lot yield, floodplain encroachment and the city's ability to shape the project's design before any rezoning is granted.

Why it matters: Opening the general plan or amending the land‑use map would be the first formal step toward a rezoning application. Council members said that rather than granting a rezoning at the outset, the city should require a developer's agreement that spells out lot sizes, open‑space commitments, design elements and how the project would handle floodplain or infrastructure impacts.

Malcolm (staff member) told the council the decision to open the general plan would not itself approve zoning: "It would simply just say we're going to begin a mutual process of developing a developer's agreement and then the zoning that would take place as part of this," he said. He recommended bringing a coordinated developer's agreement and rezoning application to the planning commission and to council so the two processes align.

Council members described how a development agreement could preserve council influence over project details. One member summarized the approach offered in a nearby city: the council would review and preliminarily approve a development plan (including materials, landscaping and open‑space commitments) before the planning commission would act on a rezoning application. That sequence, supporters said, would prevent a scenario where the city approves a rezoning without clear controls over the development's design.

Several council members said they were open to the idea of approving an amendment only if the developer provided a plan that matched what the city wants. "If we're way off, then ... we don't want to go through that effort," one council member said, urging the developer to present something "amenable" to the city.

Council discussion also touched on alternative uses and community benefits. One council member suggested the developer explore mixed uses such as a golf or recreation amenity fronting the road with higher‑density housing behind it to create an asset rather than more identical single‑family rows.

No formal vote or motion to open the general plan was recorded at the meeting. Council members said the developer would present the materials publicly, and that the item would proceed as a public hearing when the application is formally filed. Councilmembers emphasized that any rezoning would require both planning commission recommendation and council action after a development agreement was negotiated.