btw there is now new CT ECO 2019 and MetroCOG 2020 orthophoto imagery available in iD

Thanks for finishing the trail.
Just a small thing, paths and roads should not be drawn on top of each other. If a path meets a road, that is the place where the path ends.

I fixed the two overlaps so all is good.

Hi,
Thanks for the edits. Though no need to add trail name on paths. It is already included in hiking route relation:
relation/11974625

I don't have any direct contacts there, but if they don't respond to emails then the best is to call. They can't dodge you like that. I am not into cross-country skiing, but I'd say if it's not prohibited then it's allowed.

loc_name just means local name it doesn't mean that there must be a name tag. Looking at it from a rigorous perspective, when you were there, did you notice any signs or maps with those names?

General agreement is that we add the names only to the route relation, because it is not the name of the path but the name of the route that can even go over named residential roads, which have name of their own.
Rendering the name from the relation is not really difficult so if some map does not show them it's for a purpose. If maps would render only text from operator tag would we start adding trail names there?

Names of routes are shown for e.g. by [Mapy.cz](https://en.mapy.cz/turisticka?x=-72.2098595&y=41.8635217&z=15), [Waymarked trails](https://hiking.waymarkedtrails.org/#route?id=11038937&map=11!41.9103!-72.1733) in details section, [OsmAnd app](https://osmand.net/), [Thunderforest](https://www.thunderforest.com/maps/outdoors/),...

Hi,
thanks for the trail data. Just a comment on those trail names. "Dirty Dancing", "Slap Happy".. that doesn't look like an official name that CT DEEP would use. More appropriate I think would be to use loc_name=*

Also trails (particularly those that are marked) are mapped as relations and so the name of the trail is not added duplicately on the path itself.
Both Nehatic and Pachaug trail have relations 11257426, 4783347.

OK.
Thanks again for contributing!

Interesting. Thanks for the link.
Are those names also officially recognized by CT DEEP? I know I was there a few years back and I don't remember seeing trail names posted.

I was just wondering if loc_name=* would be more appropriate in this case.
name=*#Variants

Hi! Welcome and thanks for contributing to OSM!
Just a question, what is the source of these trail names? Official documents for the state park don't mention any of those names.

Hi there is an ongoing road reclassification in CT. Before you do any more edits please contact jnighan (@jnighan).

osm.wiki/User:Jnighan/Connecticut_Highway_Classification_Proposal

Awesome, more things to map!
I added your stretch to the exiting relation.

though some of the service roads look more like service=parking_aisle

Hi,
just a question. Is this a new extension of the trail?
The original trail terminates south from there:
relation/3776993

And that is what CFPA website still shows
https://www.ctwoodlands.org/blue-blazed-hiking-trails/blue-blazed-hiking-trails-interactive-map

Thanks!
I fixed your opening hours formatting

I think I just assumed, because this little area was tagged as fairway.
relation/13431265

Good job! Thanks
Just always check if the business already exists. For example John's Cafe is there now twice (once on the building itself and one on the node) or Wells Fargo bank

Obsah GoogleMaps nie je pre OSM smerodatny. Dolezite je, ci ten objekt naozaj fyzicky existuje.

Hi,
if there is a hole inside an area, we draw them as multipolygon relation where the area gets role "outer" and the holes in the area get role "inner".
So instead of "lollipops" like here way/999989533, it looks something like this:
relation/13420699

more details are about this are here: leisure=golf_course#Common_mapping_pitfalls

Hi,
generally good tracing job. But some of the areas/polygons are overlapping.
e.g.
way/1000023831
way/1000023830

If the two areas are adjacent, they should share the nodes along the line where they touch. see here leisure=golf_course#Common_mapping_pitfalls

Also if the two adjacent areas have exactly the same tags it is typically better to draw them as one area. But that is a minor point.

Hi,
those cart paths look wonky. We don't draw them as areas, but they go as a single line along the median of the road/path.
I believe this was supposed to be parking lot that should be tagged as amenity=parking: way/999972674

Also path should not cross each other. If they have to then the should share a node at the point of crossing.

Also they should not

Hi and welcome to OSM.
Several things I would like to point out:
1) Please don't delete objects to replace them with new objects. To do it correctly, modify the existing object shape to update it.
2) Hole numbers don't belong to name= tag, but should be in ref= tag.
3) Why was it necessary to delete all the Tee nodes? They contained useful information e.g. node/2908414180/history
4) This is not the correct way how polygons with holes inside of them are traced: way/1000618120 . Look at here how it is done as multipolygon: leisure=golf_course#Common_mapping_pitfalls
osm.wiki/Relation:multipolygon