[postgis-tickets] [PostGIS] #5587: Expose SFCGAL's 3DIntersects as CG_3DIntersects

[PostGIS]

#5587: Expose SFCGAL's 3DIntersects as CG_3DIntersects
---------------------+---------------------------
 Reporter:  robe     |      Owner:  pramsey
     Type:  defect   |     Status:  new
 Priority:  medium   |  Milestone:  PostGIS 3.5.0
Component:  postgis  |    Version:  3.4.x
 Keywords:           |
---------------------+---------------------------
 Prior to PostGIS 3.0, we had a backend guc that allowed to specify which
 function to use when overlapping functions between postgis and
 postgis_sfcgal.

 This switch was removed cause most overlaps were redundant or the postgis
 version was better and functions such as ST_3DIntersects were augmented to
 handle TINS and POLYHEDRALSURFACE, which were the reasons why anyone would
 want to use the SFCGAL implementation.

 However there are some corner cases where the SFCGAL version is just
 better. There is also the issue of solids.  postgis ST_3DIntersects does
 not have a concept of solids where as sfcgal does understand the
 difference between a solid and a surface.

 That said we need SFCGAL 3DIntersects back and eventually perhaps rename
 others with prefix CG, so we don't have to have arguments when SFCGAL has
 some function that GEOS now has like the whole e.g ALphaShape stuff we had
 recently.

 Thoughts?

 My main question is CG good prefix.  I avoided SF cause that sounds like
 spatial features.  And SFCGAL_ seems too long.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5587>
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.