From bb07a778752d211a2cce4c65ba50e6835aa648ad Mon Sep 17 00:00:00 2001 From: Mateusz Loskot Date: Mon, 7 Apr 2014 15:09:46 +0000 Subject: [PATCH] Document raster_columns.out_db metadata (Ticket #2705) git-svn-id: http://svn.osgeo.org/postgis/trunk@12435 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/using_raster_dataman.xml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/using_raster_dataman.xml b/doc/using_raster_dataman.xml index f23b5d83b..fb7671a12 100644 --- a/doc/using_raster_dataman.xml +++ b/doc/using_raster_dataman.xml @@ -482,6 +482,9 @@ Available GDAL raster formats: nodata_values An array of double precision numbers denoting the nodata_value for each band. You will have the same number of elements in this array as you have number of bands. These numbers define the pixel value for each band that should be ignored for most operations. This is similar information provided by . + + out_db An array of boolean flags indicating if the raster bands data is maintained outside the database. You will have the same number of elements in this array as you have number of bands. + extent This is the extent of all the raster rows in your raster set. If you plan to load more data that will change the extent of the set, you'll want to run the function before load and then reapply constraints with after load. -- 2.50.1