Reminder to keep changesets as local as possible and not globe-spanning:

osm.wiki/Changeset#Geographical_size_of_changesets

Reminder to keep changesets as local as possible and not globe-spanning:

osm.wiki/Changeset#Geographical_size_of_changesets

Saw this and wanted to let you know that using other mapping services as proof of an object's existence should be avoided, such object information can be under copyright. Creating objects using imagery sources is fine, but any other information must be locally sourced. Thanks.

osm.wiki/Copyright#Proprietary_data

I did so I can add them back in later with better geometry and with the paths.

I did not spot any ALPR device in that intersection. What is there is a standard traffic camera. Be sure to reference the deflock.me for images on existing ALPRs.

What's most commonly found on intersections like these are the white Genetecs and black Motorolas, with one node face away from the intersection in each direction.

This change could have been split into two. Having one change spanning half of the globe is not necessary.

Was there a way for this change to have been split into several localized changes so that it does not span the whole globe?

Why does this change span beyond Columbia and up into much of the US?

Please try to keep these changes localized to each area as much as possible. It's not helpful for the rest of us to have one change that spans the entire globe.

Try keeping these changes localized their respective areas as much as possible. No need for this to span between the Harrisburg and Philly areas.

dito, dmjab13

When creating sidewalk chains that have marked and unmarked crosswalks between them, please create those unmarked crosswalks.

And keep to the geometry of the path you're tracing as much as possible.

Try not to combine changes to multiple nodes that straddle the globe please.