summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMoayad Mardini <moayad.m@gmail.com>2014-05-19 16:02:42 +0300
committerTim Graham <timograham@gmail.com>2014-05-19 09:50:46 -0400
commit269291019ec2dddddd6dd3b9833a37e7b94944ab (patch)
treef0c0ddeca571730ed4c168dcdacf8cbd6cca303f /docs
parent0f84037e104d63ef341dcfa6a465bef4782fb8fb (diff)
[1.7.x] Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below
The paragraph was a copy of strictly_above. Backport of 2f43229c2f from master
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/contrib/gis/geoquerysets.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/ref/contrib/gis/geoquerysets.txt b/docs/ref/contrib/gis/geoquerysets.txt
index 0b1fee3bfe..957a0497af 100644
--- a/docs/ref/contrib/gis/geoquerysets.txt
+++ b/docs/ref/contrib/gis/geoquerysets.txt
@@ -492,16 +492,16 @@ strictly_below
*Availability*: PostGIS
-Tests if the geometry field's bounding box is strictly above the lookup
+Tests if the geometry field's bounding box is strictly below the lookup
geometry's bounding box.
Example::
- Zipcode.objects.filter(poly__strictly_above=geom)
+ Zipcode.objects.filter(poly__strictly_below=geom)
PostGIS equivalent::
- SELECT ... WHERE poly |>> geom
+ SELECT ... WHERE poly <<| geom
.. _distance-lookups: