[postgis-devel] Raster todo list

[Bryce L Nordgren]

On Thu, Jun 16, 2011 at 9:19 PM, dustymugs <dustymugs at gmail.com> wrote:



> So in the end you have a very flexible Mapalgebra working on two rasters
>> helping you to implement a bunch of other raster processes and optimized for
>> the very useful case of doing Clips and Unions. In bonus you get some
>> editing functions like ST_SetValues very usefull to implement who knows
>> what...
>>
>
I'm thinking of taking incremental steps rather than jumping in all the way
> for a two raster ST_MapAlgebra, as I suspect that this will take significant
> amount of time to implement correctly.  I can see that ST_Clip, ST_Collect,
> ST_Union will all lead to ST_MapAlgebra but having milestones allows more
> functionality to be delivered and consumed in a shorter time-frame.
>

I completely agree, and actually I think the structure of the available
functions should reflect this. For instance, rather than have many thin
wrappers over a single huge do-it-all function like MapAlgebra, I'd prefer
to build a complex function (MapAlgebra) from simpler ones
(ST_Intersection).

BTW: Bborie, I have been told that we may have some GDAL code lying around
the building which could help out with ST_Clip (or ST_Intersection(raster,
geometry)).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20110616/a877947f/attachment.html>