mirror of
https://github.com/django/django.git
synced 2025-06-05 11:39:13 +00:00
[1.10.x] Fixed typos in db-api GIS docs
Backport of 1b0287b4b8e76e17a2e1157d56e41e3df0c72674 from master
This commit is contained in:
parent
06ba492611
commit
c66f5d058a
@ -178,7 +178,7 @@ Raster Lookups
|
|||||||
.. versionadded:: 1.10
|
.. versionadded:: 1.10
|
||||||
|
|
||||||
The raster lookup syntax is similar to the syntax for geometries. The only
|
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
|
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.
|
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>__<band_index>__<lookup_type>=<parameter>)
|
||||||
>>> qs = Elevation.objects.filter(<field>__<lookup_type>=(<raster_input, <band_index>)
|
>>> 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=geom)
|
||||||
>>> qs = Elevation.objects.filter(rast__contains=rst)
|
>>> qs = Elevation.objects.filter(rast__contains=rst)
|
||||||
|
Loading…
x
Reference in New Issue
Block a user