From c281831a5cb20a31cb080ff7b4af4bcfc83fcf3d Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Sat, 14 Jun 2014 20:52:37 +0200 Subject: [PATCH] Complemented dwithin docs about using geographic geometries Refs #22830. Thanks django@gfairchild.com for the suggestion. --- docs/ref/contrib/gis/geoquerysets.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/ref/contrib/gis/geoquerysets.txt b/docs/ref/contrib/gis/geoquerysets.txt index 957a0497af..dd2dfe8efc 100644 --- a/docs/ref/contrib/gis/geoquerysets.txt +++ b/docs/ref/contrib/gis/geoquerysets.txt @@ -613,8 +613,11 @@ SpatiaLite ``Distance(poly, geom) <= 5`` dwithin ------- -Returns models where the distance to the geometry field from the -lookup geometry are within the given distance from one another. +Returns models where the distance to the geometry field from the lookup +geometry are within the given distance from one another. Note that you can only +provide :class:`~django.contrib.gis.measure.Distance` objects if the targeted +geometries are in a projected system. For geographic geometries, you should use +units of the geometry field (e.g. degrees for ``WGS84``) . Example::