pablobm left a comment (openstreetmap/openstreetmap-website#6512)
I had a call with @gravitystorm today to discuss this. I'm going to try
summarise where we got, hopefully he'll correct my misunderstandings. I'm going
to refer to this feature as "Block Zones", to avoid mixing up with other
similarly-named features.
Enabling PostGIS:
- Using PostGIS _generally_ in OSM would be a huge undertaking, just as
@tomhughes describes.
- However it doesn't have to be all or nothing: we can use it in specific
cases, and it'll enable new ideas over time.
Circles vs polygons (or other shapes):
- As discussed above, circles have downsides and don't buy us that much in
return.
- Existing libraries can help us build a UI to define polygons. An example is
https://terradraw.io, which is compatible with Leaflet and MapLibre.
- With PostGIS enabled, calculating these "block zones" would be simple and
performant. Doing the same thing with Ruby is complex and inefficient.
How should Block Zones be compared to incoming edits?
- Start by comparing the bounding box of the changeset.
- This is imperfect as these bounding boxes can expand outside the Block Zone
and evade it.
- However the alternative can be expensive. Relations/ways need to be broken
down into its constituent nodes, potentially by several levels.
- For simplicity, we are starting here, then refining as we go. We can come up
with heuristics as we learn of real-wold issues.
Things to look out for:
- Zone blocks in long-term controversial areas create a barrier to new,
legitimate users. The DWG needs to be aware of this and we can come up with
ideas over time, again as we evaluate real-world effects.
Action points for me:
- Create a new issue to cover enabling PostGIS.
- Rework description to: depend on PostGIS being enabled first, define block
zones with polygons.
- Update DWG. Remind them of potential real-world issues.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6512#issuecomment-3585423113
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
