gravitystorm left a comment (openstreetmap/openstreetmap-website#6512)
> > IIRC there is some logic that, before even applying a change to the
> > database, will extend the current changeset's bounding box. If that is
> > still the case then that would probably be the easiest place to introduce a
> > limit like this
>
> No, I removed that code. It was some sort of premature performance
> optimization that was no longer needed.
I'm surprised by this point. Is there no equivalent of
[Changeset#update_bbox](https://github.com/openstreetmap/openstreetmap-website/blob/3023ef046a102226c60237634d8e11c5d6ae9a5b/app/models/changeset.rb#L145-L153)
in cgimap? There is presumably some place where diffs (or individual element
changes) are rejected for being over the limit, before anything is committed to
the db.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6512#issuecomment-3586564779
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/6512/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
