Find a file
Regina Obe 553cfbf9df fix some incorrect statements
git-svn-id: http://svn.osgeo.org/postgis/trunk@7186 b70326c6-7e19-0410-871a-916f4a2858ee
2011-05-18 11:08:40 +00:00
doc fix some incorrect statements 2011-05-18 11:08:40 +00:00
extras more optimizations 2011-05-11 14:59:55 +00:00
java - removed a few compile errors from the javadoc build 2009-04-28 17:04:30 +00:00
liblwgeom apply astyle 2011-05-13 08:46:38 +00:00
loader Do not error out if things are clean already 2011-04-14 10:38:22 +00:00
macros Now for sure. 2010-12-02 00:51:51 +00:00
postgis Nothing like experimenting with myself. Change ST_AsX3D to use default parameters and reduce down to one proto 2011-05-17 22:50:27 +00:00
raster Strip 'SELECT' feedback from regression test outputs 2011-05-17 15:58:34 +00:00
regress Strip 'SELECT' feedback from regression test outputs 2011-05-17 15:58:34 +00:00
topology topology.GetRingEdges() implementation and test. This is the first real user of next_left_edge/next_right_edge fields in the edge table. [RT-SIGTA] 2011-05-18 08:58:34 +00:00
utils Renaming of 3D functions, #817 2011-03-27 17:50:58 +00:00
.gitignore another generated file git-ignored 2011-05-05 08:32:36 +00:00
astyle.sh Check astyle version prior to do anything. 'blessed' version is 1.23. Related to #433 and postgis-devel discussions 2010-02-23 15:21:45 +00:00
authors.svn Add Bborie Park to development team lists. Assume Paul, you've given him SVN edit rights already. 2011-05-13 19:27:04 +00:00
autogen.sh Can't put backslash-commands in 'echo' parameter in a standard way 2009-09-30 14:10:25 +00:00
ChangeLog Some function renaming: lwgeom_typename => lwtype_name. The internal float/up/down functions get slightly better names. Make collection types re-sizable: added maxgeoms to all collections, and created lwcollection_add_lwgeom() function. Remove all *_add functions. Revized homogenize function to use the new _add_lwgeom and variants. 2010-03-16 03:13:33 +00:00
config.rpath Add config rpath 2010-12-09 16:10:01 +00:00
configure.ac Drop the unused BUILD_RASTER configure variable, fix use of the RASTER variable. Fixes bug #910. 2011-04-14 13:50:39 +00:00
COPYING Initial revision 2001-06-22 17:39:29 +00:00
CREDITS Add Bborie Park to development team lists. Assume Paul, you've given him SVN edit rights already. 2011-05-13 19:27:04 +00:00
GNUmakefile.in Have 'svnrebase' rule use an authors file rather than command. Lets older git do it (old git on the machine currently mirroring the codebase to github). 2011-04-13 08:08:46 +00:00
HOWTO_RELEASE Grammar fix. 2010-03-11 14:34:19 +00:00
install-sh Newer script (2009 rather than 2006). Hoping others' won't have it updated (my ./autogen.sh runs always update it) 2010-12-01 16:15:13 +00:00
LICENSE.TXT fix typo 2011-04-28 17:57:42 +00:00
make_dist.sh Add comment about postgis_comments.sql handling in 'clean' target of docs 2010-01-12 01:01:36 +00:00
Makefile Add rules to avoid the infinite loop took before ./configure is run 2010-12-22 18:24:27 +00:00
NEWS tabs to spaces 2011-04-08 10:58:53 +00:00
postgis_config.h.in Clean out scruft from my G_ phase and start attempting to separate _internal from external liblwgeom functions. 2010-10-31 02:31:34 +00:00
README.postgis README files updated with the new raster extension information. 2010-09-26 21:41:50 +00:00
README.raster Fixes on PostGIS Raster debug system. The raster core uses 2010-10-26 17:40:32 +00:00
spatial_ref_sys.sql Synch up to 1.5 version 2010-08-20 16:40:49 +00:00
STYLE forgot to save last change 2009-07-06 07:37:47 +00:00
TODO remove ST_Maxdistance from TODO and note that C-version is still TODO for ST_DumpPoints 2010-01-23 23:29:07 +00:00
Version.config Push version numbers on trunk forward to next release. 2010-02-04 17:43:47 +00:00

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


PostGIS 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.

raster/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 raster/rt_core/testapi.c and raster/rt_core/testwkb.c for 
example usage.

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

raster/doc/ contains technical references and RFC documents.

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

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

Some PostGIS Raster functions depends on GDAL library version 1.6.0 or
higher

PostGIS Raster loader dependes on Python GDAL bindings.

PostgreSQL interface depends on PostgreSQL version 8.3.5.


BUILD
-----

To build PostGIS with raster support:

    $ ./configure --with-raster
    $ make

Note that the 'configure' script isn't there if you fetched
the code from the SVN repository. In that case running ./autogen.sh
should create it for you.

Under MinGW you might have to add "--with-pgconfig=/usr/local/pgsql/bin/pg_config" if 
configure can't find your pgsql path.


PRE-INSTALL TEST
----------------

After a successful build, you can run:

    $ make raster-check

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

INSTALL
-------

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

    $ sudo make install

POST-INSTALL TEST
-----------------

You can run the post install tests against it:

    $ make raster-post-install-check

USE
---

In order to enable your databases to use the raster
functionalities you have to feed them the enabler script:

    $ psql -f raster/rt_pg/rtpostgis.sql $MYDB

Note that you must have loaded PostGIS in the database
in order for that to work (see PostGIS documentation
for how to do that).