pablobm left a comment (openstreetmap/openstreetmap-website#6512)
Is it realistic to enable PostGIS in the DB? Asking from complete ignorance: no
idea of what the implications are on the operations side, etc. Perhaps
@tomhughes or @firefishy have opinions on this?
If that's feasible in the short term, basing the block on an existing boundary
would sound very promising. To avoid the issue of vandalised boundaries, a
specific, historic version of the boundary could be chosen.
If that wasn't feasible in the short term, would it be practical so start with
the same solution used to identify nearby users? From my ignorance on the topic
of GIS, I'm guessing that's probably not very scalable, but might just do it
initially, as better solutions are implemented iteratively and with practical
knowledge of the implications.
> we might still want to store the intersection of those circles?
I don't understand: what's special about the intersection of the circles? My
thinking is: feature is created, we iterate through all the circles to find if
something falls within. Any intersections will be checked multiple times, but
that shouldn't (?) be a big deal.
Regarding the UI, is there any prior art on an interface to define polygons,
that can be used in the admin section? Not sure we want to instantiate a
full-blown iD here... or do we?
> I meant more that two innocent changes might get blocked
This is going to be part of the tradeoffs that the DWG will have to consider
when blocking regions. In any case, from my ignorance I want to think that it
won't be a big deal: heuristics can improve, it only affects new/anonymous
accounts, the DWG will keep an eye, it's not a "proper" user-facing feature.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6512#issuecomment-3575174808
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