← All projects
OBJ-07Major Leagueidea · Tool

Spray Atlas

Every batted ball a hitter puts in play, on one field. Filter by pitch location, count and pitch type to see where he really hits it.

Builds on Read the Swing, Answers for Coach

Concept sketch of a field seen from above with a fan of batted balls, heavier toward right field
Coach questions
4
Asked on air
18×
Top question
Q-05

Coach questions it could answer

The playbook →

Data it needs

The data lake →

1 of 2 on hand; the rest arrives in phase 1, The spine.

Could use later: Fielding, Weather

The question

Where does a hitter actually hit the ball, and how much does that depend on where the pitch is? Inside pitches get pulled and outside pitches go the other way, but how strongly, and for whom?

How it would work

  • Every batted ball for a hitter drawn on a field from above, colored pull, center or opposite field.
  • Filters for pitch location, count, pitch type and exit velocity, with the league as a backdrop for comparison.
  • A side-by-side mode for two hitters, or one hitter across two seasons.

It’s also a window into Read the Swing: that game’s no-video baseline uses exactly this kind of hitter tendency plus pitch location, and it gets about 46% right on the game’s clips.

First version

  • One season, one generic field, any qualified hitter.
  • Three filters: pitch location (inner, middle, outer third), count ahead or behind, and pitch type.
  • Pull, center and opposite-field rates beside the chart, against the league.

The data

Statcast batted balls with hit coordinates, launch angle and exit velocity, 2015 onward. Answers for Coach already keeps a pitch-level Statcast cache for 2022–26.

What it needs

  • Fast drawing. A full season can be 500 batted balls per hitter and hundreds of hitters, so the field needs to render quickly on a phone.
  • Park shapes. Fences differ by park; a single generic field is the first version.

Status

An idea on the launchpad. Nothing is built yet.