> ## 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.

# Automatic Time-Bounding for Emission Events

> Automatically establish emission event start and end times using non-detection survey data to get initial volume estimates faster.

<img className="block dark:hidden" src="https://mintlify.s3.us-west-1.amazonaws.com/sensorupinc/images/automatic-timebounding-hero-light.png" alt="Automatic time-bounding overview" />

<img className="hidden dark:block" src="https://mintlify.s3.us-west-1.amazonaws.com/sensorupinc/images/automatic-timebounding-hero-dark.png" alt="Automatic time-bounding overview" />

## What is Automatic Time-Bounding?

Automatic time-bounding uses non-detection data from aerial surveys (like Insight M, Bridger) and OGI surveys to automatically establish preliminary start and end times for emission events. This eliminates manual data analysis and provides instant volume estimates for your reconciliation workflow.

<CardGroup cols={3}>
  <Card title="90-Day Lookback" icon="calendar-days">
    Searches up to 90 days for relevant non-detections
  </Card>

  <Card title="125m Precision" icon="crosshairs">
    Uses spatial matching within 125 meters
  </Card>

  <Card title="Instant Estimates" icon="bolt">
    Get preliminary volumes immediately
  </Card>
</CardGroup>

## Why Use Automatic Time-Bounding?

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

    * Manual review of survey data takes hours per event
    * Initial volume estimates require extensive research
    * Delayed response times for high-priority events
    * Inconsistent duration assumptions across teams
  </Card>

  <Card title="The Solution" icon="lightbulb">
    **With automatic time-bounding:**

    * Instant preliminary duration and volume estimates
    * Leverages all available survey data automatically
    * Consistent, defensible methodology across events
    * Faster prioritization of follow-up actions
  </Card>
</CardGroup>

## How It Works

The system automatically analyzes your survey data to find the most relevant time boundaries for each emission event:

### 1. Finding Time Boundaries

* **Start Time**: Uses the closest non-detection that occurred before the emission was detected (within 90 days)
* **End Time**: Uses the closest non-detection that occurred after the emission was detected

### 2. Smart Data Matching

* **Spatial Proximity**: Non-detections must be within 125 meters of the emission location
* **Source Attribution**: Prioritizes matching by survey source when available
* **Survey Type Compatibility**: Follows business rules about which survey types can bound which events

### 3. Volume Calculation

* Combines the automatically determined duration with emission rate data
* Provides preliminary volume estimates for immediate use in reconciliation workflows

## Getting Started

<Info>
  **Ready to use automatic time-bounding?** This feature works when you have compatible non-detection survey data available for an emission event that doesn't yet have a duration set.
</Info>

<Steps>
  <Step title="Navigate to Emission Events">
    Go to **Emission Events** in your dashboard and select the asset where you want to review an emission event.
  </Step>

  <Step title="Select an Emission Event">
    Choose an emission event that doesn't have a duration already set. Events with available non-detection data for time-bounding will show compatible observations.
  </Step>

  <Step title="Review Available Non-Detects">
    In the **Observations section** of the event blade, you'll see any compatible non-detects that can be used for automatic time-bounding. These appear when the system finds relevant survey data before or after your emission detection.
  </Step>

  <Step title="Explore Non-Detect Details">
    Click on any non-detect observation to open an additional blade with detailed information about the non-detect type, survey method, timing, and other relevant data that will be used for time-bounding.
  </Step>
</Steps>

## Survey Type Compatibility

Understanding which survey types can be used to bound different types of emission events:

<CardGroup cols={2}>
  <Card title="Universal Bounding" icon="check-circle">
    **These combinations work:**

    * Flyover to flyover event bounding
    * OGI to OGI event bounding
    * OGI to flyover event bounding
  </Card>

  <Card title="Restricted Bounding" icon="exclamation-circle">
    **This combination is restricted:**

    * Flyover to OGI event bounding is not allowed
    * This is because aerial surveys have higher detection thresholds than ground-based OGI cameras
  </Card>
</CardGroup>

## Common Use Cases

**Initial Event Assessment**
When a new emission event is detected, automatic time-bounding immediately provides a preliminary duration and volume estimate, helping you quickly assess the event's potential magnitude and prioritize your response.

**Reconciliation Workflow Support**
Use the automatically generated volume estimates as starting points in your reconciliation process, reducing the time needed to gather baseline information for regulatory reporting.

**Multi-Survey Data Integration**
Leverage all available survey data (both detections and non-detections) to create more defensible and accurate event timelines without manual cross-referencing.

## FAQ / Troubleshooting

<AccordionGroup>
  <Accordion title="What happens if no non-detection data is available?" icon="question">
    The system will use default time boundaries based on your configured settings. You can always manually override these with more precise information as it becomes available.
  </Accordion>

  <Accordion title="Can I override the automatically determined duration?" icon="question">
    Yes, you can easily override the automatic time boundaries with more precise information. The system preserves your manual adjustments and uses them for final volume calculations and reporting.
  </Accordion>

  <Accordion title="How accurate are the preliminary volume estimates?" icon="question">
    The estimates provide a defensible starting point based on available data, but they should be refined with additional information as your investigation progresses. They're designed for initial assessment and prioritization, not final reporting.
  </Accordion>

  <Accordion title="Why can't flyover non-detections bound OGI-detected events?" icon="question">
    Aerial surveys typically have higher minimum detection thresholds than ground-based OGI cameras. A flyover non-detection doesn't guarantee that a smaller emission detectable by OGI wasn't present.
  </Accordion>

  <Accordion title="What if multiple non-detections are available for the same time period?" icon="question">
    The system automatically selects the closest non-detection in time to the emission event, ensuring the most relevant temporal boundaries are used for duration calculation.
  </Accordion>
</AccordionGroup>

***

## Feedback & Support

<Warning>
  **Found an issue with automatic time-bounding?** Contact support with the specific emission event ID and survey details for assistance with duration calculations.
</Warning>

Need to customize the survey type compatibility rules for your specific operations? Contact your Customer Success Representative to discuss advanced configuration options.