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

Bryce Cogswell bryceco at yahoo.com
Sat Jun 13 21:00:16 UTC 2020


> On Jun 13, 2020, at 3:42 AM, Simon Poole <simon at poole.ch> wrote:
> 
> And all this because of a API defect (because there is just one bounding
> box per changeset instead of a list)?

This hints at a reasonable and not terribly difficult solution, which is for the editor to (optionally and automatically) split a single changeset into a sequence of changesets each with their own bbox. Maybe with an extra changeset tag that ties them together. 





More information about the talk mailing list