Opened 13 years ago
Closed 13 years ago
#987 closed defect (fixed)
Bad handling of Inf values in GEOS
Reported by: | pramsey | Owned by: | pramsey |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 1.5.4 |
Component: | postgis | Version: | 1.5.X |
Keywords: | Cc: |
Description
See http://postgis.refractions.net/pipermail/postgis-users/2011-February/028999.html
Older versions of GEOS (pre 3.3) will loop infinitely when handed some coordinates with Inf values in them. Proj4 sometimes generates those values. The solution (?) in this case is to patch PostGIS to not pass the values through to GEOS.
Attachments (3)
Change History (8)
by , 13 years ago
comment:1 by , 13 years ago
That check would make ST_IsValid throw an exception rather than returning false. Note that ST_IsValidReason will tell you it's due to NaN / Inf ...
by , 13 years ago
Attachment: | inf3.patch added |
---|
comment:2 by , 13 years ago
Milestone: | PostGIS 1.5.3 → PostGIS 2.0.0 |
---|
Committed to 1.5 branch at r7344, should be committed to 2.0 also.
comment:3 by , 13 years ago
Milestone: | PostGIS 2.0.0 → PostGIS 1.5.3 |
---|
comment:4 by , 13 years ago
Milestone: | PostGIS 1.5.3 → PostGIS 1.5.4 |
---|
comment:5 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This seems to have been applied to trunk also. Closing out.
Inf testing in the GEOS handler