North Logan planners review draft form-based code for city center

Planning staff presented a draft form‑based code for North Logan’s city center at a July Planning Commission workshop, outlining where taller, mixed‑use buildings would be allowed, how building fronts and street types would be regulated and what design standards developers would have to meet. The workshop was a presentation and Q&A; commissioners did not vote on adopting the code at the meeting.

The draft implements the vision in the city center master plan, staff said. Nathan Davis, planner for downtown redevelopment services, told commissioners “we're regulating by how the building will be built, the form, and then the function will follow.” He said the draft aims to concentrate higher density and walkable, commercial‑retail frontages in a narrow city center corridor while providing transition districts to step down height and massing adjacent to existing neighborhoods.

Under the draft, the city center core would generally allow buildings of about three to six stories; the East Side Transition Form District was described as generally three stories, stepping down to two stories within about 100 feet of the irrigation canal to “be respectful of those neighbors,” and the West Side Transition District would typically range from two to four stories depending on the street. Davis said the city center contains the most vacant land and is therefore the place envisioned for increased density.

Design and frontage rules would be a central feature. The draft identifies three frontage types (primary, secondary and tertiary) with primary frontages—named as the pedestrian mall—subject to the most stringent design standards. Davis said the city center would have the “strongest design requirements” so the final build‑out matches the master plan’s New England–inspired, timeless aesthetic. He added that the code still allows developers to propose alternate designs through formal code modification processes.

The draft also sets basic parking guidelines and other standards. The presentation listed residential parking ratios that staff said are in the draft: one parking stall per one‑bedroom unit, 1.5 stalls per two‑bedroom unit and two stalls per three‑bedroom unit. Setbacks described in the draft include zero side setbacks for core pedestrian buildings and a roughly 10‑foot setback on some arterials to allow for sidewalks and circulation.

Commissioners asked about flexibility for developers, costs and how the draft interacts with recent state housing initiatives. Davis and other staff described several mechanisms for flexibility: code modifications recommended by the Planning Commission to City Council, master developer agreements, and other tools such as impact‑fee rebates or local programs. On state policy, staff said the state has adopted programs and funding aimed at increasing housing supply and affordability that can be paired with local projects, and that some state subsidies and loan products can improve a project’s feasibility.

Commissioners and participants raised concerns about construction costs, developer return on investment and business access on a pedestrian mall. A staff example cited in the discussion said recent three‑story mixed‑use construction in a nearby area had a reported cost example of about $490 per square foot; staff emphasized costs vary by frontage quality and facade treatment and that the code concentrates higher design standards into a relatively narrow corridor to limit excessive cost across the city.

Davis and staff also noted implementation process points: the form‑based code would be adopted by reference into the municipal code (kept as a graphic‑intensive document), updating portions of Title 12 (the code sections described as 12a, 12b, 12c in the presentation). Staff said updates to the form‑based code itself would still require legislative action and that the city expects the form‑based code to be one zoning district with clear boundaries so changes remain targeted.

No formal decision or ordinance adoption occurred at the workshop. The meeting record shows routine procedural motions—adopting the meeting agenda, approving prior minutes and adjourning—were made and approved by voice vote during the session; the form‑based code remained a draft for later hearings and formal legislative steps.

Next steps: staff said they will continue outreach, refine the draft design standards and coordinate implementation mechanics (for example, master developer agreements and impact‑fee options) before returning to formal legislative review. Staff provided contact information for follow‑up questions and encouraged commissioners and the public to submit comments before further code hearings.