I'm rewriting core PostGIS Topology function to speedup topology population, with a focus on finding faces _properly_ containing a point (having the point on the interior, not on the boundary).
We currently have a topology.GetFaceByPoint function which I'm tempted to re-use as a signature for the improved function, but that function also allows finding faces having the query point on the boundary, which is NOT what I want. Now the question is: would people really need the current behavior of that function and if so, why ? I fail to understand in which case would anyone want to deal with a tolerance for finding faces, unless they accept multiple faces as answer (a point on a face boundary is ambiguous as to which face should be returned). So: do you use that function ? For what task ? Reference: https://trac.osgeo.org/postgis/ticket/4933 --strk; () Free GIS & Flash consultant/developer /\ https://strk.kbt.io/services.html _______________________________________________ postgis-users mailing list postgis-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/postgis-users
