How every number here is produced
This Atlas is a modelling exercise built on a documented parameter set. Nothing in it is metered. The value of the work lies in the parameters being explicit, the formulas being simple, and the limitations being stated before the findings.
India and Singapore are covered nationally. The USA, UK, Ireland, Germany and Brazil are each represented by ONE flagship cluster (Northern Virginia, London/Slough, Dublin, Frankfurt Rhein-Main, São Paulo State) — these rows are NOT national totals.
Structural absences: no Scope 1 emissions, no Scope 3 or embodied carbon, no measured noise, no metered energy or water, no systematic complaint register, and no sub-national grid emission factors. These are not gaps to be filled by interpretation — they are boundaries on what this dataset can support.
The full derivation chain
Nine expressions produce every environmental quantity in the Atlas.
Capacity_MW × 8,760 h × Load_Factor × PUEEnergy_MWh × WUEWater_m3 × Water_Stress_IndexEnergy_MWh × Grid_CO2_FactorEnergy_MWh × (1 − Renewable_Matched) × Grid_CO2_FactorEnergy_MWh ÷ 8,760 (annual-average thermal rejection rate)Capacity-band source level with distance attenuation to 50 mPercentile rank of the pillar indicator across all 1,098 recordsWeighted mean of the six pillar scores (equal weights by default)Read these before citing any figure
Each dimension fails in its own specific way.
Location-based Scope 2 only, using national average grid factors. Scope 1 and Scope 3 are absent entirely; sub-national grid variation is not represented.
Every energy value is MODELLED (Capacity × 8,760 × Load Factor × PUE). No facility in this dataset is metered.
Waste heat is an energy-balance proxy (an annual average rejection RATE), never a measured local temperature rise. Cooling technology is inferred from the water ratio.
Water = Energy × WUE and covers ON-SITE cooling only; it excludes upstream water embodied in electricity generation. Water stress is an area-level band, not a coordinate-level lookup.
THE WEAKEST PILLAR IN THIS WORKBOOK. Noise is a capacity-based engineering proxy and setback is a land-use class band. Neither has been measured at any facility — use for screening only.
Zero documented complaints does not mean zero complaints occurred — it means no complaint record was located in the sources consulted.
Every benchmark value and its justification
98 documented parameters — PUE bands, WUE bands, grid factors, noise source levels, employment ratios and population densities.
| Parameter | Type | Applies to | Value | Unit | Source / justification |
|---|---|---|---|---|---|
| Grid emission factor | Country parameter | India | 0.710 | tCO2e/MWh | CEA CO2 Baseline Database for the Indian Power Sector (weighted average operating margin ~0.71 tCO2/MWh) |
| Grid renewable share | Country parameter | India | 22.000 | % | Ember / CEA generation mix ~2024 (renewables incl. large hydro as % of generation) |
| Benchmark PUE | Country parameter | India | 1.600 | ratio | Uptime Institute Global Data Center Survey - Asia-Pacific regional average; same value as the source workbook |
| Benchmark WUE | Country parameter | India | 2.150 | m3/MWh | Source workbook India WUE (2.15 m3/MWh), derived from Indian colocation disclosures |
| Grid emission factor | Country parameter | USA | 0.386 | tCO2e/MWh | US EPA eGRID national annual average generation emission factor |
| Grid renewable share | Country parameter | USA | 23.000 | % | EIA / Ember US generation mix ~2024 |
| Benchmark PUE | Country parameter | USA | 1.500 | ratio | Uptime Institute Global Data Center Survey - North America regional average |
| Benchmark WUE | Country parameter | USA | 0.374 | m3/MWh | LBNL 2024 US Data Center Energy Usage Report: 17.4 bn gal direct cooling water / 176 TWh (2023) |
| Grid emission factor | Country parameter | UK | 0.207 | tCO2e/MWh | UK DESNZ/DEFRA Greenhouse Gas Conversion Factors, grid electricity generation factor |
| Grid renewable share | Country parameter | UK | 45.000 | % | DESNZ Energy Trends / Ember GB generation mix ~2024 |
| Benchmark PUE | Country parameter | UK | 1.500 | ratio | Uptime Institute Global Data Center Survey - Europe regional average |
| Benchmark WUE | Country parameter | UK | 1.000 | m3/MWh | Climate-based WUE proxy carried from the source workbook - WEAK EVIDENCE, no primary UK national figure |
| Grid emission factor | Country parameter | Ireland | 0.280 | tCO2e/MWh | SEAI Energy in Ireland - electricity CO2 intensity |
| Grid renewable share | Country parameter | Ireland | 40.000 | % | EirGrid / SEAI renewable share of electricity generation ~2024 |
| Benchmark PUE | Country parameter | Ireland | 1.400 | ratio | Cool-maritime-climate benchmark; free-cooling-dominant Dublin hyperscale fleet |
| Benchmark WUE | Country parameter | Ireland | 0.800 | m3/MWh | Cool-climate WUE proxy (free cooling reduces evaporative demand) - MODELLED, no Irish national figure |
| Grid emission factor | Country parameter | Germany | 0.380 | tCO2e/MWh | German Environment Agency (UBA) specific CO2 emissions of the German electricity mix |
| Grid renewable share | Country parameter | Germany | 55.000 | % | AGEB / Fraunhofer ISE renewable share of public net electricity generation ~2024 |
| Benchmark PUE | Country parameter | Germany | 1.450 | ratio | Uptime Institute Europe regional average adjusted for the Frankfurt free-cooling window |
| Benchmark WUE | Country parameter | Germany | 0.900 | m3/MWh | Temperate-climate WUE proxy - MODELLED, no German national data-centre figure |
| Grid emission factor | Country parameter | Brazil | 0.110 | tCO2e/MWh | MCTI / ONS Brazilian national grid emission factor (hydro-dominant system) |
| Grid renewable share | Country parameter | Brazil | 87.000 | % | ONS / EPE Brazilian generation mix ~2024 |
| Benchmark PUE | Country parameter | Brazil | 1.700 | ratio | Source workbook Brazil PUE (1.7) - warm-humid climate colocation benchmark |
| Benchmark WUE | Country parameter | Brazil | 2.150 | m3/MWh | Source workbook Brazil WUE (2.15 m3/MWh) |
| Grid emission factor | Country parameter | Singapore | 0.400 | tCO2e/MWh | Singapore EMA grid emission factor (gas-dominant system) |
| Grid renewable share | Country parameter | Singapore | 5.000 | % | EMA Singapore Energy Statistics - solar share of generation |
| Benchmark PUE | Country parameter | Singapore | 1.400 | ratio | IMDA Green Data Centre Standard / Singapore new-build PUE requirement (<=1.3 for new; 1.4 fleet benchmark) |
| Benchmark WUE | Country parameter | Singapore | 2.000 | m3/MWh | Singapore regulatory WUE CEILING (<=2.0 m3/MWh) - a ceiling, not a measured mean; likely overstates actual use |
| Fleet PUE | Operator disclosure | 1.090 | ratio | Google Environmental Report - fleet-wide average annual PUE, average WUE and carbon-free energy percentage | |
| Fleet WUE | Operator disclosure | 0.990 | m3/MWh | Google Environmental Report - fleet-wide average annual PUE, average WUE and carbon-free energy percentage | |
| Matched renewable / CFE | Operator disclosure | 64.000 | % | Google Environmental Report - fleet-wide average annual PUE, average WUE and carbon-free energy percentage | |
| Fleet PUE | Operator disclosure | Meta | 1.090 | ratio | Meta Sustainability Report - fleet PUE/WUE and 100% renewable-energy matching claim |
| Fleet WUE | Operator disclosure | Meta | 0.200 | m3/MWh | Meta Sustainability Report - fleet PUE/WUE and 100% renewable-energy matching claim |
| Matched renewable / CFE | Operator disclosure | Meta | 100.000 | % | Meta Sustainability Report - fleet PUE/WUE and 100% renewable-energy matching claim |
| Fleet PUE | Operator disclosure | Microsoft | 1.180 | ratio | Microsoft Environmental Sustainability Report - design PUE/WUE and 100% renewable purchase claim |
| Fleet WUE | Operator disclosure | Microsoft | 0.300 | m3/MWh | Microsoft Environmental Sustainability Report - design PUE/WUE and 100% renewable purchase claim |
| Matched renewable / CFE | Operator disclosure | Microsoft | 100.000 | % | Microsoft Environmental Sustainability Report - design PUE/WUE and 100% renewable purchase claim |
| Fleet PUE | Operator disclosure | Amazon AWS | 1.150 | ratio | AWS Sustainability - global WUE 0.18 L/kWh and 100% renewable-matched claim |
| Fleet WUE | Operator disclosure | Amazon AWS | 0.180 | m3/MWh | AWS Sustainability - global WUE 0.18 L/kWh and 100% renewable-matched claim |
| Matched renewable / CFE | Operator disclosure | Amazon AWS | 100.000 | % | AWS Sustainability - global WUE 0.18 L/kWh and 100% renewable-matched claim |
| Fleet PUE | Operator disclosure | Equinix | 1.420 | ratio | Equinix Sustainability Report - global portfolio PUE and renewable-coverage percentage |
| Fleet WUE | Operator disclosure | Equinix | — | m3/MWh | Equinix Sustainability Report - global portfolio PUE and renewable-coverage percentage |
| Matched renewable / CFE | Operator disclosure | Equinix | 96.000 | % | Equinix Sustainability Report - global portfolio PUE and renewable-coverage percentage |
| Fleet PUE | Operator disclosure | Digital Realty | 1.450 | ratio | Digital Realty ESG Report - global portfolio PUE and renewable-energy coverage |
| Fleet WUE | Operator disclosure | Digital Realty | — | m3/MWh | Digital Realty ESG Report - global portfolio PUE and renewable-energy coverage |
| Matched renewable / CFE | Operator disclosure | Digital Realty | 65.000 | % | Digital Realty ESG Report - global portfolio PUE and renewable-energy coverage |
| Fleet PUE | Operator disclosure | STT GDC India | 1.500 | ratio | STT GDC India sustainability disclosures - India portfolio design PUE |
| Fleet WUE | Operator disclosure | STT GDC India | — | m3/MWh | STT GDC India sustainability disclosures - India portfolio design PUE |
| Matched renewable / CFE | Operator disclosure | STT GDC India | — | % | STT GDC India sustainability disclosures - India portfolio design PUE |
| Fleet PUE | Operator disclosure | CtrlS Datacenters | 1.420 | ratio | CtrlS published design PUE for its Indian Tier-IV fleet |
| Fleet WUE | Operator disclosure | CtrlS Datacenters | — | m3/MWh | CtrlS published design PUE for its Indian Tier-IV fleet |
| Matched renewable / CFE | Operator disclosure | CtrlS Datacenters | — | % | CtrlS published design PUE for its Indian Tier-IV fleet |
| Fleet PUE | Operator disclosure | Yotta Data Services | 1.500 | ratio | Yotta NM1 published facility PUE (datacentermap facility specification) |
| Fleet WUE | Operator disclosure | Yotta Data Services | — | m3/MWh | Yotta NM1 published facility PUE (datacentermap facility specification) |
| Matched renewable / CFE | Operator disclosure | Yotta Data Services | — | % | Yotta NM1 published facility PUE (datacentermap facility specification) |
| Fleet PUE | Operator disclosure | AirTrunk | 1.250 | ratio | AirTrunk published design PUE for its APAC hyperscale fleet |
| Fleet WUE | Operator disclosure | AirTrunk | — | m3/MWh | AirTrunk published design PUE for its APAC hyperscale fleet |
| Matched renewable / CFE | Operator disclosure | AirTrunk | — | % | AirTrunk published design PUE for its APAC hyperscale fleet |
| Operational IT load | Market capacity anchor | IN-Mumbai Metropolitan Region | 595.000 | MW | Cushman & Wakefield India Data Centre Update H1 2025 - Mumbai metro operational IT load (~53% of national) |
| Operational IT load | Market capacity anchor | IN-Chennai | 191.000 | MW | Cushman & Wakefield India Data Centre Update H1 2025 - Chennai operational IT load |
| Operational IT load | Market capacity anchor | IN-Delhi NCR | 146.000 | MW | Cushman & Wakefield India Data Centre Update H1 2025 - Delhi-NCR operational IT load |
| Operational IT load | Market capacity anchor | IN-Pune | 112.000 | MW | Cushman & Wakefield India Data Centre Update H1 2025 - Pune operational IT load |
| Operational IT load | Market capacity anchor | IN-Hyderabad | 152.000 | MW | Residual of the Cushman & Wakefield national total (1,280 MW, H1 2025) after the six named metros - DERIVED, not directly reported |
| Operational IT load | Market capacity anchor | IN-Bengaluru | 76.000 | MW | Cushman & Wakefield India Data Centre Update H1 2025 - Bengaluru operational IT load |
| Operational IT load | Market capacity anchor | IN-Kolkata | 110.000 | MW | Built up from facility-level disclosures (NTT Kolkata 1 = 40 MW; STT Kolkata DC2 = 34 MW) plus six further operating facilities. The Cushman & Wakefield city figure of 8 MW is irreconcilable with these two disclosures alone and is therefore NOT used - see the 62_QC_Reconciliation sheet |
| Operational IT load | Market capacity anchor | IN-Other India | 25.000 | MW | Modelled residual for Ahmedabad/Gandhinagar, Kochi, Jaipur, Visakhapatnam, Coimbatore, Indore and Nashik - LOW CONFIDENCE |
| Operational IT load | Market capacity anchor | US-Northern Virginia | 4,000.000 | MW | Northern Virginia (Loudoun + Prince William + Fairfax) commissioned data-centre IT load, ~4 GW class, per Dominion Energy connected-load reporting and market trackers |
| Operational IT load | Market capacity anchor | UK-London & Slough | 1,300.000 | MW | Greater London / Slough Trading Estate operational IT load, ~1.3 GW class, per UK FLAP-D market trackers |
| Operational IT load | Market capacity anchor | IE-Dublin | 950.000 | MW | Dublin metropolitan operational data-centre IT load, ~0.95 GW class; EirGrid reports data centres at ~21% of national metered electricity demand |
| Operational IT load | Market capacity anchor | DE-Frankfurt Rhein-Main | 950.000 | MW | Frankfurt/Rhein-Main operational IT load, ~0.95 GW class, the largest FLAP-D market |
| Operational IT load | Market capacity anchor | BR-Sao Paulo State | 600.000 | MW | Sao Paulo state operational IT load, ~0.6 GW class (Ascenty, Scala, ODATA, Equinix, Microsoft) |
| Operational IT load | Market capacity anchor | SG-Singapore | 1,400.000 | MW | Singapore national operational IT load ~1.4 GW; consistent with the source workbook's 2024 Singapore capacity value |
| Relative IT load | Facility class weight | HYPERSCALE | 30.000 | unitless | Judgement-based ratio used only to distribute a market total across facilities; calibrated so market sums reconcile to the published anchor. |
| Relative IT load | Facility class weight | WHOLESALE | 12.000 | unitless | Judgement-based ratio used only to distribute a market total across facilities; calibrated so market sums reconcile to the published anchor. |
| Relative IT load | Facility class weight | COLO_MID | 6.000 | unitless | Judgement-based ratio used only to distribute a market total across facilities; calibrated so market sums reconcile to the published anchor. |
| Relative IT load | Facility class weight | COLO_SMALL | 1.500 | unitless | Judgement-based ratio used only to distribute a market total across facilities; calibrated so market sums reconcile to the published anchor. |
| IT-load utilisation | Load factor | HYPERSCALE | 0.800 | fraction | IT-load utilisation factors. Hyperscale 0.80 reflects operator-reported high average utilisation; colocation 0.60-0.65 reflects Indian and European colocation occupancy and diversity factors reported by JLL/CBRE (India vacancy ~4-8%, but contracted-vs-drawn load is lower). LBNL uses 0.50 for whole-fleet facility power; that value is retained for the smallest/enterprise class. |
| IT-load utilisation | Load factor | WHOLESALE | 0.650 | fraction | IT-load utilisation factors. Hyperscale 0.80 reflects operator-reported high average utilisation; colocation 0.60-0.65 reflects Indian and European colocation occupancy and diversity factors reported by JLL/CBRE (India vacancy ~4-8%, but contracted-vs-drawn load is lower). LBNL uses 0.50 for whole-fleet facility power; that value is retained for the smallest/enterprise class. |
| IT-load utilisation | Load factor | COLO_MID | 0.600 | fraction | IT-load utilisation factors. Hyperscale 0.80 reflects operator-reported high average utilisation; colocation 0.60-0.65 reflects Indian and European colocation occupancy and diversity factors reported by JLL/CBRE (India vacancy ~4-8%, but contracted-vs-drawn load is lower). LBNL uses 0.50 for whole-fleet facility power; that value is retained for the smallest/enterprise class. |
| IT-load utilisation | Load factor | COLO_SMALL | 0.500 | fraction | IT-load utilisation factors. Hyperscale 0.80 reflects operator-reported high average utilisation; colocation 0.60-0.65 reflects Indian and European colocation occupancy and diversity factors reported by JLL/CBRE (India vacancy ~4-8%, but contracted-vs-drawn load is lower). LBNL uses 0.50 for whole-fleet facility power; that value is retained for the smallest/enterprise class. |
| Share of ultimate capacity energised in 2026 | Status energisation factor | OP | 1.000 | fraction | Operational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity. |
| Share of ultimate capacity energised in 2026 | Status energisation factor | UC | 0.350 | fraction | Operational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity. |
| Share of ultimate capacity energised in 2026 | Status energisation factor | AN | 0.000 | fraction | Operational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity. |
| Share of ultimate capacity energised in 2026 | Status energisation factor | PL | 0.000 | fraction | Operational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity. |
| Share of ultimate capacity energised in 2026 | Status energisation factor | UNK | 0.500 | fraction | Operational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity. |
| Nearest residential receptor | Residential setback band | DENSE_URBAN | 60.000 | m | Land-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning). |
| Nearest residential receptor | Residential setback band | URBAN_INDUSTRIAL | 150.000 | m | Land-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning). |
| Nearest residential receptor | Residential setback band | SUBURBAN_ITPARK | 300.000 | m | Land-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning). |
| Nearest residential receptor | Residential setback band | PERI_URBAN | 800.000 | m | Land-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning). |
| Nearest residential receptor | Residential setback band | RURAL | 2,000.000 | m | Land-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning). |
| Community sensitivity weight | Land-use sensitivity | DENSE_URBAN | 1.000 | 0-1 | Judgement weight used in Pillar 5. |
| Community sensitivity weight | Land-use sensitivity | URBAN_INDUSTRIAL | 0.600 | 0-1 | Judgement weight used in Pillar 5. |
| Community sensitivity weight | Land-use sensitivity | SUBURBAN_ITPARK | 0.450 | 0-1 | Judgement weight used in Pillar 5. |
| Community sensitivity weight | Land-use sensitivity | PERI_URBAN | 0.300 | 0-1 | Judgement weight used in Pillar 5. |
| Community sensitivity weight | Land-use sensitivity | RURAL | 0.150 | 0-1 | Judgement weight used in Pillar 5. |
| Boundary noise at ~50 m | Noise model | All | 50 + 10*log10(MW), clipped 45-85 | dB(A) | Engineering proxy anchored to the 60 dB(A) Prince William County (Virginia) ordinance threshold that residents report data-centre noise exceeding. |
| Population within 1 km / 5 km | Population model | All | density*pi*1 ; density*pi*25*0.60 | persons | Area density band times circle area, with a 0.60 radial decay factor at 5 km. NOT a raster zonal statistic. |
| Permanent roles | Employment model | All | 5 per MW | FTE | Industry rule of thumb; Confidence 1. |
Methodology notes as documented by the authors
Reproduced verbatim from the workbook's methodology sheet.
METHODOLOGY, FORMULAS, ASSUMPTIONS AND LIMITS
1. DATA ARCHITECTURE (layers, in build order)
L0 Raw preserved - the supplied workbook, byte-for-byte, sheets 70-73. Never modified, never overwritten.
L1 Entity resolution - individual facilities identified from operator listings and market directories,
deduplicated by (operator, facility name, area). Multi-building campuses are carried as a
CAMPUS parent row plus child FACILITY rows; the parent is excluded from every sum so that
capacity is never double counted.
L2 Geospatial - each facility mapped to one of 283 reference AREAS (industrial estate / business park /
suburb) carrying coordinates, land-use class, resident density band, basin water-stress
score and mean annual temperature. Sheet 52.
L3 Capacity - reported where published; otherwise allocated from a documented market total. Section 3.
L4 Indicators - the six pillars' underlying quantities, derived from L3 and the benchmark parameters
in sheet 51. Sheets 11-16.
L5 Normalisation - indicators rescaled 0-1 across the whole facility population. Section 4.
L6 Pillar and composite scores, risk classes, sensitivity. Sheets 20-21.
L7 Clusters and aggregates - every aggregate is a SUM or MEDIAN of L3/L4 facility values. Sheets 30-34.
L8 Time series - the 2026 fleet back-cast to 2020. Section 6. Sheets 40-41.
L9 Provenance and quality - sheets 50, 60, 61, 62.
2. EVIDENCE TAXONOMY (inherited from the supplied workbook, extended)
Reported - taken directly from an operator disclosure, regulator, government dataset or facility specification.
Derived - arithmetic on other values in this workbook (e.g. waste heat = annual energy / 8,760).
Modelled - produced by an explicit documented formula anchored to at least one real, cited data point.
Allocated - a documented market or portfolio total distributed across facilities by a stated weighting rule.
Proxy - a real observation from a different scale (area, city, country, operator fleet) used because no
site-specific figure exists. The scale mismatch is the limitation.
Not Available - no value could be established. Left blank, and flagged in 61_Missingness_Matrix.
CONFIDENCE SCALE (as specified in the brief)
5 Directly reported or measured by the operator or a government body FOR THAT FACILITY.
4 Highly credible secondary source, or an operator fleet figure applied to that operator's own site.
3 Reliable estimate from a documented methodology.
2 Weak or incomplete evidence - typically an area-level or class-level band.
1 Inference or highly uncertain estimate.
0 No evidence.
Record_Confidence is the mean of the field confidences for capacity, PUE, WUE, coordinates, status, year and the
two context fields. It is a summary, not a substitute for the per-field confidence columns.
3. CAPACITY METHOD (the single most consequential assumption in this workbook)
Facilities with a published capacity keep it (Evidence_Type = Reported, Confidence 4).
For every other facility in a market:
Capacity_Ultimate_MW = (Market_Anchor_MW - reported capacity in that market)
x Class_Weight(facility) / SUM over the market of [Class_Weight x Energisation_Factor]
Capacity_2026_MW = Capacity_Ultimate_MW x Energisation_Factor(status)
Class weights: Hyperscale 30, Wholesale/purpose-built colocation 12, Mid-tier colocation 6, Small/edge/enterprise 1.5.
Energisation factors: Operational 1.00, Under construction 0.35, Announced 0.00, Planned 0.00.
Market anchors and their sources are in 51_Benchmarks_Reference. This construction guarantees that the facility
records sum back to the published market total, which is exactly what makes the aggregates auditable - and it
also means an individual facility's MW figure is an ALLOCATION and should not be quoted as that site's capacity.
4. INDICATOR FORMULAS
Energy_MWh = Capacity_2026_MW x 8,760 h x Load_Factor(class) x PUE
Energy_Intensity = 8,760 x Load_Factor x PUE (MWh per MW of IT capacity per year)
Water_m3 = Energy_MWh x WUE (1 L/kWh == 1 m3/MWh)
WS_Weighted_Water = Water_m3 x (basin water-stress score / 5)
CO2_Location_t = Energy_MWh x grid emission factor
CO2_Market_t = Energy_MWh x grid factor x (1 - operator matched-renewable %) [only where the operator publishes one]
Waste_Heat_MW_th = Energy_MWh / 8,760 (energy-balance proxy: essentially all electricity leaves as heat)
Heat_Island_Proxy = Waste_Heat_MW_th x resident density / 1,000
Noise_dB(A) @ ~50 m = 50 + 10 x log10(Capacity_MW), clipped to [45, 85]
Engineering proxy only. Anchored so that a ~30 MW site returns ~65 dB(A), consistent with the
60 dB(A) county ordinance threshold that Prince William County (Virginia) residents report
data-centre noise routinely exceeding.
Residential_Distance_m = land-use class band (Dense urban 60, Urban industrial 150, Suburban IT park 300,
Peri-urban 800, Rural 2,000). The dense-urban band is anchored to the Virginia JLARC 2024
finding that ~1/3 of Virginia data centres sit within 200 ft (61 m) of residential zoning.
Population_1km = resident density x pi x 1 km^2
Population_5km = resident density x pi x 25 km^2 x 0.60 (0.60 = radial density-decay factor)
Jobs_Estimate = Capacity_MW x 5 permanent roles per MW (industry rule of thumb, Confidence 1)
Infrastructure_Pressure = facility capacity as a percentage of its cluster's total capacity
5. SIX-PILLAR INDEX
Direction: for every indicator, HIGHER = GREATER environmental or community impact.
Normalisation: volume indicators (energy, water, CO2, waste heat, population, capacity) are min-max scaled on
log10(1+x) because they span five orders of magnitude; ratio and score indicators (PUE, WUE, water stress,
temperature, noise, land-use sensitivity, regulatory flags) are min-max scaled on the raw value. Scaling is
computed across the whole facility population so scores are comparable between countries.
Pillar score = weighted sum of its normalised sub-indicators x 100. Sub-indicator weights are printed in full
on 20_SixPillar_Scores. Composite = weighted mean of the six pillars; the default scheme is equal weights (1/6).
Risk class = quartiles of the composite across all 1098 facilities: Low <54.1, Medium <59.6, High <65.7, Very High above.
KNOWN PROPERTY OF THIS INDEX, STATED PLAINLY: four of the six pillars are dominated by LOCATION CONTEXT (water
stress, climate, density, land use, regulation) and only two by SCALE. A small facility in a dense, water-stressed
city therefore outranks a very large facility in a cool, low-stress rural location. That is a deliberate design
choice for a community-impact index, but it means the composite must NOT be read as 'biggest environmental
footprint'. For footprint, use the absolute columns in sheets 11-16 and the capacity-weighted aggregates.
6. TIME SERIES BACK-CAST (2020-2026)
Operational facilities are ordered by a vintage proxy (hyperscale greenfield later; lower facility numbering
earlier) and assigned a first-power year such that the cumulative fleet capacity reproduces the national capacity
growth curve that the SUPPLIED workbook already sources. Only the SHAPE of that curve is used, never its level,
because this workbook covers one flagship cluster per non-Indian country rather than the whole nation.
Under-construction, announced and planned facilities are given indicative first-power years of 2027, 2028 and 2029.
Every back-cast year carries Confidence 1. Where a real commissioning year was found it overrides the model.
7. SOURCE HIERARCHY APPLIED (highest first)
1 Government datasets and regulatory filings 2 Operator sustainability reports and official disclosures
3 Planning applications and environmental impact assessments 4 Utility and grid-operator information
5 Official company announcements 6 Peer-reviewed literature 7 Established industry datasets and market
trackers 8 Credible institutional research 9 News reporting (labelled wherever used).
Where sources conflict, the higher tier wins and the conflict is recorded in 62_QC_Reconciliation rather than
silently resolved. The Kolkata capacity conflict is the worked example.
8. WHAT THIS WORKBOOK STILL CANNOT TELL YOU
* Any individual facility's actual metered electricity or water consumption.
* Any individual facility's measured noise emission or its measured setback to the nearest dwelling.
* Actual population counts within 1 km (this needs a GHSL/WorldPop raster zonal statistic against real coordinates).
* Whether a community has in fact objected to a specific Indian, Brazilian, Singaporean or German facility.
* On-site generation, storage, heat reuse contracts or water-recycling rates at any site.
The single highest-value next step is to replace the AREA centroids with rooftop coordinates and run a real
GHSL population zonal statistic and a real WRI Aqueduct basin lookup; that alone would move Pillars 2, 5 and 6
from Confidence 1-2 to Confidence 3-4.
How to cite this Atlas responsibly
State that figures are modelled, and give the parameter basis (PUE, WUE, grid factor) alongside any total.
Use intensity metrics for comparison and absolute metrics for footprint — they answer different questions.
Name the weighting scheme whenever you quote a composite score or rank.
Treat the USA, UK, Ireland, Germany or Brazil rows as national totals — each is one flagship cluster.
Use coordinates or setback distances for property-level, boundary or receptor-level conclusions.
Read zero documented complaints as evidence that no complaints exist.