From: Mateusz Loskot <mateusz@loskot.net>
Date: Mon, 7 Apr 2014 15:09:46 +0000 (+0000)
Subject: Document raster_columns.out_db metadata (Ticket #2705)
X-Git-Tag: 2.2.0rc1~1149
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=bb07a778752d211a2cce4c65ba50e6835aa648ad;p=postgis

Document raster_columns.out_db metadata (Ticket #2705)

git-svn-id: http://svn.osgeo.org/postgis/trunk@12435 b70326c6-7e19-0410-871a-916f4a2858ee
---

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:
 				<listitem>
 					<para><varname>nodata_values</varname> An array of double precision numbers denoting the <varname>nodata_value</varname> 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 <xref linkend="RT_ST_BandNoDataValue" />.</para>
 				</listitem>
+				<listitem>
+					<para><varname>out_db</varname> 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.</para>
+				</listitem>
 				<listitem>
 					<para><varname>extent</varname> 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 <xref linkend="RT_DropRasterConstraints" /> function before load and then reapply constraints with <xref linkend="RT_AddRasterConstraints"  /> after load. </para>
 				</listitem>