Jump to content
Note: This thread is 3148 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

Hi guys, hoping to get some clarity on this situation. During a club match recently I marked my ball on the green and I then proceeded to tap the marker down with the ball. As I lifted the ball up, the marker stuck to it briefly and landed about six inches behind where I had initially marked. Neither my playing partner nor I knew how to proceed for sure, so I added a 1 stroke penalty and replaced the marker as near to where it should have been as possible. As it happens, I lost the hole due to the extra stroke, but after looking at Rule 20-1, I'm not sure I should have incurred a penalty stroke or not?

I went on to win 2&1 in the end so thankfully it didn't make a huge difference, but if the penalty shouldn't have been added and let's say I lost the match by 1 hole, how would that be rectified at the end?

FWIW, the ball marker I used has a fairly soft material on top which obviously was a little sticky, it's never happened before, but definitely lesson learned!

Thanks guys

 

 


  • Moderator

I've had this happen to me multiple times.  You can replace the marker as closely as possible to the original site of placement at no penalty. I don't remember the precise rule number or decision (if it is one).

Philip Kohnken, PGA
Director of Instruction, Lake Padden GC, Bellingham, WA

Srixon/Cleveland Club Fitter; PGA Modern Coach; Certified in Dr Kwon’s Golf Biomechanics Levels 1 & 2; Certified in SAM Putting; Certified in TPI
 
Team :srixon:!

Awards, Achievements, and Accolades

You're right with respect to Rule 20-1.  The marker should have been replaced with no penalty since the movement of the marker was directly attributable to the specific act of marking the ball.

Decision 20-1/6 applies.

  • Upvote 1

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

Thank you for the replies, I'm even more pleased it didn't affect the outcome of the match now. Good to know for future situations. 


Note: This thread is 3148 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...