Gunnison council reviews land‑use standards after developer compliance questions

The Gunnison City Council met April 29 to review how the city’s land‑use and development standards have been applied to recent commercial projects and to direct staff to return with options for clearer code language and enforcement.

The mayor opened the meeting and said the goal was to "get on the same page" so councilors and staff apply ordinances consistently and can respond uniformly when citizens raise concerns. Dennis, the city’s zoning administrator, gave a detailed overview of the statutory framework and how the city applies local rules within state authority.

"A municipality may enact all ordinances, resolutions, and rules and other forms of land use controls and development agreements that the municipality considers necessary or appropriate," Dennis said, summarizing what he identified as Title 10‑20 of state law. He emphasized that where code language leaves room for discretion, the city must put parameters into the code to avoid arbitrary decisions and potential litigation.

Dennis walked the council through a recent example—the Christiansen Insurance building—saying the project went through the technical review committee (zoning administrator, public works, police, fire) and the architectural review committee and that several design elements were revised during review to meet federal and state accessibility and drainage requirements. He also contrasted the Christiansen plan, described as conceptual, with a more detailed Dollar General landscaping plan and noted small local businesses often have fewer resources to produce highly detailed submittals.

Councilors focused substantial discussion on landscaping standards: how the city’s formula translates to trees and shrubs, whether the code’s "round up" rule increases plant counts beyond what is reasonable, and whether plant equivalencies (for example, trees counting against shrub requirements) should be allowed. "Right now the code says you have to round up," Dennis said, and used the illustrative rule of roughly one tree and five shrubs per 30 feet of frontage to show how totals can escalate.

Parking, facade material requirements and the Main Street overlay were also discussed. Dennis noted the Main Street zone allows flexibility—such as counting on‑street parking toward required spaces and, in some constrained sites, reducing landscaping mandates—while other zones generally require on‑site parking and stricter material standards.

Councilors debated who should pay to fill gaps in curb, gutter and sidewalk where a new development abuts existing public right‑of‑way. Dennis cited court precedent that municipalities can require right‑of‑way improvements, but councilors asked whether the city should occasionally share costs. Officials said the city budgets roughly $10,000 annually for curb/gutter/sidewalk work; a specific, earlier contribution of $7,500 was mentioned as an example of a city cost‑share.

At the end of the public discussion, a motion recorded as made by councilman Nelson and seconded by councilman Peterson was reconsidered; the council did not record a final vote on that motion and directed staff (and finance) to collect additional information and return with options for policy clarification. The council asked staff to draft potential code amendments or clearer standards on landscaping counts, rounding rules, acceptable plant lists, facade/material requirements and how the city treats retroactive infrastructure obligations.

The council’s next step is for staff to prepare specific proposals and cost estimates for the council’s consideration and, where necessary, for public hearing and formal amendment of the city code.