[OSM-talk] Could/should editors detect/disallow huge changeset bboxes?

Simon Poole simon at poole.ch
Sat Jun 13 10:39:46 UTC 2020

I've advocated for this in the past,  but getting this right from a
business logic pov is fairly tricky and is yet another thing that an
editor needs to keep track of when creating and modify geometries, and
changing tags. From the top my head at least: new object creation,
dragging nodes and ways, merging and splitting ways, adding and removing
relation members, copy, cut and paste, all tag changes. While each of
these might be minor things, all together they have a clear performance
and complexity impact and require UI additions to handle. This is
assuming that such a bounding box limit would not be enforced by the
API, if enforced you actively have to not allow the user to make the
change which is even more painful.

If the limit is enforced there are all kinds of vandalism/DoS scenarios
that would probably require lifting the restriction for admins/mods.  

And all this because of a API defect (because there is just one bounding
box per changeset instead of a list)?


Am 12.06.2020 um 13:00 schrieb Frederik Ramm:
> Hi,
> I wonder if it would be feasible or desirable for editors to warn users
> if they are at risk of creating country/world-spanning changesets.
> Something like "you have unsaved edits more than 500km away from where
> you are editing at the moment, please upload those before you continue"
> or so.
> World-spanning changesets are a constant source of irritation, and very
> rarely intentional.
> Bye
> Frederik

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20200613/add8ad03/attachment.sig>

More information about the talk mailing list