[postgis-devel] [PostGIS] #1364: [raster] Make ST_Union a c-implementation and also handle multiple bands

[PostGIS]

#1364: [raster] Make ST_Union a c-implementation and also handle multiple bands
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  pracine              
     Type:  task            |      Status:  new                  
 Priority:  medium          |   Milestone:  PostGIS Raster Future
Component:  postgis raster  |     Version:  trunk                
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by robe):

 No all permutations as far as I can tell assumes the first band is what
 you want to work with.  Actually I haven't tested his other permutations.
 i was mostly testing with ST_Union(rast) and ST_Union(rast, p_expression)
 -- the first just defaults to 'LAST' I think.

 I'm almost tempted to cut the rest out and just leave maybe two since I
 think the most common use case for ST_Union is going to be stitching back
 your chunked rasters based on a spatial filter or grouping which is pretty
 much satisfied by the first two.  Then leave the other permutations up for
 discussion.  I don't think Pierre would like me stripping out 5 of his
 functions (which of course is more like 20 functions).  If I keep all 7, I
 think I can do it still without introducing the rastexpr and cutting out
 most of his various permutations of state functions.  So it will still be
 a savings of about 10 functions.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1364#comment:3>
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.