GSPro — exporting range sessions for analysis
GSPro does not persist session data once you close it — this is the single most important thing to know before you play a range session you want to analyze later. GSPro is simulator software, priced at $250/year, that plays golf using shot data fed to it by whatever launch monitor you've connected (Foresight, FlightScope, Uneekor, Garmin, and others are all supported inputs); it doesn't measure anything itself, so export your session to CSV before you close the app, or the data is gone for good.
How do I export a CSV from GSPro?
Use GSPro's Practice Range or Driving Range mode, which can export a completed session to a single CSV file. Do this immediately after your range session — GSPro does not persist that data between sessions, and there's no "session history" to come back to later and export from. If you're mid-round rather than in Practice Range mode, check GSPro's own settings for a course-play export option before you assume the data survived.
What does a GSPro export include?
Whatever fields your connected launch monitor sends it — GSPro is a pass-through, not an independent measurement source, so the exact column list depends entirely on which device is feeding it data. A GSPro session from a Foresight unit will carry Foresight's fields (including camera-measured spin and club path); a GSPro session from a Garmin R10 will carry the R10's fields (including its calculated, not measured, club path). GSPro doesn't add or remove precision either way.
What does ContactCoach add?
Because the column set varies by upstream device, ContactCoach treats a GSPro CSV the same way it treats a native export from whatever monitor produced it — using measured fields directly when they're present, and estimating the rest.
| ContactCoach adds | When it applies | Guide |
|---|---|---|
| Descent angle | Estimated whenever landing angle isn't in the feed | How it's estimated |
| Face-to-path | Estimated whenever face angle + club path aren't in the feed | How it's estimated |
| Dispersion ellipses per club | Any session with carry + lateral data | Reading the ellipses |
| Gap analysis across your bag | Any session with carry data | Reading gap analysis |
| Mishit flagging | Any session with smash factor or carry | How mishits are flagged |
Measured or modeled — what should I trust?
Whatever your connected launch monitor measures directly, GSPro passes through unchanged — trust it exactly as much as you'd trust a native export from that device. Anything ContactCoach estimates on top (descent angle, face-to-path) is labeled "estimated" in the app regardless of whether the session came through GSPro or straight from the monitor, so the source software never changes how a number is labeled — only the device behind it does.
Try it
Export your GSPro session the moment you finish playing, then upload it at / — or click "Explore a sample session" on that page to see how ContactCoach handles a session first, before you risk losing one of your own.