[PostGIS] #4794: ST_3DIntersection does not behave correctly with line strings when no vertex is seen within the intersecion

[PostGIS]

#4794: ST_3DIntersection does not behave correctly with line strings when no
vertex is seen within the intersecion
------------------------+-----------------------------
  Reporter:  basilrabi  |      Owner:  Loïc Bartoletti
      Type:  defect     |     Status:  new
  Priority:  medium     |  Milestone:  PostGIS SFCGAL
 Component:  sfcgal     |    Version:  3.0.x
Resolution:             |   Keywords:
------------------------+-----------------------------
Comment (by Loïc Bartoletti):

 I haven't tested with older versions, but it's ok with PostGIS 3.7.0dev
 and SFCGAL 2.3.0dev.


 {{{
 gis=# WITH solid AS (
     SELECT CG_MakeSolid(
         CG_Extrude(
             ST_Translate(
                 ST_Force3D(
                     ST_GeomFromText('POLYGON ((-1 1,1 1,1 -1,-1 -1,-1
 1))')
                 ),
                 0, 0, -1
             ),
             0, 0, 2
         )
     ) geom
 )
 SELECT
     ST_AsText(CG_3DIntersection(
         'LINESTRING (-2 0 0,2 0 2)'::geometry,
         solid.geom
     )),
     ST_AsText(CG_3DIntersection(
         'LINESTRING (-2 0 0,0 0 1,2 0 2)'::geometry,
         solid.geom
     ))
 FROM solid;
 }}}

 returns:


 {{{
            st_astext           |           st_astext
 -------------------------------+-------------------------------
  LINESTRING Z (-1 0 0.5,0 0 1) | LINESTRING Z (-1 0 0.5,0 0 1)
 (1 ligne)
 }}}
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4794#comment:4>
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.