Oops, you CAN actually cache a bytea to raster, using encode(overlay(),
'hex')::raster. So my problem is solved.
I can now address 15+ years of NDVI imagery in a single go! This is super
efficient!
Guido
On 02/10/15, guido lemoine wrote:
>
>
> Bborie,
>
> In the meantime, I managed to use
Bborie,
In the meantime, I managed to use postgresql overlay to change the filename in
the rast, but this results in a bytea which cannot be cached back to a raster.
I found a 2013 thread
http://lists.osgeo.org/pipermail/postgis-users/2013-June/037163.html which
asked for bytea -> raster conve
Hey Guido,
ST_SetBandPath doesn't exist but sounds like a worthwhile addition. Can you
file a ticket for that?
http://trac.osgeo.org/postgis/
In the meantime, a workaround is to use symbolic links or mount points.
-bborie
On Tue, Feb 10, 2015 at 2:34 AM, guido lemoine <
guido.lemo...@jrc.ec.eu
Hmm, any thoughts on this? Just to expand my use case: I have a time series of
images that are all spatially aligned, i.e. same size, geo-location, pixel
spacing, projection.
Thus, raster2pgsql -R would always create the same tiled raster entries for
each image where only the (binary) file name
Dear List,
I have stored some rasters out-of-db (using raster2pgsql with the -R option). I
have to move these rasters
to another disk and wonder if there is a simple way to update the BandPath to
the new location, other
than dropping the tables and re-load with the new path. I see there is
ST_B
