[postgis-tickets] [PostGIS] #2280: [raster] ST_Summary(raster)

[PostGIS]

#2280: [raster] ST_Summary(raster)
-------------------------+--------------------------------------------------
 Reporter:  strk         |       Owner:  dustymugs    
     Type:  enhancement  |      Status:  assigned     
 Priority:  medium       |   Milestone:  PostGIS 2.1.0
Component:  raster       |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------

Comment(by pracine):

 The question now is: Is what strk looking for fulfilled by
 ST_SummaryStats? If yes why creating a new function? I'm wondering if it's
 not the ST_Summary result that should become more like the one provided by
 ST_SummaryStats: a multiple, typed, column result splittable on many
 columns with the "(result).*" syntax. What is the need for this verbose,
 ugly, human-only readable result? Seems to me that a result like the one
 provided by ST_SummaryStat is much more useful for any subsequent
 treatment (human or machine).

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