I was importing a very large raster set and after a day it failed with
array size exceeds the maximum allowed when setting the extent
constraint.
I redid the import again by just doing the table create and then
adding the data and then doing the final bunch of sql statements
manually to avoid havi
Hi Regina,
On 11/18/2016 3:28 AM, Regina Obe wrote:
Since you are doing 0.0, you might be better off using ST_Intersects
So
st_dwithin(pnt, a.geom, 0.0)
change to:
ST_Intersects(pnt,a.geom)
Did this change recently? I was under the impression that st_dwithin was
faster than st_intersects?
Hi Cedric,
2016-11-18 14:21 GMT+01:00 ced :
> Hi all,
>
> I am upgrading PostgreSQL and PostGIS from 9.3/2.1 to 9.5/2.3.
>
> I perform the backup on the old server (9.3/2.1) like this using pg_dump.
>
> Then, on the new server (9.5/2.3), I restore the backup using pg_restore.
>
> Everything is co
Hi all,
I am upgrading PostgreSQL and PostGIS from 9.3/2.1 to 9.5/2.3.
I perform the backup on the old server (9.3/2.1) like this using pg_dump.
Then, on the new server (9.5/2.3), I restore the backup using pg_restore.
Everything is correctly restored, except just one raster table, a DEM, whic
Since you are doing 0.0, you might be better off using ST_Intersects
So
st_dwithin(pnt, a.geom, 0.0)
change to:
ST_Intersects(pnt,a.geom)
Or did you try that already?
How many points does ST_NPoints return for your exclusion area? If a lot,
then detoasting might be an issue and then you
