[postgis-devel] [PostGIS] #985: [raster] ST_Count

[PostGIS]

#985: [raster] ST_Count
-----------------------------+----------------------------------------------
  Reporter:  dustymugs       |       Owner:  dustymugs    
      Type:  task            |      Status:  reopened     
  Priority:  medium          |   Milestone:  PostGIS 2.0.0
 Component:  postgis raster  |     Version:  trunk        
Resolution:                  |    Keywords:  history      
-----------------------------+----------------------------------------------

Comment(by pracine):

 Could not ST_Count be optimized to "ST_Height() * ST_Width()" when
 ST_BandNodataValue() = NULL in cases when we do not care about the other
 stats generated by st_summarystats()?

 A side question I have been wondering since a while: Right now, does:

 {{{
   SELECT ST_Sum(rast), ST_Mean(rast) FROM mytable
 }}}

 takes twice the time of (?):

 {{{
   SELECT (ss).sum, (ss).mean FROM (SELECT ST_SummaryStat(rast) ss FROM
 mytable) foo
 }}}


 Another one: Do we still want to conserve ST_MinMax instead of ST_Min and
 ST_Max?

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