> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sensorup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Grouping Emission Observations

> Combine multiple related emission observations into single, comprehensive events to prevent double-counting and improve accuracy.

<img className="block dark:hidden" src="https://mintlify.s3.us-west-1.amazonaws.com/sensorupinc/images/grouping-observations-hero-light.png" alt="Grouping emission observations overview" />

<img className="hidden dark:block" src="https://mintlify.s3.us-west-1.amazonaws.com/sensorupinc/images/grouping-observations-hero-dark.png" alt="Grouping emission observations overview" />

## What is Observation Grouping?

Observation grouping allows you to combine multiple related emission observations into a single, comprehensive event record. This process prevents double-counting of emissions and creates a clearer understanding of the root cause, duration, and magnitude of methane leaks by consolidating data from different detection methods.

<CardGroup cols={3}>
  <Card title="Prevent Double-Counting" icon="shield-check">
    Avoid inflating emission totals
  </Card>

  <Card title="Combine Data Sources" icon="merge">
    Unite flyover, CMS, and OGI data
  </Card>

  <Card title="Accurate Timeline" icon="clock">
    Build complete event narratives
  </Card>
</CardGroup>

## Why Use Observation Grouping?

<CardGroup cols={2}>
  <Card title="The Problem" icon="triangle-exclamation">
    **Without observation grouping:**

    * Multiple detections of the same leak appear as separate events
    * Emission volumes are counted multiple times in reports
    * Incomplete understanding of leak duration and source
    * Difficulty distinguishing planned operations from fugitive leaks
  </Card>

  <Card title="The Solution" icon="lightbulb">
    **With observation grouping:**

    * Single, comprehensive record per actual emission event
    * Accurate emission quantification without double-counting
    * Complete timeline from first detection to final repair
    * Clear attribution between planned operations and unplanned leaks
  </Card>
</CardGroup>

## Common Use Cases

### Combining Detection Methods

**Scenario**: A continuous monitoring system (CMS) detects an ongoing emission, and later a flyover survey measures the same leak.

**Solution**: Group the CMS alarm with the flyover observation to use the CMS data for duration estimation while leveraging the more accurate flyover measurement for emission rate.

### Tracking Persistent Leaks

**Scenario**: Multiple flyover surveys detect the same leak over several weeks, followed by an OGI inspection that confirms the source.

**Solution**: Group all related observations to document the complete leak lifecycle from first detection through repair verification.

### Distinguishing Operational Events

**Scenario**: An emission is detected during a planned maintenance activity like a blowdown operation.

**Solution**: Associate the detection with the operational event to correctly categorize it as planned rather than a fugitive leak, ensuring proper resource allocation.

## Getting Started

<Info>
  **Ready to start grouping observations?** Follow these steps to create your first grouped emission event. The process takes just a few minutes and immediately improves your data accuracy.
</Info>

<Steps>
  <Step title="Open an Emission Event">
    Navigate to the emission event you want to group with other observations. Click on the event in your timeline or search results to open the detailed view.
  </Step>

  <Step title="Access Grouping Options">
    In the emission event detail panel, look for the correlation options in the observations section. Click "Group Observations" to open the grouping interface.
  </Step>

  <Step title="Select Related Events">
    Choose from two grouping methods:

    * **Add Existing**: Select from a time-ordered list of nearby emission events detected within 90 days
    * **Create New**: Manually add observations with custom details and supporting evidence
  </Step>

  <Step title="Review and Confirm">
    Review the grouped observations to ensure they represent the same physical emission source. Confirm the grouping to create your consolidated emission event.
  </Step>
</Steps>

### Bulk merge

You can merge multiple emission events at once using bulk actions:

<Steps>
  <Step title="Select events">
    Select rows in the emissions table by clicking on them. To select multiple rows quickly, click on a row, hold Shift, and click on another row further down to select all rows in between.
  </Step>

  <Step title="Choose merge">
    At the bottom of the page, select **Merge**.
  </Step>

  <Step title="Select primary event and confirm">
    Choose a Primary Emission Event to merge the other events into and click **Confirm**. A success message will display to confirm the action was successful.
  </Step>
</Steps>

<Tip>
  To undo a merge, click on the event and in the Observations section, remove the Observations that were merged.
</Tip>

## Advanced Features

### Ungrouping Observations

Made a mistake? You can easily separate incorrectly grouped observations:

1. Select the observations that should be split into a new event
2. Confirm the separation to create independent emission events
3. The system maintains data integrity while preserving the audit trail

## Best Practices

<CardGroup cols={2}>
  <Card title="Group Related Sources" icon="thumbs-up">
    **Do**: Combine observations that clearly represent the same physical emission source, even if detected by different methods or at different times.
  </Card>

  <Card title="Avoid Over-Grouping" icon="thumbs-down">
    **Don't**: Group observations that might be from different leaks or locations, as this can mask important patterns and reduce accuracy.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Verify Spatial Relationships" icon="thumbs-up">
    **Do**: Check that grouped observations are from the same asset or equipment before correlating them.
  </Card>

  <Card title="Don't Rush Decisions" icon="thumbs-down">
    **Don't**: Group observations without reviewing their temporal and spatial context, as incorrect grouping can impact reporting accuracy.
  </Card>
</CardGroup>

## FAQ / Troubleshooting

<AccordionGroup>
  <Accordion title="How do I know which observations should be grouped together?" icon="question">
    Look for observations that:

    * Occurred at the same asset or nearby equipment
    * Have overlapping or sequential time periods
    * Show similar emission characteristics
    * Are part of the same operational context (like a maintenance event)
  </Accordion>

  <Accordion title="What happens to emission calculations when I group observations?" icon="question">
    The system recalculates emission estimates using the most accurate data available:

    * Combines the best rate measurements with the most complete duration information
    * Prevents double-counting by consolidating overlapping time periods
    * Updates total volumes and reporting summaries automatically
  </Accordion>

  <Accordion title="Can I undo observation grouping if I make a mistake?" icon="question">
    Yes, you can ungroup observations at any time:

    * Select the specific observations you want to separate
    * Click "Ungroup" to create new independent emission events
    * The system maintains a complete audit trail of all grouping and ungrouping actions
  </Accordion>

  <Accordion title="How does grouping affect my regulatory reports?" icon="question">
    Observation grouping improves report accuracy by:

    * Eliminating double-counting of the same emission source
    * Providing more complete event documentation
    * Correctly categorizing planned vs. unplanned emissions
    * Maintaining full traceability for audit purposes
  </Accordion>
</AccordionGroup>

***

## Feedback & Support

<Warning>
  **Found an issue with observation grouping?** Contact support with specific details about the observations you're trying to group, including event IDs and timestamps.
</Warning>