I'm confused by your tagging of osm.org/way/134605112 -- did you mean that it is now completed, or is it still just proposed? If it's complete, please remove the construction tags and the proposed values. If not, just comment here and I'll fix the tagging. Thanks!

Thanks for fixing this -- but actually, I think this could just re-tagged as:

man_made=street_cabinet
street_cabinet=postal_service

I won't do it right now (both because I don't remember how to undelete a node, and because I'd prefer to confirm it is there in person again), but I thought I'd drop the note about it now.

It looks like this changeset may have broken this relation ( osm.org/relation/11213058 ) -- I think I fixed it in osm.org/changeset/114060661 but I'm less familiar with this area -- could you check and make sure it looks right?

Thanks, sorry I didn't include the relation in the comment ( osm.org/relation/13341310 ) -- it looks like it's fixed now! I would have fixed it myself, but I wasn't sure where the proper segment should be located, so I thought I'd ask you instead. Appreciate all your work!

You removed part of the boundary with Harrison (this relation: osm.org/relation/175809 ) -- please put it back. You can see the removal here: https://overpass-api.de/achavi/?changeset=112524594

You added an incomplete relation labeled Huntington ( osm.org/relation/12238511 ) in this changeset. The borders of that CDP seem to be elsewhere. Could you clarify what you meant by that?

It looks like you broke the relation for North Bay Shore in this edit -- could you clarify what the boundaries are that you meant to put, and fix it?

Looks like you deleted part of the coastline by mistake in this changeset? Please fix that -- you can use the reverter UI http://revert.osmz.ru to undo the whole changeset, then put back the parts that were correct.

Yes, as soon as I entered this I realized it was far, far too large. I've done better going forward -- appreciate the ping.

Yeah, as soon as I made it I winced -- should have split it into smaller pieces. Sorry about that!

I fixed some of the crossed lines added in here, in osm.org/changeset/93826824

This broke the coastline for all of North & South America (by causing it to cross in Northwest Cove by Bayside). This was fixed in this changeset: osm.org/changeset/93798791

Please be careful about this sort of thing. Thanks!

I don't think this is correctly tagged; this does not seem to be any type of aerialway.

Please don't mix edits over such a long distance, as it creates very large changeset bounding boxes, that make it harder to review changes.

This is a very large change, and I'm having trouble figuring out what it is supposed to consist of. (The single word "buildings" doesn't seem explain much, as at least some of the added elements aren't tagged as buildings). Could you clarify?

As of Jan 9, 2020, Rio de la Plata was marked (incorrectly, according to you (and, unlike christiank61, I have no interest in disputing this)) as coastline.

Fixing this error in one change is large enough to trigger an automatic circuit breaker, which can only be overridden if there is clear, un-ambigous consensus among multiple mappers in support of the change.

Rather than forming and documenting this consensus (on the wiki), an alternative is to split up the change into small enough pieces not to trigger the circuit breaker.

I don't care which of those two methods you use to fix the error -- but if you continue to disruptively refuse to use either of them, you will simply be wasting everyone's time. I urge you to pick one of the feasible methods I explained, and use it.

For the sake of my email, I'd politely request that you move further discussion of whether Rio de la Plata is a coastline or not to the wiki -- but if you really want to do it here ... sigh ... I suppose you must.

While I am glad you two are discussing this (the mappers concerned about this particular area do need to come to a consensus) -- that is NOT what this changeset is about.

As I said, I do NOT have an opinion on how this mapped; I merely (but strongly) insist that the rest of the world still get coastline updates.

Of the two options I provided (small slow changes or a formal proposal on the wiki) It sounds like muralito (and hopefully christiank61) prefer the formal proposal.

To implement that, please follow this link and create this page: osm.wiki/Rio_de_la_Plata and fill it with your discussion (although you should likely have a formal vote, too.)

I don't know how much support/consensus you will need to convince joto (the person who can make an override of the update script) -- but a clear write up of the issue ON THE WIKI is an obvious precondition.

Please, for the sake of the rest of the world, DO NOT (I repeat, DO NOT) apply this (or any other) large change without previously getting a clear statement from joto, on the wiki, that he will apply a manual override.

I will revert any such change, promptly.

Sure -- it's a strange and frankly kinda silly reason, so I don't blame you at all for being confused by it!

The rendering of the coastline on openstreetmap.org is based on data produced by osmdata.openstreetmap.de, daily. As part of that process, the script that does it checks to see how much the coastline (across the world) changed since the previous valid day (normally the previous day, but, right now, all the way back to Jan 9, 2020). If the difference is more than 0.0000015 (as shown here: https://github.com/fossgis/osmdata/blob/master/scripts/coastline/compare-coastline-polygons.sh#L13 ), it automatically rejects it.

And changing the Rio de la Plata to be correctly marked as not an ocean is way bigger than that. So in order to avoid this automatic block, we need to change small sections, one each day. Or we need to make a formal proposal (probably on the wiki), get explicit buy-in from a bunch of local mappers, then go to the maintainer of the script and ask for a manual override.

Either way is fine with me -- but just making the change all at once merely causes the rest of the world to not get any coastline updates, which is bad for everyone.

Hope that explains things more -- I'm glad to clarify further if it doesn't!

Reverting (for now) to enable worldwide coastline updates to go thru. As discussed on the other edit -- this is fine to do, but it needs to be done slowly enough to not trip the automatic circuit breaker.