geolibs.txt 8.0 KB

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