[postgis-devel] [PostGIS] #590: [raster] Two rasters version of ST_MapAlgebra

[PostGIS]

#590: [raster] Two rasters version of ST_MapAlgebra
----------------------------+-----------------------------------------------
 Reporter:  pracine         |       Owner:  dustymugs    
     Type:  task            |      Status:  assigned     
 Priority:  critical        |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by pracine):

 Replying to [comment:12 robe]:
 > I concur with Bborie.  We have way too many parameters for things
 already.
 >
 > Sandro was complaining about his finger getting tired what is with all
 these permutations.  Weren't you Sandro?  We've already taken 3 keystrokes
 away from him with our ST_ - do we need to torture him any more?

 We have to understand here that rasters have much more internal properties
 (pixeltype, nodata value, take nodata value into account or not) that we
 often WANT to be able to set than geometries. There are also many ways to
 set the alignment of the new raster. This is why we end up with many
 variants. I see two solutions to this:

 1) We should systematically use DEFAULT. Most functions should be revised
 to see when variant can be removed by using DEFAULT. However from what I
 understood, using DEFAULT sometimes constraint your flexibility over the
 order of the parameters (DEFAULT parameters have to last).

 2) We should have a "parameter order policy" respected by every functions.
 We could explain this policy only once in the doc and expect every
 function to follow this policy.

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/590#comment:14>
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.