Immediately stop deleting data!

Those water areas are clearly fake. Even in the latest imagery there is forest in their place.
Please don't create fake features.

Here again. Please use multipolygon when there is a bunker inside a fairway.

1) Please don't delete objects just to replace them with a worse and less detailed version.
2) Don't create overlaps between green and fairway.
see wiki for details how to map golf courses correctly: leisure=golf_course#Common_mapping_pitfalls

Please don't create "lollipop" extensions when there is a bunker inside the fairway. Please use multipolygon.
Please refer to wiki how to properly map golf courses:
leisure=golf_course#Common_mapping_pitfalls

Same here. You deleted a perfectly fine fairway and drew almost exactly the same shape in its place.

Hi,
can you explained what was incorrect on those fairways that they needed to be deleted? They match recent imagery just fine and those you draw follow the same shape.

It seems you are right that the E Grand Street ends at house #19. I can see the same on [Stonington GIS portal](https://gis.stonington-ct.gov/ags_map/). I split the road and renamed the eastern half to Salt Acres Road. Thanks for bringing this to attention.
[Bing Streetside](https://www.bing.com/maps?cp=41.334939~-71.902559&lvl=17&dir=244.805&style=x&v=2&sV=1) from June 4, 2015 shows three signs: Causion Drive slowly, Dead End and Causion Children at Play. Could that be what you saw?

In iD you can split roads by selecting one of its nodes/points then right clicking on it and selecting "Split".
Also It's not good to use Google Maps because they are copyrighted. But one can use Bing Street Side or Mapillary. Just press "U" in iD and select them from the menu.

Happy Mapping!

Hi Andy,
thanks for contributing, but are those streets really for private use only? We typically mark road as access=private when there is a No Trespassing sign or an entrance gate. From satellite imagery there seems to be several cars driving or parking on that street.

That's great, thanks!

I can also see the same issue in OsmAnd. After poking around it seems to me that the most likely cause will be that the boundary in this place is using a part of coastline (www.openstreetmap.org/way/41744416). This seems more like a bug on the OsmAnd side. We can always duplicate the way and use it to replace the coastline in the admin relations, but then that starts to smell like a mapping for renderer.

Regarding the duplicate boundaries, back then I created one for every city (admin_level=9) and for every town (admin_level=8). It might not be necessary since all cities got consolidated with towns. All BUT one exception and that is Groton (https://en.wikipedia.org/wiki/Groton_(city),_Connecticut). So I just kept the "duplicates" for the sake of completeness and in case someone wants to query cities separately.

Hi, thanks for the nice edits. I am just checking if you are sure that those are tracks. Meaning that they can actually support movement of 4-wheeled vehicle. Some of angles also look too sharp for car turning..

Ah right B and V are right next to each other. That was probably it :)

Hi Jack, is there any reason to keep all those houses as one huge multipolygon?

Great plan. If you want to see better through tree canopies you can switch to a different background imagery. Press B and choose 'Esri World Imagery (Beta)' or 'CT ECO Orthoimagery'.
Keep up the good work!

Great job! This area is looking amazing!

Nice. Thanks for the info!

@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.