District47.US

ATLAS Data Centers — 1,698 U.S. Facilities | Reliability-Graded KMZ for ATAK, TAK Aware & Google Earth

Name: ATLAS Data Centers — 1,698 U.S. Facilities | Reliability-Graded KMZ for ATAK, TAK Aware & Google Earth
Brand: District47.US
SKU: D47-ATLAS-DC-US
Price: 4.99 USD
Availability: InStock

$4.99 USD

Sale Sold out

Product variants

Quantity

1,698 data centers. Every pin tells you how much to trust it.

A single KMZ mapping 1,698 U.S. data center facilities across 420 operators and 49 states — hyperscale campuses, wholesale halls, carrier hotels, and single-cage colocation suites.

Location data for data centers is genuinely messy. Operators publish inconsistently or not at all, aggregators copy each other's mistakes, and automated geocoders fail in ways that look completely plausible. Most map products hide that behind a uniform set of pins, so a point dropped on a city centroid looks identical to one sitting on a verified loading dock.

This file grades every facility instead. Five confidence tiers, colour-coded, separated into folders you can toggle. You always know whether you're looking at a Census-verified street address or a rough locality guess.

⚠️ Reference use only — please read

This is a research and reference aid. It is not a survey product, not a navigation aid, and not a source of operational truth.

Positions range from Census-verified building addresses down to city-centroid approximations. Not every pin is on the right building, and some are not on the right street.
The dataset is a snapshot. Facilities are built, sold, renamed, expanded and decommissioned constantly.
Nothing here is authorization to access, approach, or enter any property. Every site shown is private commercial property.
Compiled entirely from public sources.
Verify independently before relying on any point for a decision that matters.

If you need survey-grade or operationally certified location data, this is not that product — and no amount of colour-coding makes it that product.

How the colour coding works

Colour is a claim about positional confidence — how well-supported that facility's coordinate is. It is not a claim about facility size, capacity, or importance. A 300 MW hyperscale campus can carry a red pin if its address was never made public.

🟢 GREEN — VERIFIED · 566 facilities
Backed by ATLAS master data and a U.S. Census Exact geocode. A specific street address that resolved to an exact match against the federal address database, corroborated internally.
Trust: facility-level. As good as the dataset gets.

🔵 BLUE — HIGH · 528 facilities
A specific street address, strongly supported, but below the Census-Exact bar — usually a non-exact geocode return, or corroboration from one strong source rather than two.
Trust: very likely correct. Should be on or beside the right building.

🟡 YELLOW — GOOD · 139 facilities
A street address exists, but either source strength or the fit between coordinate and stated locality warrants a check.
Trust: solid starting point. Confirm before acting.

🟠 ORANGE — APPROXIMATE · 109 facilities
The position is a campus, road, intersection, or street-range anchor — not one verified building door. Common for large multi-building campuses and sites identified in planning documents by parcel rather than address.
Trust: right site, roughly. Not the right door.

🔴 RED — LOW / NEEDS RESEARCH · 356 facilities
No exact street address established. Placed on the best available locality, often a city or ZIP centroid.
Trust: directional only. The facility is real and the general area is probably right; the pin is not a claim about the building.

A red pin is a disclosure, not a defect. These facilities are included because knowing a site exists in a metro is useful even when its exact address isn't public — and many are hyperscaler sites the operators deliberately don't publish.

Inside every placemark

Tap any pin for a formatted popup carrying up to 24 fields:

Facility — name, operator/company, facility ID, type
Resolved location — street, city, state, ZIP
Known location — prior city, state, ZIP and county on record, shown beside the resolved values so you can see what changed
Position — latitude, longitude, MGRS, site ID
Grading — map reliability, locality reliability, address status, confidence, address precision
Provenance — internal corroboration, facility match status, validation flags, address source, dataset source
Evidence — the reasoning and source trail behind the placement

Every field appears on every placemark. Where a value was never established it reads "Not established" rather than being quietly filled with a guess.

File structure

Five folders matching the confidence tiers, so whole reliability classes toggle on and off:

1 — VERIFIED Census Exact (Green) · 566
2 — HIGH reliability (Blue) · 528
3 — GOOD reliability (Yellow) · 139
4 — APPROXIMATE / Anchor (Orange) · 109
5 — LOW / Needs Research (Red) · 356

Building an analysis that needs defensible positions? Switch off orange and red. Doing research and want the gaps visible? Leave everything on.

Compatibility

ATAK / CivTAK / iTAK / WinTAK — drop into Data Packages or import directly
TAK Aware (iPhone)
Google Earth Pro (desktop) and Google Earth Web
QGIS, ArcGIS, and other KML/KMZ-capable GIS software
Any application reading standard OGC KML 2.2

Custom icons are embedded — no external fetches, no broken pins. Fully functional offline once loaded.

File: single .kmz, ~304 KB · Format: OGC KML 2.2 with embedded PNG icon set

Who it's for

Infrastructure and network analysts mapping colocation and peering footprints
Site selection and commercial real estate researchers surveying regional density
Emergency management and continuity planners identifying infrastructure concentrations
Amateur radio, SIGINT and RF operators correlating infrastructure with spectrum activity
OSINT researchers and journalists who need provenance, not just dots
Educators teaching geospatial data quality

Sources & methodology

Every position is traceable. Each placemark carries Address Source, Dataset Source, Internal Corroboration and Evidence / Notes fields recording where that address came from and how it was checked.

U.S. Census Bureau Geocoding Services — the public federal address geocoder. An Exact match defines the green tier. 674 facilities carry a Census geocode in their evidence trail.
Operator location pages and facility directories — companies' own listings, matched on published facility codes (DC3, AZP-1, NNJ3) so the match is self-checking rather than inferred.
PeeringDB — used to corroborate carrier-hotel and colocation addresses.
County and municipal public records — parcel records, rezoning filings, planning-commission documents, building permits.
Public utility and regulatory filings — environmental permits, power-interconnection applications.
Local and trade press — corroboration, particularly for recently announced sites.

On directory sources. Third-party data center directories are useful for finding candidates and unreliable as final authority. During compilation, published listings were found placing one facility ~50 miles from its actual county, another in the wrong state entirely, and a third at an address belonging to a different facility in the same operator's portfolio. Where sources conflicted, the conflict is recorded in the Evidence / Notes field rather than quietly decided.

All sources are public. No proprietary, purchased, leaked, or authentication-scraped data is used anywhere in this product.

Dataset attribution

The base facility inventory is the ATLAS / Global Data Center Map dataset by Ringmast4r, used under its licence, which permits commercial products with required attribution. This product is a derivative work, not a repackaging — added on top of the base inventory: address research and verification, U.S. Census geocoding, coordinate correction, five-tier reliability grading, the colour-coded KMZ build, and the per-facility evidence trail.

Terms

Single-user licence for internal reference and research. Redistribution, resale, or repackaging of this KMZ is not permitted. Sold as-is with no warranty of accuracy, completeness, or fitness for any particular purpose.

Attribution passes through. If you publish maps, reports, visualizations, or analysis built on this file, credit must appear where a reader will find it — on the map, in the legend, or in an about panel:

This requirement comes from the upstream licence and cannot be waived.