Changes between Version 26 and Version 27 of GeoDjangoInstall

Timestamp:

Dec 25, 2007, 4:10:37 PM (17 years ago)

Author:

jbronn

Comment:

Updated GEOS and PROJ.4 installation instructions for new versions.

GeoDjangoInstall

@@ -29 +29 @@
 
 === Django ===
- * !GeoDjango exists in the `gis` branch from SVN:
+!GeoDjango exists in the `gis` branch from SVN:
 {{{
 $ svn co http://code.djangoproject.com/svn/django/branches/gis django_gis
@@ -35 +35 @@
 }}}
 
- * To detect the correct `site-packages` directory, the following command may be used:
+To detect the correct `site-packages` directory, the following command may be used:
 {{{
 $ python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"
@@ -41 +41 @@
 
 === GEOS ===
- * We have been developing using [http://geos.refractions.net/ GEOS] 3.0.0RC4, and have not tested using GEOS 2.x.  Despite the "RC" nomenclature, 3.0.0RC4 is quite stable, and will be renamed to 3.0.0 after FOSS4G.
-   * ''See'' Mateusz Loskot (GEOS lead developer), [http://lists.refractions.net/pipermail/geos-devel/2007-August/002936.html Note about GEOS 3.0.0 release].
- * !GeoDjango has its own GEOS `ctypes` wrapper; you do ''not'' need to enable the existing GEOS Python bindings.
-   * `ctypes` 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], but in Debian etch you may install the `python-ctypes` package.
- * If you are running Mac OS X 10.5 and using 3.0.0RC4 you will need to apply two quick hand-patches from [http://trac.osgeo.org/geos/ticket/162 here] and [http://lists.osgeo.org/pipermail/geos-devel/2007-November/003125.html here].
- * Configure, make, and install (`g++` is required for compilation)
-{{{
+!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.
+
+!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.
+
+First, download GEOS 3.0.0 from the refractions website and untar the source archive:
+{{{
+$ wget http://geos.refractions.net/downloads/geos-3.0.0.tar.bz2
+$ tar xjf geos-3.0.0.tar.bz2
+}}}
+
+Next, change into the directory where GEOS was unpacked, run the `configure` script, compile, and install:
+{{{
+$ cd geos-3.0.0
 $ ./configure
 $ make
 # make install
 }}}
- * '''Note:''' The path to the GEOS library may be manually specified by setting `GEOS_LIBRARY_PATH` in your settings with the full path to the GEOS library (e.g., the `.so` or `.dylib` file).
+
+'''Note:''' The path to the GEOS library may be manually specified by setting `GEOS_LIBRARY_PATH` in your settings with the full path to the GEOS library (e.g., the `.so` or `.dylib` file).
 
 === PROJ.4 ===
- * Latest [http://proj.maptools.org/ PROJ.4] version is 4.5.0.  We have no reason to believe that previous versions (''e.g.'', 4.4.x, 4.3.x) will not work.
- * First, download the PROJ [ftp://ftp.remotesensing.org/proj/proj-datumgrid-1.3.tar.gz datum shifting files].  These will come in handy for coordinate transformations when other programs (like Mapserver or Mapnik) are not able to cope with EPSG transformations (I learned the hard way). Untar/unzip these in the `nad` subdirectory of the PROJ source.  For example, if PROJ was unzipped in a directory named `proj`, then untar these files in `proj/nad`.  Do this '''before''' you do the configure/make/install dance.
-   * ''See'' [http://remotesensing.org/proj/faq.html PROJ FAQ]; ''see also'' [http://mapserver.gis.umn.edu/data2/wilma/mapserver-users/0301/msg00541.html Frank Warmerdam's reply to a Mapserver question].
- * Next, configure, make and install.
+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.
+
+First, download PROJ.4 from the remotesensing website, and untar the source archive:
+{{{
+$ wget ftp://ftp.remotesensing.org/proj/proj-4.6.0.tar.gz
+$ tar xzf proj-4.6.0.tar.gz
+}}}
+
+Next, download the PROJ.4 [ftp://ftp.remotesensing.org/proj/proj-datumgrid-1.3.tar.gz datum shifting files].  These will come in handy for coordinate transformations when other programs (like Mapserver or Mapnik) are not able to cope with EPSG transformations (I learned the hard way). Untar/unzip these in the `nad` subdirectory of the PROJ.4 source:
+{{{
+$ wget ftp://ftp.remotesensing.org/proj/proj-datumgrid-1.3.tar.gz
+$ cd proj-4.6.0/nad
+$ tar xzf ../../proj-datumgrid-1.3.tar.gz
+}}}
+Do this '''before''' you do the configure/make/install dance.
+ * ''See'' [http://remotesensing.org/proj/faq.html PROJ FAQ]; ''see also'' [http://mapserver.gis.umn.edu/data2/wilma/mapserver-users/0301/msg00541.html Frank Warmerdam's reply to a Mapserver question].
+
+Finally, configure, make and install:
 {{{
 $ ./configure