[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:           |  
---------------------+------------------------------------------------------

Old description:

> This is similar to #2108
>
> When I run below on:
>
> {{{
> SELECT postgis_full_version() || ' ' || version();
> POSTGIS="2.1.2 r12389" GEOS="3.4.2-CAPI-1.8.2 r3924" PROJ="Rel. 4.8.0, 6
> March 2012" GDAL="GDAL 1.10.0, released 2013/04/24" LIBXML="2.7.8"
> LIBJSON="UNKNOWN" RASTER PostgreSQL 9.3.4, compiled by Visual C++ build
> 1600, 64-bit
>
> }}}
>

>
> {{{
> SELECT ST_Segmentize('LINESTRING EMPTY'::geometry, 0.5);
> }}}
>
> I get
>

> {{{
> ERROR:  getPoint4d_p: point offset out of range
> }}}
>
> Would seem to me that this should just return back a LINESTRING EMPTY.
>
> Someone complained about a similar issue here:
> http://gis.stackexchange.com/questions/92552/postgis-error-getpoint4d-p
> -point-offset-out-of-range
>
> Though I wasn't able to replicate the issue with his data.  I will retry
> again.

New description:

 This is similar to #2108

 When I run below on:

 {{{
 SELECT postgis_full_version() || ' ' || version();
 POSTGIS="2.1.2 r12389" GEOS="3.4.2-CAPI-1.8.2 r3924" PROJ="Rel. 4.8.0, 6
 March 2012" GDAL="GDAL 1.10.0, released 2013/04/24" LIBXML="2.7.8"
 LIBJSON="UNKNOWN" RASTER PostgreSQL 9.3.4, compiled by Visual C++ build
 1600, 64-bit

 }}}



 {{{
 SELECT ST_Segmentize('LINESTRING EMPTY'::geometry, 0.5);
 }}}

 I get


 {{{
 ERROR:  getPoint4d_p: point offset out of range
 }}}

 Would seem to me that this should just return back a LINESTRING EMPTY.

 Someone complained about a similar issue here:
 http://gis.stackexchange.com/questions/92552/postgis-error-getpoint4d-p
 -point-offset-out-of-range

--

Comment(by robe):

 I was able to replicate the error with the data set in the stackexchange
 one, though I haven't tried in 2.0 to verify it is a new bug in 2.1. The
 final dataset that triggered the error does have a LINESTRING EMPTY row.
 Might be more than just LINESTRING EMPTY (such as how there ended up being
 a LINESTRING empty in first place). . Poster said this was not an issue in
 PostGIS 2.0.  Ihaven't tried myself in a 2.0 install.

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