BL PCF Report
Ingests livestock predation events from EarthRanger and produces a comprehensive Predator Compensation Fund incident analysis report and dashboard for the Amboseli ecosystem.
User Guide
Step-by-step instructions for loading, configuring, and running the workflow.
Technical Guide
Deeper look at the workflow's internals — the dual current/previous pipeline, colour mapping, every chart and map, and the Word report.
Troubleshooting
Common errors you may hit while configuring or running the workflow, and how to resolve them.
What it produces
- Charts — pie charts by predator, ranch, and attack location; stacked bar charts by claim type and predator; a time-of-day bar chart; multi-line and multi-bar time-series charts; and per-ranch historic (current vs. previous period) comparison charts
- Maps — an overall predation-incident density grid, a boma-attack density grid, and a livestock-species scatter map
- Summary tables — an overall predation summary, per-ranch summaries, and breakdown tables by claim type, predator species, attack location, and boma type
- Data files — the underlying current- and previous-period event tables, plus a GeoParquet file for every summary/breakdown table
- A Word document report (
overall_report.docx) — every chart, map, and table assembled into the Big Life PCF report template - An interactive dashboard — 24 widgets covering every chart, map, and table produced by the run
The analysis is restricted to three target ranches — Eselengei, Mbirikani, and Kimana — and to events marked as valid claims only.
Requirements
- Access to an EarthRanger instance with
hwc_lvstprd(livestock predation) events logged for the analysis period
The Amboseli geospatial layers and the Word report template are downloaded automatically from Dropbox at run time — no additional setup is required for these.
Get started
New to the workflow? Start with the User Guide for a walkthrough of loading the template, connecting EarthRanger, configuring the previous-period comparison, and running it. Running into an error? Check Troubleshooting first.