Citizen Portal
Sign In

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

Get email alerts on the Land Use Development topic

No spam. Unsubscribe anytime.

Meridian council approves Sky Ranch annexation with required stub street, easement and phased build limits

Meridian City Council · December 10, 2024
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

The Meridian City Council approved Sky Ranch (H2024‑0022) after staff and the applicant agreed to most conditions and the council required a stub street plus preservation of a cross‑access easement; council backed a revised seven‑phase schedule to limit annual lot filings but one member dissented.

The Meridian City Council approved Sky Ranch (file H2024‑0022) on Dec. 10, 2024, granting annexation and related approvals for a large single‑family residential project while adding conditions aimed at preserving future connectivity and limiting early build‑out. The approval includes staff conditions the applicant accepted, a required stub street at a currently proposed easement location, and adherence to a revised seven‑phase plan intended to limit the pace of final plat applications.

Staff presentation: what was proposed

City planning staff told the council the package returned from the Nov. 19 public hearing included a proposed annexation of 20.039 acres to R15, rezoning of 24.53 acres from R4 to R15, modification of an existing development agreement, and a preliminary plat that staff described as consisting of 285 building lots, 28 common lots and six common drives. Planning staff identified two unresolved conditions tied to Terrego Lane and lot sizes at the northern boundary and asked the council for direction about requiring cross access to the parcel to the south.

Public safety and technical constraints

Planning staff and the city’s transportation advisers noted ACHD (Ada County Highway District) guidance on access offsets and road‑trust triggers. As planning staff explained, ACHD’s offset threshold informed the staff concern that, without connectivity, “the property’s development potential may be significantly constrained,” and that requiring a stub road would trigger a road‑trust requirement under ACHD rules. Mr. Parsons, city staff, summarized the technical benchmark the council considered: “ACHD requires 660 offset, I believe,” and he outlined how different access thresholds drive whether a full access or a right‑in/right‑out is appropriate.

Applicant and neighbors

Heath Clark, representing the applicant, told the council the applicant had revised its phasing and was willing to preserve a private easement at the proposed location even though ACHD had not required a stub. Clark said ACHD “has taken the position that a stub is not necessary. We’ve tried to go above and beyond by providing that easement.” Several nearby homeowners urged a gentler transition to existing low‑density lots and raised traffic and visibility concerns. Sean Lanahan, whose property abuts the project area, asked the council to preserve R4 along the immediate border and requested “concessions of a feathered transition” to reduce the number of new lots adjacent to existing homes.

Council decision and conditions

Councilman Taylor moved to approve the application noting that the applicant agreed to condition 1f and to follow the revised phasing plan, and he added as part of his motion that the applicant be required to install a stub street and maintain the cross‑access easement. Councilwoman Little Roberts seconded. On roll call, Little Roberts, Taylor and Overton voted aye; Councilwoman Streeter voted no. The motion carried and the council approved H2024‑0022 with the agreed conditions, phasing commitment and the requirement regarding the stub and easement.

What happens next

With council approval, the applicant must meet the conditions established in the development agreement and the platting process, including the phasing schedule the council accepted and the cross‑access/stub requirement. Staff emphasized the city and ACHD will need to coordinate on street design and any road‑trust funding should the council or ACHD later require that a private easement be converted to a public roadway. The council’s action does not change the requirement that future final plats conform to the conditions adopted tonight.