Changes between Version 27 and Version 28 of GeoDjangoInstall

Timestamp:

Dec 27, 2007, 4:56:44 PM (17 years ago)

Author:

jbronn

Comment:

Updated installation instructions for PostGIS 1.3.2 and GDAL for 1.5.0. Documented required and recommended versions for GDAL , PROJ, and GEOS.

GeoDjangoInstall

@@ -18 +18 @@
 === Python & PostgreSQL ===
  * '''Python'''
-   * ''Required:'' Python 2.4 is required because of heavy use of 2.4 decorator syntax (''e.g.'' `@property`).  The `ctypes` module needs to be installed as well.
+   * ''Required:'' Python 2.4 is required because of heavy use of 2.4 decorator syntax (e.g. `@property`).  The `ctypes` module needs to be installed as well.
    * ''Recommended:'' Python 2.5 is recommended because the `ctypes` module comes included.  [http://www.python.org/download/releases/2.5.1/ Python 2.5.1] is the current latest.
  * '''PostgreSQL'''
@@ -41 +41 @@
 
 === GEOS ===
-!GeoDjango uses the [http://geos.refractions.net/downloads/geos-3.0.0.tar.bz2 3.0.0] version of [http://geos.refractions.net/ GEOS], and is not compatible with the 2.x versions.  With the release of 3.0.0, support for the release candidate versions will be eventually deprecated due to differences in the way geometries are serialized to WKT and HEX, as well as compilation issues for OSX 10.5.  However, the RC4 libraries are still supported for the moment, though we urge users to migrate to the 3.0.0 release.
+ * ''Required'': GEOS v3.0.0RC4 and above (''not'' compatible with the 2.x versions).
+ * ''Recommended'': GEOS [http://geos.refractions.net/downloads/geos-3.0.0.tar.bz2 3.0.0] (support for the release candidate versions will be eventually deprecated due to differences in the way geometries are serialized to WKT and HEX, as well as compilation issues for OSX 10.5 -- we urge users to migrate to 3.0.0).
+
+[http://geos.refractions.net GEOS] is an open source C++ library for performing geometric operations, and powers !GeoDjango's "lazy" geometries.
 
 !GeoDjango has its own GEOS `ctypes` wrapper; you do ''not'' need to enable the existing GEOS Python bindings. The `ctypes` library comes standard with Python 2.5; if you run Python 2.4, `ctypes` may be [http://sourceforge.net/project/showfiles.php?group_id=71702&package_id=71318 downloaded here], and in Debian etch you may install the `python-ctypes` package.
@@ -62 +65 @@
 
 === PROJ.4 ===
-The latest [http://proj.maptools.org/ PROJ.4] version is [ftp://ftp.remotesensing.org/proj/proj-4.6.0.tar.gz 4.6.0].  !GeoDjango also works with version 4.5.0, but there is no reason to believe that previous versions (''e.g.'', 4.4.x, 4.3.x) will not work.
+ * ''Required'': 4.5.0  -- this is not a strict requirement, !GeoDjango has been tested with 4.5.0, but there is no reason to believe that previous versions (e.g., 4.4.x, 4.3.x) will not work.
+ * ''Recommended'': [ftp://ftp.remotesensing.org/proj/proj-4.6.0.tar.gz 4.6.0] (the current latest).
+
+[http://www.remotesensing.org/proj/ PROJ.4] is a library for converting geospatial data to different coordinate reference systems.
 
 First, download PROJ.4 from the remotesensing website, and untar the source archive:
@@ -88 +94 @@
 === PostGIS ===
  * ''Required'':  PostGIS ~~v1.1.0~~ v1.2.1 and above.  1.1.0 support is currently pending, ''see'' #5498.
- * ''Recommended'': Postgis v1.3.1 [http://postgis.refractions.net/download/ PostGIS] (this is the [http://postgis.refractions.net/news/20070809/ latest version]).
- * First build & install PostGIS. 
+ * ''Recommended'': [http://postgis.refractions.net PostGIS] [http://postgis.refractions.net/download/postgis-1.3.2.tar.gz v1.3.2] (this is the current [http://postgis.refractions.net/news/20071201/ latest version]).
+
+First, download PostGIS, and untar the archive:
+{{{
+$ wget http://postgis.refractions.net/download/postgis-1.3.2.tar.gz
+$ tar xzf postgis-1.3.2.tar.gz
+$ cd postgis-1.3.2
+}}}
+
+Run the `configure` script enabling GEOS and PROJ support, `make`, and install. 
 {{{
 $ ./configure --with-geos --with-proj
@@ -96 +110 @@
 }}}
    * Note: the `flex` package maybe required for PostGIS compilation on Debian distributions and may be installed with the command: `apt-get install flex`
- * Next, create a role and database for your application, and allow it to access PostGIS functionality.  PostGIS SQL files are installed in the PostgreSQL share directory (`/usr/postgres/8.2/share` in the example below; use the `pg_config --sharedir` command to determine this directory on your system).
+
+Next, create a role and database for your application, and allow it to access PostGIS functionality.  PostGIS SQL files are installed in the PostgreSQL share directory (`/usr/postgres/8.2/share` in the example below; use the `pg_config --sharedir` command to determine this directory on your system).
 {{{
 # su - postgres
@@ -111 +126 @@
  * Note: if you experience errors about not finding libraries, you may need to adjust your `LD_LIBRARY_PATH` (which may be configured system-wide by editing `/etc/ld.so.conf` and running `ldconfig`)(Hint: Most of the times the libraries you are looking for are in '/usr/local/lib').  Sometimes the errors are too many and not descriptive (i.e. operation aborted), in that cases use the '-s' switch on psql to debug step by step. On Solaris platforms use the `crle` utility to configure the runtime linking environment.
 
- * Finally, update your {{{settings.py}}} to reflect the name and user for the spatially enabled database.  So far, we only plan to support the psycopg2 backend, thus: {{{DATABASE_ENGINE='postgresql_psycopg2'}}}.
+Finally, update your `settings.py` to reflect the name and user for the spatially enabled database (thus far, we only plan to support the `psycopg2` backend for PostgreSQL):
+{{{
+DATABASE_ENGINE='postgresql_psycopg2'
+DATABASE_NAME='<db_name>'
+DATABASE_USER='<user>'
+}}}
 
 === GDAL ===
- * ''Highly Recommended'': Some features (''e.g.'', a large number of {{{SpatialRefSys}}} model routines) require GDAL, but it is not necessary for core functionality like spatial queries.  
- * GDAL/OGR includes useful for coordinate transformations and reading/writing ''both'' vector (''e.g.'', SHP) and raster (''e.g.'', GeoTIFF) geographic data.
-   * For example, the following command will convert your SHP file into [http://en.wikipedia.org/wiki/WGS84 WGS84] (standard lat/lon).  Then you can import directly into your database using `shp2pgsql` (utility from PostGIS):
-{{{
-ogr2ogr -t_srs WGS84 output.shp input.shp
-}}}
- * Latest [http://trac.osgeo.org/gdal/wiki/DownloadSource GDAL] version is 1.4.2.  Configure with GEOS then make (use {{{gmake}}} on Solaris platforms) and install:
+ * ''Required'': GDAL versions 1.4.0 and above (!GeoDjango has not been tested with the 1.3.x series).
+ * ''Recommended'': GDAL version 1.5.0.
+
+GDAL/OGR is an excellent open source geospatial library that support features such as coordinate transformations and reading/writing ''both'' vector (e.g., SHP) and raster (e.g., GeoTIFF) geographic data -- however, !GeoDjango does not yet support GDAL's raster capabilities.  Installation of GDAL is ''highly recommended'' because some features (e.g., a large number of `SpatialRefSys` model routines and the `LayerMapping` utility) require GDAL capabilities; however GDAL is not required for core functionality like spatial queries.
+  
+First, download the latest [http://trac.osgeo.org/gdal/wiki/DownloadSource GDAL] version (currently [http://download.osgeo.org/gdal/gdal-1.5.0.tar.gz 1.5.0]), and untar the archive:
+{{{
+$ wget http://download.osgeo.org/gdal/gdal-1.5.0.tar.gz
+$ tar xzf gdal-1.5.0.tar.gz
+$ cd gdal-1.5.0
+}}}
+
+Configure with GEOS support, run `make` (use `gmake` on Solaris platforms) and install:
 {{{
 $ ./configure --with-geos
@@ -126 +152 @@
 # make install
 }}}
- * '''Note:''' The path to the GDAL library may be manually specified by setting `GDAL_LIBRARY_PATH` in your settings with the full path to the GDAL library (e.g., the `.so` or `.dylib` file).
- * !GeoDjango uses a native `ctypes` API to access OGR and OSR capabilities, there is no need configure the GDAL Python bindings.  If you still want to use the GDAL Python API for your own applications, then use the following configuration flags:
-   * `--with-python` `--without-ngpython`: the deprecated, but stable API.
-   * `--without-python` `--with-ngpython`: the "next-generation" SWIG-based bindings -- used to problematic for Python 2.5 users, but the GDAL team has solved a lot of these issues in 1.4.2.
+
+'''Note:''' The path to the GDAL library may be manually specified by setting `GDAL_LIBRARY_PATH` in your settings with the full path to the GDAL library (e.g., the `.so` or `.dylib` file).
+
+Because !GeoDjango uses a native `ctypes` API to access OGR and OSR capabilities, there is no need configure the GDAL Python bindings.  If you still want to use the GDAL Python API for your own applications, then use the following configuration flags:
+   * `--with-python`: Enables the GDAL Python bindings (all GDAL modules in `osgeo` namespace)
+   * `--with-ogpython`: The "old-generation" bindings (separate modules, e.g., `ogr` and `osr`)
    * ''See generally'' [http://trac.osgeo.org/gdal/wiki/GdalOgrInPython GDAL/OGR In Python] on the GDAL trac wiki.
 
@@ -140 +168 @@
 === Introduction ===
 
-These instructions will cover using binary packages to install !GeoDjango on Windows 2000/XP platforms.  Compiling prerequisite packages (''e.g.'', GEOS) from source on Windows is beyond the scope of this documentation, as it assumes the use of community-built binary installers.
+These instructions will cover using binary packages to install !GeoDjango on Windows 2000/XP platforms.  Compiling prerequisite packages (e.g., GEOS) from source on Windows is beyond the scope of this documentation, as it assumes the use of community-built binary installers.
 
 That said, here are some additional program recommendations that, while not required, make your Python experience in Windows less painful:
@@ -182 +210 @@
 === GEOS ===
 
-After PostGIS has installed, copy the GEOS (`libgeos-3-0-0rc4.dll`, `libgeos_c-1.dll`), and PROJ (`libproj.dll`) libraries from `C:\Program Files\PostgreSQL\8.2\bin` (or wherever you installed PostgreSQL) to a location accessible to the Python interpreter (''e.g.'', `C:\Python25\DLLs`, or `C:\Python25`).
+After PostGIS has installed, copy the GEOS (`libgeos-3-0-0rc4.dll`, `libgeos_c-1.dll`), and PROJ (`libproj.dll`) libraries from `C:\Program Files\PostgreSQL\8.2\bin` (or wherever you installed PostgreSQL) to a location accessible to the Python interpreter (e.g., `C:\Python25\DLLs`, or `C:\Python25`).
 
 '''Note:''' The path to the GEOS library may be manually specified by setting `GEOS_LIBRARY_PATH` in your settings with the full path of the DLL.