Release notes

OPG-2

operator_group reassigned when the group name only occurs as a substring inside a word of the raw operator (e.g. 'vantage' in 'iAdvantage'), even if a sub-brand was recorded.

OPG-1

operator_group reassigned when the raw source operator is present, no operator_subbrand records a deliberate consolidation, and the raw operator (normalised: lower-case, legal suffixes and the generic words data/datacenter(s)/center(s)/centre(s)/group/holding(s)/the removed) shares no token with the group. New group = the existing group whose normalised name equals, contains, or (≥ 3 facilities) prefixes the raw name; else the raw operator without legal suffixes. 'uncertain' = the facility name matches the old group, not the new. Same-company pairs (acquisition / rebrand) are allowlisted.

MW-CAMPUS-1

Facilities of the same operator group within 2 km (or within 10 km when the figure comes from the same source page; single linkage) that carry the exact same it_load_mw (> 0) share one campus figure. Each keeps it_load_mw; mw_shared/mw_campus_n/mw_campus_id flag it; aggregates count it once per campus. campus id = 'campus:<operator-group-slug>:<MW>:<lowest dc_uid in the campus>'.

OPG-3

spelling variants of one operator merged (legal suffixes, generic words and country names ignored: 'NorthC Deutschland GmbH' -> 'NorthC Datacenters'); the most frequent spelling names the group.

STAT-1

status mapped to operational / under_construction / planned; the source text is kept in status_raw.

CITY-1

address residue removed from city strings ('Lisbon, , 2685' -> 'Lisbon') and empty comma parts removed from addresses.

GEO-2

facilities taken from an operator's website without a street address (address says 'undisclosed', or has no street number and the point sits within 1.5 km of a town centre) are marked geo_precision='municipality': the point is the town, not the site. Site-level context is not computed for them and hub indices leave them out.

SUB-1

a subsidiary that trades under its own brand keeps its own operator group (e.g. Ascenty); its owner is shown on the operator page when Wikidata records one. A brand whose sites now trade under the parent's name is grouped with the parent (e.g. Interxion sites named 'Digital Realty …').

DUP-2

an operator-website record carrying the same MW figure, from the same source page, as a mapped record of the same operator group within 5 km is the same campus; the mapped record is kept.

EX-1

PeeringDB's demo records ('PeeringDB Example Facility …', placed in Antarctica) are not facilities and are removed.

CONT-2

Australia is part of the Asia Pacific region (the release listed it as a region of its own while New Zealand and the Pacific were in Asia Pacific).

SENT-1

placeholder strings from the sources ('N/A', '-', 'unknown'…) in text fields are treated as not stated.

OPG-4

an OpenStreetMap record whose name starts with another operator group's name than its operator tag (e.g. 'Scala Datacenter' tagged Equinix) is flagged in the 'kept' list, not re-attributed, until a second source settles it.

LINK-1

a record that lists several buildings in its name (e.g. 'MRS1/2/3/4') is linked to the separate records of those buildings within 10 km; both are kept (the listing also stands for the building at its own address) and the facility panel says so.

DUP-1

the same building recorded twice (same operator group, <= 400 m, identical names or one's site codes contained in the other's, e.g. 'Equinix AM2' vs 'Equinix AM1/AM2'): the richer record is kept.

CONT-1

continent filled from the country: the majority region_continent among the release's records of that country; hand-mapped for countries with none (CONT_HAND).

⬇ CSV

⬇ CSV

⬇ CSV · continent fills (CONT-1) are counted above, not listed.

First 150 shown; the CSV has all 320.

• VPLS → kept under Evocative: The same PeeringDB record brands the facility 'Evocative Virginia (VA1)'; only the organisation name still reads VPLS.
• Entel S.A. - EntelNet → kept under Equinix: OPG-1 exception: measured values on this record are sourced from the group's own site (equinix.com).
• ITENOS GmbH → kept under NTT: The building at this address (Eschborner Landstraße 100) is NTT's Frankfurt 1 campus, and its measured values come from NTT's own page. The facility name comes from PeeringDB, where ITENOS lists its presence in that building.
• Forsythe Data Centers → kept under STACK Infrastructure: OPG-1 exception: measured values on this record are sourced from the group's own site (stackinfra.com).
• eircom Ltd → kept under Eir: eircom rebranded as eir (2015): same company.
• 4D Data Centres Ltd → kept under Redcentric: 4D Data Centres was acquired by Redcentric; OSM already tags the site as Redcentric.
• Amazon Web Services → kept under Amazon Web Services: Kept (DUP-1 building guard): 'AWS Asia Pacific (Sydney) Region Data Centre' is mapped as two separate building footprints 257 m apart in OpenStreetMap (dc_b56383bec66c4534 and dc_3b368278a4f94b6b); counted as two buildings.
• Amazon Web Services → kept under Amazon Web Services: Kept (DUP-1 building guard): 'AWS Asia Pacific (Sydney) Region Data Centre' is mapped as two separate building footprints 94 m apart in OpenStreetMap (dc_178a30a97d4e49cd and dc_64d8cecbef2b4fff); counted as two buildings.
• Stack Infrastructure → kept under STACK Infrastructure: Kept (DUP-1 building guard): 'Stack Infrastructure - POR03' is mapped as two separate building footprints 146 m apart in OpenStreetMap (dc_571c9b2aa4df4624 and dc_fa07b8f2741443e4); counted as two buildings.
• Stack Infrastructure → kept under STACK Infrastructure: Kept (DUP-1 building guard): 'Stack Infrastructure - POR03' is mapped as two separate building footprints 118 m apart in OpenStreetMap (dc_a6620d34aed2438a and dc_6203e9ecb0c4484b); counted as two buildings.
• Digital Realty → kept under Digital Realty: Kept (DUP-1 building guard): 'Ascenty SP3' is mapped as two separate building footprints 57 m apart in OpenStreetMap (dc_7106d90a581c48df and dc_a2470b17fe3c4e69); counted as two buildings.
• Digital Realty → kept under Digital Realty: Kept (DUP-1 building guard): 'Digital Realty PDX11 Data Center' is mapped as two separate building footprints 248 m apart in OpenStreetMap (dc_92bc7aa50eb54d85 and dc_275dcbd5c571491b); counted as two buildings.
• Flexential → kept under Flexential: Kept (DUP-1 building guard): 'Flexential Portland - Hillsboro 1' is mapped as two separate building footprints 120 m apart in OpenStreetMap (dc_0f52b4f099784880 and dc_448625ceabbd450f); counted as two buildings.
• Quality Technology Services → kept under QTS: Kept (DUP-1 building guard): 'QTS Manassas DC1' is mapped as two separate building footprints 51 m apart in OpenStreetMap (dc_e52aa36255e445cc and dc_955c1b4b7a1f46e3); counted as two buildings.
• Quality Technology Services → kept under QTS: Kept (DUP-1 building guard): 'QTS Ashburn Lockridge' is mapped as two separate building footprints 148 m apart in OpenStreetMap (dc_f78e5d4b132e4912 and dc_c5f05b4006854067); counted as two buildings.
• Quality Technology Services → kept under QTS: Kept (DUP-1 building guard): 'QTS Data Center - Hillsboro 2' is mapped as two separate building footprints 177 m apart in OpenStreetMap (dc_e9c6a8eb404440ee and dc_9ccaf59eb0ca4d74); counted as two buildings.
• Quality Technology Services → kept under QTS: Kept (DUP-1 building guard): 'QTS Data Center - Hillsboro 2' is mapped as two separate building footprints 177 m apart in OpenStreetMap (dc_ae943e8800294716 and dc_8bb71c32e3ca416c); counted as two buildings.
• Quality Technology Services → kept under QTS: Kept (DUP-1 building guard): 'QTS Data Center - Hillsboro 3' is mapped as two separate building footprints 243 m apart in OpenStreetMap (dc_477a1b65df514707 and dc_113eb12f00e04401); counted as two buildings.
• Microsoft → kept under Microsoft: Kept (DUP-1 building guard): 'AMS07' is mapped as two separate building footprints 99 m apart in OpenStreetMap (dc_b2495b4e373c4f6d and dc_4234b3ee00154876); counted as two buildings.
• Microsoft → kept under Microsoft: Kept (DUP-1 building guard): 'AMS06' is mapped as two separate building footprints 100 m apart in OpenStreetMap (dc_438cf15b90454fb2 and dc_c4a91a76fa2944b5); counted as two buildings.
• T5 Data Centers → kept under T5 Data Centers: Kept (DUP-1 building guard): 'T5@Cleveland' is mapped as two separate building footprints 58 m apart in OpenStreetMap (dc_d2a2f97b67d1483b and dc_29d393fa29a74228); counted as two buildings.
• Meta → kept under Meta: Kept (DUP-1 building guard): 'Facebook Fort Worth Datacenter' is mapped as two separate building footprints 369 m apart in OpenStreetMap (dc_ab8acfbd4a93438e and dc_dae386e86ab74010); counted as two buildings.
• Meta → kept under Meta: Kept (DUP-1 building guard): 'Meta Huntsville Data center' is mapped as two separate building footprints 306 m apart in OpenStreetMap (dc_1860b55b92014d0a and dc_b6165949ed6d4549); counted as two buildings.
• Meta → kept under Meta: Kept (DUP-1 building guard): 'Meta Gallatin Data Center' is mapped as two separate building footprints 332 m apart in OpenStreetMap (dc_9827c574e1084d0a and dc_7df6fe5a883942d0); counted as two buildings.
• Meta → kept under Meta: Kept (DUP-1 building guard): 'Meta Henrico Data Center' is mapped as two separate building footprints 379 m apart in OpenStreetMap (dc_59721573cf0f46e9 and dc_4422520f0dc14c1a); counted as two buildings.
• Meta → kept under Meta: Kept (DUP-1 building guard): 'Meta Eagle Mountain Data Center' is mapped as two separate building footprints 303 m apart in OpenStreetMap (dc_b23475ce859d4585 and dc_fba5cc3edbc14367); counted as two buildings.
• Meta → kept under Meta: Kept (DUP-1 building guard): 'Meta Sarpy Data center' is mapped as two separate building footprints 264 m apart in OpenStreetMap (dc_a2f674c172b643cf and dc_320976850dc04a39); counted as two buildings.
• Meta → kept under Meta: Kept (DUP-1 building guard): 'Meta Sarpy Data center' is mapped as two separate building footprints 317 m apart in OpenStreetMap (dc_dd113eb1c2c449d6 and dc_64262e3b2ea64339); counted as two buildings.
• Meta → kept under Meta: Kept (DUP-1 building guard): 'Meta Odense Data Center' is mapped as two separate building footprints 378 m apart in OpenStreetMap (dc_06dbd22b81fc4f47 and dc_9a7379a814f34911); counted as two buildings.
• Meta → kept under Meta: Kept (DUP-1 building guard): 'Metas datacenter i Luleå' is mapped as two separate building footprints 280 m apart in OpenStreetMap (dc_933900f64d764cf6 and dc_f720ed9b03b14ef8); counted as two buildings.
• Vantage Data Centers → kept under Vantage Data Centers: Kept (DUP-1 building guard): 'Vantage Berlin II (BER2)' is mapped as two separate building footprints 98 m apart in OpenStreetMap (dc_2c509c810f4f44d6 and dc_8932122ed5734d92); counted as two buildings.
• Pulsant → kept under Pulsant: Kept (DUP-1 building guard): 'Pulsant Edinburgh South Gyle SC-1' is mapped as two separate building footprints 76 m apart in OpenStreetMap (dc_c6568581a9184ef1 and dc_a87e32eda7f54074); counted as two buildings.
• Six Degrees → kept under Six Degrees: Kept (DUP-1 building guard): 'Six Degrees Data Centre' is mapped as two separate building footprints 76 m apart in OpenStreetMap (dc_118b59f35c9243e2 and dc_326436ce56754451); counted as two buildings.
• Global Switch → kept under Global Switch: Kept (DUP-1 building guard): 'Global Switch Frankfurt' is mapped as two separate building footprints 71 m apart in OpenStreetMap (dc_42000fd86aa34fa5 and dc_8b63ad4348a842b2); counted as two buildings.
• SFR → kept under SFR: Kept (DUP-1 building guard): 'Site technique SFR' is mapped as two separate building footprints 302 m apart in OpenStreetMap (dc_193dff84e9f14de3 and dc_5013d5f7381341f2); counted as two buildings.
• OPCORE → kept under OPCORE: Kept (DUP-1 building guard): 'OPCORE DC6-6' is mapped as two separate building footprints 129 m apart in OpenStreetMap (dc_e469c4643e4440b8 and dc_b7c8266f599a468d); counted as two buildings.
• Verne Global → kept under Verne Global: Kept (DUP-1 building guard): 'Verne Gagnaver' is mapped as two separate building footprints 95 m apart in OpenStreetMap (dc_9b8b69781b214494 and dc_488c23437a4d4a17); counted as two buildings.
• Rostelecom → kept under Rostelecom: Kept (DUP-1 building guard): 'Rostelecom Nizhny Novgorod' is mapped as two separate building footprints 51 m apart in OpenStreetMap (dc_c9f3734bc2c74749 and dc_de431a5f13104798); counted as two buildings.
• Rowan Green Data LLC → kept under Rowan Green Data LLC: Kept (DUP-1 building guard): 'Percheron DC' is mapped as two separate building footprints 143 m apart in OpenStreetMap (dc_5323813ac3e9440e and dc_bc64359aed104697); counted as two buildings.
• Rowan Green Data LLC → kept under Rowan Green Data LLC: Kept (DUP-1 building guard): 'Percheron DC' is mapped as two separate building footprints 133 m apart in OpenStreetMap (dc_b7d350597c3b4006 and dc_7e9beb510a7d41fe); counted as two buildings.
• ANZ → kept under ANZ: Kept (DUP-1 building guard): 'ANZ Data Centre' is mapped as two separate building footprints 62 m apart in OpenStreetMap (dc_965b482e6e3045a3 and dc_c6e839e3098548cb); counted as two buildings.
• Sungard AS → kept under Sungard AS: Kept (DUP-1 building guard): 'Sungard AS IT' is mapped as two separate building footprints 72 m apart in OpenStreetMap (dc_fdbbc861d6d74202 and dc_b4ca35c0e9d141e4); counted as two buildings.
• ePLDT → kept under ePLDT: Flagged (OPG-4): the OpenStreetMap record is named 'VITRO Parañaque' but tagged operator=ePLDT; the name points to Vitro Inc.. Not re-attributed without a second source.
• Equinix → kept under Equinix: Flagged (OPG-4): the OpenStreetMap record is named 'Scala Datacenter' but tagged operator=Equinix; the name points to Scala Data Centers. Not re-attributed without a second source.
• DigiCo REIT → kept under DigiCo REIT: Flagged (OPG-4): the OpenStreetMap record is named 'Global Switch Sydney East Data Centre' but tagged operator=DigiCo REIT; the name points to Global Switch. Not re-attributed without a second source.