Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Data Centers And Infrastructure topic
No spam. Unsubscribe anytime.
Belmont panel raises data‑center, water and noise concerns and considers community‑benefit tools for large projects
Summary
During the LDC kickoff, councilmembers flagged data centers and other large uses as potential regulatory gaps—raising water consumption, noise and wastewater as issues—and suggested community‑benefit requirements and performance standards be considered in the code update.
Councilmembers used the facilitated discussion to ask whether the Land Development Code should anticipate emerging or uncommon uses such as data centers, large energy storage or other industrial operations that can have outsized utility and environmental impacts.
One participant said, "The biggest challenge communities are facing with some of these large data center developers or hyperscalers is water consumption," and another noted that industry responses have included closed‑loop cooling systems to reduce water use. Consultants suggested the diagnostic examine best practices from other communities and consider adding performance standards for water and wastewater, noise limits and façade/buffer requirements for large facilities.
Speakers also discussed whether the LDC could include community‑benefit provisions — for example, directing developer contributions toward streetscape, affordable housing funds or hiring local labor — as an offset for impacts from large projects. Consultants said some cities tie community benefits into conditional approvals or grant incentives; they will research models to present in the code audit.
Participants raised practical constraints: staff cautioned the city should not require technical materials it cannot review, and councilmembers noted utility triggers (e.g., high water use) and noise ordinances may fall under different regulatory codes and departments. The consultants said they will coordinate with technical staff to identify feasible performance standards and potential regulatory overlaps.
No formal regulatory language was adopted; the discussion was recorded as direction for the diagnostic and subsequent drafting phases.
