[postgis-users] Basic postgis raster questions

[Pierre Racine]

An of course: ST_Union()... But if we get an efficient ST_MapAlgebra(raster, raster) I'll do it for you in one day :-)

> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net [mailto:postgis-users-
> bounces at postgis.refractions.net] On Behalf Of Pierre Racine
> Sent: Wednesday, June 15, 2011 3:49 PM
> To: PostGIS Users Discussion
> Subject: Re: [postgis-users] Basic postgis raster questions
> 
> I totally agree but a wrapper would be convenient for people not familiar with
> intersection operations on raster. Most are familiar with vector/vector
> intersections on but not with raster/raster ones. So let's inverse 4) and 5) in my
> previous mail.
> 
> I think the only real major missing pieces are:
> 
> 1) ST_AsRaster(geometry)
> 
> 2) ST_Resample(raster)
> 
> 3) ST_MapAlgebra(raster, raster)
> 
> And then the things we can not do with them.
> 
> Pierre
> 
> > -----Original Message-----
> > From: postgis-users-bounces at postgis.refractions.net
> > [mailto:postgis-users- bounces at postgis.refractions.net] On Behalf Of
> > Bryce L Nordgren
> > Sent: Wednesday, June 15, 2011 3:38 PM
> > To: PostGIS Users Discussion
> > Subject: Re: [postgis-users] Basic postgis raster questions
> >
> >
> >
> > postgis-users-bounces at postgis.refractions.net wrote on 06/15/2011
> > 07:02:46
> > PM:
> >
> > > > 4. ST_Clip(raster, geometry)
> >
> > If ST_Intersection(raster, geometry) returns a raster having the
> > original pixel values inside the geometry, and nodata outside the
> > geometry, I'm not sure I see the need for a separate "clip" function.
> Semantically and mathematically, "clip"
> > is "intersection": area common to both arguments.
> >
> > Bryce
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users