[postgis-devel] [PostGIS] #552: [wktraster] ST_SetValue is changing the raster

PostGIS trac at osgeo.org
Wed Jul 28 07:10:06 PDT 2010


#552: [wktraster] ST_SetValue is changing the raster
-----------------------+----------------------------------------------------
 Reporter:  robe       |       Owner:  pracine        
     Type:  defect     |      Status:  new            
 Priority:  medium     |   Milestone:  WKTRaster 0.1.6
Component:  wktraster  |     Version:  1.5.X          
 Keywords:             |  
-----------------------+----------------------------------------------------

Comment(by pracine):

 1) Could you do this to demonstrate that the stored raster was actually
 edited:

 SELECT ST_Value(rast, ST_Point(3427927.75, 5793243.95)) As val FROM
 dummy_rast

 then:

 SELECT ST_Value(ST_SetValue(rast, ST_Point(3427927.75, 5793243.95),50),
 ST_Point(3427927.75, 5793243.95)) As val FROM dummy_rast

 and then:

 SELECT ST_Value(rast, ST_Point(3427927.75, 5793243.95)) As val FROM
 dummy_rast

 2) Could you do this:

 SELECT ST_BandPixelType(rast) FROM dummy_rast

 I think you got twice the same result because the pixel value was actually
 not set because 50 is out of the possible value range for this band. Let
 see...

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


More information about the postgis-devel mailing list