Independent proposal
Version 3.0 · August 2026

Proposal This is an independent proposal. It is not published by, affiliated with or endorsed by West Yorkshire Combined Authority or any government body.

Figures version Version 3.0 August 2026 · 2025/26 prices
Data

Figures & data

Every cost, rate and headline number on this site, for stations, electrification, tram track and rolling stock, is drawn from a single data file. This page lets you browse those figures, switch between versions, and cite any figure under the version it was published in.

Current version

Version 3.0 · August 2026

First public web version of the Weaver Metro proposal.

All figures at 2025/26 prices. Use the Figures version selector in the grey bar above to view an earlier version. The version you choose is carried through every page you visit.

What changed in this version

  • Initial published figure set drawn from the Version 3.0 proposal document.

How to cite a figure

Because figures may be revised, always cite the version. A figure carries the value it had in the version you reference, even after later versions change it. Each figure below has a reference key (for example phase1.total) that is stable across versions.

Weaver Metro proposal figures, Version 3.0 (August 2026).

Download this version (JSON)

Deep-link to a single figure by combining the version and its key anchor, for example figures.html?v=3.0#fig-phase1-total.

All figures

Search by name or reference key. Values shown are for the version selected above.

Loading figures… If they do not appear, this page needs to be served over HTTP (not opened directly from disk). See the note below.

Reference tables

Light rail construction benchmarks, standardised to 2025/26 prices

Used to derive the applied tram build rates. The Second City Crossing figure derives from a project cost of £165m for a 1.29km section.

RIA Electrification Cost Challenge benchmarks, normalised to 2025/26 prices

The proposal applies the complex-project ceiling of £2.03m per single-track km, with a 30% margin on top.

How versioning works

The site reads two files:

  • data/manifest.json, lists every version and marks which one is current.
  • data/versions/<id>.json, the figures for one version.
Publishing a new version (for maintainers)
  1. Copy the latest data/versions/3.0.json to a new file, e.g. data/versions/3.1.json, and edit the figures. Keep the reference keys stable so existing citations still resolve.
  2. Update the meta block in the new file, version, date, summary and the changes list.
  3. In data/manifest.json, add the new version to the versions array and set current to its id.
  4. The previous version file stays in place, so anyone who cited ?v=3.0 continues to see the exact figures they referenced.

No page markup needs to change: the baked-in fallback values in each page are only shown when JavaScript is unavailable, and are overwritten from the selected version's file on load.

On this page