gravitystorm left a comment (openstreetmap/openstreetmap-website#6512)
For one tiny part of this - I would imagine the best way to designate an area
is with a polygon - I think squares or circles would be too limiting for
moderators and they would end up creating multiple adjacent regions to fit a
real-world situation. If we go down this route, and use polygons, I think it
would therefore be best built on top of PostGIS rather than rolling our own
polygon storage and intersection testing.
Another tiny part - defining whether a changeset intersects a given polygon is
not well defined. One example is when the entities are far apart - e.g. if a
changeset contains a node in London and one in Australia, would that be blocked
by a zone over the Middle East? It's the same problem we've had for years with
the History view.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6512#issuecomment-3558865812
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
