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

 So we are in agreement?
 The signatures will be

 change: ST_Intersects(rast1,nband1,rast2,nband2) ->
 ST_Intersects(rast1,rast2)
 Put back: ST_Intersects(rast1,nband1,rast2,nband2)

 This keeps consistency and avoids the situation where someone throws in an
 untyped NULL and we then get an ambiguous path like this:

 ST_Intersects(rast,NULL,NULL,2) ;

 I'm almost tempted to say just create a new function name -- call this
 RT_Intersects for raster space intersection (which means operation done in
 raster space)

 and RT_Intersects(raster,geometry)
 RT_Intersects(raster,raster)
 RT_Intersects(raster1,band1,raster2,band2)

 The issue I have with this:
 ST_Intersects(raster, geometry)

 ST_Intersects(geometry, raster)

 As Pierre pointed out is that it is no longer commutative and people will
 assume it is when clearly you are saying one is done in raster space and
 one is done in vector space.

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