Changes between Version 46 and Version 47 of GeoDjangoInstall


Ignore:
Timestamp:
08/16/2008 01:24:49 PM (7 years ago)
Author:
springmeyer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjangoInstall

    v46 v47  
    6363}}}
    6464
    65 '''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).
     65'''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).
    6666 * 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:
    6767{{{
     
    185185'''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). 
    186186
    187 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:
     187Because !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:
    188188   * `--with-python`: Enables the GDAL Python bindings (all GDAL modules in `osgeo` namespace)
    189189   * `--with-ogpython`: The "old-generation" bindings (separate modules, e.g., `ogr` and `osr`)
Back to Top