test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Refs #24688, #27497 -- Corrected docs: distance's 'spheroid' option isn't PostGIS specific.

This commit is contained in:
Tim Graham 2017-01-06 07:55:00 -05:00 committed by GitHub
parent 72be3152d7
commit ad7f3c0b7b
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/ref/contrib/gis/geoquerysets.txt
View File

@ -596,11 +596,12 @@ and a distance value (either a number in units of the field, a
<ref/models/expressions>`). To pass a band index to the lookup, use a 3-tuple
where the second entry is the band index.
With PostGIS, on every distance lookup but :lookup:`dwithin`, an optional
element, ``'spheroid'``, may be included to tell GeoDjango to use the more
accurate spheroid distance calculation functions on fields with a geodetic
coordinate system (e.g., ``ST_Distance_Spheroid`` would be used instead of
``ST_Distance_Sphere``). The simpler ``ST_Distance`` function is used with
On every distance lookup except :lookup:`dwithin`, an optional element,
``'spheroid'``, may be included to use the more accurate spheroid distance
calculation functions on fields with a geodetic coordinate system.
On PostgreSQL, the ``'spheroid'`` option uses ``ST_Distance_Spheroid`` instead
of ``ST_Distance_Sphere``. The simpler ``ST_Distance`` function is used with
projected coordinate systems. Rasters are converted to geometries for spheroid
based lookups.
@ -608,6 +609,10 @@ based lookups.
The ability to pass an expression as the distance value was added.
.. versionadded:: 1.11
Support for the ``'spheroid'`` option on SQLite was added.
.. fieldlookup:: distance_gt
``distance_gt``