Nice bounding box, dummy.

Nice bounding box, dummy.

While I admire the nostalgia of playing a virtual version of a golf course that is no longer around, if it doesn't exist currently, it should not be added to OpenStreetMap. Can you confirm whether or not this course is actually still there? Thanks.

Hello localbirder,

OSM doesn't have a concept of a green's "fringe", so you shouldn't be creating a ring around a fringe and labeling it "fairway" as there is already a fairway there and it doesn't make any sense to have a fairway inside of another fairway as that is redundant. I've cleaned up this particular area, but figured you might want to keep this in mind when mapping future golf courses. Thx.

Hi there Capn71,

I just wanted to let you know that golf=hole ways aren't meant to define an area around a fairway, but instead being that straight line (or couple of line segments) that show the approximate path from the tee to the green. I'm making a couple of changes around the first hole and thought you might want to know for future mapping you do. Thanks for the contributions.

There is a test version of OSM if you need to test out changes with software that you're developing. Maybe that would work better for you during testing. In the meantime, I'm going to delete this way as it was still there tonight and is officially the largest fairway with 4 nodes defined in the United States.

I don't know why you couldn't delete that short way, but I was able to delete it in changeset/118616187

Oh, interesting. I didn't realize they were building out in that area. I looked at some more recent sat imagery, and I can see the construction. Thanks!

Thanks for the reminder. ;-) I've been meaning to go here and throw some axes around.

Why was the way that defined the ditch deleted?

Never heard back so I went ahead and deleted these. Guess it will remain a mystery.

Hello GolfMapper,

When you come across something like the fairway around way/861230110, it's better for you to just modify the existing fairway instead of overlapping a new area that overlaps. The correct result is to have a single fairway area that defines the entire area.

If you have any questions, please feel free to reach out.

The map shows that holes 11 and 13 cross paths when teeing off. This seems a little bit dangerous and I'm wondering if the wrong tees were used for the starting point of one or both tees.

Hello Denomyc,

I wanted to point out some problems with some golf courses that you have edited in hopes that I can correct some "bad habits" which will hopefully lead to fewer clean-ups in the future.

If you look at way/955516626, you added an extra fairway area to extend the fairway around the edge of the green. Instead of adding another area though, it would be better if you could modify the existing way so that there aren't two overlapping fairway areas. You might need to "disconnect" the node that is shared between the fairway and the green first (either right click and see the pop-up menu, or use the "D" shortcut after selecting the node).

Hope this helps. If you have any questions, please let me know.

Thanks! The work on Phase I continues and will take at least a month by my estimates. But I’ve got the workflow smoothed out so the change files are generated automatically. It’s the manual verification that is the big effort now.

Hey Denomyc,

I see you have done some really nice, detailed golf mapping and continue to do so. I thought I'd point out some areas that you could improve on though since you seem to want to create nice courses.

I noticed that you overlapped a couple of bunkers (way/897983709) and I couldn't see a good reason for this. Am I missing something, or should these two be combined into a single bunker?

I other places like way/897983707, you map around a non bunker by putting several bunkers near each other. You might want to explore how to create a "multipolygon" in iD. You can create the outer boundary of the bunker with one polygon, and another polygon for the inner grass island and then combine the two to define a complex multipolygon.

leisure=golf_course#Common_mapping_pitfalls has some good information about how to map courses using multipolygons.

If I can be of any help further explaining this, please let me know.

Happy mapping,
b-jazz

Thanks for the catch (and fix). Appreciate it.

Hey John, I'm looking over some errors in the mapping of golf courses and I came across this course and found that several of the fairways are chopped up and mapped separately, but adjacent. I can't think of a good reason for them to be mapped that way and it goes against mapping "good practice" so I was wondering if I'm missing something or if I should go ahead and join those overlapping areas. Thanks.

Hi Cdurant,
What's the purpose of the "small patches"? They aren't correctly mapped as they are a patch of fairway inside a larger patch of fairway, so it makes no sense topologically. If there is an alternative purpose of the patches (maybe they are yardage markers or something), then they need to have different tags. Please let me know. Thanks.

Thanks for simplifying!