Do not partially overlap landcovers (fairways and greens). This has been mentioned multiple times. Please acknowledge receipt and understanding of this comment.

You have not acknowledged previous comments or responded, yet are continuing to map with the same mistakes. I have not received a DM or other form of communication explaining why you are continuing to map in this manner. Doing so may result in referral to DWG for further action.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/148888757

As mentioned previously, do not partially overlap areas...
---

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

Access=private was already tagged to the ways. This is in accordance with OSM guidelines. Do not delete ways/features just because they are private. This is not the solution. You can read why here:
osm.wiki/Why_we_won%27t_delete_roads_on_private_property

osm.org/changeset/148892143

Do not partially overlap areas.
---

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

Do not partially overlap areas...
---

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

Do not "lollipop" areas to create simulated holes in an area. You should use multipolygon relations instead.

This changeset has been reverted in part or full to remove "fake holes" in the area.

I highly suggest you review the "Common Mapping Pitfalls" section of the wiki prior to making further edits:
osm.wiki/Tag:leisure%3Dgolf_course

osm.org/changeset/148879843

Why are you continuing to change service roads incorrectly to cartpaths? Do not change things to what they are not just for your silly golf game. Do not map for the renderer...
---

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

Do not "lollipop" areas to create simulated holes in an area. You should use multipolygon relations instead.

This changeset has been reverted in part or full to remove "fake holes" in the area.

I highly suggest you review the "Common Mapping Pitfalls" section of the wiki prior to making further edits:
osm.wiki/Tag:leisure%3Dgolf_course

osm.org/changeset/148879750

I am not sure. Thanks for the info. I was wondering who the actual heck tries to build a lavish and water demanding golf course community in the middle of the desert. Hahaha.

The roads have started construction, so I think construction tag is more appropraite than proposed since the ground has actually been broken. Thoughts?

Now, I recognize there are a few segments where the road hasn't been built/paved like the road *into* the community. I was assuming those segments were completed since imagery was taken. I'll adjust it a bit more tonight based on imagery to construction and lower road status from tetriary to minor/service as appropriate.

Why did you delete all these features?
---

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

Do not "lollipop" areas to create simulated holes in an area. You should use multipolygon relations instead.

This changeset has been reverted in part or full to remove "fake holes" in the area.

osm.org/changeset/148866920

Do not "lollipop" areas to create simulated holes in an area. You should use multipolygon relations instead.

This changeset has been reverted in part or full to remove "fake holes" in the area.

osm.org/changeset/148866880

Do not "lollipop areas to simulate a hole. Multipolygon relations should be used instead.

Do not partially overlap landcovers (fairway and putting green) for example.
---

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

Couple things:
1) Do not delete and readd. Just manipulate what is mapped to preserve edit history.
2) Do not "lollipop" landcovers to simulate holes. Multipolygon relations should be used instead.

I have resolved this for you for this changeset.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/148837948

This changeset has been reverted for the following reasons:
* Partial overlap of landcovers
* Removal of features to redraw them
* Many landcover areas split up to resemble multipoloygons, rather than creating multipolygons

I stongly advise you to read the following wiki section PRIOR to making further edits:
osm.wiki/Tag:leisure%3Dgolf_course#:~:text=the%20building%20itself.-,Common%20mapping%20pitfalls,-Adding%20name%3D*

osm.org/changeset/148833657

This changeset has been reverted for the following reasons:
* Partial overlap of landcovers
* Removal of features to redraw them
* Many landcover areas split up to resemble multipoloygons, rather than creating multipolygons

I stongly advise you to read the following wiki section PRIOR to making further edits:
osm.wiki/Tag:leisure%3Dgolf_course#:~:text=the%20building%20itself.-,Common%20mapping%20pitfalls,-Adding%20name%3D*

osm.org/changeset/148833244

This changeset has been reverted for the following reasons:
* Partial overlap of landcovers
* Removal of features to redraw them
* Many landcover areas split up to resemble multipoloygons, rather than creating multipolygons

I stongly advise you to read the following wiki section PRIOR to making further edits:
osm.wiki/Tag:leisure%3Dgolf_course#:~:text=the%20building%20itself.-,Common%20mapping%20pitfalls,-Adding%20name%3D*

osm.org/changeset/148832090

This changeset has been reverted for the following reasons:
* Partial overlap of landcovers
* Removal of features to redraw them
* Many landcover areas split up to resemble multipoloygons, rather than creating multipolygons

I stongly advise you to read the following wiki section PRIOR to making further edits:
osm.wiki/Tag:leisure%3Dgolf_course#:~:text=the%20building%20itself.-,Common%20mapping%20pitfalls,-Adding%20name%3D*

osm.org/changeset/148832087

This changeset has been reverted for the following reasons:
* Partial overlap of landcovers
* Removal of features to redraw them
* Many landcover areas split up to resemble multipoloygons, rather than creating multipolygons

I stongly advise you to read the following wiki section PRIOR to making further edits:
osm.wiki/Tag:leisure%3Dgolf_course#:~:text=the%20building%20itself.-,Common%20mapping%20pitfalls,-Adding%20name%3D*

osm.org/changeset/148830429