- [/] **MD 4 SB → Suitland Pkwy → Dower House Rd/Marlboro Pike ramp**: check for a stray connection/tag letting routers go straight through the MD4/Suitland Pkwy signal instead of right-turn-then-ramp. Confirm turn:lanes / restriction reflects right onto Suitland Pkwy.

-- MD 4 SB -> Suitland Pkwy is confirmed. I don't know how they are routing traffic from WB Suitland onto Dower House Rd/Marlboro Pike. Right now this connection does not exist.

- [/] **Marlboro Pike ramp geometry**: apps are routing across what should be a barrier wall — check for a stray way connection or missing physical separation (barrier=wall or way split) between the through lanes and the ramp.

-- I believe this is correct, although the jersey wall isn't shown. The ramp from Suitland goes to the intersection of Marlboro Pike and Dower House Rd. I believe one can turn left (north) to get onto MD-4 at this point, which isn't the normal direction of travel.

- [X] **No U-turn signal past Marlboro Pike ramp (SB side)**: add `no_u_turn` restriction if missing.

-- I have MD-4 SB at Dower House Rd as straight only. I don't think you can turn left or right here.

- [X] **MD 4 NB at Dower House Rd intersection**: add/confirm `no_left_turn` restriction (MD4 NB → Dower House Rd) — this left was eliminated.

-- I have MD-4 NB at Dower House Rd as straight only. I don't think you can turn left or right here.

- [X] **No U-turn at Suitland Pkwy (NB side)**: add `no_u_turn` restriction if missing.

-- Logically, a "no U turn" is here. I just added a straight-only on the connector from MD-4 NB to SB.

- [/] **NB ramp back to Suitland Pkwy**: confirm the "left onto Suitland Pkwy, then slight left onto dedicated ramp" path exists and is routable/connected correctly.

-- I'm not sure what "dedicated ramp" means here. Is this the flyover they built over the original MD-4? I thought this would have been described as a left then straight to Suitland.

- [X] **MD 4 SB → Armstrong Village/Imperial Oaks via Westphalia**: confirm left turn onto Westphalia is tagged correctly and routable.

-- I think this is tagged correctly. I don't see any restrictions that would not allow a left turn here.

- [ ] **Machinist Place left turn at MD4/Dower House Rd**: add `no_left_turn` restriction — no longer available.

-- Is "Service Road" on the NE side of MD-4 Machinist Place? I'm unsure of where the no left turn is supposed to be.

- [X] **No-right-turn MD4/Dower House Rd (NB)**: verify `no_right_turn` restriction actually exists in OSM at this node (Google is still routing through it, so this may be missing or mistagged).

-- I have a "straight_only" at this intersection preventing traffic from MD-4 from turning left or right onto Dower House Rd.

If there is a question about data quality, I should be going through here later this week and can check the suggested changes.

I grabbed GPS tracks about a month ago and did my best at a survey at highway speeds. :) I would guess that MDDOT would be a better source, particularly in this construction area. I bet there will be more changes in the future.

Opps, thought I had removed that. Thanks for cleaning that up.

I believe this is a fast food restaurant named Urban Wok. I updated the node to include that it is fast food and added the name.

Elliott, is this supposed to be a camp_site?

way/672589251/history#map=18/39.28972/-76.53436

I don't think this was intentional. Why am I getting blocked for this now? Never saw this message.

Is this a formal campsite or just a place that you have camped?

Imagery doesn't show this to be a divided highway. Is there a barrier between the lanes?

Did you mean to make this section of railroad track into a foot path? There are also some other questionable tags on this section.

Well, it's on a government facility so one can't just go there.
---

Published using OSMCha: https://osmcha.org/changesets/134546770

I think because it's not there anymore.
---

Published using OSMCha: https://osmcha.org/changesets/134460666

Thanks for finding this error. I have added it to the ACLT multipolygon.

Okay, I just reverted this changeset so the woods should be back now. Thanks for letting me know of the error!

I *thought* I was combining some areas into a single multipolygon. I noticed a gap between the areas and was trying to fix it in an efficient manner. I'll take a look at what I messed up.

Where did this track come from? I don't see anything here on satellite imagery. Is this a snow trail, maybe?

That's probably okay. Apparently it's being developed right now so as soon as new imagery is available I'm sure it'll show construction.

Yeah, I try to be careful when making changes. I can't recall, off hand, which suggestion pops up somewhat regularly which is obviously wrong (the system is assuming a different business). If there are changes that can be made to NSI lets open some bugs up. It's so annoying to search for something and not find it only to discover it was there all along but wasn't spelled correctly or was named something slightly different. :)

Yep, looks good to me. I seem to remember a discussion about not using the park tag on state and national parks. I guess this was done prior to that. Not sure if I did any more of these down along the Keys. I think I was concentrating on the campgrounds.

I've been trying combine relations to the same ways of the shoreline around here but I'll happily help working on whatever other projects there are you have cooked up. ;)