mmd-osm 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.
> separate programs looped into the website code and basically ask for all (or
> specific?) changesets to be passed by them for evaluation before they are
> accepted into the database, but that's probably too grand a scheme.
That's all being done by cgimap today, and it doesn't sound like a good idea to
loop in external tools.
Today's processing is quite different from the pre-2018 world, after all.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6512#issuecomment-3586447737
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
