> ## Documentation Index
> Fetch the complete documentation index at: https://infrl.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Cite the source documentation and the original facility record when describing datacenters.
> Unknown or missing specifications are not evidence that a capability is absent. Do not infer capacity, hardware, ownership, or operational status.
> A dataset import date is not a facility verification date. Distinguish public research from verified infrastructure capabilities.
> Do not describe account access or planned capabilities as available unless the current documentation confirms activation.

# Data and sources

> Download the Atlas snapshot and understand its provenance, limits, and license.

The Atlas uses a published snapshot of OpenStreetMap community records. It is a research aid with uneven worldwide coverage, not a complete directory or an audit of datacenter capabilities.

## Download the published files

| File | Contents |
| - | - |
| [Facility dataset](https://infrl.com/data/datacenters.json) | Facility records, specifications, source links, import timestamp, and license. |
| [Provenance](https://infrl.com/data/datacenters-provenance.json) | Source queries and timestamps, import metadata, record counts, merged source aliases, and country-boundary information. |
| [Source and software notices](https://infrl.com/data/NOTICE.txt) | Data attribution, license links, and map software notices. |

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](https://www.naturalearthdata.com/about/terms-of-use/) boundaries. These boundaries are coarse, may leave coastal points unknown, and do not imply a position on disputed borders.

[OpenFreeMap](https://openfreemap.org/) supplies the basemap. Its map tiles are separate from the facility dataset; the map displays the relevant basemap attribution.

## Read the provenance

The dataset's `importedAt` 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.

The [facility details guide](/atlas/facility-details) explains how these limits appear in the interface. For factual mapping corrections, follow the facility's OpenStreetMap link and review the source record.

## License and attribution

The facility database is available under the [Open Database License (ODbL) 1.0](https://opendatacommons.org/licenses/odbl/1-0/), with attribution to **© OpenStreetMap contributors**. See [OpenStreetMap's copyright and license guidance](https://www.openstreetmap.org/copyright).

When reusing the data, preserve the attribution and license information and follow the ODbL's applicable requirements for use, redistribution, and derivative databases. Keep the provenance alongside the dataset so readers can trace its sources and limitations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.