@David: What we are collectively trying to explain to you is that OSM takes an iterative approach. When the data are first time entered into OSM they might be somewhat inaccurate, but subsequent edits make them more refined and true to the reality. Purely deleting the data, as you are doing, does not improve anything.

In JOSM you can fast create the multipolygon relation with Ctrl+B or update an existing multipolygon with Shift+Ctrl+B. (Though I think you have to install utilsplugin2 first)

Hi David,
this is unfortunately not the first time, but I hope it will be the last time I have to say it. Please don't remove forests and other land covers. If you see any inaccuracies, you can easily move their nodes to fix the shape according to the recent aerial imagery.

It was actually just a normal pond.

Hi thanks for editing. Just a couple of questions. Why is it necessary to remove coastline tag from islands? Wiki says that it belongs there (natural=coastline).
And what does is_in:island=island tag mean? I don't see it anywhere documented.

Hi,
thanks for editing but in such cases we add `access=private` tag and don't delete the object itself.

Also please don't add hole numbers into 'name' tag. They belong to 'ref' tag.

Hi,
please don't use highway=path objects to draw outlines of parking lots (e.g. way/1080302313). Parking lots are tagged with amenity=parking.
Also please don't create overlaps between golf=green and golf=fairway. More information how to properly map golf courses can be found on wiki leisure=golf_course#Common_mapping_pitfalls

You're doing an amazing job, thanks!

That building is actually still there, just tucked under the tree canopy. In iD editor press "B" and choose "CT ECO Orthoimagery (2019)" or "Esri World Imagery (Clarity) Beta".

Hi, the driveway is behind a gate or has a no trespassing sign, you can add a `access=private` tag to the driveway line. In iD this can also be done by going to "Allowed Access > All > private"

Ok, if you know that a driveway is not to be used for delivery or general traffic, then you can add `access=private` tag which should prevent routing software to navigate through that section.

Correct, if there is a physical island then the correct way is to draw it as circle, because the car can't pass through. But if the island is missing or is just painted then it should stay as a turning_circle node.

Hi,
here you also deleted roads that still exist. They appear a bit damaged but it still seems cars could drive there. If the roads have no trespassing they should be tagged as access=private or access=no.

Hi again,
Also what I found in this changeset is that all the turning loops/roundabouts that you draw are in fact "turning circles" and those are correctly mapped as a node tagged as highway=turning_circle.
e.g. at the end of this road: way/17185414#map=19/41.88167/-72.66977

Here are more details on the distinction between the two types:
highway=turning_circle

Here you added two railway crossings between between a railway and a road that goes over the railway tracks on a bridge. This is clearly incorrect.

Here again you deleted lots of existing paths.
Also do you mind clarifying why is it important to add no-U-turn restrictions in parking lots and small driveways. Such restrictions are typically added only when there is a traffic sign prohibiting turning.

Here you as well deleted paths that exist.
I assume you are trying to use auto-validation tools. Please don't rely on these tools 100% because they can be faulty. Always inspect the object with imagery or survey before removing the object.

Hi And thanks for editing OSM. I looked at your edits and there are several problems.
1) You are deleting paths that and sidewalks that clearly exist. Always check with the latest imagery or do a in-person survey before doing modifications.
2) You are connecting roads that are not physically connected. E.g. road that is on a bridge with another road that goes under the bridge. Those have to remain unconnected otherwise the car navigation will be broken.
3) you delte skybridges: way/224144549 and way/224144525
4) You deleted this entrance that still exists node/2556089034

Please take your time getting to know how OSM works, before doing large scale edits as those can often involve errors. If you need help please reach out to me or join OSM slack osmus.slack.com

Hi,
Thanks for improving OSM. Just one thing that I noticed, please don't delete mapped driveways. These are valid data should be kept in OSM.

For this purpose we have tags `access=no` and `access=private` that indicate that such trail is not to be used.

You can find more information here:
osm.wiki/United_States/Trail_Access_Project