Indianapolis committee hears warnings on data centers’ energy, water and community impacts as residents urge moratorium
Get AI-powered insights, summaries, and transcripts
SubscribeSummary
City sustainability committee heard presentations from national labs and local advocates about data centers’ energy and water demands, tax incentives that can shield developers, and community harms; residents urged a moratorium and the committee said it will pursue legal analysis and next steps.
Chairman Barth convened the Indianapolis City Environmental Sustainability Committee on Jan. 30 for an informational session about data centers, their environmental footprint and possible local policy responses. Presenters from environmental organizations and national laboratories outlined the scale of modern data centers and the policy choices facing city officials.
Rebecca DeColstein, climate and energy senior adviser at the Hoosier Environmental Council, told the committee that state incentives and limited statewide guidance have created a “wild west” for data center siting and that local governments are often left to respond. “We are operating today in sort of the wild west, without strong safeguards, without a real understanding from a policy perspective of these impacts,” she said, urging transparent public notice, independent impact studies and enforceable community protections.
Speakers described the energy and water scales that drive concern. Shannon Anderson of Earth Charter Indiana said recent U.S. data centers typically run on about 20–100 megawatts of critical load and that hyperscale facilities can be far larger; presenters noted Project Rainier as an example that would use roughly 2.2 gigawatts. HEC and Earth Charter presenters cited an AES integrated-resource planning analysis showing utility-scale additions (new gas plants and battery storage) are modeled once data-center demand reaches certain thresholds and warned that some costs can be passed to ratepayers.
Water impacts were another focal point. The presenters said large data centers can draw millions of gallons daily; they cited a LEAP-area project that would withdraw about 25,000,000 gallons daily, with roughly 8,000,000 gallons attributed to a data center component. Presenters recommended independent water- and pollution-modeling before approvals and suggested monitoring returned water for temperature and chemical contaminants.
Council members pressed presenters on definitional and regulatory approaches. Several councilors said cities could set local benchmarks (by acreage, megawatt thresholds, or water use) and use zoning or special-use processes to require additional public review. Committee members also discussed whether developers should be required to pay 100% of incremental transmission or generation costs; Rebecca DeColstein said some developers already agree to pay incremental infrastructure costs but that incentives and statutory floors at the state level complicate local leverage.
Public commenters were numerous and largely opposed to further development without stronger local safeguards. Councilor Jesse Brown told the meeting he “favors a total moratorium on data centers effective immediately,” and resident Rachel Woolverton said a petition to protect Eagle Creek had ‘‘over 14,000 signatures’’ calling for the mayor not to sign agreements that would send drinking water to the LEAP site. Speakers also raised specific local projects (including an American Tower rezoning in Pike Township), alleged inadequate prior notification of proposals, and described concerns about diesel backup generators, brownfield siting and disproportionate impacts on historically disinvested neighborhoods.
The committee did not take votes. Chairman Barth said the session was part of an ongoing process and that legal analysis and further policy work are forthcoming; Councilor Boots announced a related Parks Committee meeting next Thursday that will include an Eagle Creek/LEAP presentation. The meeting closed with the committee asking members of the public to remain engaged as proposed ordinances or guidance are developed.
No formal actions or votes were taken at the meeting; the committee described the session as educational and pledged to pursue follow-up analysis and draft policy options.
