Download the published files
Use these files for the current snapshot date and record counts. The map’s attribution control also links to the facility dataset.
Where the data comes from
Facility identity, locations, status, and specifications come from OpenStreetMap records collected through Overpass. Each facility links to its OpenStreetMap source, and reported specifications retain their source links. Some missing country values are inferred from coordinates using public-domain Natural Earth boundaries. These boundaries are coarse, may leave coastal points unknown, and do not imply a position on disputed borders. OpenFreeMap supplies the basemap. Its map tiles are separate from the facility dataset; the map displays the relevant basemap attribution.Read the provenance
The dataset’simportedAt field records when the snapshot was generated. Source timestamps describe the upstream data used for that import. Neither timestamp is evidence that every facility or specification was checked at that time.
The provenance file distinguishes source queries used for the snapshot from the intended refresh query. It also records aliases when matching OpenStreetMap features were merged. Some nearby records remain separate because they may represent different buildings or a campus and one of its buildings.
The Atlas is a snapshot, so a correction made in OpenStreetMap appears only after a later import is published.
What remains unknown
- Missing information means unknown, not zero or the absence of a capability.
- A mapped point can be imprecise; a mapped area is shown at an approximate center.
- A datacenter tag alone does not prove operational status.
- Specifications may be incomplete, out of date, or scoped to a campus rather than a building.
- Original reported values and units are preserved. Comparing or adding them requires checking that their scope and units match.