PostGIS WKT Raster - Seamless operations between vector and raster layers
-------------------------------------------------------------------------
http://www.postgis.org/support/wiki/index.php?WKTRasterHomePage


WKT Raster's goal is to implement the RASTER type as much as possible
like the GEOMETRY type is implemented in PostGIS and to offer a single
set of overlay SQL functions (like ST_Intersects) operating seamlessly
on vector and raster coverages.

rt_core/ contains the primitives to deal with rasters in memory,
the function to serialize/deserialize both in-memory and on-disk
rasters, the functions to parse and output (hex)wkb.
You can see rt_core/testapi.c and rt_core/testwkb.c for example usage.

rt_pg/ contains postgresql-specific wrappers, and SQL code to define
the RASTER type.

REQUIREMENTS
------------

WKTRaster depends on liblwgeom, as found in postgis source
package as of SVN 2009-01 (latest 1.3.5 release won't work).

BUILD
-----

To build:

    $ ./configure --with-postgis-sources=/usr/src/postgis-svn
    $ make 

CHECK
-----

After a successful build, you can run:

    $ make check

It won't test postgresql interface, as that would require more setup
then a simple make check. See INSTALL for more info on how to test
that part.

INSTALL
-------

First you need to install the library to the postgresql library
directory. You do it by running:

    $ make install

Then you need to enable your database to use the new functions.
It is reccommended to use a test database at first:

    $ createdb test_wktraster
    $ createlang plpgsql test_wktraster
    $ psql -f rt_pg/rtpostgis.sql test_wktraster

Then you can run the IO tests against it:

    $ psql -f rt_pg/test/io.sql test_wktraster

The test succeeds if you get all 't' (true) values in last two
columns of the final query. The data is left on an rt_table
for use to further test.