Ecoscope is a modular data analysis platform built to turn complex conservation data into clear, actionable insights. Designed with conservation practitioners, researchers, and data analysts in mind, it offers a user-friendly way to run structured, repeatable analyses on spatial and temporal data.
Whether you’re exploring animal movements, analyzing patrol coverage, or evaluating patterns in event reports, Ecoscope makes it easy to configure and run workflows that produce detailed dashboards and visual outputs—no advanced programming skills required.

What Makes Ecoscope Different?
Unlike traditional live dashboard tools like Tableau or Superset that continuously query a connected database, Ecoscope workflows are run-based. Each time you run a workflow, you launch a predefined sequence of analytical steps that filter, process, and visualize your data. The result is a structured dashboard generated from that specific run.
Live dashboards are useful for real-time updates and lightweight summaries—helpful when you want to check a single metric that changes frequently, like the number of active patrols or recent event reports.
Ecoscope workflows, on the other hand, are designed for structured, repeatable insight. They support advanced logic like spatial analysis to statistical modeling and machine learning. Offering a level of analytical depth that live dashboards don’t support. And because each run saves its results, the outputs remain consistent and reproducible. Ideal for comparing trends over time, generating standardized reports, or supporting high-stakes decision-making in complex conservation environments.

How Ecoscope Workflows Work
Running a workflow in Ecoscope means executing a well-defined sequence of analysis steps. Think of it like following a recipe: your ingredients (data) go through a set of tasks that clean, process, and analyze them. The final output is a dashboard filled with maps, charts, and dashboard widgets.
Each workflow includes:
- A configuration form to select your time range, subject group, or event types
- Optional grouping (by category or time) to compare across sub-groups
- Advanced settings for fine-tuning how your data is interpreted and visualized
- A dashboard once the run is complete
In Ecoscope, dashboards are the complete visual result of a workflow run.
Within a dashboard, views are filtered slices (e.g., by subject or month).
Each panel—map, chart, or metric—is a widget, updated dynamically per view.
Key Differences: Ecoscope Workflows vs. Live Dashboards
Feature | Ecoscope Workflow | Live Dashboards (e.g. Tableau) |
Data Flow | Configure > Run > Process > Store > View | Live query on user interaction |
Real-Time | No (results saved after each run) | Yes (live connection to data source) |
Analytical Depth | High – can run Python, ML, statistics | Low–medium – mostly visual summaries |
Interactivity | View-level filters, download widgets | Highly interactive (but shallow compute) |
Compute Efficiency | Serverless – runs only on demand | Requires always-on server |
Custom Workflow Support | YAML-based config (GUI coming 2026) | GUI-based dashboard builders |
Developer Dependency | Low for standard workflows, high for custom | Medium – SQL often required |
Overview
When you log into Ecoscope you’ll see a navigation bar with three key sections:
- My Workflows (default view)
- Workflow Templates
- Data Sources

My Workflows
This is your personal workspace, where all of your created or configured workflows are listed.

Each row in the table represents a saved workflow and includes:
Name | |
Template |
The base workflow type (e.g., Subject Tracking, Events, Patrols). Also shows the template version (e.g., v1.2). Important: If a workflow was created with an older major version (e.g., v1.x) and the template is upgraded to a new major version (e.g., v2.0), that workflow may no longer be runnable or “Run Again”-able. However, its existing results will still be viewable.
|
Status | Operational status (e.g., Ready, Running, Failed). |
Last Run Start | |
Last Run Duration | How long it took to complete the latest run |
When a workflow is ready to execute, a Run button will appear. Clicking it will launch the workflow and generate results according to its configuration.
Workflow Options Menu
Each workflow has an options menu with:

- Run Again – Re-runs the workflow exactly as configured. Useful for retrying failed workflows due to intermittent issues, or re-processing with the same parameters.
- View Metadata – Opens a full JSON view of the configuration and parameters used to generate the workflow. This is particularly helpful for debugging or submitting support tickets.
- Duplicate – Copies the workflow to use as a base for a new one.
-
Edit – Opens the configuration panel to modify the workflow setup.
Editing a workflow that has previously run successfully will overwrite its results upon saving. You will be asked to confirm the edit to prevent accidentally overwriting older results. - Delete – Permanently removes the workflow from your list.
- Advanced Run – Opens expert-level execution settings (e.g., async modes, timeout configs). Only recommended for advanced users who understand system-level parameters.
Advanced Run (For Experts Only)
The Advanced Run panel allows you to control how a workflow is executed, including timeout, memory allocation, and execution mode. These settings can significantly impact performance and should be used with caution. If you're unsure which settings to choose, we recommend using the defaults or reaching out to the support team.
Workflow Run Mode*
Choose the execution mode based on the expected duration and memory requirements of your workflow:
-
Standard (Default) – For faster, lightweight runs.
Starts immediately. Recommended for workflows requiring up to 32 GB of memory and expected to complete within 9.5 minutes. -
Heavy Duty – For longer or more resource-intensive runs.
Slower startup due to server provisioning (typically 4–10 minutes). Recommended for workflows that need more than 32 GB of memory or a timeout greater than 9.5 minutes.
Workflow Timeout
Set how long the system should wait before canceling the workflow:
- Standard Mode: Between 0.1 and 9.5 minutes
- Heavy Duty Mode: Between 9.5 and 180 minutes
(Note: this does not include the 4–10 minutes of server provisioning time.)
Memory Allocation
Choose the amount of memory your workflow needs:
- 32 GB
- 64 GB
Workflow Templates
Navigate to the Workflow Templates tab to start a new workflow from a predefined structure.
Reminder: You must configure a data source before you can create a new workflow.
Available Templates
- Subject Tracking – For analyzing GPS movement and telemetry data.
- Events – For reviewing incidents, alerts, and automated triggers.
- Patrols – For visualizing ranger activity, route coverage, and operational patterns.

Each template provides a guided setup form that helps you configure what data to use, how to filter or group it, and what outputs you want to see.
Data Sources
Before you can create and run any workflow in Ecoscope, you must first configure at least one data source.
Data sources provide the underlying data used by your workflows—such as GPS tracks, event logs, or patrol records. Currently, EarthRanger is the only data source supported in Ecoscope, with additional integrations planned.
If you haven’t connected a data source yet, workflow creation will be disabled. For a complete walkthrough, see: Configuring Data Sources in Ecoscope