Changes between Version 117 and Version 118 of WKTRaster/SpecificationWorking03


Ignore:
Timestamp:
06/13/11 15:32:47 (13 years ago)
Author:
pracine
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • WKTRaster/SpecificationWorking03

    v117 v118  
    174174  -Both rasters values when they are both nodata (nodatanodataexpr in the functions below)
    175175
    176 '''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'''
    177 
    178  '''Open Question:'''
    179       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:
    180   ST_Resample(ST_MapAlgebra(raster, [raster, ...] 'mathematical expression', integer), originx, originy, pixelsizex, pixelsizey)[[BR]]
    181   ST_Resample(ST_MapAlgebra(raster, [raster, ...] 'mathematical expression', integer), rastergrid)
     176 Open Question 1:
     177      DZ: Should ST_MapAlgebra resample the resulting rasters internally, or should we let the users resample it afterward with ST_Resample:
     178  ST_Resample(ST_MapAlgebra(), originx, originy, pixelsizex, pixelsizey)[[BR]]
    182179        PR: I think this would greatly contribute to simplify the API.
     180
     181 '''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'''
     182
     183
    183184
    184185 See discussion in http://trac.osgeo.org/postgis/ticket/590