Thanks. Here are some suggestions for improvement for the next time:

* House number goes to a separate field named `addr:housenumber`
* In opening hours, days are separated with a semicolon not a coma: Mo 07:00-17:00; Tu 8:00-18:00; ...
* Telephone number needs to start with the international code +1-203-...
* Don't use country=USA field

Cheers

All looks good Mike

Thanks for fixing all the parking lots Andrew!

Wow you already created around 8.5k parking lots, 38k utility poles and 25k manhole covers!

https://shorturl.at/mnDO6

All seems good. Thanks!

Hi and welcome to OSM!
Thanks for the edits, but what I noticed you also created 2 unlabeled points and a hot spring in Connecticut that does not exist.
Best is to stay in smaller area when editing and double check the edits before uploading them.
Cheers

You can map the gate by adding barrier=gate to a node at its location. And to indicate restricted access past the gate, just add access=private to the road.

barrier=*#How_to_map_barrier_nodes

From the imagery you can see that this is not a sidewalk. Perhaps the surface is not asphalt, but it is still used by cars to access the residential buildings

You are right that this is not a residential road since there are no residential buildings that it services.
However it is also not a path. You can see from imagery that it is a service road used by cars to access the scrapyard.

Hi,
address goes only on the main building to avoid duplicates.
Cheers

All good. Thanks for editing!

@mguerini All good, thanks for clarification!

Hi,
The question is why did you remove information about operator and power lines designation from this section of power lines? way/101289577

Additional info, these lanes are separated from cars by set of poles: https://www.newhavenindependent.org/article/64_bike_lane_teeth_knocked_out

It seems to be an edge case and wiki says that in US this is a popular way to mark it:
cycleway=*#Cycle_tracks

Here you managed to split Farrel Road into three segments, but still marked all of them as a covered bridge.
I removed the bridge tag from the two surrounding segments.

Here the problem was that you accidentally merged two unrelated addresses together.
I wen't ahead and fixed that.

Hi and Welcome to OSM!
The problem here that I see is that you marked almost a mile of stream as culvert. That is clearly not how it is in reality. The correct way how to do it is to split the stream and mark the small segment that leads through a culver as such. To split a way in the editor, rigth-click on a node and select 'split'.
Also I am not sure what "RFC" in description means, but if no one can decipher the meaning it's usefulness will be limited.

One problem I found was your restructuring of the intersection between Kennedy Road and the service road leading to Stop&Shop. In that case it is better to leave it in a "square shape". See here for some recommendations: https://labs.mapbox.com/mapping/mapping-for-navigation/modeling-intersections-for-map-navigation/#intersection-between-dual-carriageways-and-bi-directional-highways
I went ahead and fixed that.
Otherwise all good.

Hi,
I couldn't find any major problems. Small thing is that if a road passes under a building, the road should not have layer=-1 tag (At least not on it's whole length) as that can cause potential problems with rendering. Better is to set layer=1 on the building.
Good job!

yes it's unfortunate that there hasn't been any response. I was thinking of trying to fix the issues myself, but I am not sure how much to trust the imported data.

I asked in local-connecticut on Slack if people think we should try to fix or completely revert.