Global Methane Emitters Tracker (GMET)
Datadory delivers global methane emitters tracker gmet data covering 18,023 methane-emitting fossil fuel assets across 166 countries - 5,000-plus coal mines, oil and gas extraction areas, gas pipelines and LNG terminals - joined to 3,474 analysed satellite plumes and roughly 93 million tonnes of modelled methane in the December 2025 Version 3 release.
What is the Global Methane Emitters Tracker?
Global Methane Emitters Tracker (GMET) is Global Energy Monitor's attribution layer between the sky and the supply chain: a global census of fossil fuel facilities that emit methane, with emission estimates pinned to each one and satellite-detected plumes attached where partners observed them. Version 3, released 12 December 2025, covers 18,023 methane-emitting assets across 166 countries - more than 5,000 coal mines alongside oil and gas extraction areas, gas pipelines and LNG terminals - linked to 3,474 analysed plume observations carrying roughly 93 million tonnes of associated methane. GEM positions it as the only public database attaching emission estimates to gas pipelines and LNG terminals worldwide.
The release keeps an unusually clean shape: one eight-sheet package fronted by a Data Dictionary, then separate sheets for Pipelines, LNG Terminals, Coal Mines (non-closed), Plumes, Oil and Gas Extraction Areas and Oil and Gas Reserves - about 7,400 extraction-area rows, roughly 3,475 plume rows and some 2,300 reserve rows. Ten country/region summary boards travel alongside, aggregating emissions for pipelines, extraction areas and coal mines, 2P-reserve emissions potential, and plume counts. It sits in the oil gas exploration production data hub as the emissions read on assets its sibling trackers catalog. Get a sample of this dataset and we will return the sheets and countries you name, shaped like the rows below.
What do sample rows look like?
One row per emitting thing - an asset on the ground, a plume in the air, a country on a summary board:
-- sheet: Oil and Gas Extraction Areas -------------------------
gem_goget_id unit_name status operator country_area latitude longitude
OG0000001 Matzen operating OMV Austria 48.41667 16.71667
-- sheet: Plumes ------------------------------------------------
gem_plume_id provider instrument observation_date emissions_kg_hr infrastructure_type
CH4T1 CarbonMapper Global Airborne Observatory 2020-11-09T18:47:16+00 37.54922973 wellpad
-- country summary boards ---------------------------------------
board country figures
Gas Pipeline Methane Emissions by Country/Area Afghanistan operating 524 t; proposed/construction 4,101 t
Oil and Gas Methane Potential at 2P Reserves by Country Algeria 12 assets with 2P estimates; 36.12 Mt total
GMET Methane Plumes by Country/Area Algeria imager NASA-JPL EMIT; 25 plumes reviewed; 1 attributedEvery figure above is quoted from the release's own tables, not paraphrased. The asset row is OMV's Matzen unit in Austria - operating, keyed OG0000001, plotted at 48.41667 N - the exact record an analyst would join to an operator universe. The plume row is CH4T1, read by Carbon Mapper's Global Airborne Observatory at 37.54922973 kg/hr over a wellpad, timezone-stamped to the minute of capture. The three boards show how the summaries roll up: Afghanistan's pipeline methane split between operating stock and proposed construction, Algeria's 2P reserves carrying 36.12 Mt of emissions potential across 12 assessed assets, and the attribution funnel in the open - 25 Algerian plumes reviewed against NASA-JPL EMIT imagery, one attached to a catalogued asset. Your sample arrives carrying the sheets and geographies you actually need rather than the full 166-country span.
Which fields does the dictionary define?
The dictionary is the release's own vocabulary, and it runs on two spines joined by GEM identifiers: asset rows that say who operates what and how much the surrounding field emits, and plume rows that say what a satellite actually saw, when, and how confidently it was attributed. All fourteen verified entries:
Where does coverage run, and at what grain?
- Geo: Global - 166 countries across 18,023 emitting assets: 5,000-plus coal mines, oil and gas extraction areas, gas pipelines and LNG terminals, plus plume observations wherever partner sensors flew
- Temporal: December 2025 release (Version 3); plume imagery spans roughly August 2022 to March 2024 with mid-2025 coal mine coverage; extraction-area records carry a February 2025 vintage and pipeline records December 2024
- Granularity: Asset-level - mine, extraction area, pipeline, terminal - and individual plume observation, rolling up to country/region summary boards
That granularity stack is the product. One release answers who operates the emitter (asset rows), what did the sensor measure (plume rows), and how does my country compare (summary boards) without a second integration. The honest caveat is printed on the numbers themselves: emission figures are modelled values derived from partner data - Climate TRACE field estimates, Carbon Mapper and OCI+ plume readings - not stack measurements, and each plume carries its own uncertainty range and attribution certainty. Treat the tracker as the most complete attribution layer available, not a regulatory monitoring report.
How is the data delivered through Datadory?
API, files, or your warehouse. Daily, weekly, or hourly.
Pick the asset classes - pipelines, LNG terminals, extraction areas, coal mines - pick the countries, pick the cadence, pick the landing zone. Because the sheets share GEM identifiers, an extract arrives pre-joined rather than as loose tables needing reconciliation: plume observations ride on the assets they were attributed to, and country boards reconcile to the rows beneath them. The sample comes first - name the scope and it lands shaped to it, dictionary attached, before any commitment. Builders wiring this into monitoring pipelines can see the pattern in developers builders use cases.
Who builds on it, and for what?
Ranked by how directly a row settles the day job:
- ESG and emissions accounting teams - asset-level methane baselines for portfolios and supply chains, with named operators instead of national aggregates that blur responsibility
- Investors and quant researchers - emissions exposure screens and transition-risk factors built on asset identifiers stable enough to join against financial data; investors quants use cases shows where factor inputs slot in
- LNG and midstream analysts - emission estimates for pipelines and terminals, the two asset classes almost every other emissions source skips
- Satellite and geospatial analysts - 3,474 attributed plumes with provider, instrument, timestamp and emission rate, ready to benchmark against independent detections
- Journalists and academics - facility-level stories and peer-reviewed designs that need citable numbers attached to named assets rather than country totals
- Data engineers - one keyed release replacing a patchwork of per-country disclosures; data scientists use cases covers the modeling side
For contrast inside the same industry: the Global Registry of Fossil Fuels scores reserves and their embedded carbon, while GMET scores what those assets emit today - potential versus performance, stacked.
Which personas get the most value?
Quants get uniform numeric columns - emission rates, tonnage estimates, decimal-degree coordinates - that survive feature assembly without unit strings to strip. ESG and market researchers get the named-operator layer that turns a corporate disclosure into a checkable claim, facility by facility; the market researchers use cases page maps the workflow. Developers get a single keyed schema across four asset families, so adding LNG terminals to an extraction-only pipeline is a filter change, not a migration. Across all of them the constant holds: one dictionary, two spines, ten roll-up boards - scoping a new country is a request, not a research project. Persona-by-persona detail lives on the oil gas exploration production data hub.
Which notes and neighboring datasets pair with it?
The neighbors divide by which half of the problem they solve. Global Oil and Gas Extraction Tracker (GOGET) is the ownership counterpart - GMET rows carry GOGET IDs precisely so emissions snap onto operators, status and location already cataloged there. Global Registry of Fossil Fuels quantifies the carbon embedded in reserves yet to be burned; GMET measures what is escaping now. JODI-Gas World Database supplies officially reported monthly gas flows at economy level - the head-to-head comparison scores attribution depth against official breadth. For geometry to overlay, OGIM v2.5.1 maps the infrastructure footprint the coordinates land on.
Three glossary notes sharpen the vocabulary before you request anything: what asset-level tracking commits a model to, why an emissions inventory model differs from a measurement campaign, and how a satellite footprint bounds what any sensor can attribute. The publishing organization's profile lives at Global Energy Monitor, and the best oil gas exploration production datasets ranking shows where this record lands in the slice. Start at Get a sample of this dataset.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
gem_goget_id | string | Unique project ID for an oil and gas extraction area, keyed to GEM's Global Oil and Gas Extraction Tracker - the hinge that joins emissions to ownership. | OG0000001 |
unit_name | string | Name of the extraction unit as reported by sources. | Matzen |
status | string | Development stage of the unit: discovered, in development, or operating. | operating |
operator | string | Company designated as operator of the unit. | OMV |
climate_trace_field_emissions_tonnes_per_year | number | Annual methane emissions estimate for the Climate TRACE field encompassing the asset. | 1234567 |
gem_methane_plume_id | string | Unique identifier for one satellite-detected methane plume observation. | CH4T1 |
satellite_data_provider | string | Organization that created the plume imagery, e.g. CarbonMapper. | CarbonMapper |
instrument | string | Sensor behind the observation - Global Airborne Observatory, NASA-JPL EMIT and peers. | Global Airborne Observatory |
observation_date | datetime | Date and time the plume imagery was captured, timezone-stamped. | 2020-11-09T18:47:16+00 |
emissions_kg_hr | number | Plume emission rate as determined by the satellite data provider. | 37.54922973 |
type_of_infrastructure | string | Broad infrastructure class near the plume, drawn largely from the California VISTA framework. | wellpad |
country_area | string | Country or area where the asset or plume sits; present on every sheet. | Austria |
latitude | number | Latitude in decimal degrees for the asset or plume origin. | 48.41667 |
quantity_boe | number | Fuel quantity converted to barrels of oil equivalent on the reserve rows. | 56789012 |
Questions buyers ask
What does the Global Methane Emitters Tracker contain?
The December 2025 release, Version 3: 18,023 methane-emitting assets across 166 countries - more than 5,000 coal mines, oil and gas extraction areas, gas pipelines and LNG terminals - plus 3,474 analysed satellite plumes, roughly 93 million tonnes of associated methane, and ten country-level summary boards. One eight-sheet release, fronted by a data dictionary.
Are GMET's emission figures measurements or estimates?
Estimates, and the release says so. Extraction-area figures come from Climate TRACE field-level modelling, plume rates from providers such as Carbon Mapper with OCI+ inputs alongside - modelled values, not stack measurements. Each plume row carries an uncertainty range and an attribution certainty grade, so confidence travels with the number rather than hiding in a footnote.
How are satellite plumes tied to specific facilities?
Through the plume sheet: every observation records provider, instrument, timestamp, emission rate in kilograms per hour, nearby infrastructure type and attribution certainty. Analysts reviewed 3,474 plumes and attributed them to catalogued assets - the country boards expose the funnel, as when NASA-JPL EMIT imagery yielded 25 Algerian plumes reviewed and one attached to a GEM asset.
Which asset types get emission estimates?
Four families: coal mines (non-closed), oil and gas extraction areas keyed by GEM GOGET ID, gas pipelines and LNG terminals. The latter two are the differentiator - GEM positions GMET as the only public database attaching emission estimates to pipelines and LNG terminals worldwide. Reserve rows extend the picture with barrels-of-oil-equivalent quantities and their emissions potential.
Can GMET be joined to other energy datasets?
By design. Extraction rows carry GEM GOGET IDs, so GMET snaps onto the Global Oil and Gas Extraction Tracker, where ownership, status and location already live - emissions meet operators on one key. Coordinates and country fields make overlays against infrastructure mapping databases straightforward, and the summary boards aggregate cleanly onto any country-dimension table you maintain.
What remains unverified about GMET?
Two gaps, flagged honestly: no publication calendar is documented, so spacing between releases is inferred from history rather than stated, and whether the supplemental coal-mine boundary file ships inside the main release or beside it could not be confirmed. Both are settled facts in a scoping sample, which is why the sample precedes any commitment.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.