[postgis-users] Postgis out-db raster

[Darafei "Komяpa" Praliaskouski]

Hi,

outdb rasters are not part of supported Postgres machinery and are really a
pretty illegal hack.

If you keep your inputs out of DB, and your outputs out of DB, you may
really want to move the processing part out of DB too and use GDAL to do
the calculations.

The postgres way to handle that would be to redesign and reimplement the
outdb raster machinery as foreign data wrapper, similar to ogr_fdw. I am
not aware of such initiatives.

On Fri, Nov 26, 2021 at 10:49 AM paul wither <paul.wither at hotmail.com>
wrote:

> Hi there,
>
> I was wondering if anyone would be able to offer some advice on running a
> raster process in postgis.
>
> The input rasters are stored as out-db, then they run through a couple of
> steps, eg reclass a couple of map algebra steps and finally a result
>
> At each step a new raster is created and I can't quite figure out if there
> is a way (or best way) to specify that the result is written out to a new
> out-db tiff rather than a new internal table
> currently everything writes to new internal table, but there will be close
> to a thousand tables eating up a lot of space. I understand the performance
> impacts, but the process is not that time precious.
> Initially I thought that maybe I had to use AsGDALRaster then reload, but
> then I read about creating empty rasters and adding bands. does anyone have
> any suggested approaches (noting I'm no sql pro 🙂)
>
> any hints, tips or examples would be greatly appreciated
>
> cheers
>
> Paul
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20211126/bb58f66c/attachment.html>