Opened 10 years ago
Last modified 10 years ago
#2712 closed defect
ST_Segmentize exception on Empty input: getPoint4d_p: point offset out of range — at Initial Version
Reported by: | robe | Owned by: | pramsey |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 2.1.4 |
Component: | postgis | Version: | 2.1.x |
Keywords: | Cc: |
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.
Note:
See TracTickets
for help on using tickets.