geolibs.txt 8.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246
  1. ===============================
  2. Installing Geospatial libraries
  3. ===============================
  4. GeoDjango uses and/or provides interfaces for the following open source
  5. geospatial libraries:
  6. ======================== ==================================== ================================ ===================================
  7. Program Description Required Supported Versions
  8. ======================== ==================================== ================================ ===================================
  9. :doc:`GEOS <../geos>` Geometry Engine Open Source Yes 3.6, 3.5, 3.4
  10. `PROJ.4`_ Cartographic Projections library Yes (PostgreSQL and SQLite only) 4.9, 4.8, 4.7, 4.6, 4.5, 4.4
  11. :doc:`GDAL <../gdal>` Geospatial Data Abstraction Library Yes 2.3, 2.2, 2.1, 2.0, 1.11
  12. :doc:`GeoIP <../geoip2>` IP-based geolocation library No 2
  13. `PostGIS`__ Spatial extensions for PostgreSQL Yes (PostgreSQL only) 2.4, 2.3, 2.2, 2.1
  14. `SpatiaLite`__ Spatial extensions for SQLite Yes (SQLite only) 4.3, 4.2, 4.1
  15. ======================== ==================================== ================================ ===================================
  16. Note that older or more recent versions of these libraries *may* also work
  17. totally fine with GeoDjango. Your mileage may vary.
  18. ..
  19. Libs release dates:
  20. GEOS 3.4.0 2013-08-11
  21. GEOS 3.5.0 2015-08-15
  22. GEOS 3.6.0 2016-10-25
  23. GDAL 1.11.0 2014-04-25
  24. GDAL 2.0.0 2015-06
  25. GDAL 2.1.0 2016-04
  26. GDAL 2.2.0 2017-05
  27. GDAL 2.3.0 2018-05
  28. PostGIS 2.1.0 2013-08-17
  29. PostGIS 2.2.0 2015-10-17
  30. PostGIS 2.3.0 2016-09-26
  31. PostGIS 2.4.0 2017-09-30
  32. SpatiaLite 4.1.0 2013-06-04
  33. SpatiaLite 4.2.0 2014-07-25
  34. SpatiaLite 4.3.0 2015-09-07
  35. .. note::
  36. The GeoDjango interfaces to GEOS, GDAL, and GeoIP may be used
  37. independently of Django. In other words, no database or settings file
  38. required -- just import them as normal from :mod:`django.contrib.gis`.
  39. .. _PROJ.4: https://github.com/OSGeo/proj.4/wiki/
  40. __ https://postgis.net/
  41. __ https://www.gaia-gis.it/gaia-sins/
  42. On Debian/Ubuntu, you are advised to install the following packages which will
  43. install, directly or by dependency, the required geospatial libraries:
  44. .. code-block:: console
  45. $ sudo apt-get install binutils libproj-dev gdal-bin
  46. Optional packages to consider:
  47. * ``libgeoip1``: for :doc:`GeoIP <../geoip2>` support
  48. * ``python-gdal`` for GDAL's own Python bindings -- includes interfaces for raster manipulation
  49. Please also consult platform-specific instructions if you are on :ref:`macos`
  50. or :ref:`windows`.
  51. .. _build_from_source:
  52. Building from source
  53. ====================
  54. When installing from source on UNIX and GNU/Linux systems, please follow
  55. the installation instructions carefully, and install the libraries in the
  56. given order. If using MySQL or Oracle as the spatial database, only GEOS
  57. is required.
  58. .. note::
  59. On Linux platforms, it may be necessary to run the ``ldconfig`` command
  60. after installing each library. For example::
  61. $ sudo make install
  62. $ sudo ldconfig
  63. .. note::
  64. macOS users must install `Xcode`_ in order to compile software from source.
  65. .. _Xcode: https://developer.apple.com/xcode/
  66. .. _geosbuild:
  67. GEOS
  68. ----
  69. GEOS is a C++ library for performing geometric operations, and is the default
  70. internal geometry representation used by GeoDjango (it's behind the "lazy"
  71. geometries). Specifically, the C API library is called (e.g., ``libgeos_c.so``)
  72. directly from Python using ctypes.
  73. First, download GEOS from the GEOS website and untar the source archive::
  74. $ wget http://download.osgeo.org/geos/geos-X.Y.Z.tar.bz2
  75. $ tar xjf geos-X.Y.Z.tar.bz2
  76. Next, change into the directory where GEOS was unpacked, run the configure
  77. script, compile, and install::
  78. $ cd geos-X.Y.Z
  79. $ ./configure
  80. $ make
  81. $ sudo make install
  82. $ cd ..
  83. Troubleshooting
  84. ~~~~~~~~~~~~~~~
  85. Can't find GEOS library
  86. ^^^^^^^^^^^^^^^^^^^^^^^
  87. When GeoDjango can't find GEOS, this error is raised:
  88. .. code-block:: text
  89. ImportError: Could not find the GEOS library (tried "geos_c"). Try setting GEOS_LIBRARY_PATH in your settings.
  90. The most common solution is to properly configure your :ref:`libsettings` *or* set
  91. :ref:`geoslibrarypath` in your settings.
  92. If using a binary package of GEOS (e.g., on Ubuntu), you may need to :ref:`binutils`.
  93. .. _geoslibrarypath:
  94. ``GEOS_LIBRARY_PATH``
  95. ^^^^^^^^^^^^^^^^^^^^^
  96. If your GEOS library is in a non-standard location, or you don't want to
  97. modify the system's library path then the :setting:`GEOS_LIBRARY_PATH`
  98. setting may be added to your Django settings file with the full path to the
  99. GEOS C library. For example::
  100. GEOS_LIBRARY_PATH = '/home/bob/local/lib/libgeos_c.so'
  101. .. note::
  102. The setting must be the *full* path to the **C** shared library; in
  103. other words you want to use ``libgeos_c.so``, not ``libgeos.so``.
  104. See also :ref:`My logs are filled with GEOS-related errors <geos-exceptions-in-logfile>`.
  105. .. _proj4:
  106. PROJ.4
  107. ------
  108. `PROJ.4`_ is a library for converting geospatial data to different coordinate
  109. reference systems.
  110. First, download the PROJ.4 source code and datum shifting files [#]_::
  111. $ wget http://download.osgeo.org/proj/proj-X.Y.Z.tar.gz
  112. $ wget http://download.osgeo.org/proj/proj-datumgrid-X.Y.tar.gz
  113. Next, untar the source code archive, and extract the datum shifting files in the
  114. ``nad`` subdirectory. This must be done *prior* to configuration::
  115. $ tar xzf proj-X.Y.Z.tar.gz
  116. $ cd proj-X.Y.Z/nad
  117. $ tar xzf ../../proj-datumgrid-X.Y.tar.gz
  118. $ cd ..
  119. Finally, configure, make and install PROJ.4::
  120. $ ./configure
  121. $ make
  122. $ sudo make install
  123. $ cd ..
  124. .. _gdalbuild:
  125. GDAL
  126. ----
  127. `GDAL`__ is an excellent open source geospatial library that has support for
  128. reading most vector and raster spatial data formats. Currently, GeoDjango only
  129. supports :doc:`GDAL's vector data <../gdal>` capabilities [#]_.
  130. :ref:`geosbuild` and :ref:`proj4` should be installed prior to building GDAL.
  131. First download the latest GDAL release version and untar the archive::
  132. $ wget http://download.osgeo.org/gdal/X.Y.Z/gdal-X.Y.Z.tar.gz
  133. $ tar xzf gdal-X.Y.Z.tar.gz
  134. $ cd gdal-X.Y.Z
  135. Configure, make and install::
  136. $ ./configure
  137. $ make # Go get some coffee, this takes a while.
  138. $ sudo make install
  139. $ cd ..
  140. .. note::
  141. Because GeoDjango has its own Python interface, the preceding instructions
  142. do not build GDAL's own Python bindings. The bindings may be built by
  143. adding the ``--with-python`` flag when running ``configure``. See
  144. `GDAL/OGR In Python`__ for more information on GDAL's bindings.
  145. If you have any problems, please see the troubleshooting section below for
  146. suggestions and solutions.
  147. __ https://trac.osgeo.org/gdal/
  148. __ https://trac.osgeo.org/gdal/wiki/GdalOgrInPython
  149. .. _gdaltrouble:
  150. Troubleshooting
  151. ~~~~~~~~~~~~~~~
  152. Can't find GDAL library
  153. ^^^^^^^^^^^^^^^^^^^^^^^
  154. When GeoDjango can't find the GDAL library, configure your :ref:`libsettings`
  155. *or* set :ref:`gdallibrarypath` in your settings.
  156. .. _gdallibrarypath:
  157. ``GDAL_LIBRARY_PATH``
  158. ^^^^^^^^^^^^^^^^^^^^^
  159. If your GDAL library is in a non-standard location, or you don't want to
  160. modify the system's library path then the :setting:`GDAL_LIBRARY_PATH`
  161. setting may be added to your Django settings file with the full path to
  162. the GDAL library. For example::
  163. GDAL_LIBRARY_PATH = '/home/sue/local/lib/libgdal.so'
  164. .. rubric:: Footnotes
  165. .. [#] The datum shifting files are needed for converting data to and from
  166. certain projections.
  167. For example, the PROJ.4 string for the `Google projection (900913 or 3857)
  168. <http://spatialreference.org/ref/sr-org/6864/prj/>`_ requires the
  169. ``null`` grid file only included in the extra datum shifting files.
  170. It is easier to install the shifting files now, then to have debug a
  171. problem caused by their absence later.
  172. .. [#] Specifically, GeoDjango provides support for the `OGR
  173. <http://gdal.org/ogr_arch.html>`_ library, a component of GDAL.