Changes between Version 46 and Version 47 of GeoDjangoInstall

Timestamp:

Aug 16, 2008, 1:24:49 PM (16 years ago)

Author:

springmeyer

Comment:

--

GeoDjangoInstall

@@ -63 +63 @@
 }}}
 
-'''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` for linux or `.dylib` file for mac).
  * You should also confirm at this time (if running linux) that the GEOS lib dir, likely `/usr/local/lib` is within `/etc/ld.so.conf`, then run:
 {{{
@@ -185 +185 @@
 '''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:
+Because !GeoDjango uses a native `ctypes` API to access OGR (Vector shape library) and OSR (Spatial reference library) 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`)