From 1b1b58bc7b2917b203ee3eb3b9e8b3a1fafaee64 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Fri, 30 Jan 2015 20:23:23 +0100 Subject: Documented GeoQuerySet replacement by functions --- docs/ref/contrib/gis/tutorial.txt | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'docs/ref/contrib/gis/tutorial.txt') diff --git a/docs/ref/contrib/gis/tutorial.txt b/docs/ref/contrib/gis/tutorial.txt index ea78274781..977e059d4b 100644 --- a/docs/ref/contrib/gis/tutorial.txt +++ b/docs/ref/contrib/gis/tutorial.txt @@ -631,8 +631,8 @@ a ``contains`` lookup using the ``pnt_wkt`` as the parameter:: >>> qs [] -Here, you retrieved a ``GeoQuerySet`` with only one model: the border of -the United States (exactly what you would expect). +Here, you retrieved a ``QuerySet`` with only one model: the border of the +United States (exactly what you would expect). Similarly, you may also use a :doc:`GEOS geometry object `. Here, you can combine the ``intersects`` spatial lookup with the ``get`` @@ -718,8 +718,12 @@ the GEOS library:: >>> pnt.contains(sm.mpoly) False -``GeoQuerySet`` Methods ------------------------ +Geographic annotations +---------------------- + +GeoDjango also offers a set of geographic annotations to compute distances and +several other operations (intersection, difference, etc.). See the +:doc:`functions` documentation. Putting your data on the map -- cgit v1.3