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:50 -0400
commit6a2f8985c13e5524d397b48951d6de982544a71a (patch)
tree0331b3cf405e82d1cca2146d2bc7c1dafa2e5615 /docs
parent26221445df5855d189b2dc4dd76ff0a9f0bd77d0 (diff)
[1.6.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 01c5bd7edc..596aeed51a 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: