I'm finally coming back to this. Since I didn't receive a response here, I made the proposed change and decided it made sense to revert the other ways to motorway_link too for consistency (osm.org/changeset/122614516).

This reverts osm.org/changeset/96369694 and additionally sets junction:ref on one of the ways where it is applicable. The use of motorway_link on osm.org/way/187934955 helps routers that don't support junction:ref distinguish the exit from the through road; see further discussion on osm.org/changeset/96369694. Also, the use of motorway_link on all three of the ways maintains logical symmetry because the ways that connect MD 200A to opposite directions of I-370/MD 200 are equally important, even if some go straight for a slightly longer distance than the others. This is consistent with the mapping of at least one other trumpet interchange in the region: that of the George Washington Memorial Parkway and I-495.

I did some more research into the general issue. There are junctions elsewhere on the map with two outgoing ways tagged "highway=motorway" where IMO it isn't reasonable to change one of them to "highway=motorway_link"; an example is osm.org/node/37192428. So the fact that OsmAnd announces the exit number for both outgoing ways has to be considered a bug in OsmAnd (https://github.com/osmandapp/OsmAnd/issues/13848). The right way to resolve the ambiguity in those cases is to put the "junction:ref" tag on the motorway that represents the exit, but this tag currently isn't recognized by either OsmAnd or OSRM. So I'd still like to change osm.org/way/187934955 to a motorway_link to solve the problem for now, since I believe it's a reasonable approach in this case.

Hi! I noticed that the change of osm.org/way/187934955 from highway=motorway_link to highway=motorway is causing poor route guidance in OsmAnd and possibly other OSM-based applications as well. Since both of the ways leaving the highway=motorway_junction node (osm.org/node/1985694885) are tagged highway=motorway, routers do not know which is the main road and which is the exit. OsmAnd seems to describe a route taking either of those ways as "take exit 3", while OSRM (on osm.org/) just says either "at the fork turn left" or "at the fork turn right" and does not use the exit number for either way.

What was the reason for the change? Is it OK with you if I change osm.org/way/187934955 back to highway=motorway_link? (I verified that this would fix the guidance in OsmAnd.) If I don't hear from you within a week, I'll go ahead with the change. Thanks for your attention!

I changed the road to no longer be a "link" ("highway=primary_link" -> "highway=primary") because it has a name and links normally don't have names. If you think it's better as a link with a name, feel free to change the "highway" tag back.

News articles:
- https://montgomeryplanning.org/montgomery-county-planning-board-approves-resolution-to-rename-montrose-parkway-in-honor-of-renowned-local-abolitionist-the-rev-josiah-henson/
- https://www.mymcmedia.org/montrose-parkway-becomes-josiah-henson-parkway-on-friday/

I noticed the updated signs today at the intersections with East Jefferson Street and Towne Road. I didn't take the extra time to confirm the signs along the full length of the road. But I'll hazard a guess that it's least confusing to rename the whole road on OSM at the same time (including the "proposed" part even though I'm unsure of its latest status) and it's valuable to get the change out ASAP even if some signs are not updated yet.

This change isn't complete (for one thing, there are more small parking areas that I didn't take the time to map now) and may have some mistakes, but it should be better than the status quo. As always, feel free to make further improvements.

- Move the "Congressional Plaza" name from the building to a new landuse=retail with my best guess of which areas should be included.

- Map the parking area on the Congressional Lane side.

- Add stairs and tunnel between the Congressional Lane and Halpine Road sides.

- Adjust some geometry according to current imagery. I know imagery can be misaligned in general, but it looks reasonably well aligned to other existing elements. Hopefully this is at least better on net than the previous geometry.

When I entered Sewer Plant Road from West Main Street, the road goes only a short way before it becomes a footway; I recorded the cutoff point by GPS. I couldn't survey from the other side to determine how much of the way is a footway because the Knoll Side Place entrance is signed "No motorcycles" and I had my motorcycle (not a car) and didn't want to take the time to walk. (The restriction on motorcycles might be worth mapping in its own right, but I'm not pursuing that now.) So my tagging of the rest of the footway is a guess based on the width of the way as seen in imagery; I thought it was better to go ahead and do this than leave a note that no one may follow up on any time soon. Feel free to change the data if you know better.

Details:

- US 40 Alternate to the west of MD 17 is signed "West Main Street" at least as far west as the intersection with North Pointe Terrace and then "Old National Pike" at the intersection with Old Hagerstown Road. I couldn't confirm the exact location of the name change (I didn't want to consult other sources for which there might be licensing issues), so I'll make the reasonable guess that it happens at the boundary of Middletown, and I'll use Knoll Side Lane as a convenient approximation rather than introducing another node.

- MD 17 north of US 40 Alternate is signed "North Church Street" as far north as the intersection with West Green Street and then "Myersville Road" at the intersection with Pete Wiles Road. Again, I don't know the exact location of the name change, but signed house numbers suggests it is near the boundary of Middletown, so I'll assume that. If gluing the new node to the Middletown boundary is inappropriate, feel free to change that.

- MD 17 south of US 40 Alternate is signed "South Church Street" starting from that intersection.

- Fix spelling of "Koogle Drive" and make it one-way northbound.

- Add signed turn restrictions in both directions for the sharp turn between West Main Street and Walnut Street.

survey:date is 2022-02-12 (apparently I forgot to add it).

My main goal in this changeset is to stop tourists unaffiliated with Madison Fields (like me) from assuming they can use the road as a through route. The entrance from Mouth of Monocacy Road is signed "private drive", so definitely "access=private". The signage at the entrance from Big Woods Road doesn't explicitly state access. "access=destination" or "access=customers" might be more accurate on that side (we'd have to figure out the division point with "access=private"), but I didn't want to take the risk of entering to seek more information. Feel free to change the access tag if you known better.

Thanks for fixing my mistake from osm.org/changeset/115794413. I probably pressed the wrong thing in the JOSM tag editor as I was trying to copy several tags from another Subway on OSM. I will try to be more careful.

Re the representation of the two areas: I thought the duplication of the node sequences of the two ways was a lesser evil than the complexity of multipolygons with a shared way, but I don't feel strongly about it. The new boundary between the areas is an estimate from imagery; feel free to improve it.

There's a plan to build another school on the Old Georgetown Road site (https://www.montgomeryschoolsmd.org/departments/facilities/construction/project/woodwardhs.aspx). I'm unsure how it is best to map the site in the interim. I saw today that the building was demolished; I couldn't easily tell whether the sports fields still existed or were accessible.

I'm trying to avoid any possible problems with osm.wiki/Copy_content_from_a_business_website. I'm treating the lookup of location-specific URLs on the business web site as "common knowledge", but all other data is only what I surveyed from publicly displayed signs at the location. survey:date is 2022-01-07 (I forgot to add it to the changeset).

Oops, somehow most of the tags I intended to add didn't get added. Fixed in osm.org/changeset/115798909.

Source is survey. I guess I'll avoid submitting changesets with OsmAnd unless/until it gains support for specifying the "source" tag.

There are other businesses in the same building. I'm only adding Subway because it's the one I care about.

I wanted to make sure you're aware that at least some users feel that closures of less than a few months shouldn't be applied to the unconditional tags; see the previous discussion on https://help.openstreetmap.org/questions/81647 . If you got a wrong route because your router doesn't support "oneway:conditional", the best solution is to fix the router. But I don't have a strong opinion and won't object to the change to the unconditional tags here.

However, there is a more specific problem: this changeset reversed several ways in preparation for tagging them "oneway=yes" but left the existing "oneway:conditional=-1 ..." tag in place, so routers that honor "oneway:conditional" (and give it priority over "oneway" when the condition is satisfied) now think this part of Randolph Road is one way westbound, which is the opposite of reality. I've made the minimal fix to this problem in osm.org/changeset/115451153 by replacing "-1" with "yes" in the "oneway:conditional" tag. An argument could be made that the "oneway:conditional" tags are currently redundant and should be removed completely, but I didn't do that for now.

Thanks for your quick and kind response. I submitted osm.org/changeset/111820423. We appreciate your support for OSM!