[postgis-devel] [PostGIS] #1212: [raster]: st_intersects signature change - documentation out of synch

[PostGIS]

#1212: [raster]: st_intersects signature change - documentation out of synch
----------------------------+-----------------------------------------------
 Reporter:  robe            |       Owner:  pracine      
     Type:  defect          |      Status:  new          
 Priority:  medium          |   Milestone:  PostGIS 2.0.0
Component:  postgis raster  |     Version:  trunk        
 Keywords:                  |  
----------------------------+-----------------------------------------------

Comment(by pracine):

 Replying to [comment:11 dustymugs]:
 > I like Regina's compromise of turning ST_Intersects(raster, raster, int,
 int) into ST_Intersects(raster, raster) with the integers assumed to be 1
 and 1.  This is consistent with other raster functions.

 Yes. This is the default. But what if I want to intersect band 2 of raster
 1 with band 3 of raster 2?

 At the beginning there was this discussion about forcing users to use
 ST_Band() to select a particular band... We choose to add a band parameter
 to every function instead. That would be a solution if there is no cost
 but what a change for just a couple of variants.

 I guess this is the first function taking two raster band. Right? This is
 why we are puzzled so much.

 On another side: Why is there two versions of _st_intersects(rast raster,
 geom geometry, nband integer DEFAULT NULL) in rtpostgis.sql.in.c?

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