AERSHED Platform

Appearance

Aerscape Platform ​

The Aerscape platform is a methane emission management system that helps operators detect, track, investigate, and resolve emission events across their infrastructure. It ingests data from aerial and satellite providers, matches emissions to operator sites and equipment, and provides tools for investigation workflows, notifications, and reporting — all configurable per operator.

This documentation covers both user-facing guides and engineering/DevOps references. Browse the sections below or use the sidebar to navigate.

Concepts ​

Core domain knowledge about how the platform models and processes emission data.

  • Emission States — lifecycle and status definitions for detected emissions (NEW, WORK_IN_PROGRESS, COMPLETED, etc.).
  • Matching — how emission data points are connected to operator infrastructure, and how matching is configured per data provider.
  • Workflows — the rule-based automation engine that drives emission events through their lifecycle using configurable conditions and actions.
  • Custom Forms — data-driven forms for capturing event investigation data: field types, conditional validation, value suggestions, and authoring.

Admin & Configuration ​

Guides for platform administrators managing users, features, and system behavior through Django Admin.

  • Admin Operations — user management, reviewer flow setup, feature flags and switches, data batch deletion, geo filter presets, analytics refresh, and company data backup/restore.
  • Notification Settings — mailing lists, notification groups, and alert configuration for emissions and data exports.

Data Import ​

How to get infrastructure and emission data into the platform using the data-pipelines helper scripts.

  • Infrastructure Import — the JSON-based API for creating and updating sites, equipment, aerial images, and pipelines.
  • Emission Import — provider-specific import scripts for Bridger, Planet Tanager-1, GHGSat, EDF MethaneAir, EPA, and a generic importer. Includes troubleshooting.

Integrations ​

Third-party data provider integrations.

  • Sensor Data — continuous monitoring (CM) provider integrations for live sensor measurements and alerting data. Currently supports Sensirion and LongPath.

Operator Customization ​

Per-operator configuration that extends the platform's default behavior.

  • Custom event fields — adding custom form fields (open text, boolean) to the emission form for specific operators, with conditional validation.
  • Custom filter areas — defining geographic filter areas per operator for map-based filtering.

Engineering / DevOps ​

Internal engineering references for infrastructure, scheduled tasks, and secrets management.

  • Environment Syncs — how production data is copied, anonymized, and restored into dev and AMI environments via ECS Fargate tasks.
  • Scheduled Jobs — reference for all Celery periodic tasks, their queues, schedules, and controlling waffle switches.
  • App Secrets — interactive tool for managing and rotating application secrets.

Tools ​

Utility tools for common operational tasks.