Site-level methane plumes, tied to a facility boundary.
Imaging spectrometry picks out super-emitter plumes and attributes each one to a site you register, on passes tasked daily where tasking allows.
The files
Every delivery is tied to a pass. Nothing here is a feed.
- Deliverable
- Plume detections
- Format
- GeoPackage or GeoJSON
- What's in it
- One polygon per detected plume, with the pass timestamp, the retrieval used and a confidence tier. Delivered per pass wherever a plume is found, and it opens as a layer in your GIS.
- Deliverable
- Site attribution
- Format
- Field on each detection
- What's in it
- The ID of the facility boundary the plume traces back to, matched against the polygons you registered. A plume that cannot be tied to one boundary is flagged unattributed instead of being assigned to the nearest site.
- Deliverable
- Detections table
- Format
- CSV
- What's in it
- One row per detection: facility ID, pass timestamp, confidence tier, attribution status and plume centroid coordinates. Built to join to your facility register on the ID you supplied.
- Deliverable
- Pass record
- Format
- CSV
- What's in it
- One row per pass over each site, including passes with no plume, with a usable or not usable flag and the reason (cloud, geometry, daylight). This is the record that shows a clean pass was a clean pass and not a gap.
- Deliverable
- Map layer
- Format
- GeoPackage
- What's in it
- Facility boundaries styled by status for the latest pass: detected, attributed, below threshold. A quick read before you open the table.
How it works
You supply
Facility boundaries as polygons (shapefile, GeoPackage or GeoJSON) with your own facility IDs, plus the area of interest and how often you want passes tasked.
We task
A hyperspectral pass is requested over the area. Where tasking and sky allow, the pass goes ahead on the day you asked for.
We retrieve
The SWIR absorption in each pixel is analyzed to pick out methane against the background. Any plume found is traced back to its source location.
You receive
The detections layer, the detections table and the pass record, with a confidence tier on each plume and a usable flag on each pass.
Limits
- Condition
- Super-emitter scale only
- Effect on the output
- The method resolves large plumes. A release below the detection threshold is not seen, and a clean pass does not mean a site is not leaking.
- Condition
- Cloud and daylight
- Effect on the output
- Cloud or poor light spoils a pass. It is logged as not usable, with the reason, and the site is retried on the next tasking window.
- Condition
- Tasking decides the date
- Effect on the output
- Daily means daily where the satellite can be tasked over your area. Competing requests and orbit geometry can push a pass back. Every result is one pass.
- Condition
- 0.5–2 m GSD
- Effect on the output
- A pixel is far smaller than a typical plume, so resolution is not what limits detection here. The spectral retrieval and the threshold are. The fine pixel helps place the source inside a boundary.
- Condition
- Spatial attribution
- Effect on the output
- Attribution says where a plume starts relative to your boundaries. It does not say who owned the equipment, what failed or whether a rule was broken. Where boundaries sit side by side the answer can be ambiguous, and those cases are flagged.
- Condition
- Onshore only
- Effect on the output
- Facility boundaries for this offer are onshore. Offshore platforms are not covered.
- Condition
- No emission rate
- Effect on the output
- Detections are located and tiered, not quantified. There is no kg/h figure on any row.
Why this exists
Large releases usually reach your team from outside. A third party sends a map, a regulator sends a notice, or an advisory names a basin. By then the response clock is running and you are working backwards: pulling the facility list, asking field operations whether anything happened, trying to put a date on it.
Between LDAR rounds and survey campaigns you cannot point at one pad and ask whether it is emitting. A fund analyst has the same gap from the other side and wants to know which holdings are large emitters.
Who it's for
For
- MRV and emissions analysts at operators who want an independent look at named sites before the quarterly self-report.
- Teams that need a pass record to show what was imaged and when, including the passes that found nothing.
- Emissions-focused fund analysts who follow a set of held facilities.
Not for
- Teams that need equipment-level leak detection or leaks below the super-emitter threshold. LDAR rounds and aerial surveys do that.
- Continuous or live monitoring of a site.
- A compliance determination or evidence of fault. Attribution is spatial.
- Offshore assets.
Technical and procurement questions
Can this see small leaks?
No. It targets super-emitter-scale plumes. Sources below the detection threshold are not resolved.
What happens when there is cloud?
The pass is marked not usable, with the reason, and the site is retried on the next tasking window.
Is this continuous monitoring?
No. It is a set of discrete passes, daily where tasking allows. Between passes you have no view of the site.
Does attribution count as legal proof?
No. It is a site-level spatial attribution, not a compliance finding, and it should not be filed as one.
Can I use it to answer a regulator's notice?
It gives you a dated pass record and a location to start your own investigation from. The finding and the response stay with your team.
Do you give an emission rate?
No. Each detection is located and tiered, without a kg/h figure.
How do we check detections against our own data?
Every detection carries its pass timestamp, so you can line it up against field logs, an LDAR round or a maintenance record. Tell us where your ground truth sits when the pilot is scoped.
What do we send you?
Facility polygons with your own IDs, in shapefile, GeoPackage or GeoJSON. The IDs come back on every detection so the table joins to your register.
Who owns the delivered layers?
Use and ownership terms for the delivered files are written into the contract before the pilot starts. The imagery sources keep their own licences.
How is it priced?
A pilot is scoped and quoted on its own: number of sites, area covered and how many passes you want tasked. You get a written scope you can take through procurement.