The spatial lookups in this section are available for GeometryField\nand RasterField.
For an introduction, see the spatial lookups introduction. For an overview of what lookups are\ncompatible with a particular spatial backend, refer to the\nspatial lookup compatibility table.
\n\nAll examples in the reference below are given for geometry fields and inputs,\nbut the lookups can be used the same way with rasters on both sides. Whenever\na lookup doesn’t support raster input, the input is automatically\nconverted to a geometry where necessary using the ST_Polygon function. See also the\nintroduction to raster lookups.
\nThe database operators used by the lookups can be divided into three categories:
\nNative raster support N: the operator accepts rasters natively on both\nsides of the lookup, and raster input can be mixed with geometry inputs.
Bilateral raster support B: the operator supports rasters only if both\nsides of the lookup receive raster inputs. Raster data is automatically\nconverted to geometries for mixed lookups.
Geometry conversion support C. The lookup does not have native raster\nsupport, all raster data is automatically converted to geometries.
The examples below show the SQL equivalent for the lookups in the different\ntypes of raster support. The same pattern applies to all spatial lookups.
\nCase | \nLookup | \nSQL Equivalent | \n
|---|---|---|
N, B | \n
| \n
| \n
N, B | \n
| \n
| \n
B, C | \n
| \n
| \n
B, C | \n
| \n
| \n
B, C | \n
| \n
| \n
B, C | \n
| \n
| \n
C | \n
| \n
| \n
C | \n
| \n
| \n
C | \n
| \n
| \n
C | \n
| \n
| \n
Spatial lookups with rasters are only supported for PostGIS backends\n(denominated as PGRaster in this section).
\nbbcontainsLink para este cabeçalho#Availability: PostGIS,\nMySQL, SpatiaLite, PGRaster (Native)
\nTests if the geometry or raster field’s bounding box completely contains the\nlookup geometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__bbcontains=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
MySQL | \n
| \n
SpatiaLite | \n
| \n
bboverlapsLink para este cabeçalho#Availability: PostGIS,\nMySQL, SpatiaLite, PGRaster (Native)
\nTests if the geometry field’s bounding box overlaps the lookup geometry’s\nbounding box.
\nExemplo
\nZipcode.objects.filter(poly__bboverlaps=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
MySQL | \n
| \n
SpatiaLite | \n
| \n
containedLink para este cabeçalho#Availability: PostGIS,\nMySQL, SpatiaLite, PGRaster (Native)
\nTests if the geometry field’s bounding box is completely contained by the\nlookup geometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__contained=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
MySQL | \n
| \n
SpatiaLite | \n
| \n
containsLink para este cabeçalho#Availability: PostGIS,\nOracle, MySQL, SpatiaLite, PGRaster (Bilateral)
\nTests if the geometry field spatially contains the lookup geometry.
\nExemplo
\nZipcode.objects.filter(poly__contains=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
MySQL | \n
| \n
SpatiaLite | \n
| \n
contains_properlyLink para este cabeçalho#Availability: PostGIS,\nPGRaster (Bilateral)
\nReturns true if the lookup geometry intersects the interior of the\ngeometry field, but not the boundary (or exterior).
\nExemplo
\nZipcode.objects.filter(poly__contains_properly=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
coveredbyLink para este cabeçalho#Availability: PostGIS,\nOracle, PGRaster (Bilateral)
\nTests if no point in the geometry field is outside the lookup geometry.\n[3]
\nExemplo
\nZipcode.objects.filter(poly__coveredby=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
coversLink para este cabeçalho#Availability: PostGIS,\nOracle, PGRaster (Bilateral)
\nTests if no point in the lookup geometry is outside the geometry field.\n[3]
\nExemplo
\nZipcode.objects.filter(poly__covers=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
crossesLink para este cabeçalho#Availability: PostGIS,\nSpatiaLite, PGRaster (Conversion)
\nTests if the geometry field spatially crosses the lookup geometry.
\nExemplo
\nZipcode.objects.filter(poly__crosses=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
SpatiaLite | \n
| \n
disjointLink para este cabeçalho#Availability: PostGIS,\nOracle, MySQL, SpatiaLite, PGRaster (Bilateral)
\nTests if the geometry field is spatially disjoint from the lookup geometry.
\nExemplo
\nZipcode.objects.filter(poly__disjoint=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
MySQL | \n
| \n
SpatiaLite | \n
| \n
equalsLink para este cabeçalho#Availability: PostGIS,\nOracle, MySQL, SpatiaLite, PGRaster (Conversion)
\nexact, same_asLink para este cabeçalho#Availability: PostGIS,\nOracle, MySQL, SpatiaLite, PGRaster (Bilateral)
\nintersectsLink para este cabeçalho#Availability: PostGIS,\nOracle, MySQL, SpatiaLite, PGRaster (Bilateral)
\nTests if the geometry field spatially intersects the lookup geometry.
\nExemplo
\nZipcode.objects.filter(poly__intersects=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
MySQL | \n
| \n
SpatiaLite | \n
| \n
isvalidLink para este cabeçalho#Availability: PostGIS,\nOracle, SpatiaLite
\nTests if the geometry is valid.
\nExemplo
\nZipcode.objects.filter(poly__isvalid=True)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS, SpatiaLite | \n
| \n
Oracle | \n
| \n
overlapsLink para este cabeçalho#Availability: PostGIS,\nOracle, MySQL, SpatiaLite, PGRaster (Bilateral)
\nrelateLink para este cabeçalho#Availability: PostGIS,\nOracle, SpatiaLite, PGRaster (Conversion)
\nTests if the geometry field is spatially related to the lookup geometry by\nthe values given in the given pattern. This lookup requires a tuple parameter,\n(geom, pattern); the form of pattern will depend on the spatial backend:
On these spatial backends the intersection pattern is a string comprising\nnine characters, which define intersections between the interior, boundary,\nand exterior of the geometry field and the lookup geometry.\nThe intersection pattern matrix may only use the following characters:\n1, 2, T, F, or *. This lookup type allows users to “fine tune”\na specific geometric relationship consistent with the DE-9IM model. [1]
Geometry example:
\n# A tuple lookup parameter is used to specify the geometry and\n# the intersection pattern (the pattern here is for 'contains').\nZipcode.objects.filter(poly__relate=(geom, 'T*T***FF*'))\nPostGIS SQL equivalent:
\nSELECT ... WHERE ST_Relate(poly, geom, 'T*T***FF*')\nSpatiaLite SQL equivalent:
\nSELECT ... WHERE Relate(poly, geom, 'T*T***FF*')\nRaster example:
\nZipcode.objects.filter(poly__relate=(rast, 1, 'T*T***FF*'))\nZipcode.objects.filter(rast__2__relate=(rast, 1, 'T*T***FF*'))\nPostGIS SQL equivalent:
\nSELECT ... WHERE ST_Relate(poly, ST_Polygon(rast, 1), 'T*T***FF*')\nSELECT ... WHERE ST_Relate(ST_Polygon(rast, 2), ST_Polygon(rast, 1), 'T*T***FF*')\nHere the relation pattern is comprised of at least one of the nine relation\nstrings: TOUCH, OVERLAPBDYDISJOINT, OVERLAPBDYINTERSECT,\nEQUAL, INSIDE, COVEREDBY, CONTAINS, COVERS, ON, and\nANYINTERACT. Multiple strings may be combined with the logical Boolean\noperator OR, for example, 'inside+touch'. [2] The relation\nstrings are case-insensitive.
Exemplo
\nZipcode.objects.filter(poly__relate=(geom, 'anyinteract'))\nOracle SQL equivalent:
\nSELECT ... WHERE SDO_RELATE(poly, geom, 'anyinteract')\ntouchesLink para este cabeçalho#Availability: PostGIS,\nOracle, MySQL, SpatiaLite
\nTests if the geometry field spatially touches the lookup geometry.
\nExemplo
\nZipcode.objects.filter(poly__touches=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
MySQL | \n
| \n
Oracle | \n
| \n
SpatiaLite | \n
| \n
withinLink para este cabeçalho#Availability: PostGIS,\nOracle, MySQL, SpatiaLite, PGRaster (Bilateral)
\nTests if the geometry field is spatially within the lookup geometry.
\nExemplo
\nZipcode.objects.filter(poly__within=geom)\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
MySQL | \n
| \n
Oracle | \n
| \n
SpatiaLite | \n
| \n
leftLink para este cabeçalho#Availability: PostGIS,\nPGRaster (Conversion)
\nTests if the geometry field’s bounding box is strictly to the left of the\nlookup geometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__left=geom)\nPostGIS equivalent:
\nSELECT ... WHERE poly << geom\nrightLink para este cabeçalho#Availability: PostGIS,\nPGRaster (Conversion)
\nTests if the geometry field’s bounding box is strictly to the right of the\nlookup geometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__right=geom)\nPostGIS equivalent:
\nSELECT ... WHERE poly >> geom\noverlaps_leftLink para este cabeçalho#Availability: PostGIS,\nPGRaster (Bilateral)
\nTests if the geometry field’s bounding box overlaps or is to the left of the lookup\ngeometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__overlaps_left=geom)\nPostGIS equivalent:
\nSELECT ... WHERE poly &< geom\noverlaps_rightLink para este cabeçalho#Availability: PostGIS,\nPGRaster (Bilateral)
\nTests if the geometry field’s bounding box overlaps or is to the right of the lookup\ngeometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__overlaps_right=geom)\nPostGIS equivalent:
\nSELECT ... WHERE poly &> geom\noverlaps_aboveLink para este cabeçalho#Availability: PostGIS,\nPGRaster (Conversion)
\nTests if the geometry field’s bounding box overlaps or is above the lookup\ngeometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__overlaps_above=geom)\nPostGIS equivalent:
\nSELECT ... WHERE poly |&> geom\noverlaps_belowLink para este cabeçalho#Availability: PostGIS,\nPGRaster (Conversion)
\nTests if the geometry field’s bounding box overlaps or is below the lookup\ngeometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__overlaps_below=geom)\nPostGIS equivalent:
\nSELECT ... WHERE poly &<| geom\nstrictly_aboveLink para este cabeçalho#Availability: PostGIS,\nPGRaster (Conversion)
\nTests if the geometry field’s bounding box is strictly above the lookup\ngeometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__strictly_above=geom)\nPostGIS equivalent:
\nSELECT ... WHERE poly |>> geom\nstrictly_belowLink para este cabeçalho#Availability: PostGIS,\nPGRaster (Conversion)
\nTests if the geometry field’s bounding box is strictly below the lookup\ngeometry’s bounding box.
\nExemplo
\nZipcode.objects.filter(poly__strictly_below=geom)\nPostGIS equivalent:
\nSELECT ... WHERE poly <<| geom\nDisponibilidade: PostGIS, Oracle, SpatiaLite, PGRaster (Native)
\nFor an overview on performing distance queries, please refer to\nthe distance queries introduction.
\nDistance lookups take the following form:
\n<field>__<distance lookup>=(<geometry/raster>, <distance value>[, 'spheroid'])\n<field>__<distance lookup>=(<raster>, <band_index>, <distance value>[, 'spheroid'])\n<field>__<band_index>__<distance lookup>=(<raster>, <band_index>, <distance value>[, 'spheroid'])\nThe value passed into a distance lookup is a tuple; the first two\nvalues are mandatory, and are the geometry to calculate distances to,\nand a distance value (either a number in units of the field, a\nDistance object, or a query expression\n<ref/models/expressions>). To pass a band index to the lookup, use a 3-tuple\nwhere the second entry is the band index.
On every distance lookup except dwithin, an optional element,\n'spheroid', may be included to use the more accurate spheroid distance\ncalculation functions on fields with a geodetic coordinate system.
On PostgreSQL, the 'spheroid' option uses ST_DistanceSpheroid instead of\nST_DistanceSphere. The\nsimpler ST_Distance function is\nused with projected coordinate systems. Rasters are converted to geometries for\nspheroid based lookups.
distance_gtLink para este cabeçalho#Returns models where the distance to the geometry field from the lookup\ngeometry is greater than the given distance value.
\nExemplo
\nZipcode.objects.filter(poly__distance_gt=(geom, D(m=5)))\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
SpatiaLite | \n
| \n
distance_gteLink para este cabeçalho#Returns models where the distance to the geometry field from the lookup\ngeometry is greater than or equal to the given distance value.
\nExemplo
\nZipcode.objects.filter(poly__distance_gte=(geom, D(m=5)))\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
SpatiaLite | \n
| \n
distance_ltLink para este cabeçalho#Returns models where the distance to the geometry field from the lookup\ngeometry is less than the given distance value.
\nExemplo
\nZipcode.objects.filter(poly__distance_lt=(geom, D(m=5)))\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
SpatiaLite | \n
| \n
distance_lteLink para este cabeçalho#Returns models where the distance to the geometry field from the lookup\ngeometry is less than or equal to the given distance value.
\nExemplo
\nZipcode.objects.filter(poly__distance_lte=(geom, D(m=5)))\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
SpatiaLite | \n
| \n
dwithinLink para este cabeçalho#Returns models where the distance to the geometry field from the lookup\ngeometry are within the given distance from one another. Note that you can only\nprovide Distance objects if the targeted\ngeometries are in a projected system. For geographic geometries, you should use\nunits of the geometry field (e.g. degrees for WGS84) .
Exemplo
\nZipcode.objects.filter(poly__dwithin=(geom, D(m=5)))\nBackend | \nSQL Equivalent | \n
|---|---|
PostGIS | \n
| \n
Oracle | \n
| \n
SpatiaLite | \n
| \n
GeoQuerySet MethodsLink para este cabeçalho#GeoQuerySet methods specify that a spatial operation be performed\non each spatial operation on each geographic\nfield in the queryset and store its output in a new attribute on the model\n(which is generally the name of the GeoQuerySet method).
There are also aggregate GeoQuerySet methods which return a single value\ninstead of a queryset. This section will describe the API and availability\nof every GeoQuerySet method available in GeoDjango.
With a few exceptions, the following keyword arguments may be used with all\nGeoQuerySet methods:
Keyword Argument | \nDescrição | \n
|---|---|
| \nBy default, On PostGIS, the | \n
| \nBy default, This keyword is required if\na method name clashes with an existing\n | \n
Availability: PostGIS, Oracle, SpatiaLite
\nareaLink para este cabeçalho#Returns the area of the geographic field in an area attribute on\neach element of this GeoQuerySet.
distanceLink para este cabeçalho#This method takes a geometry as a parameter, and attaches a distance\nattribute to every model in the returned queryset that contains the\ndistance (as a Distance object) to the given geometry.
In the following example (taken from the GeoDjango distance tests),\nthe distance from the Tasmanian city of Hobart to every other\nPointField in the AustraliaCity queryset is calculated:
>>> pnt = AustraliaCity.objects.get(name='Hobart').point\n>>> for city in AustraliaCity.objects.distance(pnt): print(city.name, city.distance)\nWollongong 990071.220408 m\nShellharbour 972804.613941 m\nThirroul 1002334.36351 m\nMittagong 975691.632637 m\nBatemans Bay 834342.185561 m\nCanberra 598140.268959 m\nMelbourne 575337.765042 m\nSydney 1056978.87363 m\nHobart 0.0 m\nAdelaide 1162031.83522 m\nHillsdale 1049200.46122 m\nlengthLink para este cabeçalho#Returns the length of the geometry field in a length attribute\n(a Distance object) on each model in\nthe queryset.
perimeterLink para este cabeçalho#Returns the perimeter of the geometry field in a perimeter attribute\n(a Distance object) on each model in\nthe queryset.
The following methods take no arguments, and attach geometry objects\neach element of the GeoQuerySet that is the result of relationship\nfunction evaluated on the geometry field.
centroidLink para este cabeçalho#Availability: PostGIS, Oracle, SpatiaLite
\nReturns the centroid value for the geographic field in a centroid\nattribute on each element of the GeoQuerySet.
envelopeLink para este cabeçalho#Availability: PostGIS, SpatiaLite
\nReturns a geometry representing the bounding box of the geometry field in\nan envelope attribute on each element of the GeoQuerySet.
point_on_surfaceLink para este cabeçalho#Availability: PostGIS, Oracle, SpatiaLite
\nReturns a Point geometry guaranteed to lie on the surface of the\ngeometry field in a point_on_surface attribute on each element\nof the queryset; otherwise sets with None.
force_rhrLink para este cabeçalho#Availability: PostGIS
\nReturns a modified version of the polygon/multipolygon in which all\nof the vertices follow the Right-Hand-Rule, and attaches as a\nforce_rhr attribute on each element of the queryset.
reverse_geomLink para este cabeçalho#Availability: PostGIS, Oracle
\nReverse the coordinate order of the geometry field, and attaches as a\nreverse attribute on each element of the queryset.
scaleLink para este cabeçalho#Availability: PostGIS, SpatiaLite
\nsnap_to_gridLink para este cabeçalho#Snap all points of the input geometry to the grid. How the\ngeometry is snapped to the grid depends on how many numeric\n(either float, integer, or long) arguments are given.
\nNumber of Arguments | \nDescrição | \n
|---|---|
1 | \nA single size to snap bot the X and Y grids to. | \n
2 | \nX and Y sizes to snap the grid to. | \n
4 | \nX, Y sizes and the corresponding X, Y origins. | \n
transformLink para este cabeçalho#Availability: PostGIS, Oracle, SpatiaLite
\nThe transform method transforms the geometry field of a model to the spatial\nreference system specified by the srid parameter. If no srid is given,\nthen 4326 (WGS84) is used by default.
Exemplo
\n>>> qs = Zipcode.objects.all().transform() # Transforms to WGS84\n>>> qs = Zipcode.objects.all().transform(32140) # Transforming to "NAD83 / Texas South Central"\n>>> print(qs[0].poly.srid)\n32140\n>>> print(qs[0].poly)\nPOLYGON ((234055.1698884720099159 4937796.9232223574072123 ...\ntranslateLink para este cabeçalho#Availability: PostGIS, SpatiaLite
\nTranslates the geometry field to a new location using the given numeric\nparameters as offsets.
\nAvailability: PostGIS, Oracle, SpatiaLite
\nThe following methods all take a geometry as a parameter and attach a geometry\nto each element of the GeoQuerySet that is the result of the operation.
differenceLink para este cabeçalho#Returns the spatial difference of the geographic field with the given\ngeometry in a difference attribute on each element of the\nGeoQuerySet.
intersectionLink para este cabeçalho#Returns the spatial intersection of the geographic field with the\ngiven geometry in an intersection attribute on each element of the\nGeoQuerySet.
sym_differenceLink para este cabeçalho#Returns the symmetric difference of the geographic field with the\ngiven geometry in a sym_difference attribute on each element of the\nGeoQuerySet.
unionLink para este cabeçalho#Returns the union of the geographic field with the given\ngeometry in an union attribute on each element of the\nGeoQuerySet.
The following GeoQuerySet methods will return an attribute that has the value\nof the geometry field in each model converted to the requested output format.
geohashLink para este cabeçalho#Attaches a geohash attribute to every model the queryset\ncontaining the GeoHash representation of the geometry.
geojsonLink para este cabeçalho#Availability: PostGIS, SpatiaLite
\nAttaches a geojson attribute to every model in the queryset that contains the\nGeoJSON representation of the geometry.
Keyword Argument | \nDescrição | \n
|---|---|
| \nIt may be used to specify the number of significant\ndigits for the coordinates in the GeoJSON\nrepresentation – the default value is 8. | \n
| \nSet this to | \n
| \nSet this to | \n
gmlLink para este cabeçalho#Availability: PostGIS, Oracle, SpatiaLite
\nAttaches a gml attribute to every model in the queryset that contains the\nGeographic Markup Language (GML) representation of the geometry.
Exemplo
\n>>> qs = Zipcode.objects.all().gml()\n>>> print(qs[0].gml)\n<gml:Polygon srsName="EPSG:4326"><gml:OuterBoundaryIs>-147.78711,70.245363 ... -147.78711,70.245363</gml:OuterBoundaryIs></gml:Polygon>\nKeyword Argument | \nDescrição | \n
|---|---|
| \nThis keyword is for PostGIS only. It may be used\nto specify the number of significant digits for the\ncoordinates in the GML representation – the default\nvalue is 8. | \n
| \nThis keyword is for PostGIS only. It may be used to\nspecify the GML version used, and may only be values\nof 2 or 3. The default value is 2. | \n
kmlLink para este cabeçalho#Availability: PostGIS, SpatiaLite
\nAttaches a kml attribute to every model in the queryset that contains the\nKeyhole Markup Language (KML) representation of the geometry fields. It\nshould be noted that the contents of the KML are transformed to WGS84 if\nnecessary.
Exemplo
\n>>> qs = Zipcode.objects.all().kml()\n>>> print(qs[0].kml)\n<Polygon><outerBoundaryIs><LinearRing><coordinates>-103.04135,36.217596,0 ... -103.04135,36.217596,0</coordinates></LinearRing></outerBoundaryIs></Polygon>\nKeyword Argument | \nDescrição | \n
|---|---|
| \nThis keyword may be used to specify the number of\nsignificant digits for the coordinates in the KML\nrepresentation – the default value is 8. | \n
svgLink para este cabeçalho#Availability: PostGIS, SpatiaLite
\nAttaches a svg attribute to every model in the queryset that contains\nthe Scalable Vector Graphics (SVG) path data of the geometry fields.
Keyword Argument | \nDescrição | \n
|---|---|
| \nIf set to | \n
| \nThis keyword may be used to specify the number of\nsignificant digits for the coordinates in the SVG\nrepresentation – the default value is 8. | \n
![Link para esta definição#](\"#django.contrib.gis.db.models.GeoQuerySet.svg\"){kind=link}
mem_sizeLink para este cabeçalho#Availability: PostGIS
\nReturns the memory size (number of bytes) that the geometry field takes\nin a mem_size attribute on each element of the GeoQuerySet.
num_geomLink para este cabeçalho#Availability: PostGIS, Oracle, SpatiaLite
\nReturns the number of geometries in a num_geom attribute on\neach element of the GeoQuerySet if the geometry field is a\ncollection (e.g., a GEOMETRYCOLLECTION or MULTI* field);\notherwise sets with None.
num_pointsLink para este cabeçalho#Availability: PostGIS, Oracle, SpatiaLite
\nReturns the number of points in the first linestring in the\ngeometry field in a num_points attribute on each element of\nthe GeoQuerySet; otherwise sets with None.
Django provides some GIS-specific aggregate functions. For details on how to\nuse these aggregate functions, see the topic guide on aggregation.
\nKeyword Argument | \nDescrição | \n
|---|---|
| \nThis keyword is for Oracle only. It is for the\ntolerance value used by the | \n
Exemplo
\n>>> from django.contrib.gis.db.models import Extent, Union\n>>> WorldBorder.objects.aggregate(Extent('mpoly'), Union('mpoly'))\nCollectLink para este cabeçalho#Availability: PostGIS,\nSpatiaLite
\nReturns a GEOMETRYCOLLECTION or a MULTI geometry object from the geometry\ncolumn. This is analogous to a simplified version of the Union\naggregate, except it can be several orders of magnitude faster than performing\na union because it simply rolls up geometries into a collection or multi object,\nnot caring about dissolving boundaries.
ExtentLink para este cabeçalho#Availability: PostGIS,\nOracle, SpatiaLite
\nReturns the extent of all geo_field in the QuerySet as a four-tuple,\ncomprising the lower left coordinate and the upper right coordinate.
Exemplo
\n>>> qs = City.objects.filter(name__in=('Houston', 'Dallas')).aggregate(Extent('poly'))\n>>> print(qs['poly__extent'])\n(-96.8016128540039, 29.7633724212646, -95.3631439208984, 32.782058715820)\nExtent3DLink para este cabeçalho#Availability: PostGIS
\nReturns the 3D extent of all geo_field in the QuerySet as a six-tuple,\ncomprising the lower left coordinate and upper right coordinate (each with x, y,\nand z coordinates).
Exemplo
\n>>> qs = City.objects.filter(name__in=('Houston', 'Dallas')).aggregate(Extent3D('poly'))\n>>> print(qs['poly__extent3d'])\n(-96.8016128540039, 29.7633724212646, 0, -95.3631439208984, 32.782058715820, 0)\nMakeLineLink para este cabeçalho#Availability: PostGIS,\nSpatiaLite
\nReturns a LineString constructed from the point field geometries in the\nQuerySet. Currently, ordering the queryset has no effect.
Exemplo
\n>>> qs = City.objects.filter(name__in=('Houston', 'Dallas')).aggregate(MakeLine('poly'))\n>>> print(qs['poly__makeline'])\nLINESTRING (-95.3631510000000020 29.7633739999999989, -96.8016109999999941 32.7820570000000018)\nUnionLink para este cabeçalho#Availability: PostGIS,\nOracle, SpatiaLite
\nThis method returns a GEOSGeometry object\ncomprising the union of every geometry in the queryset. Please note that use of\nUnion is processor intensive and may take a significant amount of time on\nlarge querysets.
Exemplo
\n>>> u = Zipcode.objects.aggregate(Union(poly)) # This may take a long time.\n>>> u = Zipcode.objects.filter(poly__within=bbox).aggregate(Union(poly)) # A more sensible approach.\nNotas de rodapé
\n\n