summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorClaude Paroz <claude@2xlibre.net>2016-08-08 15:16:28 +0200
committerTim Graham <timograham@gmail.com>2016-08-08 10:03:57 -0400
commitc66f5d058a8753143c12ec1bf55111a9d7f233bf (patch)
tree40f80d63d0bda885cfc244eaa4bbc102d50f41ec
parent06ba4926115b50285497e88b51e2e6b2e1edcf49 (diff)
[1.10.x] Fixed typos in db-api GIS docs
Backport of 1b0287b4b8e76e17a2e1157d56e41e3df0c72674 from master
-rw-r--r--docs/ref/contrib/gis/db-api.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/contrib/gis/db-api.txt b/docs/ref/contrib/gis/db-api.txt
index 0b1f7d3d0b..0cbca3896e 100644
--- a/docs/ref/contrib/gis/db-api.txt
+++ b/docs/ref/contrib/gis/db-api.txt
@@ -178,7 +178,7 @@ Raster Lookups
.. versionadded:: 1.10
The raster lookup syntax is similar to the syntax for geometries. The only
-difference is that a band index can specified as additional input. If no band
+difference is that a band index can be specified as additional input. If no band
index is specified, the first band is used by default (index ``0``). In that
case the syntax is identical to the syntax for geometry lookups.
@@ -194,7 +194,7 @@ This results in the following general form for lookups involving rasters
>>> qs = Elevation.objects.filter(<field>__<band_index>__<lookup_type>=<parameter>)
>>> qs = Elevation.objects.filter(<field>__<lookup_type>=(<raster_input, <band_index>)
-Fore example::
+For example::
>>> qs = Elevation.objects.filter(rast__contains=geom)
>>> qs = Elevation.objects.filter(rast__contains=rst)