[postgis-devel] [PostGIS] #1212: [raster]: st_intersects signature change - documentation out of synch
PostGIS
trac at osgeo.org
Thu Sep 29 07:40:25 PDT 2011
#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:22 dustymugs]:
> Replying to [comment:19 pracine]:
> > Another solution I thought about was to signal the fact that
everything was processed as raster by passing in a third argument 'RASTER'
saying "this must be processed as raster and must return a raster"...
> >
> > I think we will have to formulate two or three solutions and get
everybody to vote (Jorge, David, Mateusz, Sandro, Bryce?)... Damned open
source democracy :-)
>
> If you're going to get everyone to vote, I'd ask everyone on postgis-
devel as I'd like Paul, Mark and Sandro to have a say.
>
> Personally, I'm for keeping the seamless API at the expense of being
commutative and fully against additional function parameters.
I'm pretty sure overloading does not take the return type into account so
you will have to do something anyway otherwise ST_Intersection(raster,
geometry) -> raster will conflict with ST_Intersection(raster, geometry)
-> set of geomval. Right Robe?
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1212#comment:24>
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.
More information about the postgis-devel
mailing list