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

 I think a general rule should be: As soon as a function CAN produce nodata
 values (this is the case of ST_Intersection(raster, raster),
 ST_Intersection(raster, geometry) and ST_Clip(raster, geometry)) there
 should be a way to specify the selected nodata value in case the input
 raster do not have one defined.

 Otherwise we have to prepend ST_SetBandNodataValue() every time (if we do
 not want strange results in some cases).

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