id summary reporter owner description type status priority milestone component version resolution keywords cc 4051 Strange result with raster ST_Intersects stev00 Bborie Park "I have odd behaviour when trying to use the ST_Intersects function with rasters, which I am using to filter raster tiles using an index for an ST_Value call. On both Linux Red Hat (RDS) and Windows using Postgres 10.1 and Postgis 2.4 I get a null result for the filter call for a very small number of point geometries (in fact only one so far from around 1000 points). The only significant feature is that the x value of this point is a whole integer. I am attaching a full sql file to reproduce a minimal version of the problem. If you look at the rasters in QGIS you should be able to see it covers the point, and adding a very small increment or decrement to the X value means a value is returned (but no difference with y value). This combined with the whole number issue above means I wonder if it is something to do with the integer value. I will continue looking into this, and it could obviously be a dependent library issue, but would be interested to see if others can reproduce it." defect closed medium PostGIS 3.4.0 raster 2.4.x fixed