1) For existing areas you can select the object and then drag on the small arrows that are between each two nodes.
Or just create a new node by double clicking somewhere on the outline and then drag than new node to a new place.
(To go back to adding new nodes by clicking, you have to go through a relatively complicated workaround. But in case you want to give it a try *)

2) To create a hole in the parking lot area, select both the parking lot and the building inside (shift + click) and then press C to combine.
(This will convert it into something called "relation" where the original outline will be an "outer" and the building and "inner" boundary.
You can verify that it worked by selecting the original outline, scroll all the way down in the left panel and then clink on the Parking Lot name under Relations.)

*) Workaround:
1. Select two nodes of the parking lot between which you want to inset points.
2. Press X to cut.
3. Select the small cut segment.
4. Scroll down in the side menu to find relations. And click on the trashcan icon to remove it from relation.
5.Press DEL key to delete the small segment.
6. Select one of the two nodes where you cut and press A. Now you can add nodes by single click.
7. Finish adding new nodes by clicking on the second node.
8. Select both split segments of the parking lot (shift + click) and press C to combine it to single area.

Hi!
Thanks for editing. Few things I noticed there and there.

Sometimes you draw sidewalk on top of another sidewalk line, which creates a duplicated object.

.. and the section where there is a pedestrian crossing is normally tagged as footway=crossing instead of footway=sidewalk.
Have a look here at the first example:
footway=*#Examples

Cheers

Welcome to OSM and thanks for editing!

Just a few suggestions:
1. When the parking lot is more or less rectangular you can press Q key to automatically force all its angles to 90˚. Those shapes then look much nicer.

2. You can try to add more nodes/point to the parking lot outline to make it shape more accurate. And try to avoid overlapping its area with other objects such as buildings. As an example you can look at this parking lot: way/341662678

Cheers

This edit was reverted. Because the segment exists on recent imagery from 2023.

changeset/158596863

Hello,
I think you must be using outdated imagery. That removed highway segment is visible on 2023 CT imagery as well as on current Bing photos.

Hi and thanks for contributing!
Looking around the area shows that there is already 'Lisike Beach' mapped as area: way/1085907735

Your added point is therefore a duplicate object and should be removed.

Cheers

Hi,
out of curiosity, how are those residential areas defined? Is that coming from a database?

It's because I noticed that sometimes you draw them around one block, but other time you include several blocks including the residential roads.
way/1326132933#map=17/41.666860/-72.762756

And sometimes you include all houses in that block but sometimes you exlude several. Like in case of Day/East Street intersection.
way/1326132932

cheers

Routing software would navigate though that section of the Meadow Road regardless of the classification. I don't think there is much benefit in having it as primary.
Maybe try reaching out to @jnighan, who put a lot of thinking into road classification in CT, or ask on Slack before endeavoring in road reclassification.

Hi,
thanks for editing, but I don't think it's a good idea to make 200 ft stretches of primary roads. Ideally we would want to have long stretches of roads connecting important cities as primary and not small stubs between interstate off-ramps.

Hi and welcome to OSM!
Two tips: when you draw a building building press Q key to square its shape and make its angles 90˚. That way the building looks much nicer.

And when finished editing in one area. Please upload your changes before moving to a new area that is far away.

Cheers

Here again.
Please go through your edits and move house numbers from "name" field into "addr:housenumber"

Here you deleted a correct building that contained a correct street name and house number. Your 44 A-C should have expanded the original information in the address field not replace the already good data.

Here again, you are using the "name" tag wrong. These are house numbers.

Here a "leasing office" nor a "mail room" is a post box. Post box is: amenity=post_box

Please fix your edits.

Hi,
here again the house number belongs to addr:housenumber
Also when you draw a building please press Q key to make all its angles 90˚

Hi,
I noticed that you are using name tags wrong. That field is reserved for an actual name of the object.
If number `1159` is an address then it should be added to the address number addr:housenumber=1159

addr:housenumber=*

I think those are regular residential roads for accessing residential buildings. Driveways are shorter, leading to a garage of place where people park their car.

Since there is no physical barrier nor a traffic sign preventing entry anybody can legally use those roads. And I assume delivery trucks and visitors regularly do so. In this case it is better to change access=private to ownership=private.

ok. Thanks for the info.
I looked into CT ECO imagery from 2019 and saw some containers no the road so I added a track until that point.
Maybe you can check if that reflects the reality that you saw.

Hi and welcome to OSM!
I ist impassable because there is a gate or were all traces of the road removed?
If the road is still physically there but the access is restricted, we keep the road in OSM and add an access=private tag to it.

Cheers

Hi are there any gates preventing car access or no trespassing signs?
I can't see anything from streetlevel photos nor from aerial imagery.