Skip to content

Add note about wildlife data and change to "What before windmill" #968

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions blog/2025-05-22-conservation-metrics-case-study/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ This testimonial is based on conversations with [Rudo Kemper](https://www.linked

[Conservation Metrics](https://conservationmetrics.com/) works with indigenous communities worldwide to provide tools and systems for environmental monitoring and protection. As part of our [Guardian Connector](https://guardianconnector.net) toolkit, our team needed a workflow orchestrator that could handle data processing from various sources, particularly for centralizing data from many different field data collection applications used by communities, and monitoring illegal activities in protected territories.

Having migrated from [Dagster](https://dagster.io/), we found that Windmill offered the accessibility and ease of use we needed for our small teams and non-technical users. Its intuitive interface and flexibility allowed us to focus on our core mission, rather than spending time on framework configuration or building additional user interfaces.
While evaluating different tools like [Dagster](https://dagster.io/), our primary focus was on accessibility and ease of use, as we needed a solution that could be managed by small teams and understood by non-technical users. We found that Dagster was too code-heavy and its UI wasn't optimal for our use case. We were actually in the process of building our own user interface on top of Dagster to make it easier when we discovered Windmill. Having migrated from Dagster, we were able to focus entirely on the core business logic of our scripts without needing to spend any time on framework configuration.

## How we use Windmill

Expand All @@ -45,7 +45,7 @@ This pipeline has been successfully implemented with community partners in Brazi
### Data processing and integration

We use Windmill for various [ETL](/docs/core_concepts/data_pipelines) workflows:
- Extracting tabular and binary data from multiple environmental monitoring and field data collection sources (such as [KoboToolbox](https://www.kobotoolbox.org/), [ODK](https://getodk.org/), and [CoMapeo](https://www.comapeo.app/))
- Extracting tabular and binary data from multiple environmental monitoring and field data collection sources (such as [KoboToolbox](https://www.kobotoolbox.org/), [ODK](https://getodk.org/), [CoMapeo](https://www.comapeo.app/)), and wildlife sensors (camera trap and bioacoustic devices)
- Transforming and processing the data
- Loading results into our databases
- Generating automated reports and alerts
Expand Down Expand Up @@ -105,4 +105,4 @@ This has allowed our small team to focus on our core mission of supporting indig

We're excited about Windmill's continued evolution and its potential to further empower organizations working in environmental conservation. The upcoming improvements to the app builder will make it even more valuable for our work.

Our experience with Windmill demonstrates how the right tools can amplify the impact of organizations working on critical environmental and social issues, even with limited technical resources.
Our experience with Windmill demonstrates how the right tools can amplify the impact of organizations working on critical environmental and social issues, even with limited technical resources.
Loading