I think this restriction was left over from the temporary closure of westbound Randolph Road in 2021-2022. I have on hand a track from 2025-08-02 that shows that I took the turn in question; I think that's sufficient evidence that it's no longer restricted.

Addendum to the source tag: I consulted aerial imagery for a general sense of scale, not to trace the actual new geometry (the images I could find hadn't updated yet). The imagery might have been any of the following: Esri World Imagery; Esri World Imagery (Clarity) Beta; Bing.

I also consulted Esri World Imagery to try to refine the location, so that should be a source too.

Correction to changeset message: I don't remember whether the bookcase belongs to 10 or 11 Scotch Mist Court. The location is approximately correct from GPS (I guess I should have added that as a source).

Re unknown246: I agree it seems bizarre for someone to reference CPAP in their user profile. But shaming a medical condition on OSM seems uncalled for, if that was indeed what you meant. As it happens, I currently use a CPAP. I too am frustrated to have to spend time dealing with this vandalism rather than just contributing to the map, but let's find some other way to express it.

DWG has blocked cpapdaddy (osm.org/user_blocks/18566) and I've reverted the remaining changesets except for the stream names (I leave it to others to decide about those). I'll be watching in case similar vandalism comes from another user account.

While I can't immediately prove this edit is incorrect, I consider that it risks "bringing the project into disrepute" per osm.wiki/Vandalism and cpapdaddy has shown bad faith elsewhere, so I've gone ahead and reverted it in changeset/170269180 .

It looks like the vandalism has continued, e.g., in changeset/170268366. I've submitted a request to the Data Working Group to block cpapdaddy and will revert some of the vandalism in the meantime, though I'm not going to sit around watching for changesets to revert them as soon as they happen.

Hey! This changeset appears to consist mostly if not completely of spam, similar to the spam we previously saw from unknown246's account (discussion on changeset/169357242). For now, I've gone ahead and reverted the whole thing in changeset/169829340 .

What happened? Was your account hacked too? If you are intentionally creating new accounts in order to continue spamming, I'll have to ask what tools the Data Working Group has available to stop this. If you believe some of your edits to elements are valid, please explain which ones and where you got the data (your changeset has an unhelpful description and no source) and we can reinstate those edits.

Thanks for your cooperation.

OK, I reverted the remaining parts of your changesets 169310048 through 169373059, even the parts that looked potentially valid. (Technicality: I didn't revert discardable tags.) I think this is the best way, to make sure that other users don't contact you with questions about data you didn't intend to submit. If any of the changes are valid and important, someone can redo them later.

I didn't touch your changesets after 169373059, except I reverted changeset/169482172 because I didn't think it made sense to leave the business with a city, state, and zip but no house number or street. If you can vouch for all the address tags, feel free to resubmit them.

Thanks again for your cooperation. I'm glad to see that this incident apparently hasn't turned you off of contributing to OSM.

See changeset/169357242 for discussion.

I've cleaned up almost all of the 5TDGBRCH4MS037831 stuff as well as some links to irrelevant photos on Flickr. However, some of the same changesets that included the obvious spam also included other edits that look like they could be either truthful or bogus. unknown246, did you intentionally make any edits to OpenStreetMap since July 21, or can I assume that all the edits from your account in that time period are from the hacker? If the latter, then I will revert the rest of the edits. (I was going to leave them alone, but then I noticed changeset/169310048, with stream names that look pretty unlikely to be truthful.) Thanks for your cooperation in getting this mess cleaned up.

See the discussion on changeset/169357242 . I'm already working on reverting the "5TDGBRCH4MS037831" spam in all of unknown246's changesets. But I'm a relatively junior user; if DWG wants to take this over and has better tools, go for it. Is there a better place to put a notice so other mappers don't inquire on more individual changesets?

Oh, that makes sense. Thanks for letting us know what's going on. I assume you already locked the hacker out (e.g., by changing your password and revoking any OAuth authorizations they could be using)? I'll work on cleaning up the 5TDGBRCH4MS037831 stuff.

Hey, why did you name so many elements "5TDGBRCH4MS037831"? I don't see how this could be accurate. Did your editor go haywire?

This change looks good. Thank you for the contribution! I only found two minor issues:
1. node/7515008604 should not be tagged highway=crossing because the intersecting way is not a road. (It's unclear if the intersecting way represents a trail or a park boundary, but that's not our problem here.) I went ahead and fixed this in changeset/169027531.
2. way/1412528283 has an extra node on the west end after the connection to the crossing. That could be valid if the sidewalk extends a little beyond the crossing, but looking at the imagery, I think you may have intended to connect the crossing to the west endpoint of the sidewalk instead of the second node from the west. I'll leave this for you to change if you feel it's appropriate.

Looks good. Thanks.

The change itself looks good. I'd encourage you to specify the source as you did on some of your other changesets. I know the iD editor doesn't make this obvious (https://github.com/openstreetmap/iD/issues/7755 for the record).

The change looks fine to me. Thanks for contributing. It looks like there are some other service roads internal to the plant that have no access tag. If you think it's safe to assume they're private too, you could consider tagging them so.
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/168872107

Thanks for pointing this out. I performed the deletion in changeset/168986891. To delete part of an OSM way, you would select both the way and the cutoff point, use the "split" command, and then delete one of the two ways left after the split.

In the future, if you need a change made to the map but are not sure how to perform it, it's better to create a note with the information (osm.wiki/Notes) than to add dummy data to the map. Thanks for your contributions!