Changes between Initial Version and Version 1 of Ticket #2712


Ignore:
Timestamp:
Apr 11, 2014, 8:20:19 PM (10 years ago)
Author:
robe
Comment:

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.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2712 – Description

    initial v1  
    2727http://gis.stackexchange.com/questions/92552/postgis-error-getpoint4d-p-point-offset-out-of-range
    2828
    29 Though I wasn't able to replicate the issue with his data.  I will retry again.
    30