mirror of
https://github.com/django/django.git
synced 2025-10-24 06:06:09 +00:00
Refs #36485 -- Rewrapped docs to 79 columns line length.
Lines in the docs files were manually adjusted to conform to the 79 columns limit per line (plus newline), improving readability and consistency across the content.
This commit is contained in:
David Smith
nessita
@@ -145,10 +145,11 @@ When GeoDjango can't find GEOS, this error is raised:
|
||||
|
||||
ImportError: Could not find the GEOS library (tried "geos_c"). Try setting GEOS_LIBRARY_PATH in your settings.
|
||||
|
||||
The most common solution is to properly configure your :ref:`libsettings` *or* set
|
||||
:ref:`geoslibrarypath` in your settings.
|
||||
The most common solution is to properly configure your :ref:`libsettings` *or*
|
||||
set :ref:`geoslibrarypath` in your settings.
|
||||
|
||||
If using a binary package of GEOS (e.g., on Ubuntu), you may need to :ref:`binutils`.
|
||||
If using a binary package of GEOS (e.g., on Ubuntu), you may need to
|
||||
:ref:`binutils`.
|
||||
|
||||
.. _geoslibrarypath:
|
||||
|
||||
@@ -169,7 +170,8 @@ GEOS C library. For example:
|
||||
The setting must be the *full* path to the **C** shared library; in
|
||||
other words you want to use ``libgeos_c.so``, not ``libgeos.so``.
|
||||
|
||||
See also :ref:`My logs are filled with GEOS-related errors <geos-exceptions-in-logfile>`.
|
||||
See also :ref:`My logs are filled with GEOS-related errors
|
||||
<geos-exceptions-in-logfile>`.
|
||||
|
||||
.. _proj4:
|
||||
|
||||
@@ -192,8 +194,8 @@ PROJ < 7.x) [#]_:
|
||||
|
||||
$ wget https://download.osgeo.org/proj/proj-data-X.Y.tar.gz
|
||||
|
||||
Next, untar the source code archive, and extract the datum shifting files in the
|
||||
``data`` subdirectory. This must be done *prior* to configuration:
|
||||
Next, untar the source code archive, and extract the datum shifting files in
|
||||
the ``data`` subdirectory. This must be done *prior* to configuration:
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
|
||||
@@ -19,11 +19,12 @@ instructions are available for:
|
||||
|
||||
.. admonition:: Use the Source
|
||||
|
||||
Because GeoDjango takes advantage of the latest in the open source geospatial
|
||||
software technology, recent versions of the libraries are necessary.
|
||||
If binary packages aren't available for your platform, installation from
|
||||
source may be required. When compiling the libraries from source, please
|
||||
follow the directions closely, especially if you're a beginner.
|
||||
Because GeoDjango takes advantage of the latest in the open source
|
||||
geospatial software technology, recent versions of the libraries are
|
||||
necessary. If binary packages aren't available for your platform,
|
||||
installation from source may be required. When compiling the libraries from
|
||||
source, please follow the directions closely, especially if you're a
|
||||
beginner.
|
||||
|
||||
Requirements
|
||||
============
|
||||
@@ -99,7 +100,8 @@ Add ``django.contrib.gis`` to :setting:`INSTALLED_APPS`
|
||||
Like other Django contrib applications, you will *only* need to add
|
||||
:mod:`django.contrib.gis` to :setting:`INSTALLED_APPS` in your settings.
|
||||
This is so that the ``gis`` templates can be located -- if not done, then
|
||||
features such as the geographic admin or KML sitemaps will not function properly.
|
||||
features such as the geographic admin or KML sitemaps will not function
|
||||
properly.
|
||||
|
||||
Troubleshooting
|
||||
===============
|
||||
@@ -145,10 +147,11 @@ could place the following in their bash profile:
|
||||
Setting system library path
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
On GNU/Linux systems, there is typically a file in ``/etc/ld.so.conf``, which may include
|
||||
additional paths from files in another directory, such as ``/etc/ld.so.conf.d``.
|
||||
As the root user, add the custom library path (like ``/usr/local/lib``) on a
|
||||
new line in ``ld.so.conf``. This is *one* example of how to do so:
|
||||
On GNU/Linux systems, there is typically a file in ``/etc/ld.so.conf``, which
|
||||
may include additional paths from files in another directory, such as
|
||||
``/etc/ld.so.conf.d``. As the root user, add the custom library path (like
|
||||
``/usr/local/lib``) on a new line in ``ld.so.conf``. This is *one* example of
|
||||
how to do so:
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
@@ -174,10 +177,11 @@ module) to discover libraries. The ``find_library`` routine uses a program
|
||||
called ``objdump`` (part of the ``binutils`` package) to verify a shared
|
||||
library on GNU/Linux systems. Thus, if ``binutils`` is not installed on your
|
||||
Linux system then Python's ctypes may not be able to find your library even if
|
||||
your library path is set correctly and geospatial libraries were built perfectly.
|
||||
your library path is set correctly and geospatial libraries were built
|
||||
perfectly.
|
||||
|
||||
The ``binutils`` package may be installed on Debian and Ubuntu systems using the
|
||||
following command:
|
||||
The ``binutils`` package may be installed on Debian and Ubuntu systems using
|
||||
the following command:
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
@@ -279,9 +283,10 @@ __ https://brew.sh/
|
||||
Fink
|
||||
^^^^
|
||||
|
||||
`Kurt Schwehr`__ has been gracious enough to create GeoDjango packages for users
|
||||
of the `Fink`__ package system. `Different packages are available`__ (starting
|
||||
with ``django-gis``), depending on which version of Python you want to use.
|
||||
`Kurt Schwehr`__ has been gracious enough to create GeoDjango packages for
|
||||
users of the `Fink`__ package system. `Different packages are available`__
|
||||
(starting with ``django-gis``), depending on which version of Python you want
|
||||
to use.
|
||||
|
||||
__ https://schwehr.blogspot.com/
|
||||
__ https://www.finkproject.org/
|
||||
|
||||
@@ -39,8 +39,8 @@ command line interface and enter the following query:
|
||||
|
||||
sqlite> CREATE VIRTUAL TABLE testrtree USING rtree(id,minX,maxX,minY,maxY);
|
||||
|
||||
If you obtain an error, you will have to recompile SQLite from source. Otherwise,
|
||||
skip this section.
|
||||
If you obtain an error, you will have to recompile SQLite from source.
|
||||
Otherwise, skip this section.
|
||||
|
||||
To install from sources, download the latest amalgamation source archive from
|
||||
the `SQLite download page`__, and extract:
|
||||
@@ -51,8 +51,9 @@ the `SQLite download page`__, and extract:
|
||||
$ unzip sqlite-amalgamation-XXX0000.zip
|
||||
$ cd sqlite-amalgamation-XXX0000
|
||||
|
||||
Next, run the ``configure`` script -- however the ``CFLAGS`` environment variable
|
||||
needs to be customized so that SQLite knows to build the R*Tree module:
|
||||
Next, run the ``configure`` script -- however the ``CFLAGS`` environment
|
||||
variable needs to be customized so that SQLite knows to build the R*Tree
|
||||
module:
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
|
||||
Reference in New Issue
Block a user