[postgis-devel] [PostGIS] #1536: [raster] There should be an option for certain variants of ST_Intersection(raster, raster)

[PostGIS]

#1536: [raster] There should be an option for certain variants of
ST_Intersection(raster, raster)
---------------------+------------------------------------------------------
 Reporter:  pracine  |       Owner:  pracine      
     Type:  defect   |      Status:  new          
 Priority:  low      |   Milestone:  PostGIS 2.0.0
Component:  raster   |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by pracine):

 Another example involving the two raster version of ST_Intersection:

 {{{
 SELECT
 ST_BandNodataValue(ST_Intersection(ST_AddBand(ST_MakeEmptyRaster(48, 63,
 0, 0, 0.001, -0.001, 0, 0, 4269), '8BSI'::text, 0, NULL),
                                    ST_AddBand(ST_MakeEmptyRaster(48, 63,
 0.01, -0.01, 0.001, -0.001, 0, 0, 4269), '8BSI'::text, 1, NULL),
 'FIRST'));
 }}}

 the result of this is -128 meaning that the nodata value chosen must be
 equal to ST_MinPossibleValue('8BSI'). I have no way to change this other
 than by assigning a nodata value to the first raster before calling
 ST_Intersection(). Might be fair enough though...

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/1536#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.