Let me try to address some of these issues in my response that I'm working on to your other comment so that we don't have two threads going. I appreciate the discussion.

Thanks for getting back to me malifica so we can discuss this further. I'm not sure exactly what is "comical". There is only so much that someone can do to correct mapping irregularities. Because I don't get to them all in one instant doesn't mean I don't care about them and won't eventually get to them. If you could point out the other failures, I'd be glad to discuss them and any plans that I have for them. Thanks.

As discussed in osm.org/changeset/163633938, you shouldn't be making your fairways and greens overlap, but instead you should be sharing every node at their border. Please see the wiki in the previous comments for further instructions on how to properly map these golf course features. Thanks.

As I wrote in osm.org/changeset/164269073, you shouldn't be using lollipop mapping when trying to place a feature like a bunker within another feature (like a fairway). See my previous notes for the wiki that describes the proper way to map these features. Please let me know that you've seen this comment. thanks.

RE: osm.org/way/1372369336

Your fairways and greens need to share all of the nodes between them, not just a select few. See the wiki for more helpful information about mapping golf courses. osm.wiki/Tag:leisure%3Dgolf_course

Also, don't draw lollipops in order to get around a feature contained in another feature. For example: a bunker in the middle of a fairway. See osm.org/way/1373179981 where you did this. The wiki mentioned above shows the proper way to use multipolygons to map something like that.

RE: osm.org/way/1373179979

Hello golf course mapper. The lines that define Fairways and Greens should never intersect or partially overlap each other and we noticed that they are overlapping in one or more of the fairway/green pairs in this changeset. If there is no obvious fringe around the green, the fairway should butt up against the green and every node between them must be *shared*. If there is a fringe around the green that is similar to the fairway, the fairway should extend around the green and the two objects should be merged together into a multipolygon (See osm.wiki/Relation:multipolygon for how to create them with your map editor). Please read the wiki for instructions and examples of how to better map golf courses: osm.wiki/Tag:leisure%3Dgolf_course#Common_mapping_pitfalls. If you have any questions, please reply here and I'll gladly help clarify things. Thanks!

Interesting. I didn't realize there were separate notification prefs for those two types of communications. I get emails for both, so I assumed everyone else does as well.

You shouldn't be using the "lollipop" style of mapping as seen in osm.org/way/1372794901. You need to create proper multipolygon relations in order to map features like roughs/bunkers that are within other features. Please see osm.wiki/wiki/Relation:multipolygon and osm.wiki/wiki/Tag:leisure%3Dgolf_course#Common_mapping_pitfalls for help in understanding how to map this situation.
And you shouldn't be creating a multipolygon just to split the fairway into two segments. That's not the right use of multipolygons.

If those aren't clear, please let me know and I'll help explain them further. Thanks.

Hello golf course mapper. The lines that define Fairways and Greens should never intersect or partially overlap each other and we noticed that they are overlapping in one or more of the fairway/green pairs in this changeset. If there is no obvious fringe around the green, the fairway should butt up against the green and every node between them should be *shared*. If there is a fringe around the green that is similar to the fairway, the fairway should extend around the green and the two objects should be merged together into a multipolygon (See osm.wiki/Relation:multipolygon for how to create them with your map editor). Please read the wiki for instructions and examples of how to better map golf courses: osm.wiki/Tag:leisure%3Dgolf_course#Common_mapping_pitfalls. If you have any questions, please reply here and I'll gladly help clarify things. Thanks!

Well. That was something.

Yup, encoding problem. This one should work.

osm.wiki/Tag:leisure%3Dgolf_course

Your latest argument makes no sense and isn’t convincing anyone that you understand mapping. If you’re saving your best arguments for another day, I guess we won’t be blessed to read them.

osm.wiki/Tag:leisure%253Dgolf_course

osm.wiki/Relation:multipolygon

osm.wiki/Keep_the_history

First you would need to find out what map provider is used by your vehicle for navigation. Is this something built into your car or are you just talking about a navigation app on your phone?

I see you are adding a bunch of addresses to the building, which isn't the best way to go. I'm not aware of routing software that looks for housenumber1..N. I've added a few address points that would be the "more correct" way to map multiple units in a building.

You should also be aware that there can be a huge lag time (weeks) between when you make a change to a map and when that actually shows up on navigation apps.

I feel your pain. I've dealt with housing complexes that had unnecessarily complex routing issues.

I'm sorry, but this isn't a question of opinions. It's just proper mapping vs improper mapping. And yes, this is a community project and we all need to respect each other's work and abide by a common set of goals and practices. Multipolygons are correct. While the lack of a multipolygon isn't necessarily "damaging", removing a proper polygon is most certainly damaging. Deleting other people's fairway so that you can draw your own *is* damaging. Sloppily drawing fairways across a green *is* damaging.
We appreciate golf simulator mappers filling out golf courses. There is no question about that, but we want them to map according to community standards.
There are well over 20,000 fairways in the US that have the fairway overlapping the green and they need to be fixed thanks to simulator mappers. It's going to take me a year to fix that and try to get others to stop that bad practice.

When you draw the polygon for a fairway, you are saying that absolutely everything within that polygon is a fairway. So even if there is a green in that fairway boundary, you are saying that it is a fairway as well. Both a fairway AND a green at the same time. The purpose of a multipolygon is to say everything within that boundary is a fairway EXCEPT any "inner" relations of the multipolygon. And yes, roughs should be drawn correctly and tagged as multipolygons as well.
I'm guessing you would probably agree, but just struggle because a tool you use doesn't handle them properly.

Thanks for reverting. Just because a third party tool doesn't behave correctly is no excuse to not map properly. There are hundreds of other apps/tools/services that use OSM and they all need to be following the same guidelines.

Are you talking about Chad's Tool? If so, maybe you could pressure the maintainers to incorporate the following fix into their next release: https://github.com/chadrockey/TGC-Designer-Tools/pull/143

It sounds like that might resolve the problem.

That is 100% not true. Can you please tell me why you think that is? If you'd like to join the various forums/communities and discuss there, I'd be happy to join you.

Hello golf course mapper. The lines that define Fairways and Greens should never intersect or partially overlap each other and we noticed that they are overlapping in one or more of the fairway/green pairs in this changeset. If there is no obvious fringe around the green, the fairway should butt up against the green and every node between them should be *shared*. If there is a fringe around the green that is similar to the fairway, the fairway should extend around the green and the two objects should be merged together into a multipolygon (See osm.wiki/Relation:multipolygon for how to create them with your map editor). Please read the wiki for instructions and examples of how to better map golf courses: osm.wiki/Tag:leisure%3Dgolf_course#Common_mapping_pitfalls. If you have any questions, please reply here and I'll gladly help clarify things. Thanks!

Thanks for helping map golf courses. There are some serious problems with your edits however and your mapping needs to be fixed going forward so you don't continue to step on the efforts of others. For starters, read the following wiki: osm.wiki/Keep_the_history on how important it is to *not* delete map elements when you should be updating them instead. You have been breaking multipolygon relations when you do this. You should also read the golf_course wiki (osm.wiki/Tag:leisure%3Dgolf_course#Common_mapping_pitfalls) and the general wiki on how to properly work with multipolygons (osm.wiki/Relation:multipolygon#iD). Until you understand these issues, please refrain from modifying other mapper's work. Thanks. If you have any questions, please reach out and we'll gladly help you.