What was the issue? It looks like you've updated it all to trunk, right? According to the (still work in progress) guideline, trunk should connect two regional cities of importance when an interstate freeway is not available. In this case I would extent the Trunk designation all the way up to Salisbury. The physical characteristics of the road don't matter, though the dualized part could be tagged as a motorroad=yes

Some years ago I did a cool run where I ran the length of Cabin John from Clara Barton up towards North Bethesda. That was so fun! Are there some other SVPs with a trail that runs up the spine?

Nice work here. The more tedious effort is merging them, which I am doing via JOSM as I can.

Hi there. This edit deleted a protected area of public land that TPC leases from the government.

Forgot to add MNCPPC as a source

Hi there, was there a reason to modify the columbia pipeline here?

Hi there. the edits to the course here look great, mostly, but there is an issue with way trees are mapped. Trees should be mapped with the natural=tree tag, not natural=wood. The latter is for polygon areas of tree cover, the former for individual trees. Also, I would consider adding the golf paths as single lines, in addition to the area highways. Thanks!

Assuming it is not a shared use path, then the foot=no should be added to the bike path. Routing engines in the USA assume a cycleway allows foot traffic osm.wiki/OSM_tags_for_routing/Access_restrictions#United_States_of_America

I made some minor tagging tweaks here osm.org/way/931223087#map=17/40.70624/-73.99693

Since you're not on OSM US slack yet (we're discussing here on #local-newyorkstate) https://osmus.slack.com/archives/CJ4QKU40H/p1631849526014300

Wahoo! Thank you for adding this!! I look forward to riding it one day. Saw it in the news. Have you been across?

I updated the wiki just now, but I think it will be up for discussion. You can keep using it though osm.wiki/Key:traffic_signals

Ah, perhaps ID doesn't match the wiki. Good pickup then.

Yes, the wiki mentions that if it is a specialized signal, you should use one of the other terms. But the default is =signal

The new MD imagery show this area well. It has the new circle too. Want to update?

Here is the correct changeset comment osm.org/changeset/111219556#map=14/39.6139/-76.8546

This changeset was uploaded in error. I meant to upload the changes to Hampstead separate.

hey DUGA, traffic_signals=traffic_lights is not a known value for traffic lights. Use traffic_signals=signal per osm.wiki/Key:traffic_signals

I will update osm.org/node/102880848

Wrong changeset name! Should have been: deleted unused way

deleted