Free tool / No sign-up

Read your numbers. Keep their limits.

Explain · don’t predict

Enter the numbers from your report. Get a plain-language record of what they mean, what you know about their source, and what is still missing. No carry estimate or “ideal” fitting score.

Add the context behind the numbers optional, but useful

Your entries are not verified measurements. Different devices and modes can produce different kinds of output. The decoder explains labels; it does not test a device, calculate a trajectory or choose equipment. Read File 01: the measurement distinction.

Confirmed

Foresight’s GC2 technical guide makes a useful distinction. Cameras capture launch conditions, including ball speed, launch angle, total spin, initial horizontal direction and spin-axis tilt. An algorithm then calculates ball-flight outputs such as carry. This is a documented example for the GC2, not a claim that every device uses the same method.

Source: Foresight Sports

Its reference units are miles per hour (mph) for speed, degrees (°) for launch angle, revolutions per minute (rpm) for spin and yards (yd) for carry. Carry describes flight distance; total distance adds bounce and roll. Keep those labels attached when copying a result.

Source: Foresight Sports

Trackman’s explanation of Normalization describes a different distinction: a modeled flight for calm conditions at a selected altitude and temperature. Normalized distance answers a “what if” question; it should not be presented as the landing point observed in that session.

Source: Trackman

Our note

Read a report in three passes. First identify the device, model and mode. Then separate captured inputs from calculated outputs. Finally ask which settings could change the displayed flight without changing the shot you actually hit. That is a better starting point than deciding whether one screen looks more precise than another.

  • Record the ball model, indoor or outdoor setup, units and software mode beside the session.
  • Ask whether spin was measured on this shot or substituted by an estimate; keep any device warning attached.
  • Keep carry and total in separate columns. Do not turn a total-distance headline into a carry claim.
  • Ask whether normalization or ball conversion is enabled, and retain the selected environmental settings.

A decimal place is formatting, not an accuracy certificate. For a comparison, we would rather have a clearly described session and the complete shot record than a single impressive number with its context removed. This is our reporting preference, not a claim that we tested these systems.

Still unknown

These documents do not establish the accuracy of every model, software version or installation. We have not independently validated either system. Without the session settings and the device’s shot-level flags, we cannot say whether a particular result was measured, estimated or transformed.

Sources & scope

  1. Foresight Sports: Understanding Ball Launch & Club Data
    Manufacturer technical guide · 2013 · Checked 2 November 2026.
  2. Trackman: The Normalization feature explained
    Manufacturer technical explanation · 2014-07-09 · Checked 2 November 2026.

“Confirmed” means the cited publisher documents the stated detail, not that The Fairway File independently tested it. We have not personally tested equipment for this article.