Clapham × Walthamstow
draft · score 82Fairest shortlist winner: The Gun, Spitalfields — 47 min vs 48 min (gap 1).
Opposite-side pair: East-of-centre pub balances Northern + Overground vs Northern + Victoria.
Public /meet URL after admin Approve
BetaFairWhere is in beta. Plans currently work for London only · more cities later.
Research · London beta · Status: preview
London Journey Fairness Index
How journey burden falls when people from different London neighbourhoods meet — built from FairWhere's area-pair matrix, not crow-flies midpoints.
Curated areas
24
Unordered pair capacity
276
Preview pairs on this page
2
The Index is the research sibling of the meet-pair content factory ( /meet/{a}/{b}). Factory cadence is two drafts/day with human Approve; the Index publishes once as a durable page plus CSV when the matrix is stable.
What the Index measures
Area × area, not pin × pin
Each origin is a neighbourhood represented by its primary station — Clapham Common, Walthamstow Central — so the index answers how people search (“where should we meet between…”) without storing home addresses.
Same matrix as meet-pair pages
The content factory writes crawlable /meet/{a}/{b} pages from this precompute. The Fairness Index is the research sibling: one durable page (plus CSV) that summarises burden patterns across the matrix — not 2 pages/day.
Fairness gap, not crow-flies
Primary signal is the gap between the two door-to-door estimates to the winning venue, plus FairWhere Score balance. Midpoint geometry is deliberately ignored.
Human publish for trust
Pair pages stay draft until admin Approve. The first Index CSV will ship the same way: no silent live edits when a winner flips — refresh → review → publish.
Preview pairs from the content factory
Same precompute that will back the Index. Drafts stay private until Approve — paths appear here only when live.
Brixton × Stratford
draft · score 85Fairest shortlist winner: The Crown Tavern — 44 min vs 45 min (gap 1).
South × East: fairest shortlist clusters around Clerkenwell / City fringe, not the geographic midpoint.
Public /meet URL after admin Approve
Roadmap to CSV
Now
Framing + preview pairs
This page, methodology anchors, and sample pairs from the meet-pair factory while drafts await Approve.
Next
Stable matrix artefacts
Nightly job writes full A×B winner + gap minutes for the curated area set (and expands beyond the editorial seed once organic volume ≥ 10 plans/day).
Then
Published Index + CSV
Versioned London Journey Fairness Index with downloadable CSV (areaA, areaB, winner, minutes, gap, score, computedAt) and Dataset JSON-LD.
Planned CSV columns: areaA, areaB, stationA, stationB, winner, minutesA, minutesB, gapMinutes, score, computedAt, provider. Download link appears here on first publish — not before.
Frequently asked questions
- What is the London Journey Fairness Index?
- A FairWhere research view of how journey burden falls when people from different London neighbourhoods meet. It uses the same area-pair travel-time matrix as FairWhere’s meet-between pages — not geographic midpoints.
- How is this different from “meet in the middle”?
- Meet-in-the-middle optimises for crow-flies centre. The Index reports the fairest venues and the minute gap between two origins on real transit estimates, so opposite sides of town often meet east or west of the map midpoint.
- Where does the data come from?
- From FairWhere’s meet-pair precompute: curated neighbourhood stations, candidate Placelist venues, and FairPath (or a published heuristic while FairPath rolls out). Organic plan volume reorders which pairs are computed next once volume is meaningful — never founder-testing alone.
- Can I download the data?
- A versioned CSV is planned for the first published Index release. Until then this page shows methodology and preview pairs only.
- Is this navigation advice?
- No. Times are planning estimates for comparing venues fairly. Always check live TfL or your usual app before you travel.