User is continuing to overlap landcovers. They "fixed" the issue they caused in this case in changeset:
changeset/145221413
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/145220897

Why are you continuing to map things with overlapping landcovers. I have mentioned this as a changeset comment previously, on multiple occasions, but yet, you are continuing to purposely overlap areas. It seems you know better since after deliberating changing it to overlap, you are changing it back.

As a reminder, do not edit for the renderer. Just map it correctly the first time, rather than changing it back and forth.

I went ahead and updated it to private for you last night when I readded it. :)
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/145087006

Thank you for this edit. Looks good.
---

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

Why did you intentionally map the house as a golf rough?

Why did you intentionally map the building as a golf rough?

You've done this multiple times across multiple changesets, including:
changeset/145114159

Why did you map houses as golf roughs?

Why did you map the parking lot as a golf rought? This is incorrect tagging, and I am pretty sure you are just doing it for your golf game.

Do not tag for the renderer. Ensure you are only using the correct tags.

'Changeset has been reverted since this path clearly exists. access tags can be used instead to denote it is private, but deletion is not permitted. You can read more on why we don'"'"'t remove "private" roads here:

osm.wiki/Why_we_won%27t_delete_roads_on_private_property#:~:text=In%20OSM%2C%20we%20map%20what'"'"'s,path%20and%20add%20it%20again.'

changeset/145137259

I have mentioned this previously to Faddie. Did they adjust the others?
---

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

Why did you map the fairway with a small string to simulate a hole? A multi-polygon relation should be used.

I know I have gone over this with you before. Rather than continuing to create the same mistake and continuing to get comments on your changeset, please try to avoid repeating mistakes. If anything that I have previously said in a comment is unclear, please let me know. We're not here to make it difficult, but this is a community who is always welcoming, we just want to make sure the edits are of high quality. Continuing to submit changesets with the same error(s) is infuriating, especially when comments have been posted multiple times pointing out resources and other tools.

Please reach out via changeset comment if you have any questions or need additional guidance. Thanks.
---

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

Please avoid deleting and readding features. It is strongly encouraged to just edit the feature that exists.
---

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

Again, I am noticing that you are "lollipoping" landcovers. Rather than using a multirelation, you are trying to mimick a hole in one landcover by creating a thin strip where it doesn't touch. Please read up here to avoid further mapping pitfalls.:

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

I have already contacted you about this. Continued poor mapping will result in escalation to DWG.

Do not map landcovers such that they partially overlap.

Also, do not map such that landcovers overlap partially.

Again, I am noticing that you are "lollipoping" landcovers. Rather than using a multirelation, you are trying to mimick a hole in one landcover by creating a thin strip where it doesn't touch. Please read up here to avoid further mapping pitfalls.:

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

I have already contacted you about this. Continued poor mapping will result in escalation to DWG.

Again, I am noticing that you are "lollipoping" landcovers. Rather than using a multirelation, you are trying to mimick a hole in one landcover by creating a thin strip where it doesn't touch. Please read up here to avoid further mapping pitfalls.:

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

I have already contacted you about this. Continued poor mapping will result in escalation to DWG.

Again, I am noticing that you are "lollipoping" landcovers. Rather than using a multirelation, you are trying to mimick a hole in one landcover by creating a thin strip where it doesn't touch. Please read up here to avoid further mapping pitfalls.:

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

I have already contacted you about this. Continued poor mapping will result in escalation to DWG.

Again, I am noticing that you are "lollipoping" landcovers. Rather than using a multirelation, you are trying to mimick a hole in one landcover by creating a thin strip where it doesn't touch. Please read up here to avoid further mapping pitfalls.:

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

I have already contacted you about this. Continued poor mapping will result in escalation to DWG.

Why did you not connect the golf cartpaths with a bridge where there is one? You seem very detail oriented, so I encourage you to add the last bit of detail. I have gone ahead and added the cartpath bridge for you.