News:

Welcome to the Golf Club Atlas Discussion Group!

Each user is approved by the Golf Club Atlas editorial staff. For any new inquiries, please contact us.


JJShanley

  • Karma: +0/-0
Which Variables Merit Discussion?
« on: June 14, 2017, 10:59:04 AM »
The presence of strimmers and flymos (as we call them in the U.K.) to trim tall grass on several holes at Erin Hills yesterday sent Golf Channel into a brief frenzy.  Two of the panelists discussed briefly Mike Davis' ability to switch up a number of tees for certain holes this morning, but also the fact that Erin Hills will play to a par 72.


GCA.com contributors have argued persuasively that architecture that provides an enduring test trumps set-up, based on resistance to par or otherwise.  Although courses (championship venues or otherwise) may offer contrasting challenges, the merits of which we may wish to discuss, to what extent should the course blend into the background as a round or championship unfolds.


Does an official's ability to move tees a significant distance or change an angle of play deserve as much discussion as does the potential for inclement weather at, say, the Open Championship? 


Does golf, which through the Golf Channel and other media has a 24-hour news cycle, simply need to fill time by discussing anything that appears, whether set-up or which putter a player will use for the first time that week?

corey miller

  • Karma: +0/-0
Re: Which Variables Merit Discussion?
« Reply #1 on: June 14, 2017, 11:09:55 AM »

A player better than me, that has played in competitive multi-day tourneys might have a different opinion but I do wonder why such "flexibility" is needed?  Do they let the players know where the course set up for each day will be  prior to the event? And if not, can't Davis set up the course any day for the benefit of one player?

Would be a little nervous if MLB was able to make a decision as to home plate umpire after each game of the World Series....


Tags:
Tags:

An Error Has Occurred!

Call to undefined function theme_linktree()
Back