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.

Hi, Please don't create overlaps between Fairways and Greens polygons. See here: leisure=golf_course#Common_mapping_pitfalls

PS Let me know if you need more help!

The way how you can do it in iD editor is to select a node that belongs to Richmond Drive (either exiting or creating a new one with double click), right click and choose 'Split'. Then select the newly created fragment and change its type to 'Driveway' and remove the name.

Also it's better to remove the 'yard' polygon as that one is incorrectly mapped.

Cheers

Hi, and welcome to OSM. I am guessing you wanted to change the end of Richmond Drive to driveway?
Residential areas are to mark whole areas where houses and residential buildings are; and as a rule we don't give them descriptive names.

I think this all looks great. Thanks!

Thanks, I just guess what it is from the imagery.

Hi,
There are few things in your edits that I need to point out:
1) Don't delete objects just to replace them with a new one. Always update the old shape by dragging its nodes.
2) Don't create overlaps between green and fairways. Use multipolygon instead.
3) Don't map paths by tracing their outline (e.g. way/1174315924). Draw a single line that follows the median of the path.

Please read OSM wiki for detailed information how to do correct edits:
leisure=golf_course#Common_mapping_pitfalls

Hi,
and thanks for trying to improve OSM. However it would have been better if you had discussed your data import prior executing the upload.

There are official guidelines for how to proceed with adding new data in bulk: osm.wiki/Import/Guidelines
At minimum, would you mind to go to OSMUS Slack and discuss your intentions there in the #import and #local-connecticut channels? https://slack.openstreetmap.us/

Just briefly looking at the imported nodes I can see issues like:
1) name= tag values are all upper case. Which is not how we write names.
2) All nodes appear to have a FIXME note: "This bus stop could be redundant". It is not clear what does that mean; and who and how will determine if the stop is indeed redundant.
3) I am not sure what gtfs_id, gtfs_stop_code, route_ref represent or if they are anyhow important information that need to be in OSM. Also a typical syntax is e.g. ref:route=
4) Is it really true that stops in Hartford belong to network=CTTransit- New Haven ?
5) the network tag value has a space after the dash. Normally I would think that "CTTransit" would be sufficient, but if we really need to subdivide then maybe come up with some logical system of the values like "CTTransit:NH"
6) some of the tags e.g. gtfs_id have value "missing". If the value is not known then the tag should not be present.
7) You are also missing a tag that would describe what those points actually are. I assume these are places where people wait for a bus. So in that case you need something like public_transport=platform + highway=bus_stop. More documentation here: highway=bus_stop

Cheers

Hi,
just a heads up, here you deleted a line that was part of administrative boundaries. Now it's fixed.
Cheers

The most northern three buildings (e.g. way/1170460647) though seem to be in a process of being replaced by new structures. Check out Bing imagery which is the most up to date for CT.
There are already some building outlines that you could trace if you want.