VIEWS Reporting: Visualization, Statistics & Mapping

Part of the VIEWS Platform ecosystem for large-scale conflict forecasting.

Table of Contents

1. Overview
2. Role in the VIEWS Pipeline
3. Architecture
4. Features
5. Installation
6. Running Tests
7. Project Structure
8. Governance
9. Contributing
10. Acknowledgements

Overview

VIEWS Reporting provides the visualization, statistical analysis, reconciliation, and report generation layer for the VIEWS conflict forecasting pipeline. It produces HTML evaluation reports, interactive choropleth maps, posterior distribution analyses, and hierarchical forecast reconciliation.

All incoming data is expected on its original measurement scale -- this library does not infer or reverse mathematical transformations from column names (ADR-011, Architecture Decision Record).

Key Capabilities:

• Bayesian posterior analysis -- MAP (Maximum A Posteriori) estimation, HDI (Highest Density Interval) computation, and credible interval reporting
• Hierarchical forecast reconciliation -- proportional scaling to ensure country-grid consistency
• HTML report generation -- Tailwind CSS-styled evaluation and forecast reports with XSS-safe text content (add_html is the one deliberate raw path, for trusted figure HTML only)
• Interactive mapping -- choropleth maps at country and PRIO-GRID (Peace Research Institute Oslo grid) resolution via GeoPandas and Mapclassify

Role in the VIEWS Pipeline

VIEWS Reporting sits at the output end of the forecasting pipeline, consuming model predictions and producing human-readable reports, maps, and statistical summaries.

Integration with Other Repositories

• views-pipeline-core: Pipeline infrastructure -- provides orchestration, configuration, and the queryset/partition framework that reporting consumes.
• views-models: Model outputs -- predictions and posterior samples evaluated and visualized by this library.
• views-evaluation: Evaluation metrics -- scoring and calibration results displayed in evaluation reports.
• views-stepshifter: Stepshift model predictions consumed for reconciliation and visualization.
• docs: Organization/pipeline level documentation.

Integration Workflow

1. Data Input: Receives evaluated predictions and posterior samples from the pipeline.
2. Analysis: Computes MAP estimates, HDI intervals, and reconciles hierarchical forecasts.
3. Output: Generates HTML reports, distribution plots, historical line graphs, and choropleth maps.

Architecture

The repository follows a five-layer dependency model (ADR-002):

Data flows upward: ingestion -> compute -> render -> compose. No downward dependencies (ADR-002).

Adoption in progress (epic #137): the leaf data contract is moving to views-frames — PredictionFrame / TargetFrame / SpatioTemporalIndex / SpatialLevel as the Foundation (Layer 1) values, replacing pipeline-core private dataset internals (ADR-018). The statistics layer already delegates MAP/HDI to views_frames_summarize; the loader and render layers adopt the frame contract next.

Features

• Posterior Distribution Analysis: MAP via histogram density peak, HDI via shortest-interval on sorted samples, configurable credible masses and zero-mass thresholds.
• Forecast Reconciliation: Proportional scaling that preserves zeros, clamps non-negative, and ensures country totals match grid sums. Parallel execution via ProcessPoolExecutor.
• HTML Reports: Content accumulation API (headings, paragraphs, tables, images, footers) with html.escape() on all user-facing text. Exception (documented trust boundary, register C-117): add_html embeds its input verbatim -- it exists to carry trusted, code-generated figure HTML (Plotly, base64 maps) and must never receive externally-influenced text; a markup-less input logs a warning. Tailwind CSS styling. Export to standalone HTML files.
• Choropleth Mapping: Country and PRIO-GRID level maps with bundled shapefiles, configurable classification schemes, and interactive Folium output.
• Historical Line Graphs: Plotly-based time series with HDI bands, forecast cutoff markers, and entity dropdown navigation.
• Distribution Plots: HDI and MAP overlays on posterior sample histograms.

Installation

Prerequisites

• Python 3.11 (tested-on) — the declared envelope is >=3.11,<3.15 (the platform-wide range, decision 2026-08-02), but in practice 3.11 is the only version the full stack installs on today: an upstream transitive dependency (views-pipeline-core → ingester3 → levenshtein 0.20.9) has no 3.12+ wheel and its source build fails there, so a 3.12–3.14 install resolves and then fails loudly at that build. See ADR-014 and risk register C-36. The package is resolved for Linux and macOS.
• uv for development (hatchling + uv per ADR-014).

Steps

For development (recommended):

git clone https://github.com/views-platform/views-reporting
cd views-reporting
uv sync          # creates .venv from uv.lock

Or install the published package into an existing environment:

pip install views-reporting

See the organization/pipeline level docs for full environment setup.

Running Tests

uv run pytest tests/ -q                 # full suite
uv run pytest tests/ -q -m "not slow"   # skip slow integration tests

Fixture-dependent tests skip automatically when their data is absent.

Project Structure

views-reporting/
├── README.md                   # Documentation
├── tests/                      # 85–161 tests depending on environment
├── views_reporting/            # Main source code
│   ├── assets/                 # Shapefiles and header images
│   ├── mapping/                # Choropleth map generation
│   ├── metadata/               # Entity metadata accessors
│   ├── reconciliation/         # Hierarchical forecast reconciliation
│   ├── reports/                # HTML report builder + Tailwind CSS
│   ├── statistics/             # Posterior analysis (MAP, HDI)
│   ├── templates/              # Report templates (evaluation, forecast)
│   ├── visualizations/         # Distribution and historical plots
│   └── __init__.py             # Package initialization
├── documentation/
│   ├── ADRs/                   # 18 Architecture Decision Records
│   ├── CICs/                   # 13 Class Intent Contracts
│   └── guides/                 # Operational runbooks (e.g. publishing to PyPI)
├── reports/                    # Technical risk register
├── .github/workflows/          # CI configuration
└── pyproject.toml              # Project metadata (PEP 621) + hatchling/uv

Governance

This repository uses structured governance documented in documentation/:

• 19 ADRs (000-018) -- architectural decisions, from foundational principles to data ingestion, build tooling, release automation, configuration, evaluation-report standards, and the render-from-given-data responsibility mandate (ADR-018)
• 13 CICs -- intent contracts covering every non-trivial class plus the full Ingestion-layer loader surface (ADR-006)
• Risk register -- reports/technical_risk_register.md (ADR-010)
• Testing doctrine -- red/green/beige team taxonomy (ADR-005)
• Guides -- operational runbooks in documentation/guides/ (e.g. publishing to PyPI)

Start with documentation/ADRs/README.md for the governance map.

Contributing

We welcome contributions! Please follow the contribution guidelines outlined in the VIEWS Documentation. See also documentation/contributor_protocols/ for repo-specific protocols.

All contributions must comply with the constitutional ADRs in documentation/ADRs/, including:

• ADR-003 -- Explicit declarations over inference; fail loud on semantic ambiguity
• ADR-005 -- Testing is mandatory (red / beige / green taxonomy)
• ADR-006 -- Non-trivial classes require intent contracts
• ADR-007 -- Silicon-based agents are untrusted contributors

Acknowledgements

Special thanks to the VIEWS MD&D Team for their collaboration and support.