pablobm left a comment (openstreetmap/openstreetmap-website#6512)
I agree that polygon would be great, but I'm worried that implementing it could
turn into a rabbit hole. There's building the UI to create the selection, and
having to enable PostGIS in the process (as I understand it's not present
currently).
In conversation with the DWG, an idea came up of using existing boundary
relations. That would be really handy but I suspect we don't have a good way to
determine if a point is within a boundary (perhaps another reason to add
PostGIS after all?).
So with the above, a circle might be the simplest solution that gets us going
with something useful. In some cases moderators would need to create multiple
circles, but the UI could be made to define several circles as part of a single
"block" which might hit a right balance of complexity vs utility.
As for those corner cases of London-Sydney-Bethlehem, etc, I think it's fine
for the use case as this is not a proper user-facing feature. Having said that,
perhaps this can be exploited... someone could create a changeset with
vandalism in a defined area, plus an unrelated change 3000km away, thus
triggering this edge case. Perhaps the focus should be in individual nodes
rather than the changeset bounding box? But then we risk slowing down large
edits... But! The important part here is to reduce the workload of moderators,
not to come up with a perfect solution. Heuristics can be devised and impacts
measured as we go on.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6512#issuecomment-3562624167
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
