[postgis-tickets] [PostGIS] #2712: ST_Segmentize exception on Empty input: getPoint4d_p: point offset out of range

[PostGIS]

#2712: ST_Segmentize exception on Empty input: getPoint4d_p: point offset out of
range
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.1.3
Component:  postgis  |     Version:  2.1.x        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by robe):

 The starting chain that triggered the LINESTRING EMPTY was this:


 {{{
  SELECT ST_AsText(ST_OffsetCurve('LINESTRING(1116773.8702957
 7172132.24526899,1116768.15226771 7172128.54354244,1116752.61206679
 7172126.30820484,1116742.74915991 7172090.05035972,1116746.60081429
 7172083.8179674,1116759.05746531 7172082.54875741,1116767.82944119
 7172087.37933384,1116770.23394219 7172116.41968508,1116768.15226771
 7172128.54354244)'::geometry, 30));
 }}}


 Which returns a LINESTRING EMPTY.  The linestring winds about itself.  I
 was tempted to report that as a bug, but in retrospect, since the offset
 is so big relative to the line string and the offset would collapse into
 itself I don't think any valid linestring could ever be returned. -30
 works just fine.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2712#comment:2>
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.