San Marcos, Texas

No Zoning District

One sentence changed the first-reading Heavy Industrial proposal into a city-limits prohibition, 4–3. The matrix rule is adopted; its legality remains untested.

A marked San Marcos ordinance sheet closes the last zoning cellAgainst a dusk view of limestone, cypress, Old Main, and the San Marcos River, a physical development-code sheet compares the proposal entering final reading with the amended rule. Heavy Industrial changes from C-star, a conditional use, to a dash for every district after a four-to-three floor amendment.SAN MARCOS RIVERCITY OF SAN MARCOSDevelopment CodeTABLE 5.1 · DATA CENTER USEPROPOSALENTERING FINAL READINGALL OTHER DISTRICTSHEAVY INDUSTRIALC*CONDITIONAL USEAMENDEDAFTER FLOOR VOTEALL DISTRICTSNOT ADMITTEDFLOOR AMENDMENT43JUNE 16 · FINAL READINGSan Marcos closes the last zoning cell for data centersA mobile-scale development-code sheet stacks the proposal and adopted rule. Heavy Industrial changes from C-star, a conditional use, to a dash in every zoning district after a four-to-three floor amendment.CITY OF SAN MARCOSDevelopment CodeTABLE 5.1 · DATA CENTER USEPROPOSALENTERING FINAL READINGHEAVY INDUSTRIALC*CONDITIONAL USE43 FLOOR AMENDMENTONE CELL CHANGEDADOPTED RULEAFTER FLOOR VOTEALL ZONING DISTRICTSNOT ADMITTEDJUNE 16 · FINAL READING
The proposal entering final reading placed the lone conditional-use mark in Heavy Industrial. The 4–3 floor amendment changed that cell to a dash before adoption.

At 2:46:42 into San Marcos's June 16 council meeting, Lorenzo Gonzalez offered a sentence shorter than many zoning footnotes. Amend Table 5.1, he said, “to prohibit data centers in all zoning districts.” Mayor Jane Hughson asked him to repeat it slowly. He did.

The sentence removed one mark from one cell in the proposal entering final reading: C*, a council-approved conditional-use designation in Heavy Industrial. Dashes filled every other proposed column. Four council members closed the last one; three wanted to keep it available for case-by-case review. The full development code then passed 70.

The timing is the point. San Marcos had already stopped one application path for the 199.49-acre Highlander proposal in February. The Texas Tribune reported no data-center proposal inside city limits at the end of June. The amendment was about the next application, not a project then pending before council.

Watch the record

The motion, the countercase and both votes

The official recording opens on Gonzalez's motion. The verified moments also include Hughson's argument for keeping the door open, Gonzalez's answer, the 43 amendment result and the 70 final package. The same offsets are available in the Hamlet meeting record.

Loading the verified moment at 2:46:42…

San Marcos, Texas · San Marcos City Council
City Council Regular Meeting2026-06-16

Select a verified moment. The recording will seek to the exact point; expand the verified context note for what happens around it.

The inline player uses excerpts cut from the city's official recording. The complete recording remains linked at the exact source time below.

Verified context

Gonzalez states the amendment. Mayor Jane Hughson asks him to repeat it slowly; he repeats: “Motion to amend Table 5.1 of the land use matrix to prohibit data centers in all zoning districts.”

Verified context

Hughson explains that a yes vote would prohibit data centers everywhere in the city. She says she wants to preserve council discretion in case the technology improves, then says she will vote no.

Verified context

Gonzalez agrees technology could change, but calls the current process less transparent. He argues the council could amend the development code again later if circumstances changed.

Verified context

The clerk announces that the amendment passed 4–3 and begins naming the dissenting members. The official city recap supplies the clean roll call because automated transcript recognition garbles the names.

Verified context

After the mayor clarifies that the final vote covers the proposed code plus amendments from both meetings, the clerk announces the 7–0 result.

At a Glance
4–3
data-center floor amendment
7–0
complete development code
199.49
acres in the rejected application
20K–35K
applicant-projected gallons per day; draft ceiling was 75K
What changed
The February vote ended one application path. The June amendment changed the rule for future data-center applications inside San Marcos zoning jurisdiction.
01 · The mechanism

The last proposed cell

The code proposal entering final reading would have admitted data centers only in Heavy Industrial, through a conditional-use permit approved by council. That was the path council directed in April and advanced on first reading May 5—not the city's preexisting effective code. The markup also carried setbacks, screening, a noise limit and a bar on potable water for cooling. Gonzalez's amendment did not delete that definition or those operating standards. It changed the proposed land-use matrix before final adoption.

That produces an odd-looking code: rules for a use that no zoning district admits. During the meeting, the city attorney explained that the specific prohibition in the matrix controls the broader language. The city was still preparing a consolidated code after the floor amendments at this reporting cutoff; its code-update page directs readers to the video for changes made from the dais.

The mechanism

One conditional cell became a dash

In the proposal entering final reading, C* meant a council-approved conditional use. A dash means the use is not admitted in that district.

On narrow screens, the summary stacks above; swipe the source table sideways to compare every column.

Data-center land-use matrix before and after the June 16 amendment
StatusOther zoning districtsHeavy Industrial
Proposal entering final reading — not admittedC* — council-approved conditional use
After 4–3 floor amendment — not admitted — not admitted
02 · The sequence

First one application path. Then the rule.

The Highlander SM One applications concerned 199.49 acres west of Francis Harris Lane. The tract included land inside San Marcos and land in its extraterritorial jurisdiction. No site plan was before the commission. Planning and Zoning recommended the land-use requests 62 after a long January hearing.

This was an entitlement hearing, not a construction-permit or site-plan hearing. In the preliminary record, an unsigned draft covenant proposed a 75,000-gallon daily ceiling and closed-loop cooling. The packet named Crystal Clear Special Utility District for water, Pedernales Electric Cooperative for power and San Marcos for wastewater. The applicant and supporters argued the project would add construction jobs and tax base beside an existing power plant; city GIS marked the tract outside the mapped floodplain, Edwards Aquifer Recharge Zone and San Marcos River Corridor. Those were proposals and attributed benefits—not findings about an approved or operating campus.

Council ended that route on February 17 by voting 52 to deny the Preferred Scenario Amendment. Because that prerequisite failed, the zoning case was not heard. The June prohibition therefore did not kill an active version of the January project.

The code rewrite followed its own track. On April 21, council backed the Heavy Industrial conditional route 6–1; Amanda Rodriguez's full prohibition failed 3–4. By June, Gonzalez had changed his vote. His amendment passed 4–3, then all seven members approved the larger code package. Agreement on the code did not erase disagreement over this use.

Five meetings, two tracks

One application path ended before the prohibition began

  1. 62 · Advisory approval

    Planning and Zoning recommended both land-use requests.

  2. 52 · Application path denied

    Council denied the prerequisite plan amendment; the zoning case was not heard.

  3. 6–1 for a conditional route; 3–4 on prohibition

    Council first chose Heavy Industrial with its own approval. A full prohibition failed.

  4. First reading · Code package advanced

    Council advanced the code package with the proposed Heavy Industrial conditional route.

  5. 43 · Every district closed

    Gonzalez's floor amendment changed the last C* to a dash.

  6. 70 · Complete code adopted

    The same council then approved Ordinance 2026-08 unanimously.

The boundary matters. Spectrum News reported that CloudBurst had already broken ground near the San Marcos–New Braunfels border, beyond San Marcos's zoning reach; this amendment does not stop it. Hays County's June 23 resolution paused only discretionary actions within the county's existing authority—it did not create countywide zoning. The Tribune reported on June 30 that no data-center project was then proposed inside San Marcos city limits.

03 · The numbers

A ceiling is not a forecast

The water argument accumulated a number large enough to travel on its own: 75,000 gallons per day. In the January packet, that figure appeared in an unsigned preliminary covenant. It was a ceiling, contingent on zoning approval that never arrived. The applicant's projected total campus use was lower: 20,000 to 35,000 gallons per day. Separately, the applicant proposed closed-loop, non-evaporative cooling.

Multiply the ceiling by 365 and it becomes 27,375,000 gallons. Apply the same arithmetic to the projection and the range is 7,300,000 to 12,775,000. Those annual figures describe arithmetic, not an operating campus. The site was unbuilt, and no consumption was measured.

Ceiling versus projection

The larger number was not expected use

Applicant figures for an unbuilt campus, measured in gallons per day.

Daily applicant water figures and their straight-line annualizations
QuantityDaily gallons365-day arithmetic
Draft ceiling75,00027,375,000
Projected range20,00035,0007,300,00012,775,000

Annual figures multiply each daily quantity by 365. They are not forecasts or measured consumption.

Power carried a similar risk of false precision. An earlier applicant pitch reported by the Austin Chronicle described five buildings at roughly 76 megawatts apiece—about 380 megawatts. The city packet contained no verified final load or utility design, so that number is not a final project specification. It remains an attributed early pitch.

From the January hearing

The commissioner who separated the two numbers

William Agnew asks why the draft covenant used 75,000 rather than the applicant's 35,000-gallon upper projection. The companion moment records the commission's 6–2 recommendation.

Loading the verified moment at 6:42:58…

San Marcos, Texas · San Marcos Planning and Zoning Commission
Planning and Zoning Commission Regular Meeting2026-01-13

Select a verified moment. The recording will seek to the exact point; expand the verified context note for what happens around it.

The inline player uses excerpts cut from the city's official recording. The complete recording remains linked at the exact source time below.

Verified context

Following the roll call on the Preferred Scenario Amendment recommendation, the recording secretary announces that the motion passed 6–2. The final minutes provide the authoritative spelling and member-level vote.

Verified context

Agnew distinguishes the draft 75,000-gallon daily allocation from the applicant's projected 20,000-to-35,000-gallon daily use and asks why the covenant is not written to the lower projected figure.

04 · The countercase

The matrix rule is adopted. Its legality remains untested.

Hughson's objection was not an endorsement of the rejected campus. She preferred the Heavy Industrial route because every application would still return to council for a public yes-or-no decision. If cooling or power technology improved, she argued, San Marcos would have preserved an option. Josh Paselk echoed her. Gonzalez answered that council could amend the code again when the facts changed.

“As long as it's still up to us, yes or no, I think we should at least allow the possibility.”

Mayor Jane Hughson · June 16, 2026

The next argument may take place outside council chambers. Texas Sen. Paul Bettencourt told The Texas Tribune that he planned to challenge San Marcos under state laws governing development moratoria and local regulation. Land-use lawyers quoted in the same report disputed whether a zoning amendment is the kind of moratorium that statute covers and pointed to San Marcos's home-rule zoning authority as a materially different posture from county moratoria. As of August 20, 2026, this reporting had identified no filed lawsuit or attorney-general opinion resolving the question.

The Tribune and Spectrum News described San Marcos as the first Texas city to prohibit data centers citywide. That is their statewide characterization, not the product of an exhaustive audit here. It also says nothing about county land beyond San Marcos's zoning reach.

The official recap and video show council adopted the matrix change; the pre-floor markup retained the data-center standards, but the city had not posted a consolidated Exhibit A by July 9. Under the adopted matrix, a new application has no listed zoning district unless the code changes. The January applicant never reached that line; four votes drew it for whoever comes next.

In the weeks after the June vote, the state took up the same question. On August 3, Gov. Greg Abbott directed the Public Utility Commission and ERCOT to audit the data-center projects moving through the grid-connection queue and to pause new approvals until that review is finished. State officials and reporting put the queue at roughly 474 gigawatts of pending requests, most of them data centers, and the Texas Tribune reported that fewer than one in ten data centers had complied with state power- and water-use reporting. Abbott, who had courted the industry, tied the pause to the same grid and water strain San Marcos council members cited in June. The audit does not override the city's zoning change, and it reaches only projects that connect to the grid, not those that supply their own power; Bettencourt has still filed no challenge. The water and power questions San Marcos answered inside its own code are now the state's to weigh.

Methodology

How we reconstructed the vote

Primary record: We checked the signed ordinance, city code-update chronology, official recaps, January and February records, the pre-floor-amendment code markup and both complete meeting videos. Every displayed moment was watched at its saved offset.

Sequence: The unit is one project path and one development-code process. The January advisory votes, February denial, April direction, June amendment and final code adoption are kept separate because they answered different questions.

Water arithmetic: The 75,000-gallon ceiling and 20,000–35,000-gallon projection come from applicant materials for an unbuilt site. Annual values multiply each daily amount by 365; they are not forecasts or measurements.

Limits: GovGraph supplied 15 reporting leads, not facts. The city had not posted a consolidated final exhibit incorporating every floor amendment, no final project power demand appears in the official packet, and the legal posture is current only through August 20, 2026. This analysis relies on public records.

Enjoying The District?

Get data-driven local government stories in your inbox every week. Free, no spam.

Open the June 16 council meeting on Hamlet
Verified Sources

Sources & Data

All claims in this article are grounded in public records, government data, and independent reporting.