Skip to main content

Emissions & LDAR API Guide

The Emissions API provides comprehensive Leak Detection and Repair (LDAR) capabilities through three specialized subgraphs: su-methane-ldar-backend, su-methane-reconcile-backend, and su-detections-ingress.

Overview

The Emissions API enables you to:
  • Track and manage emission observations (detections)
  • Coordinate LDAR inspection workflows
  • Reconcile emissions for compliance reporting
  • Ingest detection data from various sources

Key Concepts

  • Emission Observation: A detected emission event requiring investigation
  • Detection: Raw detection data from sensors, flyovers, satellites, etc.
  • Inspection Request: Request for follow-up inspection (OGI, drone, visual)
  • Reconciliation: Process of matching emissions to compliance requirements
  • Clue: Additional context about a detection (equipment, location, etc.)

Emission Observations

Query Emission Observations

Get Specific Emission Observation

Detection Types

Detection Status Workflow

Priority Levels

Inspection Requests

Inspection requests coordinate follow-up investigations of emission observations.

Create Inspection Request

Variables:

Update Inspection Request

Query Inspection Requests

Inspection Types

Clues (Equipment Context)

Clues provide context about where an emission was detected.

Query Clues for Detection

Equipment Components

Resolution Modes

When resolving emission observations:

Resolve Detection

Variables:

Emission Observation Reports

Query Reports by Site and Month

Variables:

Filter Reports

Detection Ingress

The su-detections-ingress subgraph handles incoming detection data.

Query Available Datasets

Reload Datasets

Reconciliation Workflow

The su-methane-reconcile-backend handles compliance reconciliation.

Query Reconciliation Status

Submit for Reconciliation

Compliance Severity

Geospatial Queries

Get Detections Near Location

Variables:

Audit & Acknowledgment

Acknowledge Detection

Query Acknowledgment History

Common Patterns

Processing New Detections

Tracking Inspection Progress

Best Practices

  1. Prioritize high-severity detections: Focus on DETECTION_PRIORITY_HIGH first
  2. Track acknowledgment: Always acknowledge when reviewing detections
  3. Use clues for context: Clues help identify specific equipment and components
  4. Monitor status transitions: Track detections through the complete workflow
  5. Coordinate inspections: Link inspection requests to specific detections
  6. Reconcile regularly: Don’t let pending emissions accumulate
  7. Use geospatial queries: Find nearby detections to optimize field work
  8. Archive resolved detections: Keep historical data for compliance

Schema Reference