* GDAL (Optional, Version 1.6.0 or higher)
- GDAL is required if you want to compile PostGIS with raster support.
-
- http://www.gdal.org/
-
-See README.raster for further information on how to compile PostGIS with
-Raster support.
+ GDAL (http://gdal.org) is *required* if you want to compile PostGIS
+ with raster support. To compile without raster support you
+ must ``./configure --without-raster``
CONFIGURATION
refuse to proceed. You can specify an alternative ``geos-config`` file using
the ``--with-geosconfig=/path/to/geos-config`` option.
+If GDAL cannot be found, configure will complain and refuse to proceed.
+You can either procede without raster support using ``--without-raster``
+or use ``--with-gdalconfig=/path/to/gdal-config`` option.
+
By default, both Topology and Raster extensions are enabled in ``./configure``.
If you want to compile PostGIS *without* Raster support, you must provide the
make
-See README.raster to know how to build PostGIS Raster extension.
-
TESTING
-------
failed. If you have any failure please file a bug report using the online bug
tracker: http://trac.osgeo.org/postgis/report/3
-See README.raster to know how to test PostGIS raster extension.
-
INSTALLATION
------------
You can change them using ``./configure`` switches. See CONFIGURATION section.
-See README.raster to know how to install PostGIS Raster extension.
-
CREATING NEW SPATIAL DATABASES
------------------------------
Your database should now be spatially enabled.
+ADDING RASTER SUPPORT TO A SPATIAL DATABASE
+-------------------------------------------
+
+To enable raster support you must first load the ``postgis.sql`` file.
+You can then load the ``rtpostgis.sql`` file.
+
+ psql -f postgis/rtpostgis.sql -d <your_database>
+
+
UPGRADING EXISTING SPATIAL DATABASES
------------------------------------
# [3] Restore the dump into your new database.
$ perl utils/postgis_restore.pl -v olddb.dump \
- 2> restore.log | psql newdb 2> errors.txt
+ 2> restore.log | psql newdb 2> errors.log
The ``spatial_ref_sys`` entries found in your dump will be restored, but they
will not override existing ones in ``spatial_ref_sys``. This is to ensure that
SELECT AddGeometryColumn('db', 'geotest', 'geopoint', 1, 'POINT', 2);
INSERT INTO geotest (id, name, geopoint)
- VALUES (1, 'Olympia', GeometryFromText('POINT(-122.90 46.97)', 1));
+ VALUES (1, 'Olympia', ST_GeomFromText('POINT(-122.90 46.97)', 1));
INSERT INTO geotest (id, name, geopoint)
- VALUES (2, 'Renton', GeometryFromText('POINT(-122.22 47.50)', 1));
+ VALUES (2, 'Renton', ST_GeomFromText('POINT(-122.22 47.50)', 1));
SELECT name, AsText(geopoint) FROM geotest;
index. This gathers statistics which the query planner uses to optimize index
usage.
-PostGIS Raster support
-~~~~~~~~~~~~~~~~~~~~~~
-
-See README.raster to know how to enable raster support on a spatially enabled
-database.
PostGIS Topology support
~~~~~~~~~~~~~~~~~~~~~~~~
+++ /dev/null
-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).
-
projects / postgis / commitdiff