Facility or project event · Rezoning approved · Official record

Rezoning approved on 6 January 2026: Gemini Addition (Sioux Falls, SD) — city council minutes dated 6 January 2026

The Sioux Falls City Council on January 6, 2026 adopted Ordinance No. 5-26 rezoning land south of E. Rice St. and east of Veterans Pkwy (petition 022049-2025) and Resolution No. 4-26 approving the Gemini Addition preliminary plan, conditioned on any data center being limited to domestic water usage; applicant Gemini Data Center SD, LLC.

What this is. The source (city council minutes, dated 6 January 2026) dates this rezoning approval to 6 January 2026. This event does not establish any later stage.
Event date
Minutes header 'Tuesday, January 6, 2026'; Resolution 4-26 'Date adopted: 01/06/26'.
Source dated
Minutes document date (meeting date); approval date of the minutes not shown.
Source accessed
Retrieved by DataCenterData; not an event date.
Added to Latest updates
When this entry entered the updates log; not an event date.
Event type
Rezoning approved · Approvals
Evidence basis
Official record · Sioux Falls City Council
Confidence
HighOfficial minutes with votes; exact applicant and petition match.
State
South Dakota
Linked records
Gemini Addition gemini-addition-data-center-sioux-falls-sd
Linked claims
None linked

What the source says

That the preliminary plan of Gemini’s Addition to the City of Sioux Falls, Minnehaha County, SD, is hereby approved with the below condition

Where: Item 33 (Ordinance No. 5-26, roll call 7-0) and Item 39 (Resolution No. 4-26 as amended, roll call 7-0)

Internet Archive copy (captured 15 January 2026)

What this does not establish

  • Final plat or site-plan approval
  • Building permit or construction start
  • Operation

Still unknown

  • Final plat, site plan and building permit status
  • End user/operator and capacity
  • Official record of the January 2026 referral-petition outcome (reported in news as insufficient; not verified from a city record)

Identifiers

Event ID 36f436d4a29128a3ba9dce6f80cd8d620c2d642e69726223f18825fd44fbf734. The ID is derived from the event itself and never changes. A later correction would be published as a separate, linked entry.

Report a problem with this entry →

All latest updates →