Well, it's not just Illinois (or Indiana or Iowa) that is the problem. It's the entire country. I have some rudimentary tools that watch all the changes to golf course features (greens, fairways, water hazards, etc) and if any change is made that violate certain "rules", it shows up a on a report that I look at every day.  So when you reduce the nodes in a golf green for instance, that's great and all, but if that green already has errors in it (typically being crossed by a fairway due to historically bad golf course mapping), it shows up on my report and makes extra work for me.

If there is some way we could coordinate to reduce the noise in my nightly reports, it would make my life a lot easier. This could be you giving me enough heads up that I can fix these fairway/green errors before you come along, or it could be you not applying your fixes to golf course objects that have other errors on them. I'm open to suggestions. Thanks.
