Yes they are really cosmetic.

What I’ve done is adding the full name of the garage and drop TIGER tags of 2 streets after aligning them.

Please avoid attaching any park area with road segments.

How about learning road type first?

You created a mess here, literally make the data unusable.

way/824297022#map=19/39.92517/-77.61639

There is no reason to add a segment to the parking lot when it is alongside the road.

way/910660632

Also do not use Bing to edit Pennsylvania.

PEMA imagery has been added to the OSM. Please take a look with your previous edits to see if there is any offset.

osm.org/#map=19/39.93948/-77.62645

osm.wiki/Naming_conventions

How about not importing garbages? The building you added has been demolished probably since 10 years ago.

way/647432578

The entire area, which you added using Mapbox, has offset issue.

Not really. I was reading the history of way/32119090.

You are the author of the name "South 37th Street Walk". There is no such street with that dumb name. Even if it is a street for pedestrian "walking", there is no need to change the name. The sign is firmly installed on Walnut St.

Unless the history is messed or I misunderstood something.

Are you sure that it is a driveway?

way/961483994#map=19/39.73498/-76.77274

Hi,

You have created a huge mess in Salisbury MD, likely all your changesets starting from this one to the most recent will be reverted.

Please carefully read wiki before making any edits, you will be closely watched:

cycleway=*

osm.wiki/Editing_Standards_and_Conventions

osm.wiki/Good_practice

Theoretically road is a continuous area, you intersect road area with land use features could be acceptable. However:

1) OSM community does not favor drawing road as an area.

2) Intersecting will increase the workload of others when they only wish to cleanup the road but not any other features. And other people have to disconnect the area you attached to the road in order to do the cleanup. Not a big issue at this place, but when there are multiple area features combined (boundaries, woods…), it will become a huge problem.

3) The boundary of the school here is limited exactly at the edge of the road. If you connect the school area onto the road, you accidentally put half of the road area as part of the school parcel, which is basically incorrect.

PS: PA is not an area with low res imagery.

Please do not connect any landuse feature with highway.

way/694820729/history#map=19/39.76381/-76.85434

The driveways you added here have offset. Please check your sources carefully before applying changes.

way/792438215

Thiere is no need to create multiple parking lots in the same place, especially when there is no difference between any of them.

way/626539767#map=19/39.60704/-77.05975

The pedestrian area feature should only be applied to Baltimore St between Mechanic St and George St.

way/495568913/history#map=19/39.65186/-78.76058

Please consider using "
MD Latest 6 Inch Aerial Imagery" editing Maryland. Using ESRI only to track new aerial updates which do not exist in MD 6in.

This is not a one way link.

way/197330797/history#map=19/39.65964/-78.77524

Your edit has been reverted since it is not a bridge.

Please be careful editing Pennsylvania because I (and many other people) monitor all changes in this area.

changeset/104967605#map=16/39.8987/-75.5416

This is hilarious.

You dont have to create a no left turn, just dont connect the segments together.

relation/7830418#map=18/39.30384/-76.59253