[postgis-devel] Another idea to speedup raster value editing
Pierre.Racine at sbf.ulaval.ca
Mon Feb 6 09:06:24 PST 2012
> This suggests a user visible API addition of
> ST_DumpRasterAsGeomval(rast raster, cell_pt geometry OUT, values array
How is this different from ST_DumpAsPolygons()? I agree that ST_DumpAsPolygonValues() would have been clearer...
> ST_LoadRasterFromGeomval(rast raster, t_name text, pt_col text default
> "cell_pt", values array)
> t_name = table name
> pt_col = name of column containing points
> values = array of column names containing values to load into raster.
How is this different from the planned ST_UnionToRaster()? What do you do when two or more points fall into the same pixel?
More information about the postgis-devel