mirror of
https://github.com/django/django.git
synced 2025-08-04 10:59:45 +00:00
Dropped support for GDAL 1.6
This commit is contained in:
parent
c5d1df70a4
commit
41903d025a
5 changed files with 8 additions and 67 deletions
|
@ -12,7 +12,7 @@ Program Description Required
|
|||
======================== ==================================== ================================ ==========================
|
||||
:ref:`GEOS <ref-geos>` Geometry Engine Open Source Yes 3.4, 3.3, 3.2
|
||||
`PROJ.4`_ Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.8, 4.7, 4.6, 4.5, 4.4
|
||||
:ref:`GDAL <ref-gdal>` Geospatial Data Abstraction Library No (but, required for SQLite) 1.9, 1.8, 1.7, 1.6
|
||||
:ref:`GDAL <ref-gdal>` Geospatial Data Abstraction Library No (but, required for SQLite) 1.9, 1.8, 1.7
|
||||
:ref:`GeoIP <ref-geoip>` IP-based geolocation library No 1.4
|
||||
`PostGIS`__ Spatial extensions for PostgreSQL Yes (PostgreSQL only) 2.0, 1.5, 1.4, 1.3
|
||||
`SpatiaLite`__ Spatial extensions for SQLite Yes (SQLite only) 4.1, 4.0, 3.0, 2.4, 2.3
|
||||
|
@ -26,7 +26,6 @@ totally fine with GeoDjango. Your mileage may vary.
|
|||
GEOS 3.2.0 2009-12-14
|
||||
GEOS 3.3.0 2011-05-30
|
||||
GEOS 3.4.0 2013-08-11
|
||||
GDAL 1.6.0 2008-12-04
|
||||
GDAL 1.7.1 2010-02-08
|
||||
GDAL 1.8.0 2011-01-13
|
||||
GDAL 1.9.0 2012-01-03
|
||||
|
@ -263,34 +262,6 @@ the GDAL library. For example:
|
|||
|
||||
GDAL_LIBRARY_PATH = '/home/sue/local/lib/libgdal.so'
|
||||
|
||||
.. _gdaldata:
|
||||
|
||||
Can't find GDAL data files (``GDAL_DATA``)
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
When installed from source, GDAL versions 1.5.1 and below have an autoconf bug
|
||||
that places data in the wrong location. [#]_ This can lead to error messages
|
||||
like this:
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
ERROR 4: Unable to open EPSG support file gcs.csv.
|
||||
...
|
||||
OGRException: OGR failure.
|
||||
|
||||
The solution is to set the ``GDAL_DATA`` environment variable to the location of the
|
||||
GDAL data files before invoking Python (typically ``/usr/local/share``; use
|
||||
``gdal-config --datadir`` to find out). For example::
|
||||
|
||||
$ export GDAL_DATA=`gdal-config --datadir`
|
||||
$ python manage.py shell
|
||||
|
||||
If using Apache, you may need to add this environment variable to your configuration
|
||||
file:
|
||||
|
||||
.. code-block:: apache
|
||||
|
||||
SetEnv GDAL_DATA /usr/local/share
|
||||
|
||||
.. rubric:: Footnotes
|
||||
.. [#] The datum shifting files are needed for converting data to and from
|
||||
|
@ -302,5 +273,3 @@ file:
|
|||
problem caused by their absence later.
|
||||
.. [#] Specifically, GeoDjango provides support for the `OGR
|
||||
<http://gdal.org/ogr>`_ library, a component of GDAL.
|
||||
.. [#] See `GDAL ticket #2382 <http://trac.osgeo.org/gdal/ticket/2382>`_.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue