Council reviews two annexation requests including 700‑acre data‑center site; staff and developer seek flexibility on access, noise mitigation

Council members received a staff briefing Thursday on two voluntary annexation requests the city is processing, including a large site proposed for a data‑center campus and a smaller parcel cleanup near Spur FN/93.

The larger request covers roughly 700 acres adjacent to Wild White Road and would come forward as a plan‑development (PD) zoning case after annexation. City staff said the annexation as proposed would bring contiguous city limits around the property and allow the subsequent PD application to include conditions addressing access, noise and utilities.

Why it matters: A campus of this scale would affect road alignments, emergency access and public infrastructure. Staff emphasized coordination on the East Outer Loop alignment and requiring utility‑service agreements so the city can evaluate energy and water needs up front and ensure the developer is responsible for infrastructure repair or replacement tied to construction.

City planning staff described the primary outstanding issues the council could consider before second reading: (1) final alignment of the Outer Loop thoroughfare, (2) how many public access points must be provided, and (3) noise mitigation standards for mechanical equipment. Staff said final access design will be set during the planning stage in coordination with the fire marshal rather than fixed at annexation.

Staff noted data centers tend not to be large daily traffic generators and estimated employment in the range of "50 to a 100 employees," but added the number of access points is driven by emergency access needs rather than commuter volume. Staff also flagged prior noise complaints tied to an earlier facility in East Temple that used cooling towers; they advised a noise mitigation study that evaluates both decibel levels and frequency/continuity of sound from cooling and backup systems.

Developers asked for conceptual flexibility on two access locations shown on the site plan, and asked for language clarifying that the two points are preferred rather than binding at preliminary stages. Staff recommended clarifying PD conditions to note that the two shown locations are conceptual and that final locations will be confirmed in plan review with the fire marshal. Staff also reported the developer is willing to dedicate right‑of‑way for the Outer Loop once an alignment is confirmed.

Next steps: Staff offered the option to take PD‑annexation action tonight or move the items to a subsequent public hearing/second reading once plan‑development conditions are finalized. At the workshop council members did not take a final vote.

Ending: Staff said they will bring refined PD conditions back for council consideration, including a noise‑mitigation study requirement that accounts for hours of operation and the continuous pitch of any cooling systems, and clearer language about access points and Outer Loop coordination.