Hey Tom,
Good job, those look much nicer now!

I edited a couple that needed a bit more love. Their shape was cut of by trees.
e.g. way/1333568636

When editing try to change your background imagery. Hit 'B' key or click on 'Background settings' on the right side. Then select either 'Esri World Imagery (Clarity) Beta' or ' CT ECO Orthoimagery (2019)'. This will remove the trees for you.

Then it's just as simple as drawing a bunch of straight lines by placing the nodes in the corners of parking lots.

Let me know how it goes.

Cheers

Hi,
I would suggest merging areas together in order to avoid creating duplicate preserves.

1) merge ways 1333563490, 1333563488 and 1333563489 into a single area since they are touching each other and there is no additional information to distinguish them.
2) Group this new area together with way/1333563491 into a multipolygon relation and move all the tags from these way to the relation

Hi again.
Unfortunately, some of your parking lots are traced in very low quality. For example this one: way/1333568636

I would suggest that you switch your background to 'Esri World Imagery (Clarity) Beta' which would allow you to see parking lot outlines through trees canopies. Try drawing the area tightly along the outlines and avoid unnecessary overlaps with buildings or other objects.

Just let me know if you need help!
Cheers

hi,
sorry I reverted your edit because Stop and Shop already exists at this location.
way/888324386

Hi and welcome to OSM!

Thanks for adding all those parking lots. I just wanted to give you a few tips for future editing:

1) When editing, you can change the background imagery by pressing B and then selecting for e.g. 'Esri World Imagery (Clarity) Beta' or a newer version 'CT ECO Orthoimagery (2019)'.
They have much higher resolution and trees are without leaves for better visibility.

2) After you draw a parking lot area you can press Q to make its angles 90˚ which makes it shape more true to the reality.

3) Don't be afraid to place more nodes or move the nodes around to make the shape more accurate. As an example look at this parking lot near by: way/1146150031

You can contact me any time in case you need help.

Cheers.

I agree that this relation looks like something that should be part of wikidata project.

Hi and thanks for editing OSM!

'Storrs-Mansfield' might be recommended for address field by USPS, but I've never heard anyone calling it like that. Any maps that I know show simple 'Storrs' and GNIS under Id number 212656 shows name as 'Storrs'.

I would suggest having name=Storrs, official_name=Storrs-Mansfield and alt_name=Storrsville

Wikipedia link also needs to be fixed as there is no wiki page named 'Storrs-Mansfield, Connecticut' only https://en.wikipedia.org/wiki/Storrs,_Connecticut

Also you accidentally removed wikidata Id which should be moved back wikidata=Q166302

Cheers.

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.