Hello, thanks for editing OSM. Generally you shouldn't describe things in the name tag, for example adding name=pool to a pool, unless it's official name is literally pool. Thanks! See: osm.wiki/Names#Names_are_not_for_descriptions

Additionally, be careful with the Mapbox imagery. It can be pretty far off reality sometimes, in this case about 20ft off. Esri and Bing are typically quite well-aligned in Connecticut.

Hi HockeyHasher, I noticed you added many leisure=pitch with the sport in the name tag, for example name=tennis. Generally you shouldn't put descriptions in the name tag (see: osm.wiki/Names#Names_are_not_for_descriptions), instead put them in the description tag. In this specific case, you can use the sport tag (e.g. sport=tennis) to tag the type of pitch. Thanks!

Hi, thanks for adding the trails. Just a note that mtb trails such as 1070387809 should be added as highway=path (with bicycle=yes), not highway=cycleway. I've already fixed it. Thanks!

Hi cdkj, thanks for adding the new bike lanes on Meadow St. Just a note: I noticed you added separate highway=cycleway ways for the parts that are on-street. Generally for on-street lanes, especially ones that are immediately next to car lanes and not separated by parking or physical barriers, you should use cycleway tags on the road instead of creating separate ways. Thanks! More information: highway=cycleway#When_not_to_use

Hi AirportExpert, thanks for adding footways in/around Cadigan Park. Just a note (which you might've already fixed since this was early in your OSM career), I noticed that a few of them don't quite connect with other ways, for example the footways that lead to parking lot service roads but you terminate at the edge of the parking lot rather than connecting them to the service roads. I've fixed them in this instance. Thanks.

One of my favorite OSM finds 😂

Ah, I see what you mean. Long answer: Despite being called OpenStreetMap, OSM at its core is really just a database. What you see on this openstreetmap.org website is just one of hundreds of renderings of the underlying data. This one is called OpenStreetMap Carto (osm.wiki/OpenStreetMap_Carto).
The goal of OSM isn't really to improve Carto, but to have the most accurate data, then it's up to the Carto project and other consumers to use this data to the best of their abilities. More info: osm.wiki/Tagging_for_the_renderer
As to why Carto doesn't show the name of the refuge at a certain zoom level, it's because producing good map images automatically from the data is quite hard and involves a ton of heuristics to decide where and when to position text, and it isn't always perfect, given the thousands of possible tags competing for space. In this case, without looking into the code I have a feeling the central placement of Murdock Hill in the refuge, combined with the long name of the refuge itself, means it isn't being rendered. Unfortunately the only solution is to raise an issue with the Carto team and have them tweak the code/heuristics so that the names of reserves take precedence over hills in situations like this.
However! Not many end users actually see/use the Carto map at all, it's mainly used by OSM contributors. Popular apps like Strava have their own OSM renderers that don't render hills, for example, and the name of the refuge seems to show up just fine. ...And just now I see that on the fws.gov site you're using OSM maps with Carto. My suggestion would be to find a different rendering that happens to render the name. The Humanitarian layer (which is also available on this website on the right toolbar) seems to show it (it hasn't updated on all zoom levels yet since I pushed the change yesterday, but it should in a few days).

Hi Shaun, thanks for adding the info. Just a heads up that I made some fixes:
- I noticed you converted it from leisure=nature_reserve to leisure=park, however I think the original tag was better, so I've reverted it. park typically means something like a city park. But let me know if I've misunderstood. See leisure=park and leisure=nature_reserve
- The opening_hours tag must follow a certain format, not plain english (see: opening_hours=*).

On 1078932140, you replaced the name of Satan's Kingdom Road with "Blue-Green Trail". If a named road is a part of a route do not replace the name of the road with the route name, just add it to the relation. I don't think you should add trail names to unnamed tracks either, because then it can be ambiguous as to whether it's an official name from the town or the name of the parent route. Hikers are not the only users of OpenStreetMap.
Also are you sure the mentioned way is on blue-green trail? The official trail map shows blue-black on that segment, but it's from 2008, so perhaps things have changed?
Also on 437581064 you changed the name to a typo with an uppercase "Satan'S", but it was fine before...

Why did you remove the name of River Road (170403311)?

Hi again. When adding man_made=bridge please also connect the path/road to the ends of the man_made=bridge, as well as add the normal bridge[=yes] and layer[=1] tags to the path/road segment. Lastly, add layer[=1] to the man_made=bridge as well. More information and examples are on the wiki: man_made=bridge

I just did a 30mi ride in Meshomasic yesterday and yeah it's tricky. Paved roads for example, even if they get super beat up with pot holes and washboard, should still be tagged as paved, but with an additional smoothness=bad or similar tag (smoothness=*). Similarly, according to the wiki surface=compacted is basically synonymous with macadam construction, which the main roads in Meshomasic are, and when it degrades it should remain compacted (surface=compacted) -- up until it becomes only gravel, but I think it's still a fair ways from that. On a gravel bike those roads are still quite easy, but "pure" gravel using the original osm definition would be kinda tricky on any bike as the tires are never in contact with a steady surface

Hi SwKurtz, as Mashin said thanks for getting all the trails in Huntington. I noticed you used Bing Imagery, which I use all the time because it's fairly up to date, but the downside is that you usually can't see anything on the ground in the woods. I'd recommend using Esri World Imagery next time, which often lets you see the trails on the ground quite well (at least in this part of CT). Then you'll have a nice point of reference for your GPX file. I'm saying this because I noticed the trails you added are sometimes bit off from reality (see screenshot here with strava heatmap overlaid https://i.imgur.com/DpMBbsD.png).

Fixed in 124449095.

Oops, I think the previous geometry on Black Ash Road was current/correct, rerouted near Old Colchester Road.

Hi waterDucky, nice work in the park. However, when creating parking lots and the trails/roads around them, make sure to connect the trails/roads to one another, and not terminate them on the parking lot itself. Otherwise routers based on OSM won't work. Thanks!

When adding residential driveways, do not use highway=track, even if it's unpaved. Instead, use highway=service, service=driveway, and surface=unpaved. Thanks. Learn more here: osm.wiki/Highway%3Dtrack

Sorry to bother, but another note: unpaved tracks generally shouldn't be tagged with tracktype=grade1 (as you did with way/1069517914). See: tracktype=*

Hi, FYI I noticed you converted a few roads in the power plant to highway=track. Based on the "How to decide" section on the wiki page (highway=track), I think the previous highway=service value is better. I can change it back.