Why one dataset isn't enough
Every dataset has a personality. ERA5 is a reanalysis — a weather model run over history, nudged by observations. It's superb for temperature but has known biases for precipitation (models struggle with rain). So an ERA5-only rainfall trend could be partly an artefact of the model, not the climate.
The fix is triangulation. CHIRPS is built completely differently — it blends rain-gauge records with satellite cloud-temperature estimates. If ERA5 and CHIRPS both say "drying, about this fast," the answer survived an independent check. That's what the "Cross-check" line on a /verify precipitation trend reports.
What "agree" actually means
Two estimates agree when they point the same direction and their confidence intervals overlap — i.e. the difference between them is within the noise. It's a weak-but-real test: cheap to run, and it catches gross errors and product-specific artefacts.
Play with it
Two trend estimates with their uncertainty. Slide them apart, or widen the uncertainty, and watch the verdict flip between agree and disagree.
Do it yourself
This is internal consistency — the system checking itself. It's necessary but not sufficient. The next guide, ground-truth anchoring, is the step that actually leaves the models and checks against the physical world.