Ghana Fire Regime-RP1 Analysis
# RP_Ghana_Fires
This README is the end-to-end project run guide for the current checkout.
Assume a clean clone contains code, docs, configs, tests, and the maintained
ACZ source-layer exception, but not the full operational data bundle.
External-data policy:
- Treat operational data as absent from a clean clone unless a dataset is
explicitly documented as a maintained in-repo exception.
- The authoritative external-data classification for this repository lives in
`RP1_Project/docs/external_data_contract.md`.
- The canonical user-facing acquisition and staging guide lives in
`docs/data_access.md`.
- The current maintained in-repo exception is the ACZ source shapefile used by
`geo_data_prep`.
- No operational data bundles are hosted as GitHub release assets in the
current RePo.
## Executed stage order
The live RP1 workflow runs in this exact order:
```text
geo_data_prep -> rp1_mv_firms_panels -> merge_af_ba_panels.py -> RP1_Analysis_c1.ipynb
```
Supporting prerequisite:
- `RP1_Project/rp1_gee_ba_scripts/` contains the governed Earth Engine scripts
used to generate the burned-area CSV bundles required by
`merge_af_ba_panels.py`.
- Do not assume those exported burned-area bundles are
already present. Users must generate or otherwise obtain them separately and
place them under the expected local export roots before Stage 3 runs.
## Repository surface used by the bootstrap guide
- `geo_data_prep/`
Stage 1 canonical geography preparation.
- `RP1_Project/rp1_mv_firms_panels/`
MODIS and VIIRS active-fire monthly panel pipeline.
- `RP1_Project/rp1_gee_ba_scripts/`
Earth Engine scripts plus the expected local roots for burned-area exports.
- `RP1_Project/merge_af_ba_panels.py`
Consolidation step that merges active-fire and burned-area inputs into the
notebook-ready fire panels.
- `RP1_Project/rp1_analysis/`
Canonical notebook, helper package, and run-scoped analytical outputs.
## Core documentation
Read these before staging data or running any step:
- `RP1_Project/ …