Heron Commons: Garden City’s next zoning draft

Heron Commons would set new development rules for the area between Heron Park and the Waterfront District, on both sides of Adams Street. The application includes properties on East 37th and 38th streets, Adams Street, and Reed Street. Garden City is the public applicant for case SAPFY2026-0001; the proposal includes the former Ada County Highway District operations yard and surrounding properties.

The draft map ordinance would move affected land from C-2 and R-3 zoning into the proposed SAPD-02 district. Its parcel descriptions matter: a property’s proximity to the yard does not establish that it would receive the proposed zoning. Owners should match their parcel and legal description against the exhibit before applying any proposed standard to their land.

This is also a broader question than what replaces the yard. Separate owners, existing buildings, river access, and connections through neighboring streets all sit within the planning problem. A single district name does not mean a single owner controls the entire redevelopment.

The city’s application page lists a continued Planning and Zoning hearing for September 16, 2026, and a continued City Council hearing for September 28. Draft 5 and the associated staff report are prepared for the September hearing. Those document dates identify the meeting they support; they do not mean that meeting has occurred.

The posted recommendation form is expressly a staff suggestion. It contains proposed findings and approval language, along with incomplete fields and references carried from earlier paperwork. Reading a sentence in that form as a completed vote would misstate the record. The reviewed file does not establish an adopted Heron Commons ordinance, a final project approval, or a construction start.

After the hearings, the evidence to look for is the actual written action and adopted ordinance. Any applicable reconsideration or appeal would need to be checked separately. An agenda entry establishes an opportunity for a decision; the signed record establishes what the decision was.

The September staff report describes replacing the earlier 50-dwelling-unit-per-acre requirement with a different approach. Properties larger than one acre would need evidence that development can sustain the intended mix of uses. For properties smaller than one acre, the draft offers alternatives: mixed uses, entirely nonresidential uses, or residential density of at least 15 dwellings per acre. These are proposed development standards, not a forecast of occupied homes.

The operative height language is more specific than a general description of taller mixed-use development. The table below summarizes Draft 5, pages 40–41. Each provision remains proposed.

The rezone proposal implements a planning vision, but the existing zoning, comprehensive plan, and proposed district serve different purposes. The July staff report identifies future-planning-area, mixed-use, Main Street Corridor, and future park or open-space designations in the application area. Those designations describe policy direction; the proposed district would supply more detailed rules for later development.

For a property review, keep those layers on separate lines: existing zoning, requested zoning, future land-use designation, and project-specific approval. A desirable future use on a planning map does not by itself establish a permitted building envelope. Likewise, a proposed rezoning should not be substituted for the rules in force when assessing an existing property.

The question for the hearing is how the proposed rules implement that vision while addressing neighboring property and public infrastructure. The question for a later building proposal will be how that particular design satisfies the adopted requirements.

ACHD’s July 16 response explains that the Adams Street connection remains on its Master Street Map. Removing or changing the planned roadway connection would require ACHD Commission consideration and approval. City adoption of the specific area plan could provide the basis for that review.

The same letter distinguishes a general public roadway from a connection limited to bicycles, pedestrians, and emergency access. It also raises the existing stub-street policy and says staff still needed to consider options before providing a final response. That correspondence does not settle whether everyday vehicle traffic would pass through.

The practical consequence is a design dependency. A plan that assumes a limited connection should identify the ACHD decision supporting that assumption. A plan prepared before that decision should show what would change if a public roadway is required: circulation, usable site area, emergency access, and responsibility for the connection. Nearby owners should also look for the approved traffic-management design before relying on a particular traffic outcome.

The August engineering correspondence records a specific concern about using a newer hydraulic model. Engineer Nick Kraus cautioned that lower modeled flood elevations could conflict with the effective study used by flood-insurance underwriting. He distinguished using a model for a no-rise analysis from using it to establish finished-floor elevations.

That exchange led to revised proposed language tying flood-protection design to the modeling behind the city’s adopted flood study, with updates through formally accepted information. It is evidence of technical review and a drafting response. It is not a parcel-specific flood certification or an insurance commitment.

Before pricing a river-adjacent project, the unresolved inputs include the accepted model, required floor elevations, the proposed protection system, effects on neighboring property, and the insurer’s treatment of the finished design. A drawing that fits the zoning envelope can still leave those questions unanswered. Engineering and insurance confirmation need to address the same actual site and proposed elevations.

In a separate August 11 exchange, city staff asked whether redevelopment would require removal of an existing ACHD outfall to the Boise River. Engineer Joseph Canning replied that the city requires stormwater retention on site with redevelopment and that the discharge would be eliminated. This is a site-servicing issue with consequences for the eventual civil design; the email supplies no finished drainage plan or construction cost.

DEQ’s response to the initial agency notice stated that it had no comments at that time. That limited response does not establish site cleanup, water capacity, sewer capacity, or clearance for a later project. The source file is labeled on the city page with a different date; the correspondence itself is dated April 6, so that is the record date used here.

A development review still needs project-specific utility availability, required extensions or upgrades, drainage design, and relevant environmental records for the former operations yard. This review did not verify capacity commitments or a completed environmental assessment. Their absence from this evidence packet should be treated as an open diligence item, without assuming either a capacity shortage or a clean bill of health.

The July staff report describes public streets, pathways, flood protection, open space, and Greenbelt access being delivered or financially secured alongside development. It also identifies long-term maintenance mechanisms and public access easements. These obligations make the timing and cost of public improvements part of the development question.

Draft 5 retains detailed phasing provisions. It ties relevant improvements to development, allows specified financial security, and provides for alternative timing when required findings are met. A phasing allowance should therefore be read with its conditions; it does not establish that an improvement has already been funded or built.

For a builder, the useful schedule starts with obligations attached to the specific parcel. It should identify the improvement, responsible party, approval needed, timing trigger, security arrangement, and long-term maintenance responsibility. A later phase’s success should not be assumed to fund an earlier phase’s essential access or protection. The reviewed records do not provide an executed construction schedule for the district.

ACHD’s May 22 correspondence said the agency did not intend to include land-use information in its surplus sale and regarded that as buyer due diligence. That statement separates the seller’s disposition process from the city’s zoning process. The later July email refers to an anticipated September sale; this research has not verified a completed sale or a new owner.

Before relying on redevelopment potential in a purchase decision, a buyer would need the actual sale terms, current title, legal parcel status, recorded restrictions and easements, and the approval record applicable to the proposed use. A zoning proposal does not establish that those interests can be assembled on acceptable terms.

Renew’s assessment is that the most consequential uncertainty is how the eventual private project fits the public requirements. An acquisition budget should be supported by actual land terms and civil, building, and financing estimates. This public file is insufficient to calculate a defensible land value, development profit, achievable rent, or completion date.

The September staff report describes an approximately 34-acre district. Multiplying that gross area by a density figure would not produce a defensible home count: the proposal spans different properties and uses, and the proposed standards allow different development patterns. There is no verified district-wide delivery total in this review.

The draft recommendation itself would limit the action to the specific area plan and related zoning. Its proposed conditions say the action would not authorize land work, vegetation removal, construction, or commencement of a use, and that additional approvals may be necessary.

To track actual supply, follow the sequence at each site: adopted zoning; a project proposal and its written decision; any unresolved review or appeal; required civil and building permits; documented site work and construction; and completion or occupancy records. A future article can report advancement when those records exist. Until then, Heron Commons is a consequential land-use proposal with identifiable design and infrastructure questions, but no verified schedule of homes reaching the market.