[postgis-devel] [PostGIS] #493: ST_DumpValues to Dump Pixel values

[PostGIS]

#493: ST_DumpValues to Dump Pixel values
-----------------------+----------------------------------------------------
 Reporter:  robe       |       Owner:  pracine         
     Type:  defect     |      Status:  new             
 Priority:  medium     |   Milestone:  WKTRaster Future
Component:  wktraster  |     Version:  trunk           
 Keywords:             |  
-----------------------+----------------------------------------------------
 This is just a suggestion, and will probably become less useful as we
 build out the other functions.

 I'm finding ST_Value to be the most useful function in the mix to build
 out all sorts of other plpgsql functions.  The problem is that the
 multiple calls is killing speed.

 One trivial reason making ST_Value slower than it should be is that echo
 NOTICE in there.  Can we take that out or do I have some level of
 debugging enabled that I don't know about?

 The other issue is the cost of going into the postgis raster layer. I
 think its the same issue with ran into with PostGIS why using ST_Dump was
 so much faster than doing the same thing with generate_series.

 So anyway just thought I would throw it out there as a suggestion.

 Now exploding out all values might be a bit too much -- so might want to
 add an x y range.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/493>
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.