Thanks for replying. I see several problems here.

1) You didn't follow any of the steps from the import guidelines. At minimum, please create an import documentation page on osm wiki where you detail where you downloaded the data from, how were they processed, where you asked for permission and if the license is compatible. Then post an announcement message to the community forum and answer any comments there might be. This is all outlined in the guidelines linked by Mateusz.

2) The license message you linked is from year 2020. They might have given permission at that time, but we cannot assume it is forever. Please double check that the license is public domain or CC0.

3) The message says that Westchester County GIS needs to be credited. I don't see their name anywhere in the source tag or nor even in the comment message.

4) After you've gone through that all imports have to be marked in this list: osm.wiki/Import/Catalogue

If you have some questions you can contact us on Slack or Community forum.

This changeset was corrected.
node id 9021781541 moved back to original position

changeset/159703659

Hi,
please be careful. You often move nodes with addresses to a wrong location. If you accidentally make an adit that you didn't want you can always undo your changes with ctrl+z or clicking on the back arrow.

In this case it was this node: node/9008446356
I have moved it back.

Cheers

Hi,
this looks like an import rather than hand drawn shapes from imagery. What is the source of the data and is the license compatible with ODbL?

Sure. I also think that the current values scale very poorly for large countries like US, but how does it justify to do such dramatic change that will make the trails disappear from some maps? I missed discussion about this.

What is the idea for network values for the rest of the hiking trails countrywide? Are those values going to fix the hierarchy issue? Does that mean that global hiking map project will have to hardcode network values in order to infer hierarchy?
I fear that the change will be done on the scenic trails, but nothing will be done for the rest and we end up with some nonfunctional cat-dog hybrid.

ok. Thanks for clarification.

Hi Quincy,
I don't think this is a good idea.
First the network tag is for hiking routes is described having only lwn, rwn, nwn, iwn values.
route=hiking
And second some data consumers depend on this values. Waymarkedtrails being one of them I think.
Cheers

Hi,
here just be a bit careful, because the gnis:feature_id and wikidata tags were not moved.
I re-added them to the whole grounds.
Cheers

Hi,
I corrected shape fo the driveway a bit as part of it was obstructed by trees.

You can see it clearly if you switch the background imagery to 'CT ECO Orthoimagery (2019)' or 'Esri World Imagery (Clarity) Beta'.

https://learnosm.org/en/hot-tips/imagery/#changing-the-background-aerial-imagery

Hi,
This looks good. Thanks!

Hi,
by 'informal path' you mean an actual path that people use? Because from aerial imagery it looks like it leads through someone's backyard.

Hi,
generally we put private tag on roads only if there is a gate meant to prevent public access or a 'no trespassing' sign.

Hi,
you are correct. There should be only one copy of an address.
Thanks!

When you switch the background, you will see that this parking lot has still some hidden parts that are obstructed by trees.

way/1334626417

Welcome to OSM and thanks for editing!
Here are a few tips for editing:

1) When drawing a parking lot area, try placing new nodes at every corner of the parking lot and make sure the line traces the outline precisely. Try to avoid cases where the line would cross grass, buildings or other objects that are not part of the parking.

2) I suggest you switch from the default background to 'CT ECO Orthoimagery (2019)'. It was made in spring when the tree leaves are gone and you can see the parking lot outlines under tree canopies better.
Here is how to change the background: https://learnosm.org/en/beginner/id-editor/#configuring-the-background-layer

Let me know if you need help.
Cheers

Thanks for checking

Thanks for the pointers. I briefly read through the discussion there and the arguments there pretty much summarize my thoughts. In the mean time I have moved Storrs-Mansfield to offical_name.

Hi,
I combined all of Housatonic State Forest into one relation.
Did I correctly added this area as an inner exclusion zone?
way/1333323436

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