Changes between Version 117 and Version 118 of WKTRaster/SpecificationWorking03

Timestamp:

Jun 13, 2011, 3:32:47 PM (13 years ago)

Author:

pracine

Comment:

—

WKTRaster/SpecificationWorking03

@@ -174 +174 @@
   -Both rasters values when they are both nodata (nodatanodataexpr in the functions below)
 
-'''Details for 5) ST_MapAlgebraExpr(rast1 raster, band1 integer, rast2 raster, band2 integer, expression text, pixeltype text, extentexpr text, nodata1expr text, nodata2expr text, nodatanodataexpr text) -> raster'''
-
- '''Open Question:''' 
-      DZ: Should ST_MapAlgebra resample rasters internally, or produce a raster that can be processed by ST_Resample? If so, variant 1 and variant 3 can be removed, and all ST_MapAlgebra results can be processed through ST_Resample, like:
-  ST_Resample(ST_MapAlgebra(raster, [raster, ...] 'mathematical expression', integer), originx, originy, pixelsizex, pixelsizey)[[BR]]
-  ST_Resample(ST_MapAlgebra(raster, [raster, ...] 'mathematical expression', integer), rastergrid)
+ Open Question 1: 
+      DZ: Should ST_MapAlgebra resample the resulting rasters internally, or should we let the users resample it afterward with ST_Resample:
+  ST_Resample(ST_MapAlgebra(), originx, originy, pixelsizex, pixelsizey)[[BR]]
         PR: I think this would greatly contribute to simplify the API.
+
+ '''Details for 5) ST_MapAlgebraExpr(rast1 raster, band1 integer, rast2 raster, band2 integer, expression text, pixeltype text, extentexpr text, nodata1expr text, nodata2expr text, nodatanodataexpr text) -> raster'''
+
+
 
  See discussion in http://trac.osgeo.org/postgis/ticket/590