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 B02a - Being able to register TIFF and JPEG tiles as raster stored outside the database.

Mostly changes to raster2pgsql.exe and ST_RasterFromText().
ST_GetPath(raster, band) → string
ST_SetPath(raster, band, string)

---

Objective B02b - Being able to import JPEG rasters using raster2pgsql.exe.

Mostly changes to raster2pgsql.exe

---

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

ST_AsRaster(geometry, pixelsize) → raster
Changes to ST_Intersection

---

Objective B02d - 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 B02e - Being able to create on the fly and get data from registered (out-db) raster.

Mostly change to Core API functions rt_band_get_data using GDAL to read from external raster.
Add a ST_AddBand() SQL function
Allow then to create, in SQL, a new out-db raster and to load it into the database:

CREATE TABLE newIndbRastTable AS SELECT ST_AddBand(ST_NewRasterFromFile("c:/temp/myraster.tif"), "c:/temp/myraster.tif");

and to tile it in a new table using a new easy to implement pl/PgSQL function using ST_Clip. No more need of gdal2wktraster.py to load a raster.