LNG Atlas

Data

Download the data

The tables behind the site, one row per asset, as CSV for a spreadsheet or JSON for code. Rebuilt with every release of the tracker.

Files

DatasetGEM releaseRowsDownload
LNG terminalsSeptember 2025813CSV · JSON
LNG terminal units (trains and phases)September 20251,206CSV · JSON
Gas pipelinesNovember 20254,246CSV · JSON
LNG carriers and floating vesselsJune 20261,220CSV · JSON

Licence and attribution

The underlying data is Global Energy Monitor's, published under CC BY 4.0. You may reuse these files, including commercially, provided you credit the source. The credit is written into every row (the data_source column) and at the top of each JSON file, so it survives being passed around. Please keep it.

Please cite it as: Data: Global Gas Infrastructure Tracker, Global Energy Monitor, September 2025, with the release shown for the dataset you used. The exact text for each file is in that file.

Reading the files

  • An empty cell means not reported. The tracker does not give that field for that asset. It is never zero, and nothing is estimated.
  • Capacity is never totalled. Operating, construction and proposed capacity are separate columns because they are different things. There is deliberately no total column, and adding them would overstate what exists.
  • Terminals are one row per terminal, grouped from GEM's one-row-per-train data. Capacity is in Mtpa and bcm/y as separate columns.
  • Terminal units are one row per train or phase, the level at which GEM reports status, capacity, estimated cost and the low-carbon flags. estimated_cost_usd is GEM's estimate converted to US dollars, not adjusted for inflation. A flag column is true where GEM records a yes and empty otherwise, which is not a confirmed no. Capacity here is per unit, so do not add units of different statuses.
  • Pipelines are one row per project. length_km_mapped_route is measured from the route we hold; length_basis says whether length_km is GEM's reported figure or that measurement.
  • Carriers include FSRUs and other floating vessels; filter on vessel_type. imo_check_digit_valid is false where the IMO number fails its check digit, and the number is kept anyway.
  • Every row has a url to its page here, which carries the full detail and the link to GEM's own project history.

The method, including how status and capacity are normalised, is on the methodology page. The other files the site publishes (GeoJSON, chart images, the chokepoint export) and example code are in the developer guide.

Share this page:XLinkedInFacebookBlueskyRedditEmail