[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):

 Actually setting the nodata value with ST_SetBandNoDataValue on the first
 raster do not solve the first problem:

 {{{
 SELECT
 ST_BandNodataValue(ST_Intersection(ST_AddBand(ST_MakeEmptyRaster(48, 63,
 0, 0, 0.001, -0.001, 0, 0, 4269), '8BSI'::text, 0, 2),
                            ST_AddBand(ST_MakeEmptyRaster(48, 63, 0.1, 0.1,
 0.001, -0.001, 0, 0, 4269), '8BSI'::text, 0, NULL)::geometry,
                            'SECOND'))
 }}}

 do not set 2 as the nodata value... It select the default nodata value
 assigned to the rasterization of the geometry which is 0.

 so this seems like a real bug to me. Might be related to #1537 though.

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