RacesReviewed / Race Intelligence Demo

Boston Marathon

A single-race deep dive showing how RacesReviewed can turn one event into a dense, technical research surface before full results-derived enrichment is online.

Real course + standards where knownDerived geometry analyticsMocked placeholders flagged inline

Course posture

Point-to-point

Real event shape. Logistics penalty is part of the product story.

Net drop

447 ft

Derived from the demo course profile using stored elevation points.

Hardest zone

Miles 17-21.2

Derived segment difficulty based on grade concentration and timing.

Data confidence

Mixed

Real standards + records, mocked logistics + review synthesis.

Course Elevation Story

Boston is a downhill trap followed by a controlled collapse test.

Derived from course geometry

The opening half asks whether the runner can resist “free pace.” The back half asks whether they carried enough restraint into Newton.

Synced course focus

Heartbreak crest

Mile 21.1 · 248 ft · Highest pressure point on the course narrative.

Early descent

Stored data supports the grade story. We still need official mile-segment labels from Boston-specific enrichment.

Heartbreak setup

The climb is not isolated. This chart works because the prior 17 miles soften the runner first.

Missing later

Split overlays and historical weather impact should layer here once results + NOAA history are ingested.

Difficulty Meter

Composite course demand

Derived

86/100

Terrain penalty: +31
Logistics penalty: +18
Prestige pressure: +12
Weather model: Live NOAA race window

Route-aligned wind

+6.6 mph

Interpretation

Strong tailwind assist

NOAA race-window forecast is live. Wind is scored relative to the Hopkinton-to-Boylston course bearing.

Course bearing 69.6 degAverage wind 7.0 mphDominant direction W

Estimated weather effect

+2.21%

Heuristic read

Major weather drag

Help score

-40

Hopkinton

79F

Mostly Cloudy

6.0 mph · W

Newton

81F

Mostly Clear

6.0 mph · W

Boylston

84F

Clear

9.0 mph · W

Weather effect is a heuristic estimate informed by marathon-weather literature and route-aligned wind, not a strict prediction model.

Segment Difficulty Strip

Where the race changes shape

Derived

Active segment

Heartbreak build

Highest sustained demand of the day. Heartbreak is the headline, but the setup matters more.

Avg grade +3.3%Focused mile 21.1Derived from course geometry

Point-to-Point Logistics Panel

The course is only half the operational problem.

Mocked logistics callouts

Shape

Point-to-point

Real course fact

Start / finish gap

26.2 miles apart

Real course fact

Athlete village load-in

Bus-first morning

Mocked summary pending official packet guide

Bag flow

Start staging + finish reclaim

Mocked until official logistics scraped

Spectator rail hotspots

Wellesley / Newton / Kenmore

Derived from course geography

Interactive Course Map

Hopkinton to Boylston with the pressure points called out.

Real route shape, mocked basemap treatment

Hovered location

Heartbreak crest

Highest pressure point on the course narrative.

Mile 21.1248 ftHeartbreak build

What is real

Route shape, start/finish posture, and segment order.

What is missing

Spectator access, aid stations, transit overlays, and official closures need new enrichment.

Why this matters

Boston planning is as much transport and family coordination as pacing discipline.

Qualifying Standards Explainer

Boston is qualification-gated, then still effectively selective.

Mostly real

Men 18-34

3:00:00

Athlete village cutoff likely faster in practice

Real data

Women 18-34

3:30:00

The race behaves like a prestige event, not a standard city marathon

Real data

Men 35-39

3:05:00

Aging buffer exists, but demand still rises at registration

Real data

Women 35-39

3:35:00

Qualification is necessary, not always sufficient

Real data

Non-binary

Policy-specific

Current standards and field handling should come from official BAA policy

Mocked / missing source

Historical Record Board

Prestige becomes obvious when the benchmark table is this sharp.

Real records + mocked extension

Men open

2:03:02

Geoffrey Mutai

2011

Real data

Women open

2:19:59

Buzunesh Deba

2014

Real data

Wheelchair men

1:15:33

Marcel Hug

2023

Real data

Wheelchair women

1:28:17

Manuela Schar

2017

Real data

Masters trend

Future module

Historical winners view

Mocked

Mocked / missing source

Review Radar

What runners appear to love, and where the experience still creates friction.

Mocked until review corpus is richer

Course prestige

98/100

Crowd support

95/100

Logistics friction

61/100

Field depth

93/100

Pace friendliness

72/100

Post-race ease

66/100

Fast mobile intake

Ran this race?

The fastest real review flow is a one-thumb questionnaire: structured taps first, optional note second.

Tap `Yes` if you ran the race or `Watched` if you spectated.
Score four prompts with one thumb: course, logistics, crowd support, and post-race flow.
Add one short note only if the runner wants nuance. Everything else should be structured taps.

Missing Data Register

What this demo still needs before it becomes a production-grade race intelligence page.

Weather overlays

Need segment-level wind and historical methodology surface, not just instance-level weather snapshots.

Aid stations

Need a dedicated `course_aid_stations` table with mile markers and service types.

Spectator logistics

Need `spectator_access_points` plus transit or city closure overlays.

Results overlays

Need historical split ingestion before this page can show how Boston actually breaks pace.