If there is a chance of being readded, don't delete it and instead add the life cycle prefix.

osm.wiki/Lifecycle_prefix

For instance this may have been better tagged with the abandoned prefix.

This will keep it from being rendered/used, but it also keeps people from accidentally readding it from old maps / aerials.

This gets all new mappers as the ID editor does not make it obvious.

You need to change the building tag on the the razed buildings to demolished:building (this is done manually in tags). The large building should be a construction area or a building under construction.

You can delete the businesses POIs that are no longer present.

Let me know if you need more help.

On the intersection of East Hutchinson Avenue, Streetside does confirm it should be Street.

I could not find a sign on streetside to back up the change and the parcel maps show that the suffix is Street not Way.

I'm sorry that people are getting confused between the addresses, but please don't change the name of the road as it causes people who live there problems.

I have reverted the changeset.

Thanks for contributing.

Try not to delete roads/paths/buildings that still exist on the ground. Instead change access and other tags and other tags to prevent routing through them. It's a common mistake.

I have resolved the issue for you.

Old roads rarely are straight up deleted unless they were added incorrectly, or completely razed.

Instead we often do a prefix code to indicate they exist, but were states of disrepair. This is sometimes useful for hikers and for people to not accidentally re-add them off older aerials. It does keep it from being used by routers. So it doesn't have much of a downside.

See here:
osm.wiki/Lifecycle_prefix

In Id (the name of the web editor) it's done through the advanced tag editor. This would be disused:highway or abandoned:highway. It also is used a lot of recently demolished buildings (aka demolished:building)

Fortunately, you can revert your change here via the changeset # where you deleted it (aka this one)
https://revert.monicz.dev/

If it's just a really terrible road, consider changing it to a track.

This catches everybody cause the web editor doesn't indicate *it all*.

Accidentally re-used a comment summary. I added a business, max weight and some roads.

The OSM discord consensus is you should be setting them to access=private.

access=destination is used for "No Thru Traffic" signs.

The routers treat them a little differently.

You actually look like you updated it fairly well. Do you know if it's really a one way? I'm also not sure if the turn restriction is necessary if only emergency access vehicles will be using it.

Looks like you accidentally glued Eagle Acre Estates to the roads.

You should revert this and change it to a vacant shop and remove other tags. This helps maintain details like the address / suite number (when it has one). This also makes checking the history of a location easier.

You can revert it here by the changeset number.
https://revert.monicz.dev/

In the case OsmAnd doesn't make that easy let me know and I'll do it for you.

I don't use those tags much. I have updated it. Thanks for letting me know.

They recently added the circle.

https://www.avonoldfarms.com/old-farms-road-project-update

Their website was having issues so I could not find out what happened to the original road.

BC720, if you know if the road was closed or demolished we can update it appropriately.

Hypsometric, If you want to revert and change it to demolished feel free. I'm ok waiting for a response.

I know you're new, but the correct thing to do is to keep the road and change the lifestyle prefix, add barriers, and/or access levels depending on how it's closed/removed.

Otherwise people unfamiliar with the area come back and re-add it accidentally and we have to go through this again.

Properly tagged will prevent GPS systems from using it.

Do you know how it was closed?

Thanks. I work on (or at least investigate) a lot of random notes across the US. I'll try to keep it in mind if I find myself here again.

While the first instincts of many new mappers are to removed it, the approved approach is change the tags on it to accurately describe the road's state. (known as lifecycle prefixes)

osm.wiki/Lifecycle_prefix

access=no
Changed the highway type to destroyed:highway
or abandoned:highway

See:
destroyed:*=*

These are lesser known tags to new mappers. The reason we do this is it accurately describes the road, the access tag will prevent routers (gps systems) from using it.

The main reason we do this is it prevents future mappers from readding it without knowing the state

So I'd recommend you revert the change and add the tags. You can revert it here (https://revert.monicz.dev/ ) with the changeset/166997227.

None of this is obvious to new mappers or even shows up in the editor without manually editing the tags, so don't feel bad. Let me know if you need more help with it.

Sorry, I meant I'm not sure about the Eastern side. It might be scrub or already in development.

I was looking at ESRI which had the buildings for the gas station so it was newer. They cleared at least the Western half down to green tinted dirt which I assumed would become grass.

I was comparing the texture to the woods directly North and lack of significant shadows.

But to be honest I'm not 100% sure on the Western side, I just assumed they cleared it out to continue development.

I fixed the road classification to be consistent with OSM for you. You can choose service road for most parking lots roads.

Word of advice.

Don't split up parking lots into a bunch of tiny parking lots. If you were going out out of the building you'd think "These 5 spots are a parking lot?" No, you'd think the big rectangular section is one continuous parking lot. Sometimes there are "Lot A" and "Lot B" that should be split.

It makes it easier to tag ownership, renders a bit better, and in GPS systems it won't show up a 5 different parking lots.

You can turn parking lots into MP (multi polygons) if you really want to pull out components that you don't like, like the island/separators. You can also map individual parking spaces but I recommend doing that in JOSM with the gridify plugin.

Yes, OSM gets into a lot of tedious debates about what noun means and you'll run into classification debates like this constantly.