[postgis-devel] [PostGIS] #1268: [raster] ST_MapAlgebraExpr for 2 rasters
PostGIS
trac at osgeo.org
Sun Nov 6 11:23:20 PST 2011
#1268: [raster] ST_MapAlgebraExpr for 2 rasters
----------------------------+-----------------------------------------------
Reporter: dustymugs | Owner: pracine
Type: task | Status: new
Priority: medium | Milestone: PostGIS 2.0.0
Component: postgis raster | Version: trunk
Keywords: |
----------------------------+-----------------------------------------------
Set of function variants for expression-based map-algebra for two rasters.
1. ST_MapAlgebraExpr(
rast1 raster, band1 integer,[[BR]]
rast2 raster, band2 integer,[[BR]]
expression text DEFAULT NULL,[[BR]]
pixeltype text DEFAULT NULL, extenttype text DEFAULT
'INTERSECTION',[[BR]]
nodata1expr text DEFAULT NULL, nodata2expr text DEFAULT NULL,
nodatanodataexpr text DEFAULT NULL
)
2. ST_MapAlgebraExpr(
rast1 raster,[[BR]]
rast2 raster,[[BR]]
expression text DEFAULT NULL,[[BR]]
pixeltype text DEFAULT NULL, extenttype text DEFAULT
'INTERSECTION',[[BR]]
nodata1expr text DEFAULT NULL, nodata2expr text DEFAULT NULL,
nodatanodataexpr text DEFAULT NULL
)
Should we consider a different function name? Something like
ST_MapAlgebra2Expr? Also, is there any reason why we have all the
ST_MapAgebraXXX except for distinguishing the type of MapAlgebra? I think
there isn't any issue with calling all of the ST_MapAlgebraXXX functions
ST_MapAlgebra due to the different signatures.
The code I've written for this function can definitely be modularized so
that there are separate parts, some of which will be done for
ST_MapAlgebraFct of 2 raster.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1268>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-devel
mailing list