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.

The updates to the coastline have not been updated for six months. That's what I'm trying to fix. I have no opinion on this particular change -- but it's so large that it triggers an automatic circuit breaker. Once we've gotten the updates to go thru, please DO revert Rio de la Plata back to being marked as not-coastline -- just do so in small enough chunks that it doesn't trigger the circuit breaker. I'm happy to work with you to help do that.

I'm not sure I follow. What do you intend the "oneway=yes" tag to mean? The wiki page for it says it refers to access restrictions for vehicles -- as far as I know, no vehicles are allowed on this canal, in either direction. Please say more?

Awesome, that's a great source, thank you! (and thanks for exploring them :-) )

I wasn't able to find any information online about "Hanging Flat Mine" (there's one in the UK, but that's obviously a different thing). What's your source for it?

Removed in: osm.org/changeset/79774935

I'm not sure why you marked a canal as "oneway=yes" in this changeset. I've removed that for now, feel free to put it back if it was intended.

FYI, voltage should be a raw number, in volts, without the "k"

I think you made Node: 6183029905 by mistake. I've removed it, feel free to add it back if it was intentional.