Changes between Version 62 and Version 63 of WKTRaster/SpecificationWorking03

Timestamp:

Apr 15, 2011, 8:35:13 AM (13 years ago)

Author:

Bborie Park

Comment:

added numbering for functions in FV.01

WKTRaster/SpecificationWorking03

@@ -44 +44 @@
 Bborie: A complete implementation of ST_Band should include the following:
 
-ST_Band(rast raster, nbands int[]) -> raster
+1. ST_Band(rast raster, nbands int[]) -> raster
 
     nbands is an array of 1-based band indices of the bands to copy into the output raster
@@ -59 +59 @@
 }}}
 
-ST_Band(rast raster, nband int) -> raster
+2. ST_Band(rast raster, nband int) -> raster
 
     nband is a single integer of the 1-based band index of the band to copy into the output raster
@@ -69 +69 @@
 }}}
 
-ST_Band(rast raster, nbands text) -> raster
+3. ST_Band(rast raster, nbands text) -> raster
 
     nbands is a comma separated string of 1-based band indices indicating the bands to copy into the output raster
@@ -79 +79 @@
 }}}
 
-ST_Band(rast raster, nbands text, delimiter char) -> raster
+4. ST_Band(rast raster, nbands text, delimiter char) -> raster
 
     nbands is a user-specified delimiter separated string of 1-based band indices indicating the bands to copy into the output raster
@@ -89 +89 @@
 }}}
 
-ST_Band(rast raster) -> raster
+5. ST_Band(rast raster) -> raster
 
     the band to extract is automatically assumed to be one.
@@ -105 +105 @@
 As part of the process to provide complete implementations of ST_AsJPEG and ST_AsPNG, a method is required to reclassify larger numbers unable to be contained in 8BUI (JPEG and PNG) and 16BUI (PNG). For this reclassification function, we need to get the min and max values of a band, thus ST_MinMax.
 
-ST_MinMax(rast raster, nband int) -> record
+1. ST_MinMax(rast raster, nband int) -> record
 
     returns one record of two columns (min, max)
@@ -113 +113 @@
 }}}
 
-ST_MinMax(rast raster) -> record
+2. ST_MinMax(rast raster) -> record
 
     assumes that the band index = 1
@@ -211 +211 @@
 The TIFF format is probably the most robust available for converting rasters to GDAL rasters. Not only does it support all PostGIS Raster pixel types, it also provides plenty of creation options and possibly no issues with the number of bands. The only limitation found is that there can only be one NODATA value for all bands.
 
+''If the compression parameter/option is specified to JPEG, all bands must be of pixel type 8BUI.  If the compression parameter/option is specified to one of the CCITT options, all bands must be of pixel type 1BB.''
+
 The next three functions are the most basic of the ST_AsTIFF functions.
 
@@ -344 +346 @@
 Bborie: this is a generic interface to outputting a supported and installed GDAL raster:
 
-ST_AsGDALRaster(rast raster, format text, options text[], srs text) -> bytea
+1. ST_AsGDALRaster(rast raster, format text, options text[], srs text) -> bytea
 
   This is the most generic and GDAL-specific method to convert a raster to a GDAL raster.  All other version of ST_AsGDALRaster and other format specific functions (ST_AsJPEG, ST_AsTIFF and ST_AsPNG) are all wrappers around this function.  Reference information for the format and options arguments of a particular format are specified at: http://gdal.org/formats_list.html.  The arguments specified are:
@@ -361 +363 @@
 
 
-ST_AsGDALRaster(rast raster, format text, options text[]) -> bytea
+2. ST_AsGDALRaster(rast raster, format text, options text[]) -> bytea
 
   This one removes the user-specified srs argument.  The output GDAL raster's spatial reference will be set to the same as the input raster, if possible.
@@ -371 +373 @@
 }}}
 
-ST_AsGDALRaster(rast raster, format text) -> bytea
+3. ST_AsGDALRaster(rast raster, format text) -> bytea
 
   The simplest implementation of this function.  Since the options argument has been removed, the output GDAL raster will be created with default options.  Like the prior function, the spatial reference of the GDAL raster will be set to the same as the input raster.