[postgis-devel] Another idea to speedup raster value editing

Pierre Racine Pierre.Racine at sbf.ulaval.ca
Wed Feb 1 09:27:24 PST 2012

> Yeah, but the step forward here is that the _value_ to burn-in would be
> embedded in the point-or-multipoint itself. Rather than burning a constant into
> the raster where the vector hits, you'd burn a value that the vector holds. For
> points it'd be straightforward, for lines might still do something smart like
> linearly interpolating, for polygons I can't imagine anything smart.

Yes. Nevertheless the logic is in ST_AsRaster(). The default behavior when not passing a value is to print the value '1'. The default behavior when passing a point or a multipoint could be to print the value of M. There could also be an option explicitly saying print 'M' or 'Z' if they exist.


More information about the postgis-devel mailing list