Again, you are deleting features with no discussion, and no details in your changeset comments.

Please immediately explain why you are deleting these features beyond "Updated", or again, this changeset will be reverted due to vandalism.

What is your reason for deleting all these features? This is not the first time you have just deleted all these features that were properly mapped and it looks like vandalism.

Please more descriptive than "Updated", especially when mass-deleting features, and explain why you are mass-deleting these features.

Reverted changeset due to mass deletion. Please do not delete features when they still exist and are mapped correctly.

changeset/150371707

Reverted changeset due to mass deletion. Please do not delete features when they still exist and are mapped correctly.

changeset/150371705

Reverted changeset due to mass deletion. Please do not delete features when they still exist and are mapped correctly.

changeset/150371699

Individual trees should be mapped as nodes, not tiny woods.
---

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

Why did you delete these features?
---

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

Again, do not delete and readd features. This causes the loss of history for the various features. Further edits doing the same thing (without a response from you) will result in escalation to the DWG for assistance.
---

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

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

Do not "lollipop" features.

Actually, changeset reverted.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/150196834

Please map features as they are. Parking aisles should be mapped as parking aisles, and NOT cartpaths. I have gone through and corrected this error for you.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/150196834

Do not try to incorrectly map parking lots as buildings. changeset reverted in part or full.

When adding buildings and other features with 90 degree corners, press "Q" when it is selected to square the corners.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/150187709

Do not partially overlap areas...

Do not "lollipop" features by folding an area back upon itself to simulate a hole in the area. Multipolygon relations should be used instead.

Do not partially overlap areas.

Do not delete features just to readd them with less quality and more errors. Again, you have partially overlapped areas, and this is not allowed on OSM.
---

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

Do not falsely change river areas to a golf water feature. This changeset has been reverted in part or full.

Copied private message received from user=jpotas for public discussion:

"I merged the sand traps that you messaged me about. I don’t really understand why they had to be merged but I did it anyways. For practical use, the way I had them mapped would work for any commercial application.

As far as ading extra splines, I had to drag a spline from a couple features in order for my software to pick the feature up. I can not explain why this happens but in order to get the features to download as accurately as possible I have to do this. I then immediately correct them, within a matter of a minute.

As a side note, when I finish mapping a course, it is extremely accurate and very useful for anybody that needs the information at a later date. This should be much better than not being mapped at all. I do not understand the “practical” reason for the different conforming issues that OSM admins sometimes have with my mapping. Commercial applications will see two sand traps side by side, they don’t need to have them mapped as one large sand trap. Boundries will match. Please explain and include commercial apllications that are affected if you would please, it would help me understand.

Thank you"

As discussed previously, you should not make changes that damages the OSM dataset just for your renderer or application. If your software is unable to read and interpret OSM data that conforms to OSM standards, then that is an issue with whatever software you are using.

OSM has guidelines to ensure software (when properly designed) can read data correctly. Making intentional changes that do not represent reality or mapping with poor quality (partial overlapping, simulated holes, etc.) Is against the OSM guidelines.

You are not the only user of OSM data, and thus the guidelines that are on the Wiki have to be respected.