Tom,
Would you mind explaining your rational for deciding what trees should be removed when you are consulting or completing a master plan for a course?
Thanks.
I have never tried to prepare a checklist as Mike Policano did, but his list of reasons is pretty good. I would have substituted "room to play" for playability and "views" for aesthetics, but it's a good list.
In the master plan phase we are deliberately vague about such things, because no one really wants to hear the number of trees that ought to be taken out. I've worked at clubs where we had to take out 600, 800, even 1000 trees -- and we never would have gotten permission at the start of the process if we had used those numbers. Usually, though, I've found that when we open up a couple of holes to where they should be, the light comes on for most members, and most of the resistance melts away ... although there are a few members at any club who feel strongly that NO tree should ever be removed. [I just wish those same people hadn't overplanted the course to begin with.]
We have been whittling away at the trees on Medinah #1 for the last month, and it is a VERY different course now than it was a month ago. Some of the trees had to go for grading work including drainage detention, so there are some big holes in the landscape where it would be nice to plant a few trees when we're done [if the engineers let us!]. There are also places along the perimeter of the course (Medinah Road) where more planting is warranted, and we have some nice trees we've preserved to move into those spots. But at the same time, we've adjusted the engineers' plans to preserve a few more big old oaks, and done our best to highlight the big trees which remain -- whereas previously you couldn't see the trees for the forest of little ones that had been planted.