Do not partially overlap areas.

Do not wrap areas around themselves to simulate "holes". Multipolygon relations should be used instead.

Do not delete features just to re-add them...
---

Published using OSMCha: https://osmcha.org/changesets/149753972

When adding buildings, be sure to press "Q" to square them and give them right angles.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/149755545

Do not partially overlap areas. Please review this webpage before making further edits:

leisure=golf_course#:~:text=the%20building%20itself.-,Common%20mapping%20pitfalls,-Adding%20name%3D*
---

Published using OSMCha: https://osmcha.org/changesets/149757038

Rather than creating all these areas to try and create holes, creatively, you should use one large are then put holes using mutlipolygon relations.

These sand trap areas will need to be merged.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/149653661

What are you doing? Why did you drag these nodes intentionally just for a download? Damaging data (whether temporary or not) for a download is not permitted on OSM.
---

Published using OSMCha: https://osmcha.org/changesets/149659077

Do not make temporary edits to the map for your golf game.

They have made similar edits since. I just reported them to the DWG.

Seems they already have a block for doing this type of edit.

Do not map pools as buildings...

This is not how you map driveways... I have contacted the DWG regarding these changesets and problematic mapping.

Do not use skinny lines and close points to try and connect two points, multipolygon relations should be used instead.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/149592555

As stated before, there are errors that are thrown when you map areas with partial overlap. The database and most renderers are unable to figure out which is on "top" when they partially overlap. People do care and they do notice. It may not be right away, but it happens, especially when focused on resolving errors and ensuring a high quality map.

It is clear you are mapping for the renderer. There are many services that rely on OSM data, beyond just a little golf game, and it is important that the data follow certain guidelines to ensure consistency across all those swrvices.

There is no golf course where the fairway and greens co-exist in the same space. They touch, yes, but there is no small area (or corners) of the green where there is a fairway somehow underneath and coexisting in the same space.

I continue to remind people mapping golf courses to review this page on golf tags, especially the section on common pitfalls to avoid. Specifically, you are mapping partial overlaps, which is very explicit and even has a photo!

leisure=golf_course#:~:text=Overlapping%20green/fairway/rough%20polygons%20(see%20graphic%20below).

Further, problematic mappers who repeatedly map in poor quality with errors are documented and handled by the DWG:
osm.wiki/Problematic_mapping/golf

Do not partially overlap areas...
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/149576946

Edit looks good.
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/149566012

Do not partially overlap landcovers.
---

Published using OSMCha: https://osmcha.org/changesets/149574644

DO NOT PARTIALLY OVERLAP AREAS!
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/149532419

...dude...

Again, I have merged your areas to be a large area and multipolygon as I have stated many times before...
---

Published using OSMCha: https://osmcha.org/changesets/149547829

Access tags should be used for the "private" portions.
---

Published using OSMCha: https://osmcha.org/changesets/149536438

Corrected.

I somehow missed it already being tagged.
---

Published using OSMCha: https://osmcha.org/changesets/149505371