mirror of
				https://github.com/django/django.git
				synced 2025-10-31 09:41:08 +00:00 
			
		
		
		
	[1.10.x] Fixed typos in db-api GIS docs
Backport of 1b0287b4b8 from master
			
			
This commit is contained in:
		| @@ -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) | ||||||
|   | |||||||
		Reference in New Issue
	
	Block a user