Thanks for creating these greens, but please make sure your greens don't intersect with other existing (or created) golf areas like fairways. If you need to fix someone else's work, please do so that it doesn't create an inconsistency (error) in the map. Thanks.

Hey there ICT,

Just wanted to let you know that golf holes have a direction to them and go from the tee to the green. I've gone ahead and fixed them on this course but wanted you to know for future mapping. Thanks.

Hi Jaker, I just wanted to let you know I made a couple of small changes to your golf course mapping. The start of the golf=hole line you drew in a couple of places was labelled as a golf=tee. But the area around that was already marked as a tee, which is redundant. So I removed the tag on the node itself. Just thought you'd want to know.

RE: way/1443109313

There are a couple problems with this "rough" area. The first is that it crosses over cart paths. It should be kept to the grass, so should be split into two whenever a path intersects the rough. The second problem is that it intersects with a bunker. Areas like fairways, roughs, greens, bunkers, tees, etc should never intersect each other.

If you could go back in and fix this, I would appreciate it. Thanks.

You're the best! Thanks.

Hey wadenick, looks like you are doing a lot of great work. However, I did come across this one bunker (way/1435238413) that seems to have been ignored as you were drawing the fairway and crossed over it. Seeing how all of the other bunkers here are correct, I'm guessing this was just a mistake.

Thanks for getting back to me Chris. Much appreciated. You are correct in saying that putting fairway/green pairs into a multipolygon relation "isn't mandatory". However, taking an existing pair that is in a relation and breaking that relation is frowned upon.

As for getting the author to make a change, that would be fantastic. If you are talking about "Chad's Tool", there already exists a fix that just hasn't been incorporated yet. It's been out there for at least 6 months. Any pressure you can put on the author would be appreciated. If you are technical, I'm guessing you could incorporate that fix in your own fork of the tool and have a private working version. If that is the tool you're talking about and you need more info, let me know.

Hey Chris. What you've done here with "removing inner/outer definitions" is incorrect. A fairway that surrounds a green is defined with a multipolygon with the fairway as the outer and a green as the inner. Please stop making changes to relations unless you fully understand how they are used. Thanks.

Holes shouldn't have "names" typically. There are rare exceptions, but the hole is not named "1". It has a reference number of "1" and that's how you know which hole it is. Please don't add names in the future. Thanks.

You need to work with the author of your tool to implement a fix on their side. OSM has strict, well documented, standards on how to map everything from roads to golf courses to zoos. This isn't an OSM problem, it's a golf simulator problem.

This is a long standing bug that they are aware of. There is even a fix that has been proposed that hasn't been integrated yet. See https://github.com/chadrockey/TGC-Designer-Tools/pull/143. Maybe you could add your voice to the pull request asking it to be incorporated. If you're technical enough, you could pull it yourself into a private version of the tool and run your own fixed version.

Breaking golf courses in OSM and causing others to have to clean up after you will likely result in a ban. And honestly, none of us want to see that happen. Thanks.

RE: way/1441878752

Please don't use the "lollipop" style of mapping golf course elements as you've done in the URL above. You need to create proper multipolygon relations in order to map features like roughs/bunkers that are within other features like fairways. Please see leisure=golf_course#Common_mapping_pitfalls and osm.wiki/Relation:multipolygon for help in understanding how to map this situation. If those aren't clear, please let me know and I'll help explain them further. Thanks.

They will be. It takes time to correct years of bad practices. The vast majority of them have already been fixed.

This edit is incorrect and breaks the existing relation.

Please see the wiki that explains this: osm.wiki/ID_understanding_golf_course_relations

thanks

I tried to revert my change, but since you've made additional edits to the area, that creates conflicts that are nearly impossible to resolve. Sorry.

While you're in there, please don't have separate fairways for the main fairway and for the fringe around the green. They really should be a single fairway. Even if there are subtle difference in how the grass is cut. Thanks.

Reverted this and several other changes on this course over the last 24 hours that violate rule #1 of golf course mapping: golf course areas (fairways, greens, roughs, tees, etc) should not intersect each other. The previous versions of these holes were correct. If you need to adjust geometries, please make sure you read the golf_course wiki and follow the rules as laid out there. Thanks.

You made some changes to the green at way/685037079. It used to be a multipolygon with a fringe defined by the outer way/fringe and the green. But somehow the fairway was deleted and the relation between the two is "broken". Not sure what the purpose of the change was. Sometimes you see people deleting a feature entirely and then re-adding it from scratch and wind up with this situation, but that doesn't appear to be the case here.

I'm starting to write a wiki article about how to handle multipolygon relations and golf course mapping, but it doesn't directly match this case, but maybe you'll find it useful how to deal with relations in iD (which can be confusing).

osm.wiki/ID_understanding_golf_course_relations

RE: the area around node/13205320063

When drawing golf course areas (such as greens, fairways, bunkers, tees, etc.), please be aware that the ways used to outline those areas can't cross over each other. Fairway outlines shouldn't cross over greens or bunkers or other fairways for example. In the case above where you have a rough next to another rough, all of the nodes at the border should be shared between each rough. If you could go back and clean up where you've made this mistake, that would be helpful. But more importantly, if you could stop from doing this in the future, it would be greatly appreciated. Please read the wiki for instructions and examples of how to better map golf courses: leisure=golf_course#Common_mapping_pitfalls. If you have any questions about golf course mapping, feel free to reach out.

I reverted this change as there were several problems with it.

* You broke up the fairway on the first hole into two line strings and then combined them with a multipolygon. There isn't any reason to do this. It should remain as a single polygon.
* You removed the fringe around the first green. The fringe exists and was drawn correctly.
* When you did remove the fringe, you reused nodes on the outer side of the green which is incorrect when including the green inside the fairway.
* On the second green, you crisscrossed the fairway and green boundaries. They shouldn't intersect as they did.

If you have any questions about this, please reach out. Thanks.

Thanks for helping out with golf courses. Please don't use two fairway areas to define a single fairway (one for the main fairway, and another around the green). Just use one single fairway that goes all the way around. Thanks.

Thanks for letting me know!