[postgis-tickets] [PostGIS] #5162: Expose GEOSConstrainedDelaunayTriangulation

[PostGIS]

#5162: Expose GEOSConstrainedDelaunayTriangulation
-------------------------+---------------------------
 Reporter:  mdavis       |      Owner:  pramsey
     Type:  enhancement  |     Status:  new
 Priority:  medium       |  Milestone:  PostGIS 3.3.0
Component:  postgis      |    Version:  3.2.x
 Keywords:               |
-------------------------+---------------------------
 GEOS 3.11 has added
 [http://libgeos.org/doxygen/geos__c_8h.html#a1849ca38fe31c72787463989b50bbb0d
 GEOSConstrainedDelaunayTriangulation] to provide Constrained Delaunay
 Triangulation for polygonal geometry.

 How should this be exposed?   Existing functions which are similar are
 both backed by SFGCAL: [https://postgis.net/docs/manual-
 dev/ST_Tesselate.html ST_Tesselate] and [https://postgis.net/docs/manual-
 dev/ST_ConstrainedDelaunayTriangles.html ST_ConstrainedDelaunayTriangles].
 However, both of these have some additional functionality which isn't in
 `GEOSConstrainedDelaunayTriangulation`, and both produce TINs only as
 output.  Design options include:

 - add a new new function for the GEOS functionality.  Perhaps
 `ST_Triangulate` or `ST_TriangulatePolygon`.  This could output either a
 Polygon collection or a TIN or both (see switch on
 [https://postgis.net/docs/manual-dev/ST_DelaunayTriangles.html
 ST_DelaunayTriangles]).
 - add a branch to `ST_Tesselate` to use GEOS for polygonal inputs.  This
 would be moved to be under **Geometry Processing** in the doc.  But would
 be nice to allow Polygon collection output, which means adding a flag.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5162>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.