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

 I don't believe you need to have a nodata parameter as the intersection
 isn't doing anything to the intersecting rasters' bands unless you use
 'OTHER' for the "returnband" parameter.

 returnband: can be FIRST, SECOND, BOTH, OTHER

 FIRST returns the band of rast1 in the intersecting extent. returning
 raster will have one band.
 SECOND returns the band of rast2 in the intersecting extent. returning
 raster will have one band.
 BOTH returns the bands of rast1 and rast2 in the intersection extent.
 returning raster will have two bands.
 OTHER returns the computed band based upon rast1 and rast2 in the
 intersecting extent. returning raster will have one band. If OTHER, must
 provide a regprocedure to otherfunc

 So, specifying a NODATA isn't useful as that attribute would be copied
 over from the source band's metadata.  If the source band's metadata
 doesn't have a NODATA, the output band shouldn't have a NODATA.

 I did just notice that the user doc for ST_Intersection is not complete.
 The section in the Working Specs is complete and correct though.

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