Jump to content
Note: This thread is 2911 days old. We appreciate that you found this thread instead of starting a new one, but if you plan to post here please make sure it's still relevant. If not, please start a new topic. Thank you!

Recommended Posts

(edited)
58 minutes ago, VOX said:

Biggest impact from being allowed to drop from 0.5" will probably be in the sand. No more plugged lie drops.

The proposal says a minimum of 1.0"

Edited by Rulesman

I would prefer a minimum height to drop from (over an inch, I guess). I think this could be messy when someone wants to drop as low as possible to the ground to get a good lie. I think it could lead to some arguments on the course about whether it was a proper drop.

Two thoughts: (1) knee height or (2) 6 inches. Knee height is probably not fair to taller people, but it would still be pretty close to the ground. 6 inches is a little hard to measure exactly, but I think that would be better than what they have currently.

-- Daniel

In my bag: :callaway: Paradym :callaway: Epic Flash 3.5W (16 degrees)

:callaway: Rogue Pro 3-PW :edel: SMS Wedges - V-Grind (48, 54, 58):edel: Putter

 :aimpoint:

Awards, Achievements, and Accolades

I'm glad they "kept" dropping, but there is still some gray area...if a ball is touching blades of grass when you drop it, but then it drops to the ground, is that a drop?

I wonder if they can do something like require that the ball is dropped while a player is standing?  You could lower (extend) your arm all the way, but never really get within a few feet of the ground.  And it'd be fairly easy to police, since a couple inches of "crouch" in the knee wouldn't help you much...to actually gain an advantage, you'd have to truly crouch or bend and that would probably guarantee a minimum drop height of a couple feet.

Eh, whatever, no strong feeling on this.  I'm glad the dropping thing is less mechanical, and very glad they didn't go with "placing everywhere", but I do wish there was an easy way to get some height on drops.

- John

Awards, Achievements, and Accolades

7 hours ago, Rulesman said:

The proposal says a minimum of 1.0"

I missed that.  Where does it say that?

In David's bag....

Driver: Titleist 910 D-3;  9.5* Diamana Kai'li
3-Wood: Titleist 910F;  15* Diamana Kai'li
Hybrids: Titleist 910H 19* and 21* Diamana Kai'li
Irons: Titleist 695cb 5-Pw

Wedges: Scratch 51-11 TNC grind, Vokey SM-5's;  56-14 F grind and 60-11 K grind
Putter: Scotty Cameron Kombi S
Ball: ProV1

Awards, Achievements, and Accolades

I don't mind these rules. I do like they take away the advantage some savvy golfers can have when dropping the ball. I like that the ball will be nearer to the where the ball originally came to rest. 

 

Matt Dougherty, P.E.
 fasdfa dfdsaf 

What's in My Bag
Driver; :pxg: 0311 Gen 5,  3-Wood: 
:titleist: 917h3 ,  Hybrid:  :titleist: 915 2-Hybrid,  Irons: Sub 70 TAIII Fordged
Wedges: :edel: (52, 56, 60),  Putter: :edel:,  Ball: :snell: MTB,  Shoe: :true_linkswear:,  Rangfinder: :leupold:
Bag: :ping:

Awards, Achievements, and Accolades

  • Moderator
8 hours ago, DeadMan said:

I would prefer a minimum height to drop from (over an inch, I guess). I think this could be messy when someone wants to drop as low as possible to the ground to get a good lie. I think it could lead to some arguments on the course about whether it was a proper drop.

I'm finding it kind of odd that they aren't recommending a minimum height much higher than 1". Just seems like it's not much of a "drop" from that height.

  • Upvote 1

Mike McLoughlin

Check out my friends on Evolvr!
Follow The Sand Trap on Twitter!  and on Facebook
Golf Terminology -  Analyzr  -  My FacebookTwitter and Instagram 

Awards, Achievements, and Accolades

(edited)
4 hours ago, David in FL said:

I missed that.  Where does it say that?

Rule 14.3 

But the basic requirement is that it "falls through the air before coming to rest." 

2 hours ago, mvmac said:

I'm finding it kind of odd that they aren't recommending a minimum height much higher than 1". Just seems like it's not much of a "drop" from that height.

It is really only trying to ensure the player doesn't carefully place it on a convenient protrusion (wormcast etc)

Edited by Rulesman

  • iacas unpinned this topic
Note: This thread is 2911 days old. We appreciate that you found this thread instead of starting a new one, but if you plan to post here please make sure it's still relevant. If not, please start a new topic. Thank you!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Want to join this community?

    We'd love to have you!

    Sign Up
  • TST Partners

    PlayBetter
    TourStriker PlaneMate
    Golfer's Journal
    ShotScope
    The Stack System
    FitForGolf
    FlightScope Mevo
    Direct: Mevo, Mevo+, and Pro Package.

    Coupon Codes (save 10-20%): "IACAS" for Mevo/Stack/FitForGolf, "IACASPLUS" for Mevo+/Pro Package, and "THESANDTRAP" for ShotScope. 15% off TourStriker (no code).
  • Posts

    • If you still have that code available, I would love to get a copy. We have PowerShell code that pulls indexes and individual 9-hole handicaps for the tee sets of the course we play. We have 40 players and use this data for skins. We do skins by flight which we have 4 of them A,B,C,D and without pulling this data it would be almost impossible to do in the application. Right now, we also grab each "card" as it comes off the course and put it into a spreadsheet to help us understand who won the round and helps us with skins. Each golfer is required to enter their own scores in GHIN also. Our goal is to have each golfer enter in the scores in GHIN but pull the individual hole scores down each week after the round is posted so that we can figure skins, and points. I found a site for APIs, but it is old referencing https://api.ghin.com/api/v1. Our current code uses https://api2.ghin.com/api/v1. I tried using that along with what was provided in the old doc, but it appears many of the API signatures changed. I'm hoping I can use the python code to get examples of the API calls I need. if nothing else I could recode ours to use python.
    • This is pretty interesting. I don't have a Stack radar so I can't use the app, but given what they say it should be fairly easy to come up with some kind of proxy to it if I spend an hour with a trackman. Just note what ball speed gives what distances and plot it. It's presumably not directly linear, but if you hit 50 shots between 30 and 100 yards, you'll have enough to pin down most yardages in that window (yards vs ball speed). Then rather than trying to match distances, just try to match ball speeds with whatever radar you do have. The whole strokes gained thing would be more difficult, but that's not really necessary to work on it. Or just buy a Stack radar...
    • I don't think that is what the study was showing. It just showed that golfers who spent less time over the ball performed better. It didn't say pending their normal pace.
    • No…? When we edit the title of topics, a little note appears.
    • Rush or delay your own pace and you are probably going to suffer in the long run. PGA pro are well oiled machines that work on an specific pace, it's not surprise that if you move them out of their normal routine things are going to go sideways. I normally don't rush shots, but I sometimes delay the trigger if I'm not feeling it. The result is a lack of athleticism, I kind of get a little stiff and I could loose some yards and accuracy.   
×
×
  • Create New...

Important Information

Welcome to TST! Signing up is free, and you'll see fewer ads and can talk with fellow golf enthusiasts! By using TST, you agree to our Terms of Use, our Privacy Policy, and our Guidelines.

The popup will be closed in 10 seconds...