Longest Drive, Longest Putt, Longest Hole Out stats fixed!

[Tim]

I know, I know - this have been wrong for a while.. but not anymore.

Starting with the scores after 12pm EST all of these stats will now be correct:

Longest Drive - Corrected to only count if the ending surface is 'fairway' or 'green'.
Longest Putt - Corrected to only count the longest "made" putt, not attempted.
Longest Hole Out - Corrected to only count if it was your last shot, and the surface was not green, and the carry distance greater than 0 (meaning a chip). Before it was also counting long putts.

Also, we will be adding a Meters or Yards in your profile this week that will let you see these stats in your preferred unit of measure!

Thanks!
Tim

[Deleted]

Thanks Tim! Sorry to ask immediately for even more lol, but can you clarify how you get these stats in the first place please? I always assumed you just pulled it from the game stats since they all already exist in the 'event stats' page, but Doyley mentioned on the stream that for any other stats people should provide calculations so the devs can do it. That implies the API isn't taking the in-game stats directly, but rather you guys code the calculations in from other data.

If that implication is correct, before we can start giving calculations for stat requests, can you let us know what scoring-based data you actually get? i.e. let's say we want proximity to hole (which we absolutely do ) - do you retrieve enough data so you can do this? The stat would be better if only counting when GIR is made or else it can be wildly skewed by being miles out, going OB or in the water. So you'd need:

- data that shows whether or not GIR is made on each hole
- data that shows the first putt length on each hole

Then you can simply filter the second variable to be recorded only when the first is true, and then add the second variable up and divide it by the GIR count to get the average distance to hole when making GIR. Is that doable do you think?

[mcbogga]

Strokes gained! We need it, it can be done and I know you want it - Tim, Doyley and Jeff...

When?

[SmilingGoats]

Oct 23, 2018 11:22:57 GMT -5 @larrymalone said:

Thanks Tim! Sorry to ask immediately for even more lol, but can you clarify how you get these stats in the first place please? I always assumed you just pulled it from the game stats since they all already exist in the 'event stats' page, but Doyley mentioned on the stream that for any other stats people should provide calculations so the devs can do it. That implies the API isn't taking the in-game stats directly, but rather you guys code the calculations in from other data.

If that implication is correct, before we can start giving calculations for stat requests, can you let us know what scoring-based data you actually get? i.e. let's say we want proximity to hole (which we absolutely do ) - do you retrieve enough data so you can do this? The stat would be better if only counting when GIR is made or else it can be wildly skewed by being miles out, going OB or in the water. So you'd need:

- data that shows whether or not GIR is made on each hole
- data that shows the first putt length on each hole

Then you can simply filter the second variable to be recorded only when the first is true, and then add the second variable up and divide it by the GIR count to get the average distance to hole when making GIR. Is that doable do you think?

We do not get the event data but rather data on every shot.  So for each hole we get Par for the hole and the User's score for the hole.  We get a true/false for Green in Regulation and Fairway in Regulation.  And then for each shot on the hole we get:

Surface (green, fairway, sand etc)
Carry Distance
Total Distance
Teeshot (true/false)

That's about it.  You can calculate most thing from that info.  For example, you can extrapolate whether the shot is a putt or not by interpreting Carry Distance and Surface.

[mcbogga]

Oct 23, 2018 13:02:00 GMT -5 SmilingGoats said:

Oct 23, 2018 11:22:57 GMT -5 @larrymalone said:

Thanks Tim! Sorry to ask immediately for even more lol, but can you clarify how you get these stats in the first place please? I always assumed you just pulled it from the game stats since they all already exist in the 'event stats' page, but Doyley mentioned on the stream that for any other stats people should provide calculations so the devs can do it. That implies the API isn't taking the in-game stats directly, but rather you guys code the calculations in from other data.

If that implication is correct, before we can start giving calculations for stat requests, can you let us know what scoring-based data you actually get? i.e. let's say we want proximity to hole (which we absolutely do ) - do you retrieve enough data so you can do this? The stat would be better if only counting when GIR is made or else it can be wildly skewed by being miles out, going OB or in the water. So you'd need:

- data that shows whether or not GIR is made on each hole
- data that shows the first putt length on each hole

Then you can simply filter the second variable to be recorded only when the first is true, and then add the second variable up and divide it by the GIR count to get the average distance to hole when making GIR. Is that doable do you think?

We do not get the event data but rather data on every shot.  So for each hole we get Par for the hole and the User's score for the hole.  We get a true/false for Green in Regulation and Fairway in Regulation.  And then for each shot on the hole we get:

Surface (green, fairway, sand etc)
Carry Distance
Total Distance
Teeshot (true/false)

That's about it.  You can calculate most thing from that info.  For example, you can extrapolate whether the shot is a putt or not by interpreting Carry Distance and Surface.

Or strokes gained.....

;-)

[Tim]

For any stats you want, just give me the formula and I'll get it in!

[Tenahka]

Thanks Tim

You guys do an AMAZING job behind the scenes, just letting you know that it's really appreciated!!!

[alexandre]

Ops.

[ErixonStone]

I would love Strokes Gained, but that requires Proximity to Hole for all shots. It also requires that TGCT maintain tour averages for scoring from particular distances/surfaces, e.g. "the average score from 175 yards out in a bunker is 3.2" and "the average score from 16 feet is 1.6".

[CuseHokie]

Oct 23, 2018 15:58:34 GMT -5 Tim said:

For any stats you want, just give me the formula and I'll get it in!

Scrambling?

Par or better for missed GIRs.

[Epiphanic]

Oct 24, 2018 8:50:47 GMT -5 ErixonStone said:

I would love Strokes Gained, but that requires Proximity to Hole for all shots. It also requires that TGCT maintain tour averages for scoring from particular distances/surfaces, e.g. "the average score from 175 yards out in a bunker is 3.2" and "the average score from 16 feet is 1.6".

Perhaps there's a way to calculate some sort of strokes gained without proximity to the hole. We already have average strokes taken on for specific hole in an event so a Strokes Gained:Hole stat is calculable currently. SmilingGoats showed that they can infer putts based on carry distance and surface. That should allow average putts taken by hole to be calculated. From that Strokes Gained:Putts can be calculated. Strokes Gained:Tee-to-Green would be simply the residual.

Obviously this isn't how Strokes Gained is calculated in real life, but something along these lines might give a reasonable proxy. Thoughts?

[mcbogga]

Nov 15, 2018 17:12:36 GMT -5 Epiphanic said:

Oct 24, 2018 8:50:47 GMT -5 ErixonStone said:

I would love Strokes Gained, but that requires Proximity to Hole for all shots. It also requires that TGCT maintain tour averages for scoring from particular distances/surfaces, e.g. "the average score from 175 yards out in a bunker is 3.2" and "the average score from 16 feet is 1.6".

Perhaps there's a way to calculate some sort of strokes gained without proximity to the hole. We already have average strokes taken on for specific hole in an event so a Strokes Gained:Hole stat is calculable currently. SmilingGoats showed that they can infer putts based on carry distance and surface. That should allow average putts taken by hole to be calculated. From that Strokes Gained:Putts can be calculated. Strokes Gained:Tee-to-Green would be simply the residual.

Obviously this isn't how Strokes Gained is calculated in real life, but something along these lines might give a reasonable proxy. Thoughts?

Strokes gained doesnt work like that, however. Its about what distance and lie the shots are from as well. For strokes gained putting as an example the distance from hole of the first putt is important.

[Epiphanic]

I understand that. But since the data that TGCT collects doesn't have distance to pin, calculating strokes gained on per shot basis is impossible. My suggestion is to calculate a reasonable proxy to strokes gained given the data that *is* available. In real life, strokes gained for each stroke taken equals the difference between the player's actual strokes taken and the field average. An event-based sum of this stat is already available on a given player TGCT profile page. It also appears that TGCT can calculate the average strokes taken for a specific hole in a round so a hole specific strokes gained stat is also easily calculable.

If we want to go deeper down the rabbit hole we can define the sections of the hole as tee-to-green and putts. From what SmilingGoats said earlier in the thread, which strokes are putts can be inferred based on starting surface and carry distance. So it should be possible to calculate the average number of putts taken on a given hole and from that we can calculate a player's strokes gained on the green. To calculate the strokes gained in the tee-to-green section is simply the residual between total strokes gained for the round and strokes gained via putts.

I'm aware that the real-life strokes gained stat is based on surface and distance and calculated on a shot-by-shot basis. And it'd be great if TGCTours had the data to be able to calculate a strokes gained stat for each player's shot in every round. However, it appears that the data needed to generate such a stat is not available. I'm simply suggesting an alternative method to calculate a strokes gained stat using the information that is available. It's obviously less granular, but still captures the essence.

[mcbogga]

Would be nice if API spit out distance left to hole or something like that, not just distance of shot....