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
| Type | Description | Common Source |
|---|---|---|
DETECTION_TYPE_SATELLITE | Satellite-based detection | Remote sensing |
DETECTION_TYPE_FLYOVER | Aircraft-based detection | Aerial surveys |
DETECTION_TYPE_DRONE | Drone-based detection | UAV inspection |
DETECTION_TYPE_OGI | Optical Gas Imaging | Ground inspection |
DETECTION_TYPE_CMS | Continuous Monitoring System | Fixed sensors |
DETECTION_TYPE_OWD | On-site Walk Down | Manual inspection |
DETECTION_TYPE_VENTING_FLARING_BLOWDOWN | Planned releases | Operations |
Detection Status Workflow
Priority Levels
| Priority | Integer Value | Description |
|---|---|---|
DETECTION_PRIORITY_HIGH | 100 | Requires immediate attention |
DETECTION_PRIORITY_MEDIUM | 50 | Normal priority |
DETECTION_PRIORITY_LOW | 1 | Low priority or informational |
Inspection Requests
Inspection requests coordinate follow-up investigations of emission observations.Create Inspection Request
Update Inspection Request
Query Inspection Requests
Inspection Types
| Type | Description | Typical Use |
|---|---|---|
INSPECTION_OGI | Optical Gas Imaging | Confirm and locate leaks |
INSPECTION_DRONE | Drone inspection | Aerial investigation |
Clues (Equipment Context)
Clues provide context about where an emission was detected.Query Clues for Detection
Equipment Components
Resolution Modes
When resolving emission observations:| Mode | Description |
|---|---|
DETECTION_RESOLVED_CORRELATED | Correlated with another detection |
DETECTION_RESOLVED_FALSE_ALARM | Determined to be false positive |
DETECTION_RESOLVED_READY_TO_RECONCILE | Ready for compliance reconciliation |
Resolve Detection
Emission Observation Reports
Query Reports by Site and Month
Filter Reports
Detection Ingress
Thesu-detections-ingress subgraph handles incoming detection data.
Query Available Datasets
Reload Datasets
Reconciliation Workflow
Thesu-methane-reconcile-backend handles compliance reconciliation.
Query Reconciliation Status
Submit for Reconciliation
Compliance Severity
| Severity | Description |
|---|---|
HIGH | Critical compliance issue |
MEDIUM | Moderate compliance concern |
LOW | Minor compliance matter |
Geospatial Queries
Get Detections Near Location
Audit & Acknowledgment
Acknowledge Detection
Query Acknowledgment History
Common Patterns
Processing New Detections
Tracking Inspection Progress
Best Practices
-
Prioritize high-severity detections: Focus on
DETECTION_PRIORITY_HIGHfirst - Track acknowledgment: Always acknowledge when reviewing detections
- Use clues for context: Clues help identify specific equipment and components
- Monitor status transitions: Track detections through the complete workflow
- Coordinate inspections: Link inspection requests to specific detections
- Reconcile regularly: Don’t let pending emissions accumulate
- Use geospatial queries: Find nearby detections to optimize field work
- Archive resolved detections: Keep historical data for compliance
Related Resources
- LDAR Backend Reference - Complete schema
- Reconcile Backend Reference - Reconciliation schema