PostGIS WKT Raster Beta 0.2.4 Working Specifications

Quick Links

• WKT Raster Home Page
• Planning & Funding

• Beta 0.1.6 Working Specifications
• Beta 0.1.6 Documentation

• Working Specifications for Future Versions

---

Objective B02x - Being able to intersect vector and raster to produce raster.

ST_Intersects(raster, raster)
ST_AsRaster(geometry, pixelsize) → raster
ST_Intersection(geometry, raster, band) → raster

Rasterize the geometry as a new raster (ST_AsRaster(geometry, pixeltype, val, nodataval, raster)) and then copy only pixels for which both raster bands have a value. Optionally trim the raster to withvalue extent.

Variants

ST_Intersection(geometry, val, raster, band) → raster with the same metadatada as the provided raster. Non intersecting pixels are filled with nodata values.

ST_Intersection(geometry, val, raster, band, “TRIM”) → raster with the same metadatada as the provided raster but the extent is reduced to the geometry extent. Non intersecting pixels are filled with nodata values.

---

Objective B02x - Being able to use "group by" to accumulate tiles to form a new raster.

ST_Union(raster|geometry, raster|geometry, ‘raster’|’geometry’) → raster/geometry
ST_Accum(raster set|geometry set, ‘raster’|’geometry’) → raster/geometry

---

Objective B02x - Being able to set and get the skew of a raster in terms of rotation.

ST_SetRotation(raster, angle)

Set the rotation of the raster. This method actually derive values for pixelsizex, pixelsizey, skewx and skewy based on the provided rotation angle.

Open Question:

PR: The angle should be provided in radian or in degree?

ST_Rotation(raster) → float64

Return the georeference's rotation angle in (degree or radiant?) derived from the pixel size and the skew.

PR: I think getting the rotation get no sence since the result of pixelsizes and skew is not necessarily a rotation. It make sence to set it though.